diff options
1404 files changed, 0 insertions, 43109 deletions
diff --git a/doc/bugs/--help_should_not_demand_being_in_the_git_repo.mdwn b/doc/bugs/--help_should_not_demand_being_in_the_git_repo.mdwn deleted file mode 100644 index 83ba3319f..000000000 --- a/doc/bugs/--help_should_not_demand_being_in_the_git_repo.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -subj -- happens for sync and merge commands at least - - -[[!format sh """ -$> git annex sync --help -git-annex: Not in a git repository. - -$> git annex merge --help -git-annex: Not in a git repository. - -$> git annex version -git-annex version: 5.20150819+gitgc587698-1~ndall+1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA Database -key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - -"""]] - -### 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 ;) - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/--json_issues.mdwn b/doc/bugs/--json_issues.mdwn deleted file mode 100644 index 4a73540c4..000000000 --- a/doc/bugs/--json_issues.mdwn +++ /dev/null @@ -1,49 +0,0 @@ -### Please describe the problem. -Duplicate "note" properties in JSON output of whereis command. The JSON output is "[strictly speaking](http://stackoverflow.com/questions/21832701/does-json-syntax-allow-duplicate-keys-in-an-object)" valid, however, the duplicate property makes it difficult to use python-json, and possibly other implementations (I just checked node and chromium and they also keep the value of the last property after deserialization). - -I noticed the problem being mentioned [here](https://git-annex.branchable.com/forum/git_annex_whereis_--json_output_with_two_variables_with_same_name/), where the user desires to parse an entry in the machine parsable json output that is apparently not meant to be parsed by a machine, which makes a person wonder why it's there anyway. Even so, obtaining the actual url in the web remote for an annexed object relies on one of the "note" properties in the json output. Using [whereis]( -http://git-annex.branchable.com/tips/using_the_web_as_a_special_remote/#comment-7878bde74289b42500e4fac3a122a535) to get the url(s) for a file is the recommended method. A json implementation that sets the first property, then ignores remaining duplicates will only parse the "2 copies" note, and ignore the url. - -If the "note" properties are meant to be comments, it might be a good idea to find another property for the url(s). Please note that I haven't looked at multiple urls for an object, so I'm not sure that only the last listed url will appear in parsed json object. - -> The note properties are any notes git-annex normally displays while -> running a command. - -### What steps will reproduce the problem? - -git-annex whereis --json - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20151208-1 (sid chroot) - -### 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 -umeboshi@bard:~/tmp$ git init testweb -Initialized empty Git repository in /freespace/home/umeboshi/tmp/testweb/.git/ -umeboshi@bard:~/tmp$ cd testweb/ -umeboshi@bard:~/tmp/testweb$ git-annex init -init ok -(recording state in git...) -umeboshi@bard:~/tmp/testweb$ git-annex addurl http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf -addurl www.ecma_international.org_publications_files_ECMA_ST_ECMA_404.pdf (downloading http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf ...) -/freespace/home/ume 100%[===================>] 1.08M 917KB/s in 1.2s -ok -(recording state in git...) -umeboshi@bard:~/tmp/testweb$ git-annex whereis www.ecma_international.org_publications_files_ECMA_ST_ECMA_404.pdf --json -{"command":"whereis","file":"www.ecma_international.org_publications_files_ECMA_ST_ECMA_404.pdf","note":"2 copies","whereis":[{"uuid":"00000000-0000-0000-0000-000000000001","description":"web","here":false},{"uuid":"996522e8-a433-42ff-85f2-48e456fdb120","description":"umeboshi@bard:~/tmp/testweb","here":true}],"note":"\t00000000-0000-0000-0000-000000000001 -- web\n \t996522e8-a433-42ff-85f2-48e456fdb120 -- umeboshi@bard:~/tmp/testweb [here]\n","untrusted":[],"note":"web: http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf\n","success":true} - -umeboshi@bard:~/tmp/testweb$ - - -# 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) - -Lol! Positive note! I spend a couple of days making specially crafted rss files for importfeed, so I can have appropriate filenames, then look back and see that you are working on '--batch --with-files' options to addurl. Have a Happy New Year! :) - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes.mdwn b/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes.mdwn deleted file mode 100644 index 177cc66e1..000000000 --- a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -Some time in may 2014, git-annex stopped working with previous versions of git-annex. - -### What steps will reproduce the problem? - -Trying to sync with the server fails with: - - git-annex-shell: Not a git-annex or gcrypt repository. - -With older versions (e.g. 5.20140412), it's even worse: - - Remote marcos does not have git-annex installed; setting annex-ignore - This could be a problem with the git-annex installation on the remote. Please make sure that git-annex-shell is available in PATH when you ssh into the remote. Once you have fixed the git-annex installation, run: git config remote.marcos.annex-ignore false - -Basically, if git-annex-shell is missing, newer versions of git-annex just crash and burn instead of going the more gentle, backward-compatible way... - -### What version of git-annex are you using? On what operating system? - -git-annex from debian sid (5.20140517) on the "client" side and from jessie (5.20140421) on the "server". - -### 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 -ssh server -git init books -exit -git remote add server server:books -git annex sync server -# End of transcript or log. -"""]] - -If this is intended behavior, it seems to me the major version of git annex should be bumped, at the very least... -- [[anarcat]] - -> [[done]], seems operator error --[[Joey]] diff --git a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_1_323262a080daed9cebd4caee4c887210._comment b/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_1_323262a080daed9cebd4caee4c887210._comment deleted file mode 100644 index f54eb1769..000000000 --- a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_1_323262a080daed9cebd4caee4c887210._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="24.159.78.125" - subject="comment 1" - date="2014-05-23T14:25:04Z" - content=""" -git-annex has always required the remote have git-annex-shell installed in order to store files on it. Nothing has changed in this area. - -So, you seem to be very confused about something, but I cannot tell what from this bug report, and I certianly see no evidence of any bug in the information provided so far. You need to install git-annex on your server and then it should work, assuming the server actually has a git-annex repository set up on it. -"""]] diff --git a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_2_6172dcd7db2322084483a18d4f3cc2d6._comment b/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_2_6172dcd7db2322084483a18d4f3cc2d6._comment deleted file mode 100644 index 98b297868..000000000 --- a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_2_6172dcd7db2322084483a18d4f3cc2d6._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="comment 2" - date="2014-05-27T03:00:48Z" - content=""" -marcos has had git-annex installed ever since i started using git-annex, which is around version 4.x. furthermore, i have assumed that the procedure i detailed in the last part were enough to reproduce the bug, but i may be mistaken. -"""]] diff --git a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_3_5ae2178863709230ddb995905c629c4e._comment b/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_3_5ae2178863709230ddb995905c629c4e._comment deleted file mode 100644 index 3234ff75b..000000000 --- a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_3_5ae2178863709230ddb995905c629c4e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 3" - date="2014-05-27T17:54:06Z" - content=""" -Well, your transcript shows you init a git repository. But you have not run `git annex init` in it, so git-annex-shell won't use it. - - -"""]] diff --git a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_4_19d32634789a09c1b04e9d3fcde364f7._comment b/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_4_19d32634789a09c1b04e9d3fcde364f7._comment deleted file mode 100644 index 66d3c07f8..000000000 --- a/doc/bugs/5.20140517_fails_to_talk_to_other_5.x_git-annex_remotes/comment_4_19d32634789a09c1b04e9d3fcde364f7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="comment 4" - date="2014-06-04T04:53:36Z" - content=""" -ah. i see. certainly an operator error then. feels like a usability issue now, or i just feel stupid, not sure which. :) -"""]] diff --git a/doc/bugs/Addurl_downloads_but_does_not_checkout_files.mdwn b/doc/bugs/Addurl_downloads_but_does_not_checkout_files.mdwn deleted file mode 100644 index 7038fe2e6..000000000 --- a/doc/bugs/Addurl_downloads_but_does_not_checkout_files.mdwn +++ /dev/null @@ -1,74 +0,0 @@ -What steps will reproduce the problem? - -Example below illustrates downloading a podcast with git annex addurl: - -list directory before... - -~/Podcasts/TuxRadar Linux Podcast (Ogg)$ ls -folder.jpg tuxradar_s04e24.ogg -tuxradar_s04e09.ogg tuxradar_s05e01.ogg -tuxradar_s04e11.ogg tuxradar_s05e02.ogg -tuxradar_s04e13.ogg tuxradar_s05e03.ogg -tuxradar_s04e15.ogg tuxradar_s05e04.ogg -tuxradar_s04e16.ogg www.tuxradar.com_files_podcast_tuxradar_s04e10.ogg -tuxradar_s04e19.ogg www.tuxradar.com_files_podcast_tuxradar_s04e12.ogg -tuxradar_s04e20.ogg www.tuxradar.com_files_podcast_tuxradar_s04e14.ogg -tuxradar_s04e21.ogg www.tuxradar.com_files_podcast_tuxradar_s04e17.ogg -tuxradar_s04e22.ogg www.tuxradar.com_files_podcast_tuxradar_s04e18.ogg -tuxradar_s04e23.ogg - -download file... - -~/Podcasts/TuxRadar Linux Podcast (Ogg)$ git annex addurl http://www.tuxradar.com/files/podcast/tuxradar_s05e05.ogg -addurl www.tuxradar.com_files_podcast_tuxradar_s05e05.ogg (downloading http://www.tuxradar.com/files/podcast/tuxradar_s05e05.ogg ...) --2013-04-10 21:18:12-- http://www.tuxradar.com/files/podcast/tuxradar_s05e05.ogg -Resolving www.tuxradar.com (www.tuxradar.com)... 80.244.178.150 -Connecting to www.tuxradar.com (www.tuxradar.com)|80.244.178.150|:80... connected. -HTTP request sent, awaiting response... 200 OK -Length: 33249291 (32M) [application/ogg] -Saving to: `/home/rob/Podcasts/.git/annex/tmp/URL--http&c%%www.tuxradar.com%files%podcast%tuxradar_s05e05.ogg' - -100%[===============================>] 33,249,291 404K/s in 81s - -2013-04-10 21:19:35 (399 KB/s) - `/home/rob/Podcasts/.git/annex/tmp/URL--http&c%%www.tuxradar.com%files%podcast%tuxradar_s05e05.ogg' saved [33249291/33249291] - -(checksum...) ok -(Recording state in git...) - -file appears to have been downloaded, but isn't there... - -~/Podcasts/TuxRadar Linux Podcast (Ogg)$ ls -folder.jpg tuxradar_s04e24.ogg -tuxradar_s04e09.ogg tuxradar_s05e01.ogg -tuxradar_s04e11.ogg tuxradar_s05e02.ogg -tuxradar_s04e13.ogg tuxradar_s05e03.ogg -tuxradar_s04e15.ogg tuxradar_s05e04.ogg -tuxradar_s04e16.ogg www.tuxradar.com_files_podcast_tuxradar_s04e10.ogg -tuxradar_s04e19.ogg www.tuxradar.com_files_podcast_tuxradar_s04e12.ogg -tuxradar_s04e20.ogg www.tuxradar.com_files_podcast_tuxradar_s04e14.ogg -tuxradar_s04e21.ogg www.tuxradar.com_files_podcast_tuxradar_s04e17.ogg -tuxradar_s04e22.ogg www.tuxradar.com_files_podcast_tuxradar_s04e18.ogg -tuxradar_s04e23.ogg - -What is the expected output? What do you see instead? - -File should exist in current directory. As you can see from above output, this has worked in the past (with older versions). - -What version of git-annex are you using? On what operating system? - -git-annex version: 4.20130405 -local repository version: 3 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP - -OS: Debian Testing/Unstable - -Please provide any additional information below. - -The repository in question was created by the assistant and I tried the above with the assistant both running and not running, with no difference. I have also tried downloading other files. - -EDIT: formatting - -> Bug only affected direct mode. I think it used to work but I broke -> it when fixing another bug in direct mode. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn b/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn deleted file mode 100644 index 999d648b8..000000000 --- a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -### Please describe the problem. -Can't add Amazon S3 repository hosted in Frankfurt - -### What steps will reproduce the problem? -Create Amazon S3 account, create a bucket hosted in Frankfurt and create an access key. - -### What version of git-annex are you using? On what operating system? -Ubuntu, git-annex via repositories. Aptitude says 5.20140717. - -### Please provide any additional information below. -The git-annex assistant does not offer the selection of hosting in Frankfurt. If I enter "EU (Ireland)" instead, of course while also providing the other necessary details (access key id, secret access key, data center), the result is the following error: - -[[!format sh """ -The request signature we calculated does not match the signature you provided. Check your key and signing method. -"""]] - -I have not tried other hosting locations but I assume it has to do with the location which is not listed in the dropdown-list. - -> [[done]]; etooold --[[Joey]] diff --git a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable/comment_1_013f8f609ac2f8b6666bbae2db2a147a._comment b/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable/comment_1_013f8f609ac2f8b6666bbae2db2a147a._comment deleted file mode 100644 index 475dc34e7..000000000 --- a/doc/bugs/Amazon_S3_storage_hosted_in_Frankfurt_not_usable/comment_1_013f8f609ac2f8b6666bbae2db2a147a._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""step 1: upgrade""" - date="2015-05-27T21:12:38Z" - content=""" -Your version is almost a year out of date. - -Frankfurt was added to the webapp in 20141023. - -The entire S3 backend library has been changed, so it is vanishingly -unlikely that the current version would have whatever problem the old one -had. -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__.mdwn b/doc/bugs/Android___91__Terminal_session_finished__93__.mdwn deleted file mode 100644 index 17ed66381..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. - -Launching the Git Annex app on Android, the shell just reads: -[[!format sh """ -[Terminal session finished] -"""]] - -Attempting to launch /data/data/ga.androidterm/runshell via the adb shell does also not work: -[[!format sh """ -/system/bin/sh: /data/data/ga.androidterm/runshell: not found -"""]] - -Listing the contents of that directory from the git annex terminal appears to confirm this: -[[!format sh """ -u0_a172@android:/data/data/ga.androidterm $ ls -cache -lib -shared_prefs -"""]] - -Following the instructions for the similar issue here [[http://git-annex.branchable.com/Android/oldcomments/#comment-4c5a944c1288ddd46108969a4c664584]]: -[[!format sh """ -u0_a172@android:/ $ ls -ld /data/data/ga.androidterm -drwxr-x--x u0_a172 u0_a172 2014-04-20 11:12 ga.androidterm -"""]] - -### What version of git-annex are you using? On what operating system? - -version 5.20140413 of the Git Annex app (tested using the daily build and regular build). - -Samsung Galaxy Tab 3 (GT-P5210) running Android 4.2.2 (without root access). - -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_1_31af3e5226430a4e94de58c0e33bd22b._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_1_31af3e5226430a4e94de58c0e33bd22b._comment deleted file mode 100644 index 73f7b05ca..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_1_31af3e5226430a4e94de58c0e33bd22b._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 1" - date="2014-04-20T17:16:50Z" - content=""" -From the git-annex terminal, try to run: - -/data/data/ga.androidterm/lib/lib.start.so - -Paste me any output.. -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_2_a5bcbd2f85283e29e237e9850cd8109a._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_2_a5bcbd2f85283e29e237e9850cd8109a._comment deleted file mode 100644 index 01cc33730..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_2_a5bcbd2f85283e29e237e9850cd8109a._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="cbaines" - ip="86.166.14.171" - subject="comment 2" - date="2014-04-20T19:40:11Z" - content=""" -When I run that, I get: -[[!format sh \"\"\" -/system/bin/sh: /data/data/ga.androidterm/lib/lib.start.so: not found -\"\"\"]] - -Which makes some sense, as the file is not there. The following files can be found under /data/data/ga.androidterm: -[[!format sh \"\"\" -/data/data/ga.androidterm/cache/com.android.renderscript.cache/ <- empty directory -/data/data/ga.androidterm/lib/libga-androidterm4.so -/data/data/ga.androidterm/shared_prefs/ga.androidterm_preferences.xml -\"\"\"]] - -I tried running libga-androidterm4.so, but I just got Segmentation fault back. - -I also tried using logcat to see if I could see anything obvious going wrong when running the app for the first time after installation, but I could not see anything obvious in the logs (there was a lot of noise, so I might of missed something), will anything useful appear with the use of a filter? -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_3_965efa6736dcff4d7010ea5533f31a59._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_3_965efa6736dcff4d7010ea5533f31a59._comment deleted file mode 100644 index ed3d36908..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_3_965efa6736dcff4d7010ea5533f31a59._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="cbaines" - ip="86.166.14.171" - subject="comment 3" - date="2014-04-20T19:50:12Z" - content=""" -Looking at the contents of the apk for the x86 architecture (which this tablet is), would you expect that file to be there? That file only appears in the /lib/armeabi and not /lib/x86 ? -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_4_90a0be2296b4a1d8c1708423666c9619._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_4_90a0be2296b4a1d8c1708423666c9619._comment deleted file mode 100644 index 12fd901bc..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_4_90a0be2296b4a1d8c1708423666c9619._comment +++ /dev/null @@ -1,31 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 4" - date="2014-04-20T19:55:59Z" - content=""" -Ok, so the git-annex.apk ships several libraries (and pseudo-libraries), and it seems your version of Android only installed the one that is really an Android java application. I don't know why. - -Here's the full list of files that are supposed to be installed in the lib dir. If you can find something about them in the logs, that might help. - -I suppose it's possible they were installed to some other location in the android file system (which might be hard to find w/o root.. You could check if git-annex in the app list has a larger installed size than the size of libga-androidterm4.so, that might give a hint. - -<pre> -lib.busybox.so -lib.git-annex.so -lib.git-shell.so -lib.git-upload-pack.so -lib.git.so -lib.git.tar.gz.so -lib.gpg.so -lib.rsync.so -lib.runshell.so -lib.ssh-keygen.so -lib.ssh.so -lib.start.so -lib.version.so -libga-androidterm4.so -</pre> - -(I just installed the 5.20140414-gb70cd37 autobuild on an android device and it worked ok.) -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_5_be4b720293992f75b9cc3e8f6687fb87._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_5_be4b720293992f75b9cc3e8f6687fb87._comment deleted file mode 100644 index 2d82bb7b5..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_5_be4b720293992f75b9cc3e8f6687fb87._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="cbaines" - ip="86.166.14.171" - subject="comment 5" - date="2014-04-20T20:20:55Z" - content=""" -I'm guessing you missed my last comment regarding the architecture. Sorry I did not pick this up earlier, but it only came to mind when I had a poke around in the apk? -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_6_8e439138c97b8853ab2b6f96f6111568._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_6_8e439138c97b8853ab2b6f96f6111568._comment deleted file mode 100644 index 40404029e..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_6_8e439138c97b8853ab2b6f96f6111568._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 6" - date="2014-04-20T20:58:22Z" - content=""" -Yes, that fully explains it. git-annex is a native program and for android it's only built for arm. -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_7_6142516d816f78c724e22737aa3bca53._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_7_6142516d816f78c724e22737aa3bca53._comment deleted file mode 100644 index d6ce0fe3a..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_7_6142516d816f78c724e22737aa3bca53._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 7" - date="2014-04-20T20:59:35Z" - content=""" -So, this is a dup of [[todo/Not_working_on_Android-x86]] -"""]] diff --git a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_8_e28f25897caa301e69ad7aabab821086._comment b/doc/bugs/Android___91__Terminal_session_finished__93__/comment_8_e28f25897caa301e69ad7aabab821086._comment deleted file mode 100644 index 26fa6a612..000000000 --- a/doc/bugs/Android___91__Terminal_session_finished__93__/comment_8_e28f25897caa301e69ad7aabab821086._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkAm9yT27yU-qBTGKIsTMdWW3AgL_WAfkc" - nickname="Cameron" - subject="Similar issue here" - date="2015-03-28T22:17:08Z" - content=""" -Im on the LG F60 (ms395) not rooted. I downloaded a cracked.apk of KBOX and it kept failing to start due to not having Busybox in its file path. So I got the Busybox .apk and copied it into KBOX's path. Now k box is stoped at 'In mgmain JNI_OnLoad'. As soon as I try to ENTER anything, it force closes. Also, I'm not sure if it's related, but my phone is not and does not get recognized by my car stereo via usb. I managed to get around not having permission to look at the 'usbautorun.iso' file. No luck though, it's coded. Any ideas? - -"""]] diff --git a/doc/bugs/Android_build_missing_webapp.mdwn b/doc/bugs/Android_build_missing_webapp.mdwn deleted file mode 100644 index dc9c4db20..000000000 --- a/doc/bugs/Android_build_missing_webapp.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. - -Setting git-annex on an Android device (either the released version, or the autobuilder apk), I'm told: - -[[!format sh """ -git-annex: unknown command webapp -"""]] - -Looking in the logs on the Android autobuilder I see many instances of: - -[[!format sh """ -#warning Building without the webapp. You probably need to install Yesod.. -"""]] - -### What steps will reproduce the problem? - -Run git-annex. - -### What version of git-annex are you using? On what operating system? - -v5.20150617~g031b85a - -### 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. -"""]] - -> I've reverted to the previous release, which included the webapp, afaik. -> -> Unfortunately, the android autobuilder remains broken after I spent 12 -> hours fighting with it. Unsure when that will be resolved and a newer -> release will be able to be made. -> -> Anyhow, the immediate bug is [[done]] --[[Joey]] diff --git a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean.mdwn b/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean.mdwn deleted file mode 100644 index c7f5e582c..000000000 --- a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean.mdwn +++ /dev/null @@ -1,166 +0,0 @@ -### Please describe the problem. - -Install seems to die because /data/app-lib not found. Sorry, I did not copy. Git-annex log is below. - -I tried To run git-annex second time, here's what terminal says. - - -Falling back to hardcoded app location; cannot find expected files in /data/app-lib -git annex webapp -u0_a36@manta:/sdcard/git-annex.home $ git annex webapp -WARNING: linker: git-annex has text relocations. This is wasting memory and is a security risk. Please fix. -error: fchmod on /sdcard/mediashare/.git/config.lock failed: Operation not permitted -error: fchmod on /sdcard/mediashare/.git/config.lock failed: Operation not permitted - -From git terminal, can start web viewer, it offers to make repo. I chose /sdcard/mediashare, result is browser fail: - -git [Param "config",Param "annex.uuid",Param "380f6ec2-a7b0-43db-9447-f0de1b5a1b5b"] failed - -The install did create /sdcard/mediashare. I did have the sdcard directory all along. - -I can't say for sure what else is in file system. ES File manager shows /data exists, but it is empty. But tablet not easy to diagnose - -### What steps will reproduce the problem? - -Install git-annex.apk from website. I downloaded 20140620. - -### What version of git-annex are you using? On what operating system? - -Android 4.4.2 on Nexus tablet. - -### Please provide any additional information below. - -Git-anex-install.log. it is only file in /sdcard/git-annex.home. note it says it is installing to /data/data/. I may manually create that structure and see if a reinstall ends differently. - -[[!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 -Installation starting to /data/data/ga.androidterm -1bebb0d66f3f7c5ac4889b86669cab04ebee9bba -installing busybox -installing git-annex -installing git-shell -installing git-upload-pack -installing git -installing gpg -installing rsync -installing ssh -installing ssh-keygen -linking ./bin/git-upload-archive to git -linking ./bin/git-receive-pack to git -linking ./libexec/git-core/git-help to git -linking ./libexec/git-core/git-fsck to git -linking ./libexec/git-core/git-cat-file to git -linking ./libexec/git-core/git-init to git -linking ./libexec/git-core/git-checkout-index to git -linking ./libexec/git-core/git-notes to git -linking ./libexec/git-core/git-grep to git -linking ./libexec/git-core/git-blame to git -linking ./libexec/git-core/git-verify-tag to git -linking ./libexec/git-core/git-write-tree to git -linking ./libexec/git-core/git-log to git -linking ./libexec/git-core/git-stage to git -linking ./libexec/git-core/git-update-ref to git -linking ./libexec/git-core/git-status to git -linking ./libexec/git-core/git-show-branch to git -linking ./libexec/git-core/git-merge-file to git -linking ./libexec/git-core/git-for-each-ref to git -linking ./libexec/git-core/git to git -linking ./libexec/git-core/git-replace to git -linking ./libexec/git-core/git-update-index to git -linking ./libexec/git-core/git-annotate to git -linking ./libexec/git-core/git-patch-id to git -linking ./libexec/git-core/git-merge-recursive to git -linking ./libexec/git-core/git-rm to git -linking ./libexec/git-core/git-ls-tree to git -linking ./libexec/git-core/git-update-server-info to git -linking ./libexec/git-core/git-diff-tree to git -linking ./libexec/git-core/git-merge-tree to git -linking ./libexec/git-core/git-mktag to git -linking ./libexec/git-core/git-rev-list to git -linking ./libexec/git-core/git-column to git -linking ./libexec/git-core/git-apply to git -linking ./libexec/git-core/git-var to git -linking ./libexec/git-core/git-rev-parse to git -linking ./libexec/git-core/git-archive to git -linking ./libexec/git-core/git-verify-pack to git -linking ./libexec/git-core/git-push to git -linking ./libexec/git-core/git-commit to git -linking ./libexec/git-core/git-tag to git -linking ./libexec/git-core/git-pack-refs to git -linking ./libexec/git-core/git-fmt-merge-msg to git -linking ./libexec/git-core/git-fast-export to git -linking ./libexec/git-core/git-remote-ext to git -linking ./libexec/git-core/git-mailsplit to git -linking ./libexec/git-core/git-send-pack to git -linking ./libexec/git-core/git-diff-index to git -linking ./libexec/git-core/git-mailinfo to git -linking ./libexec/git-core/git-revert to git -linking ./libexec/git-core/git-diff-files to git -linking ./libexec/git-core/git-merge-ours to git -linking ./libexec/git-core/git-show-ref to git -linking ./libexec/git-core/git-diff to git -linking ./libexec/git-core/git-clean to git -linking ./libexec/git-core/git-bundle to git -linking ./libexec/git-core/git-check-mailmap to git -linking ./libexec/git-core/git-describe to git -linking ./libexec/git-core/git-branch to git -linking ./libexec/git-core/git-checkout to git -linking ./libexec/git-core/git-name-rev to git -linking ./libexec/git-core/git-gc to git -linking ./libexec/git-core/git-fetch to git -linking ./libexec/git-core/git-whatchanged to git -linking ./libexec/git-core/git-cherry to git -linking ./libexec/git-core/git-reflog to git -linking ./libexec/git-core/git-hash-object to git -linking ./libexec/git-core/git-init-db to git -linking ./libexec/git-core/git-rerere to git -linking ./libexec/git-core/git-reset to git -linking ./libexec/git-core/git-stripspace to git -linking ./libexec/git-core/git-prune to git -linking ./libexec/git-core/git-mktree to git -linking ./libexec/git-core/git-unpack-file to git -linking ./libexec/git-core/git-remote to git -linking ./libexec/git-core/git-commit-tree to git -linking ./libexec/git-core/git-symbolic-ref to git -linking ./libexec/git-core/git-credential to git -linking ./libexec/git-core/git-check-ignore to git -linking ./libexec/git-core/git-shortlog to git -linking ./libexec/git-core/git-fetch-pack to git -linking ./libexec/git-core/git-clone to git -linking ./libexec/git-core/git-mv to git -linking ./libexec/git-core/git-read-tree to git -linking ./libexec/git-core/git-merge-subtree to git -linking ./libexec/git-core/git-ls-remote to git -linking ./libexec/git-core/git-config to git -linking ./libexec/git-core/git-cherry-pick to git -linking ./libexec/git-core/git-merge to git -linking ./libexec/git-core/git-prune-packed to git -linking ./libexec/git-core/git-count-objects to git -linking ./libexec/git-core/git-merge-base to git -linking ./libexec/git-core/git-index-pack to git -linking ./libexec/git-core/git-repack to git -linking ./libexec/git-core/git-show to git -linking ./libexec/git-core/git-fsck-objects to git -linking ./libexec/git-core/git-format-patch to git -linking ./libexec/git-core/git-bisect--helper to git -linking ./libexec/git-core/git-upload-archive to git -linking ./libexec/git-core/git-ls-files to git -linking ./libexec/git-core/git-check-attr to git -linking ./libexec/git-core/git-get-tar-commit-id to git -linking ./libexec/git-core/git-remote-fd to git -linking ./libexec/git-core/git-unpack-objects to git -linking ./libexec/git-core/git-add to git -linking ./libexec/git-core/git-check-ref-format to git -linking ./libexec/git-core/git-merge-index to git -linking ./libexec/git-core/git-pack-objects to git -linking ./libexec/git-core/git-receive-pack to git -linking ./libexec/git-core/git-pack-redundant to git -linking ./libexec/git-core/git-shell to git-shell -linking ./libexec/git-core/git-upload-pack to git-upload-pack -Installation complete - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_1_b41666c032aeb2d0de35023328391edb._comment b/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_1_b41666c032aeb2d0de35023328391edb._comment deleted file mode 100644 index cc0fcf30e..000000000 --- a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_1_b41666c032aeb2d0de35023328391edb._comment +++ /dev/null @@ -1,25 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-03T20:10:41Z" - content=""" -This is not an installation problem; the /data/app-lib message is a red herring. - -Is /sdcard/mediashare a directory that already existed? If so, perhaps it's some \"mediashare\" thing that has a even more crippled filesystem than usual. Seems possible, but I don't know. Want to rule it out.. - -The actual failure seems to be when git tries to write to its config.lock file, and changes its permissions. This is a recent change in git, commit daa22c6f8da466bd7a438f1bc27375fd737ffcf3, \"config: preserve config file permissions on edits\". - -[[!language C \"\"\" -+ if (fchmod(fd, st.st_mode & 07777) < 0) { -+ error(\"fchmod on %s failed: %s\", -+ lock->filename, strerror(errno)); -+ ret = CONFIG_NO_WRITE; -+ goto out_free; -+ } -\"\"\"]] - -This seems utterly innocuous; the config file has some mode, and this just sets that same mode back (excluding some high bit flags). But Android goes out of its way to make /sdcard the most craptacular filesystem in use on any Linux system, so I'm not really surprised that it might just refuse all fchmod even when it's a no-op. (This is the only fchmod call currently in git.) - -I've patched the bundled git to work around this. Will be a while until there is an updated autobuild.. -"""]] diff --git a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_2_95ebed938df3db2b6d4ebe4c666c08f8._comment b/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_2_95ebed938df3db2b6d4ebe4c666c08f8._comment deleted file mode 100644 index 392f7007f..000000000 --- a/doc/bugs/Android_fails_on_Google_Nexus_10_Jellybean/comment_2_95ebed938df3db2b6d4ebe4c666c08f8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-04T17:52:35Z" - content=""" -This problem should be fixed in the most recent daily build of git-annex for android. Testing appreciated. -"""]] diff --git a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810.mdwn b/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810.mdwn deleted file mode 100644 index 24b2af22a..000000000 --- a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -The armel daily build linked from https://git-annex.branchable.com/install/Linux_standalone/ doesn't seem to work. - -When runshell is run as root, it hangs with no output and trying to run git directly from the bin directory gives - -"/git: exec: line 2: : Permission denied:." - -When run as an ordinary user, it gives - -"./runshell: line 40: can't create /root/.ssh/git-annex-shell: Permission denied -chmod: /root/.ssh/git-annex-shell: Permission denied" - -### What steps will reproduce the problem? - -- Login in to NAS as root via SSH -- Download latest daily build via curl -- Untar, chown -R root:root, and CD in to git-annex.linux -- ./runshell or 'cd bin; ./git" - -### What version of git-annex are you using? On what operating system? - -Synology DSM 4.3-3810 and latest nightly build of git-annex. - -> The shimming was broken, causing the hang. [[fixed|done]] -> -> (It looks like you somehow forgot to set HOME when becoming the non-root -> user.) --[[Joey]] diff --git a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_1_c398f92de91729e60b59127733759a38._comment b/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_1_c398f92de91729e60b59127733759a38._comment deleted file mode 100644 index 897b588b3..000000000 --- a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_1_c398f92de91729e60b59127733759a38._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Same hang when added to $PATH" - date="2013-12-21T03:28:07Z" - content=""" -DiskStation> echo $PATH - -/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin:/root/git-annex.linux - -DiskStation> git-annex-shell - -[...hangs...] -"""]] diff --git a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_2_646087d44ee32f78784ae9e8d65d87e6._comment b/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_2_646087d44ee32f78784ae9e8d65d87e6._comment deleted file mode 100644 index 16d282470..000000000 --- a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_2_646087d44ee32f78784ae9e8d65d87e6._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 2" - date="2013-12-21T06:27:49Z" - content=""" -Try not as root, see how far that gets you. -"""]] diff --git a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_3_205e41cb0abaed3e16d45206bb2e77a4._comment b/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_3_205e41cb0abaed3e16d45206bb2e77a4._comment deleted file mode 100644 index 2c78250b5..000000000 --- a/doc/bugs/Armel_version_broken_on_Synology_DSM_4.3-3810/comment_3_205e41cb0abaed3e16d45206bb2e77a4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="comment 3" - date="2013-12-21T08:22:28Z" - content=""" -Hi Greg, I tried that and got a permissions error. - -\"./runshell: line 40: can't create /root/.ssh/git-annex-shell: Permission denied chmod: /root/.ssh/git-annex-shell: Permission denied\" -"""]] diff --git a/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp.mdwn b/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp.mdwn deleted file mode 100644 index 256bc1e7f..000000000 --- a/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -The assistant web UI says: `SanityCheckerStartup crashed: /home/zerodogg/Delt/.git/annex/tmp/Sak_7.pdf: getFileStatus: does not exist (No such file or directory)` with a «Restart thread»-button. Clicking said button merely makes the error re-appear. The file in question is a broken symlink. Deleting the symlink and then restarting the thread fixes the problem. - -I'm not sure what causes said symlink to appear (which has the name of a file that does exist in the annex), but it has done so on several systems accross different distributions here (Fedora 20, Ubuntu 14.04, Archlinux). Perhaps an rsync copies over a symlink instead of a file? - -git-annex version: 5.20140517-gee56d21 - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp/comment_1_659e0c5127c92b1c7643823d0c240543._comment b/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp/comment_1_659e0c5127c92b1c7643823d0c240543._comment deleted file mode 100644 index 22e7b66f4..000000000 --- a/doc/bugs/Assistant_breaks_when_broken_symlinks_are_in_.git__47__annex__47__tmp/comment_1_659e0c5127c92b1c7643823d0c240543._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 1" - date="2014-05-30T18:58:56Z" - content=""" -Well, Sak7.pdf is not a git-annex object filename. And .git/annex/tmp used to be used as a general-purpose temp directory, but in recent versions we're moving away from that; it's only supposed to contain git-annex objects. - -So, this must be a leftover file from an old version of git-annex. I don't know offhand what would create a symlink in the temp directory. However, the crash is from the code that was added to the assistant to clean up such left behind files. So, I'll fix that code. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files.mdwn b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files.mdwn deleted file mode 100644 index ebf238072..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files.mdwn +++ /dev/null @@ -1,64 +0,0 @@ -### Please describe the problem. - -The assistant/webapp doesn't drop files from the local (source) repository after transferring it to the 2 backup repositories (numcopies 2), but they are listed with: - - git annex find --want-drop - -### What steps will reproduce the problem? - -#### mintcream #### - - git init annex - cd ~/annex - git commit -m "create" --allow-empty - git annex init mintcream - git annex numcopies 2 - git annex group here source - git config annex.autocommit false - git annex webapp - -#### liquorice #### - - git init annex - cd ~/annex - git annex init liquorice - git annex group here backup - -#### candyfloss #### - - git init annex - cd ~/annex - git annex init candyfloss - git annex group here backup - -#### mintcream #### - - (add both backup repositories in webapp as "remote repositories") - (copy files into ~/annex directory) - git annex add - git commit -m "add some files" - (use "sync now" to prod assistant into noticing the commit) - -### What was I expecting to happen? ### - -The assistant to transfer the files to liquorice and candyfloss, then for the assistant to drop the files from mintcream. - -### What actually happened? ### - -The assistant transfers the files to liquorice and candyfloss. No files are dropped from mintcream. - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140707-g923b436 - -Arch Linux (git-annex-bin from AUR) - -### Please provide any additional information below. - -I wish to retain control of the commits on "master" (annex.autocommit false) but want the assistant to handle moving/dropping the files as required in the background. - - git annex drop --auto - -works as expected. - -> [[done]]; user misconfiguration. --[[Joey]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_1_f32fbae29e4db039804c0853256c238c._comment b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_1_f32fbae29e4db039804c0853256c238c._comment deleted file mode 100644 index 61c62703c..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_1_f32fbae29e4db039804c0853256c238c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-10T18:48:17Z" - content=""" -Reproduced. `git annex sync --content` has the same problem. - -Of course, both it and the assistant *do* check if files can be dropped. For some reason, it is deciding it is not safe to drop the file. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_2_405bfa00dfd433352c263afe75e94b2c._comment b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_2_405bfa00dfd433352c263afe75e94b2c._comment deleted file mode 100644 index d7d288b39..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_2_405bfa00dfd433352c263afe75e94b2c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="user misconfiguration" - date="2014-07-10T19:02:00Z" - content=""" -Reason is simple: You manually put the repository into the source group, but its preferred content is not set to \"standard\". No matter what group a repository is in, you have to set its preferred content to something, or git-annex will default to assuming you want the repo to retain all files. - -So, `git annex wanted mintcream standard` and away you go. You'll also want to set that for the other 2 repos probably.. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_3_c8cac8d800199ca4d8a65ba72abf678e._comment b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_3_c8cac8d800199ca4d8a65ba72abf678e._comment deleted file mode 100644 index 81b25c8f0..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_3_c8cac8d800199ca4d8a65ba72abf678e._comment +++ /dev/null @@ -1,40 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - ip="81.111.193.130" - subject="comment 3" - date="2014-07-11T10:41:23Z" - content=""" -Ohhh I see! - -I was expecting \"standard\" to be the default because of what vicfg shows.. - - # Repository preferred contents - # (for web) - #wanted 00000000-0000-0000-0000-000000000001 = standard - # (for test) - #wanted 025d4d21-7648-426c-a406-bb7f27688afe = standard - - # Group preferred contents - # (Used by repositories with \"groupwanted\" in their preferred contents) - #groupwanted archive = standard - #groupwanted backup = standard - #groupwanted client = standard - #groupwanted incrementalbackup = standard - #groupwanted manual = standard - #groupwanted public = standard - #groupwanted smallarchive = standard - #groupwanted source = standard - #groupwanted transfer = standard - -In my experience with configuration files, a commented out line like this: - - #wanted 025d4d21-7648-426c-a406-bb7f27688afe = standard - -without any \"this is an example\" text above it means \"this is the default setting\". Everything in vicfg looks like it is the current settings, rather than just placeholders.. - -I understand why you need to set the wanted explicitly (at least from the command line), but the way information is shown in vicfg led me to interact with it incorrectly. Would it be worth adding a disclaimer that commented lines are examples, not defaults? As far as I am aware, the logic I explained above (commented line == default) is the \"norm\" in *nix configuration files, which would make vicfg non-intuitive. - -All I need to do now is not be so bothered by how messy the git-annex branch looks when the assistant is running things! :D - -Thankies -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_4_ee5fa8a22d1571b0040aa97c4979ef92._comment b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_4_ee5fa8a22d1571b0040aa97c4979ef92._comment deleted file mode 100644 index 237182879..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_4_ee5fa8a22d1571b0040aa97c4979ef92._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - ip="81.111.193.130" - subject="comment 4" - date="2014-07-11T10:57:58Z" - content=""" -Actually, I'm still a little confused. - -If git-annex was presuming I wanted to keep all the files as you say, why were they listed in `git annex find --want-drop` and dropped by `git annex drop --auto`? - -Shouldn't they have been empty and a no-op respectively? - -There seems to be a difference in the behaviour between the command line (wanting to and actually dropping the files) and the assistant (wanting to keep them) for the same settings. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_5_eef448b9e3dd1a717430a60d1001a7ee._comment b/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_5_eef448b9e3dd1a717430a60d1001a7ee._comment deleted file mode 100644 index 11c690cb7..000000000 --- a/doc/bugs/Assistant_doesn__39__t_check_if_it_can_drop_files/comment_5_eef448b9e3dd1a717430a60d1001a7ee._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 5" - date="2014-07-11T18:27:44Z" - content=""" -The assistant defaults to assuming all files are wanted if there's no preferred content settings, while command-line dropping stuff defaults to assuming no files are wanted (or more accurately, that you'll drop anything you don't want and get anything you do) when there's no preferred content settings. So the default differs, but this only matters when not setting preferred contents. - -I agree that the vicfg could be misread, so have changed it. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate.mdwn b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate.mdwn deleted file mode 100644 index 0ad0f1eb3..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate.mdwn +++ /dev/null @@ -1,435 +0,0 @@ -### Please describe the problem. - -On two hosts, I've configured two separate local repositories (~/foo and ~/bar) with the assistant and added a transfer repository to ~/foo. - -While files are kept separate, the configuration seems to get mixed up. This results in all files beeing uploaded to the configured transfer repository. - -The reason might be, that informations about ~/bar are included in the configuration of ~/foo (see below). - -### What steps will reproduce the problem? - -* Create local repository ~/foo on both hosts -* Add transfer repository to ~/foo on both hosts -* Add some files to ~/foo and let it sync -* Create local repository ~/bar and select keep the repositories separate on both hosts -* All files of ~/foo will now be uploaded again to the transfer repository - -### What version of git-annex are you using? On what operating system? - -5.20140421~bpo70+1 on Debian 7.5 amd64 - -### Please provide any additional information below. - -*trh@czc4142wfz:~/foo$ git-annex info* -<pre><code>repository mode: direct -trusted repositories: 0 -semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - bd23a5ed-af6e-466d-ac8c-9ea38a220c62 -- trh@r9-y3pll:~/foo - cc888105-b6c3-4926-8396-e3870f6bfc05 -- transfer_foo - f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 -- here (trh@czc4142wfz:~/foo) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 356.11 gigabytes (+1 megabyte reserved) -local annex keys: 2 -local annex size: 2.99 gigabytes -annexed files in working tree: 2 -size of annexed files in working tree: 2.99 gigabytes -bloom filter size: 16 mebibytes (0% full) -backend usage: - SHA256E: 4 -</code></pre> - -*trh@czc4142wfz:~/bar$ git-annex info* -<pre><code>repository mode: direct -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - f1478436-cf7b-4a05-91a6-91157ae5e9c4 -- here (trh@czc4142wfz:~/bar) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 356.11 gigabytes (+1 megabyte reserved) -local annex keys: 0 -local annex size: 0 bytes -annexed files in working tree: 0 -size of annexed files in working tree: 0 bytes -bloom filter size: 16 mebibytes (0% full) -backend usage: -</code></pre> - -*trh@czc4142wfz:~/foo$ git-annex vicfg* -<pre><code># git-annex configuration -# -# Changes saved to this file will be recorded in the git-annex branch. -# -# Lines in this file have the format: -# setting field = value - -# Repository trust configuration -# (Valid trust levels: trusted semitrusted untrusted dead) -# (for web) -#trust 00000000-0000-0000-0000-000000000001 = semitrusted -# (for trh@r9-y3pll:~/foo) -#trust bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = semitrusted -# (for transfer_foo) -#trust cc888105-b6c3-4926-8396-e3870f6bfc05 = semitrusted -# (for trh@czc4142wfz:~/foo) -#trust f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = semitrusted - -# Repository groups -# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) -# (Separate group names with spaces) -# (for ) -group 357eaef4-af1b-491a-a003-01c2d583056e = client -# (for trh@r9-y3pll:~/foo) -group bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = client -# (for ) -group f1478436-cf7b-4a05-91a6-91157ae5e9c4 = client -# (for trh@czc4142wfz:~/foo) -group f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = client -# (for transfer_foo) -group cc888105-b6c3-4926-8396-e3870f6bfc05 = transfer -# (for web) -#group 00000000-0000-0000-0000-000000000001 = - -# Repository preferred contents -# (for ) -wanted 357eaef4-af1b-491a-a003-01c2d583056e = standard -# (for trh@r9-y3pll:~/foo) -wanted bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = standard -# (for transfer_foo) -wanted cc888105-b6c3-4926-8396-e3870f6bfc05 = standard -# (for ) -wanted f1478436-cf7b-4a05-91a6-91157ae5e9c4 = standard -# (for trh@czc4142wfz:~/foo) -wanted f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = standard -# (for web) -#wanted 00000000-0000-0000-0000-000000000001 = standard - -# Group preferred contents -# (Used by repositories with "groupwanted" in their preferred contents) -#groupwanted archive = standard -#groupwanted backup = standard -#groupwanted client = standard -#groupwanted incrementalbackup = standard -#groupwanted manual = standard -#groupwanted public = standard -#groupwanted smallarchive = standard -#groupwanted source = standard -#groupwanted transfer = standard -#groupwanted unwanted = standard - -# Standard preferred contents -# (Used by wanted or groupwanted expressions containing "standard") -# (For reference only; built-in and cannot be changed!) -# standard client = (((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1 -# standard transfer = (not (inallgroup=client and copies=client:2) and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard backup = include=* or unused -# standard incrementalbackup = ((include=* or unused) and (not copies=incrementalbackup:1)) or approxlackingcopies=1 -# standard smallarchive = ((include=*/archive/* or include=archive/*) and ((not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard archive = (not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1 -# standard source = not (copies=1) -# standard manual = present and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1) -# standard public = inpreferreddir -# standard unwanted = exclude=* - -# Repository required contents -# (for web) -#required 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/foo) -#required bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = -# (for transfer_foo) -#required cc888105-b6c3-4926-8396-e3870f6bfc05 = -# (for trh@czc4142wfz:~/foo) -#required f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = - -# Scheduled activities -# (Separate multiple activities with "; ") -# (for web) -#schedule 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/foo) -#schedule bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = -# (for transfer_foo) -#schedule cc888105-b6c3-4926-8396-e3870f6bfc05 = -# (for trh@czc4142wfz:~/foo) -#schedule f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = -</code></pre> - -**Note: f1478436-cf7b-4a05-91a6-91157ae5e9c4 is id of ~/bar on local host (see below) / 357eaef4-af1b-491a-a003-01c2d583056e is id of ~/bar on r9-y3pll** - -*trh@czc4142wfz:~/bar$ git-annex vicfg* -<pre><code># git-annex configuration -# -# Changes saved to this file will be recorded in the git-annex branch. -# -# Lines in this file have the format: -# setting field = value - -# Repository trust configuration -# (Valid trust levels: trusted semitrusted untrusted dead) -# (for web) -#trust 00000000-0000-0000-0000-000000000001 = semitrusted -# (for trh@czc4142wfz:~/bar) -#trust f1478436-cf7b-4a05-91a6-91157ae5e9c4 = semitrusted - -# Repository groups -# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) -# (Separate group names with spaces) -# (for web) -#group 00000000-0000-0000-0000-000000000001 = -# (for trh@czc4142wfz:~/bar) -#group f1478436-cf7b-4a05-91a6-91157ae5e9c4 = - -# Repository preferred contents -# (for web) -#wanted 00000000-0000-0000-0000-000000000001 = standard -# (for trh@czc4142wfz:~/bar) -#wanted f1478436-cf7b-4a05-91a6-91157ae5e9c4 = standard - -# Group preferred contents -# (Used by repositories with "groupwanted" in their preferred contents) -#groupwanted archive = standard -#groupwanted backup = standard -#groupwanted client = standard -#groupwanted incrementalbackup = standard -#groupwanted manual = standard -#groupwanted public = standard -#groupwanted smallarchive = standard -#groupwanted source = standard -#groupwanted transfer = standard -#groupwanted unwanted = standard - -# Standard preferred contents -# (Used by wanted or groupwanted expressions containing "standard") -# (For reference only; built-in and cannot be changed!) -# standard client = (((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1 -# standard transfer = (not (inallgroup=client and copies=client:2) and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard backup = include=* or unused -# standard incrementalbackup = ((include=* or unused) and (not copies=incrementalbackup:1)) or approxlackingcopies=1 -# standard smallarchive = ((include=*/archive/* or include=archive/*) and ((not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard archive = (not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1 -# standard source = not (copies=1) -# standard manual = present and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1) -# standard public = inpreferreddir -# standard unwanted = exclude=* - -# Repository required contents -# (for web) -#required 00000000-0000-0000-0000-000000000001 = -# (for trh@czc4142wfz:~/bar) -#required f1478436-cf7b-4a05-91a6-91157ae5e9c4 = - -# Scheduled activities -# (Separate multiple activities with "; ") -# (for web) -#schedule 00000000-0000-0000-0000-000000000001 = -# (for trh@czc4142wfz:~/bar) -#schedule f1478436-cf7b-4a05-91a6-91157ae5e9c4 = -</code></pre> - -*trh@r9-y3pll:~/foo$ git-annex info* -<pre><code>repository mode: direct -trusted repositories: 0 -semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - bd23a5ed-af6e-466d-ac8c-9ea38a220c62 -- here (trh@r9-y3pll:~/foo) - cc888105-b6c3-4926-8396-e3870f6bfc05 -- transfer_foo - f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 -- trh@czc4142wfz:~/foo -untrusted repositories: 0 -transfers in progress: none -available local disk space: 280.24 gigabytes (+1 megabyte reserved) -local annex keys: 2 -local annex size: 2.99 gigabytes -annexed files in working tree: 2 -size of annexed files in working tree: 2.99 gigabytes -bloom filter size: 16 mebibytes (0% full) -backend usage: - SHA256E: 4 -</code></pre> - -*trh@r9-y3pll:~/bar$ git-annex info* -<pre><code>repository mode: direct -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - 357eaef4-af1b-491a-a003-01c2d583056e -- here (trh@r9-y3pll:~/bar) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 280.24 gigabytes (+1 megabyte reserved) -local annex keys: 0 -local annex size: 0 bytes -annexed files in working tree: 0 -size of annexed files in working tree: 0 bytes -bloom filter size: 16 mebibytes (0% full) -backend usage: -</code></pre> - -*trh@r9-y3pll:~/foo$ git-annex vicfg* -<pre><code># git-annex configuration -# -# Changes saved to this file will be recorded in the git-annex branch. -# -# Lines in this file have the format: -# setting field = value - -# Repository trust configuration -# (Valid trust levels: trusted semitrusted untrusted dead) -# (for web) -#trust 00000000-0000-0000-0000-000000000001 = semitrusted -# (for trh@r9-y3pll:~/foo) -#trust bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = semitrusted -# (for transfer_foo) -#trust cc888105-b6c3-4926-8396-e3870f6bfc05 = semitrusted -# (for trh@czc4142wfz:~/foo) -#trust f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = semitrusted - -# Repository groups -# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) -# (Separate group names with spaces) -# (for ) -group 357eaef4-af1b-491a-a003-01c2d583056e = client -# (for trh@r9-y3pll:~/foo) -group bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = client -# (for ) -group f1478436-cf7b-4a05-91a6-91157ae5e9c4 = client -# (for trh@czc4142wfz:~/foo) -group f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = client -# (for transfer_foo) -group cc888105-b6c3-4926-8396-e3870f6bfc05 = transfer -# (for web) -#group 00000000-0000-0000-0000-000000000001 = - -# Repository preferred contents -# (for ) -wanted 357eaef4-af1b-491a-a003-01c2d583056e = standard -# (for trh@r9-y3pll:~/foo) -wanted bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = standard -# (for transfer_foo) -wanted cc888105-b6c3-4926-8396-e3870f6bfc05 = standard -# (for ) -wanted f1478436-cf7b-4a05-91a6-91157ae5e9c4 = standard -# (for trh@czc4142wfz:~/foo) -wanted f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = standard -# (for web) -#wanted 00000000-0000-0000-0000-000000000001 = standard - -# Group preferred contents -# (Used by repositories with "groupwanted" in their preferred contents) -#groupwanted archive = standard -#groupwanted backup = standard -#groupwanted client = standard -#groupwanted incrementalbackup = standard -#groupwanted manual = standard -#groupwanted public = standard -#groupwanted smallarchive = standard -#groupwanted source = standard -#groupwanted transfer = standard -#groupwanted unwanted = standard - -# Standard preferred contents -# (Used by wanted or groupwanted expressions containing "standard") -# (For reference only; built-in and cannot be changed!) -# standard client = (((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1 -# standard transfer = (not (inallgroup=client and copies=client:2) and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard backup = include=* or unused -# standard incrementalbackup = ((include=* or unused) and (not copies=incrementalbackup:1)) or approxlackingcopies=1 -# standard smallarchive = ((include=*/archive/* or include=archive/*) and ((not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard archive = (not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1 -# standard source = not (copies=1) -# standard manual = present and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1) -# standard public = inpreferreddir -# standard unwanted = exclude=* - -# Repository required contents -# (for web) -#required 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/foo) -#required bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = -# (for transfer_foo) -#required cc888105-b6c3-4926-8396-e3870f6bfc05 = -# (for trh@czc4142wfz:~/foo) -#required f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = - -# Scheduled activities -# (Separate multiple activities with "; ") -# (for web) -#schedule 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/foo) -#schedule bd23a5ed-af6e-466d-ac8c-9ea38a220c62 = -# (for transfer_foo) -#schedule cc888105-b6c3-4926-8396-e3870f6bfc05 = -# (for trh@czc4142wfz:~/foo) -#schedule f3b332fd-4b7a-4a5b-b077-8f13d3d9a407 = -</code></pre> - -*trh@r9-y3pll:~/bar$ git-annex vicfg* -<pre><code># git-annex configuration -# -# Changes saved to this file will be recorded in the git-annex branch. -# -# Lines in this file have the format: -# setting field = value - -# Repository trust configuration -# (Valid trust levels: trusted semitrusted untrusted dead) -# (for web) -#trust 00000000-0000-0000-0000-000000000001 = semitrusted -# (for trh@r9-y3pll:~/bar) -#trust 357eaef4-af1b-491a-a003-01c2d583056e = semitrusted - -# Repository groups -# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) -# (Separate group names with spaces) -# (for web) -#group 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/bar) -#group 357eaef4-af1b-491a-a003-01c2d583056e = - -# Repository preferred contents -# (for web) -#wanted 00000000-0000-0000-0000-000000000001 = standard -# (for trh@r9-y3pll:~/bar) -#wanted 357eaef4-af1b-491a-a003-01c2d583056e = standard - -# Group preferred contents -# (Used by repositories with "groupwanted" in their preferred contents) -#groupwanted archive = standard -#groupwanted backup = standard -#groupwanted client = standard -#groupwanted incrementalbackup = standard -#groupwanted manual = standard -#groupwanted public = standard -#groupwanted smallarchive = standard -#groupwanted source = standard -#groupwanted transfer = standard -#groupwanted unwanted = standard - -# Standard preferred contents -# (Used by wanted or groupwanted expressions containing "standard") -# (For reference only; built-in and cannot be changed!) -# standard client = (((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1 -# standard transfer = (not (inallgroup=client and copies=client:2) and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard backup = include=* or unused -# standard incrementalbackup = ((include=* or unused) and (not copies=incrementalbackup:1)) or approxlackingcopies=1 -# standard smallarchive = ((include=*/archive/* or include=archive/*) and ((not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1)) or approxlackingcopies=1 -# standard archive = (not (copies=archive:1 or copies=smallarchive:1)) or approxlackingcopies=1 -# standard source = not (copies=1) -# standard manual = present and ((((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) and not unused) or approxlackingcopies=1) -# standard public = inpreferreddir -# standard unwanted = exclude=* - -# Repository required contents -# (for web) -#required 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/bar) -#required 357eaef4-af1b-491a-a003-01c2d583056e = - -# Scheduled activities -# (Separate multiple activities with "; ") -# (for web) -#schedule 00000000-0000-0000-0000-000000000001 = -# (for trh@r9-y3pll:~/bar) -#schedule 357eaef4-af1b-491a-a003-01c2d583056e = -</code></pre> - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_1_418103046e296a43cfe0f0cf69e729d5._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_1_418103046e296a43cfe0f0cf69e729d5._comment deleted file mode 100644 index 7a21b52ce..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_1_418103046e296a43cfe0f0cf69e729d5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 1" - date="2014-05-29T18:21:30Z" - content=""" -As far as I can understand the description (which has an lot of different \"foo\"'s in it that seem to refer to different things?) -- This is the assistant behaving as designed: Any time two repositories are pointed at the same transfer repository, or removable drive repository, etc, they will unify and share all their files. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_2_9405804842bb23e8040ec85b271b18af._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_2_9405804842bb23e8040ec85b271b18af._comment deleted file mode 100644 index f6a37583a..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_2_9405804842bb23e8040ec85b271b18af._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmi0jblSiI4c5-EswqKw4PXkx5M4fuVvdk" - nickname="Henry" - subject="comment 2" - date="2014-05-29T19:10:08Z" - content=""" -I'm using the same folder name on different hosts. So yes, ~/foo exists 3 times. Let me try to clarify it: - -<pre> -Client Transfer Client -r9-y3pll edhp-transfer czc4142wfz -~/foo <-> ~/foo <-> ~/foo -~/bar ~/bar -</pre> - -So, I have two clients and one transfer server. Both clients have two local repositories ~/foo and ~/bar. - -The transfer repository has only be configured to the ~/foo client repositories, but not to the ~/bar repositories. - -But for some reason, the ~/foo repositories know about the ~/bar repositories (see the id's of the git-annex vicfg output for ~/foo repositories above) and keep uploading files to the transfer repository, even I did select keep the repositories separate on both hosts. - - -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_3_01fc26e443ea3a8a351174b45f25dc2a._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_3_01fc26e443ea3a8a351174b45f25dc2a._comment deleted file mode 100644 index acbc51c8e..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_3_01fc26e443ea3a8a351174b45f25dc2a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 3" - date="2014-05-29T19:14:51Z" - content=""" -Are you using XMPP? - -There's no way for the foo repositories to learn about the bar repositories unless one of the foo repositories has a remote that is either one of the bar repositories, or that one of the bar repositories points to. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_4_6e8f0889359bb2f3e3438658c9776f76._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_4_6e8f0889359bb2f3e3438658c9776f76._comment deleted file mode 100644 index 58804fccf..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_4_6e8f0889359bb2f3e3438658c9776f76._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmi0jblSiI4c5-EswqKw4PXkx5M4fuVvdk" - nickname="Henry" - subject="comment 4" - date="2014-05-29T20:10:15Z" - content=""" -No, I haven't configured XMPP yet. - -I just tried something else: - -Within assistant I've switched to repository ~bar and then added another repository ~/foobar and again selected keep the repositories separate. - -The result is, ~/bar knows (vicfg) about ~/foobar, but ~/foo doesn't. It seems to me, that when adding another local repository, the new repository gets known to the currently selected repository. -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_5_902fe9ff295453461b66d84463205fc3._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_5_902fe9ff295453461b66d84463205fc3._comment deleted file mode 100644 index 9954f7b01..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_5_902fe9ff295453461b66d84463205fc3._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 5" - date="2014-05-29T20:46:47Z" - content=""" -Ok, reproduced that. - -Webapp seems to be setting up the newly created repository's group and preferred content settings inside the current repository. The 2 repositories are not otherwise linked or sharing data in any way, so this the impact is limited to 2 lines that won't affect anything being committed to the git-annex branch, and to the newly created repository not defaulting to being in the client group or having the standard preferred content setting (which can easily be fixed with the webapp). -"""]] diff --git a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_6_ce01656b191d2bb13a3ddc29794e1e7a._comment b/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_6_ce01656b191d2bb13a3ddc29794e1e7a._comment deleted file mode 100644 index fd589eb18..000000000 --- a/doc/bugs/Assistant_doesn__39__t_keep_separate_local_repositories_100__37___separate/comment_6_ce01656b191d2bb13a3ddc29794e1e7a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmi0jblSiI4c5-EswqKw4PXkx5M4fuVvdk" - nickname="Henry" - subject="comment 6" - date="2014-06-11T16:31:09Z" - content=""" -I've just installed 5.20140606 from sid and the problem is gone :-) - -Now hoping that this or one of the next release will make it into wheezy backports ;-) - -Thank you for your great work and support and sorry for my late feedback. -"""]] diff --git a/doc/bugs/Assistant_dropping_from_backup_repo.mdwn b/doc/bugs/Assistant_dropping_from_backup_repo.mdwn deleted file mode 100644 index 0e0fd5909..000000000 --- a/doc/bugs/Assistant_dropping_from_backup_repo.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -Setup: - -* fresh install of Debian Wheezy with git-annex 4.20130227 pulled in from unstable - -Steps: - -* clone existing repository and activate assistant -* Have USB drive, U, with repository group `backup` and preferred content string `standard` - -Expected: - -* Assistant never ever tries to drop anything from U - -Actual: - -* Assistant immediately tries to drop files from U; fortunately I didn't have the USB drive plugged in -* Changing the preferred content string of U to `present or include=*` stops the dropping, but this was never required before - -Additional information: - -* The files that the Assistant started trying to drop were, I believe, the first (alphabetically) files in my repository to contain non-ascii characters in their file names (some French accented letters) - -Thanks. - -> The non-ascii characters are the giveaway: For 1 version, git-annex used -> a regex library that failed to ever match non-ascii characters. So it -> thought backup repos, which match "*" with a regex, wanted no such files. -> This is [[fixed|done]]. --[[Joey]] diff --git a/doc/bugs/Assistant_dropping_from_backup_repo/comment_1_c13d86fb2541676ee4ca1446b99e0e68._comment b/doc/bugs/Assistant_dropping_from_backup_repo/comment_1_c13d86fb2541676ee4ca1446b99e0e68._comment deleted file mode 100644 index 5e69655e0..000000000 --- a/doc/bugs/Assistant_dropping_from_backup_repo/comment_1_c13d86fb2541676ee4ca1446b99e0e68._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="173.162.44.162" - subject="comment 1" - date="2013-03-12T14:25:16Z" - content=""" -This sounds very similar to [[http://git-annex.branchable.com/bugs/__39__client__39___repo_starts_pulling_in___39__archive__39___content/]]; my client was pulling in content prior to dropping it from a \"backup\" repo on a USB drive. -"""]] diff --git a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup.mdwn b/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup.mdwn deleted file mode 100644 index fc87672c4..000000000 --- a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -The assistant from the standalone 64bit build crashes upon startup. - -### Version information - - [0 zerodogg@firefly annexed]$ git annex version - git-annex version: 5.20131230-g4aa88d8 - build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav glacier hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - [0 zerodogg@firefly annexed]$ uname -a - Linux firefly 3.12.5-302.fc20.x86_64 #1 SMP Tue Dec 17 20:42:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux - [0 zerodogg@firefly annexed]$ cat /etc/fedora-release - Fedora release 20 (Heisenbug) - [0 zerodogg@firefly annexed]$ - -### Error - - [0 zerodogg@firefly annexed]$ git annex webapp - Launching web browser on file:///home/zerodogg/Documents/annexed/.git/annex/webapp.html - - (process:6045): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed - libgcc_s.so.1 must be installed for pthread_cancel to work - error: git-annex died of signal 6 - [134 zerodogg@firefly annexed]$ ls -l /usr/lib64/libgcc_s.so.1 - lrwxrwxrwx. 1 root root 28 2013-12-18 10:54 /usr/lib64/libgcc_s.so.1 -> libgcc_s-4.8.2-20131212.so.1 - [0 zerodogg@firefly annexed]$ - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_1_56befc288c40e062e086d93d26064342._comment b/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_1_56befc288c40e062e086d93d26064342._comment deleted file mode 100644 index 951d2687a..000000000 --- a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_1_56befc288c40e062e086d93d26064342._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 1" - date="2013-12-31T18:55:36Z" - content=""" -You seem to show `git-annex version` being run without crashing, so it does not seem to crash on startup generally. - -Also, this build of git-annex is not linked to libgcc at all. - -Also, git-annex seems to start your web browser. - -So, it seems more likely that your web browser is crashing than that git-annex is crashing. The web browser crash may be taking out git-annex in some way. -"""]] diff --git a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_2_107ab23eac98a168d2920bb88b4ec86f._comment b/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_2_107ab23eac98a168d2920bb88b4ec86f._comment deleted file mode 100644 index ef1beb973..000000000 --- a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_2_107ab23eac98a168d2920bb88b4ec86f._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 2" - date="2013-12-31T19:11:16Z" - content=""" -I've verified that git-annex runs the web browser in a cleaned up environment, that does not, for example, have the `LD_LIBRARY_PATH` used by the bundle set. - -I checked this by making a ~/dumpenv script: - -[[!format sh \"\"\" -#!/bin/sh -set -echo \"$@\" -\"\"\"]] - -Then `chmod +x ~/dumpenv; git config web.browser ~/dumpenv` and `git annex webapp` to run it. - -I did notice that it set `GCONV_PATH=''`, rather than unsetting that variable, and have made a commit fixing that. But I doubt that caused this problem. - -The \"g_slice_set_config: assertion 'sys_page_size == 0\" seems to be a Mozilla bug: <https://bugzilla.mozilla.org/show_bug.cgi?id=672671>, and does not seem to be related, probably firefox is printing that well before crashing. - -It looks like libc can somehow demand-load libgcc_s.so, so I have force included that into the bundle. Don't know if that will help. Will be available in autobuilds in an hour. -"""]] diff --git a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_3_7707c47aacde425ca6149dd828dd27fb._comment b/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_3_7707c47aacde425ca6149dd828dd27fb._comment deleted file mode 100644 index dd1239733..000000000 --- a/doc/bugs/Assistant_from_standalone_5.20131230_64bit_crashes_on_startup/comment_3_7707c47aacde425ca6149dd828dd27fb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="EskildHustvedt" - ip="80.202.213.197" - subject="comment 3" - date="2014-01-01T02:36:47Z" - content=""" -The browser doesn't crash, it stays up, though the git annex page disappears (replaced by the usual \"connection refused\" page from firefox) after a few seconds (ie. \"git annex webapp\" starts the browser, the git-annex page appears for a few seconds, and then it disappears as git-annex crashes, leaving the browser still running). - -The latest daily build appears to work now though: git-annex version: 5.20140101-gf9e5218, so that seems to have done the trick. -"""]] diff --git a/doc/bugs/Assistant_merge_loop.mdwn b/doc/bugs/Assistant_merge_loop.mdwn deleted file mode 100644 index edff5e4b3..000000000 --- a/doc/bugs/Assistant_merge_loop.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -The assistant appears to be in a merge loop with at least two of my repos. It's creating thousands of merge commits without any changes. One repository that contains around 600 files that change very very rarely now has 63528 commits. - -Here's a screenshot from tig: [[https://ssl.zerodogg.org/~zerodogg/private/tmp/Skjermdump_fra_2014-07-05_07:09:22-2014-07-05.png]] - -I can privately provide a copy of the git repo itself if needed. - -Using the standalone build, 64bit, on ArchLinux, Fedora 20 and Ubuntu 14.04. - - $ git annex version - git-annex version: 5.20140610-g5ec8bcf - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -> [[fixed|done]]. Note that 5.20140708 contained an incomplete fix for this -> bug. --[[Joey]] diff --git a/doc/bugs/Assistant_merge_loop/comment_10_8fe176691f0f61c15085d3c38f0ea50f._comment b/doc/bugs/Assistant_merge_loop/comment_10_8fe176691f0f61c15085d3c38f0ea50f._comment deleted file mode 100644 index 1826e313a..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_10_8fe176691f0f61c15085d3c38f0ea50f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 10" - date="2014-07-16T20:32:57Z" - content=""" -I have two computers with Debian testing (5.20140529) that aren't having the issue, and one with Debian Sid (5.20140709) that is still creating the empty merge commits -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_11_6e3a78327c0b813415ebf85e298813d4._comment b/doc/bugs/Assistant_merge_loop/comment_11_6e3a78327c0b813415ebf85e298813d4._comment deleted file mode 100644 index 7823176ef..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_11_6e3a78327c0b813415ebf85e298813d4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 11" - date="2014-07-16T20:36:32Z" - content=""" -Has the assistant been restarted since git-annex was upgraded to the fixed version? - -Can you post a debug.log? -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_12_fc5ceb09cc358521b32877fe4b0fb821._comment b/doc/bugs/Assistant_merge_loop/comment_12_fc5ceb09cc358521b32877fe4b0fb821._comment deleted file mode 100644 index 7e0a534da..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_12_fc5ceb09cc358521b32877fe4b0fb821._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="EskildHustvedt" - ip="80.202.103.55" - subject="comment 12" - date="2014-07-19T06:22:57Z" - content=""" -This issue has been resolved for me. No new empty merges since 2014-07-12. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_14_46bddc2451da3bf5029248198cf02dcd._comment b/doc/bugs/Assistant_merge_loop/comment_14_46bddc2451da3bf5029248198cf02dcd._comment deleted file mode 100644 index 6ee3fb79e..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_14_46bddc2451da3bf5029248198cf02dcd._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 14" - date="2014-09-08T07:27:46Z" - content=""" -Still experiencing this bug in Debian testing (5.20140717) and Debian sid (5.20140831) -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_14_89947f4af19ceae36fbe0a69aa10df25._comment b/doc/bugs/Assistant_merge_loop/comment_14_89947f4af19ceae36fbe0a69aa10df25._comment deleted file mode 100644 index fb95257ec..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_14_89947f4af19ceae36fbe0a69aa10df25._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 14" - date="2014-11-09T22:56:31Z" - content=""" -I have 3 computers syncing through a private github repo (with annex-ignore = true) and a box account for transferring files. The computers are up to date debian:testing:amd64, debian:testing:i386 and debian:sid:amd64. - -I'm getting lots of empty commits with the text \"merge refs/remotes/github/synced/master\". I would really like to help in debugging this issue if possible. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_15_494f55419f131495a7994afe2a0e9bc3._comment b/doc/bugs/Assistant_merge_loop/comment_15_494f55419f131495a7994afe2a0e9bc3._comment deleted file mode 100644 index db92aadc6..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_15_494f55419f131495a7994afe2a0e9bc3._comment +++ /dev/null @@ -1,54 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 15" - date="2015-02-18T12:39:04Z" - content=""" -This is happening in in a repo shared by two computers using the webapp with version 5.20141125. All are empty commits. - - * 23da33e - (7 minutes ago) merge refs/remotes/bitbucket/synced/master (HEAD, bitbucket/synced/master, annex/direct/master) - * 7bd23db - (67 minutes ago) merge refs/remotes/bitbucket/synced/master - * d2f5c6b - (2 hours ago) merge refs/remotes/bitbucket/synced/master - * 05c0448 - (12 hours ago) merge refs/remotes/bitbucket/synced/master - * 5c370aa - (19 hours ago) merge refs/remotes/bitbucket/synced/master - * c6d7be4 - (20 hours ago) merge refs/remotes/bitbucket/synced/master - * 507a6c7 - (21 hours ago) merge refs/remotes/bitbucket/synced/master - * 6932fec - (22 hours ago) merge refs/remotes/bitbucket/synced/master - * cc0efa1 - (23 hours ago) merge refs/remotes/bitbucket/synced/master - * 12a7b8f - (24 hours ago) merge refs/remotes/bitbucket/synced/master - * 49a3f2c - (25 hours ago) merge refs/remotes/bitbucket/synced/master - * 6611612 - (26 hours ago) merge refs/remotes/bitbucket/synced/master - * 303895c - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 3f8c96b - (2 days ago) merge refs/remotes/bitbucket/synced/master - * f283e20 - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 96b920e - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 2c88b50 - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 5f6643b - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 7a2f5ff - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 3bdb942 - (2 days ago) merge refs/remotes/bitbucket/synced/master - * d24de2b - (2 days ago) merge refs/remotes/bitbucket/synced/master - * b29d45e - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 871adb7 - (2 days ago) merge refs/remotes/bitbucket/synced/master - |\ - * | 4138b01 - (2 days ago) merge refs/remotes/bitbucket/synced/master - |/ - * c754adc - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 587a56a - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 2d257fd - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 23018bf - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 9f202b7 - (2 days ago) merge refs/remotes/bitbucket/synced/master - * bdd40f4 - (2 days ago) merge refs/remotes/bitbucket/synced/master - * 146b1a5 - (4 days ago) merge refs/remotes/bitbucket/synced/master (bitbucket/master) - |\ - * | 3886b4a - (4 days ago) merge refs/remotes/github/synced/master - * | 5714860 - (4 days ago) merge refs/remotes/github/synced/master - * | 64325a0 - (4 days ago) merge refs/remotes/github/synced/master - * | f1b49e6 - (5 days ago) merge refs/remotes/github/synced/master - * | 17330c8 - (5 days ago) merge refs/remotes/github/synced/master - |/ - * 54f9a8b - (6 days ago) (synced/master, master) - * ceb8133 - (6 days ago) - * f36ae3b - (6 days ago) - * 6acdf4c - (6 days ago) - -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_16_cb57e3a438c115b59e4504d80e6f8273._comment b/doc/bugs/Assistant_merge_loop/comment_16_cb57e3a438c115b59e4504d80e6f8273._comment deleted file mode 100644 index 122d9559a..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_16_cb57e3a438c115b59e4504d80e6f8273._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="happening every hour" - date="2015-03-18T17:35:09Z" - content=""" -I've noticed that when this happens it occurs every hour, so it has to be related to something the assistant is doing every hour. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_1_ccf46511b924f86b488dba25060baa06._comment b/doc/bugs/Assistant_merge_loop/comment_1_ccf46511b924f86b488dba25060baa06._comment deleted file mode 100644 index c5f9c2187..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_1_ccf46511b924f86b488dba25060baa06._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-05T20:34:39Z" - content=""" -I am seeing some evidence of this in my own family's repo, where one node updated to 5.20140613 and started making series of empty commits with message \"merge refs/heads/synced/master\" and only 1 parent (so not really a merge). - -Quite likely [[!commit d6711800ad261fb4c37fc361bc84918d1e296bc4]] is at fault. Probably the fastForwardable check isn't quite right. - -This should only affect direct mode repositories. When only one node has the problem, it won't be bad, but if multiple nodes are doing this, their repos never converge and keep growing. - -Hmm, I think I have partially reproduced it with 2 direct mode repos, each having the other as a remote. `git annex sync` repeatedly in each does not add unncessary commits, but running the assistant in each does. In this particular case, it manages to converge eventually after several commits. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_2_afcbf3f8575e1a967c79693b94ef055c._comment b/doc/bugs/Assistant_merge_loop/comment_2_afcbf3f8575e1a967c79693b94ef055c._comment deleted file mode 100644 index eb3deb2ee..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_2_afcbf3f8575e1a967c79693b94ef055c._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-05T21:17:17Z" - content=""" -Well, it looks like this is as simple as the assistant trying to merge refs/remotes/$foo/synced/master into the current branch, when that ref is behind or the same as the current branch. Nothing to merge, so it does some pointless work and then the fastForwardable check runs -- and that check looks for refs between the \"old\" and \"new\" refs. Since the \"new\" is behind the \"old\", there are no such commits, and the unnecessary empty commit results. - -The reason only the assistant is affected is because `git-annex sync` already checked Git.Branch.changed before trying to do any merging, which avoids the problem. - -Fix committed. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_3_07341221b2839fdc1c43634e011451d2._comment b/doc/bugs/Assistant_merge_loop/comment_3_07341221b2839fdc1c43634e011451d2._comment deleted file mode 100644 index 1b6956483..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_3_07341221b2839fdc1c43634e011451d2._comment +++ /dev/null @@ -1,62 +0,0 @@ -[[!comment format=mdwn - username="EskildHustvedt" - ip="80.202.103.55" - subject="comment 3" - date="2014-07-08T08:13:40Z" - content=""" -I'm still seeing this problem in 5.20140707-g923b436 - - [0 zerodogg@firefly annexed]$ git annex version - git-annex version: 5.20140707-g923b436 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - [0 zerodogg@firefly annexed]$ git graph | head -n20 - * d4bf68f - (HEAD, annex/direct/master) merge refs/remotes/serenity/synced/master (3 minutes ago) <Eskild Hustvedt> - |\ - * | d03f280 - merge refs/remotes/browncoats/synced/master (3 minutes ago) <Eskild Hustvedt> - |/ - * e6863b8 - (serenity/synced/master, browncoats/synced/master) merge refs/remotes/serenity/synced/master (3 minutes ago) <Eskild Hustvedt> - |\ - * \ 616d985 - merge refs/remotes/browncoats/synced/master (3 minutes ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 3b39706 - merge refs/remotes/serenity/synced/master (3 minutes ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 6d354cc - merge refs/remotes/browncoats/synced/master (4 minutes ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 710c3c1 - merge refs/remotes/serenity/synced/master (4 minutes ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 763930f - merge refs/remotes/browncoats/synced/master (4 minutes ago) <Eskild Hustvedt> - |/ - [0 zerodogg@firefly annexed]$ git annex assistant --stop - [0 zerodogg@firefly annexed]$ git annex assistant - [0 zerodogg@firefly annexed]$ git graph | head -n20 - * 947f1a2 - (HEAD, annex/direct/master) merge refs/remotes/serenity/synced/master (15 seconds ago) <Eskild Hustvedt> - |\ - * | 19c6043 - merge refs/remotes/browncoats/synced/master (18 seconds ago) <Eskild Hustvedt> - |/ - * b453741 - (serenity/synced/master, browncoats/synced/master) merge refs/remotes/serenity/synced/master (18 seconds ago) <Eskild Hustvedt> - |\ - * \ 6baaebd - merge refs/remotes/browncoats/synced/master (18 seconds ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 03e4fa2 - merge refs/remotes/serenity/synced/master (24 seconds ago) <Eskild Hustvedt> - |\ \ - | |/ - * | 33302d8 - merge refs/remotes/browncoats/synced/master (24 seconds ago) <Eskild Hustvedt> - |\ \ - | |/ - * | d4bf68f - merge refs/remotes/serenity/synced/master (4 minutes ago) <Eskild Hustvedt> - |\ \ - | |/ - * | d03f280 - merge refs/remotes/browncoats/synced/master (4 minutes ago) <Eskild Hustvedt> - |/ - [0 zerodogg@firefly annexed]$ -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_4_7ae215b478843d2a8c705cac385fcf22._comment b/doc/bugs/Assistant_merge_loop/comment_4_7ae215b478843d2a8c705cac385fcf22._comment deleted file mode 100644 index 32468557b..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_4_7ae215b478843d2a8c705cac385fcf22._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="EskildHustvedt" - ip="80.202.103.55" - subject="comment 4" - date="2014-07-09T00:24:36Z" - content=""" -As far as I can see in my repo, the empty merges started on 2014-05-27, but then appear to resolve themselves after 40-50 commits on that day. They reappear again on 2014-06-03, and appears to have kept going daily ever since. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_5_11873461f093a266f0bb7e129bc21cde._comment b/doc/bugs/Assistant_merge_loop/comment_5_11873461f093a266f0bb7e129bc21cde._comment deleted file mode 100644 index 188317bb8..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_5_11873461f093a266f0bb7e129bc21cde._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 5" - date="2014-07-09T19:00:35Z" - content=""" -I have confirmed this is still happening, though I had certianly thought I had reproduced and fixed it. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_6_e7b6ecdd7e2b0222ea0baa0ed770e66d._comment b/doc/bugs/Assistant_merge_loop/comment_6_e7b6ecdd7e2b0222ea0baa0ed770e66d._comment deleted file mode 100644 index e408643ca..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_6_e7b6ecdd7e2b0222ea0baa0ed770e66d._comment +++ /dev/null @@ -1,80 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmN5jDf53oRJZsTo8Ahj2uXzCzq6HcvEro" - nickname="Gregory" - subject="confirmed?" - date="2014-07-15T01:29:00Z" - content=""" -I seem to be getting this behavior, in tandem with the [bad merge commit deleting all files](http://git-annex.branchable.com/bugs/bad_merge_commit_deleting_all_files/) on - - git-annex version: 5.20140709-gf15d2aa - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: unknown - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -Here is my log over the past couple weeks when I basically made no changes to the filesystem. - -git log --oneline --decorate --color --graph - -<pre> -* b304ad7 (HEAD, origin/synced/master, origin/master, origin/HEAD, master) -* 568cf6c merge refs/remotes/diskb/synced/master -* 5e426d0 merge refs/remotes/diskb/synced/master -* b2fa076 merge refs/remotes/diskb/synced/master -* b66a37d merge refs/remotes/diskb/synced/master -|\ -* | 910cba5 merge refs/remotes/diskb/synced/master -|/ -* 60736c3 merge refs/remotes/diskb/synced/master -* a957439 merge refs/remotes/diskb/synced/master -|\ -* \ 5c135c0 merge refs/remotes/diskb/synced/master -|\ \ -| |/ -* | 52d8b66 merge refs/heads/synced/master -|\ \ -* | | d77f3a2 merge refs/remotes/diskb/synced/master -| |/ -|/| -* | 03bb56a merge refs/remotes/diskb/synced/master -|\ \ -* \ \ bb000db merge refs/heads/synced/master -|\ \ \ -| |/ / -|/| / -| |/ -* | 3bc8520 merge refs/heads/synced/master -|/ -* 1c3ee7e -* d3b096a merge refs/remotes/diskb/synced/master -|\ -* \ 0fa0f6d merge refs/heads/synced/master -|\ \ -| |/ -* | 173592c merge refs/remotes/diskb/synced/master -|\ \ -| |/ -* | 3dd8086 merge refs/remotes/diskb/synced/master -|\ \ -| |/ -* | 68be2a1 merge refs/heads/synced/master -|\ \ -| |/ -* | bb304f4 merge refs/remotes/diskb/synced/master -|\ \ -| |/ -|/| -* | 1c9a2cd -* | 298b362 merge refs/heads/synced/master -|/ -* 4c23257 merge refs/remotes/diskb/synced/master -|\ -* | b709997 merge refs/remotes/diskb/synced/master -|/ -* 215f061 merge refs/remotes/diskb/synced/master -|\ -* \ e0f75b4 merge refs/heads/synced/master -</pre> -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_7_7717d074611943b831f00ad10918b515._comment b/doc/bugs/Assistant_merge_loop/comment_7_7717d074611943b831f00ad10918b515._comment deleted file mode 100644 index 9c70f2646..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_7_7717d074611943b831f00ad10918b515._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 7" - date="2014-07-15T19:15:13Z" - content=""" -This bug and the other one are fixed in 5.20140709. I assume that your `git log` dates from an earlier version. -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_8_5ce91ac76498539ada344d1639984302._comment b/doc/bugs/Assistant_merge_loop/comment_8_5ce91ac76498539ada344d1639984302._comment deleted file mode 100644 index c12c84264..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_8_5ce91ac76498539ada344d1639984302._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 8" - date="2014-07-16T13:42:16Z" - content=""" -I'm still having this issue in 5.20140709 -"""]] diff --git a/doc/bugs/Assistant_merge_loop/comment_9_b09a5eaa2588559e19b3549bd3c8b496._comment b/doc/bugs/Assistant_merge_loop/comment_9_b09a5eaa2588559e19b3549bd3c8b496._comment deleted file mode 100644 index b6bfc68eb..000000000 --- a/doc/bugs/Assistant_merge_loop/comment_9_b09a5eaa2588559e19b3549bd3c8b496._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 9" - date="2014-07-16T18:08:26Z" - content=""" -Are you sure that you have upgraded git-annex on every machine that uses that repository? You could have one old un-upgraded one still causing commits that would of course be visible on the rest. - -Also, what version exactly does `git-annex version` show? -"""]] diff --git a/doc/bugs/Assistant_removed_all_references_to_files.mdwn b/doc/bugs/Assistant_removed_all_references_to_files.mdwn deleted file mode 100644 index 4014bc729..000000000 --- a/doc/bugs/Assistant_removed_all_references_to_files.mdwn +++ /dev/null @@ -1,1305 +0,0 @@ -### Please describe the problem. - -Over the last few days, the assistant has recorded commits which have removed all the files from four (which is to say: all) of my local repositories. Two were direct mode, two indirect. All still had the actual file data saved still, so switching to indirect mode and reverting the relevant commits restored all my files. The two indirect repositories are synced with each other. - -One of the direct repositories also got all of its refs scrambled, pointing to objects that don't exist. I reset that one to indirect mode, found a valid commit from a clone and reset master to that commit. The other I've yet to work on. - -The iffy commits appear to have arrived just after the assistant auto-updated to 20140708. - -### What steps will reproduce the problem? - -I've not tried reproducing it. - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140708-g42df533 -Fedora 20 -I'm letting the assistant auto-update itself. - -### Please provide any additional information below. - -Here's a log for the indirect mode repo that's synced. I have two commits at 18:56:43, each removing half of the files. - -[[!format text """ -[2014-08-30 18:56:40 BST] main: starting assistant version 5.20140708-g42df533 -[2014-08-30 18:56:40 BST] TransferScanner: Syncing with apollo -[2014-08-30 18:56:40 BST] UpgradeWatcher: Finished upgrading git-annex to version 5.20140708-g42df533 - -(scanning...) [2014-08-30 18:56:40 BST] Watcher: Performing startup scan -error: Ref refs/remotes/apollo/master is at cca3ca9633a98af7af4e029199b31768925298ed but expected efb22a8c5ff1c116ce43d99156112d4cafbdf967 -From apollo.aylett.co.uk:Annex/Family - ! efb22a8..cca3ca9 master -> apollo/master (unable to update local ref) -TransferScanner crashed: /home/axa/Annex/Family/.git/annex/merge/: getDirectoryContents: does not exist (No such file or directory) -[2014-08-30 18:56:41 BST] TransferScanner: warning TransferScanner crashed: /home/axa/Annex/Family/.git/annex/merge/: getDirectoryContents: does not exist (No such file or directory) - - - -(started...) [2014-08-30 18:56:43 BST] Committer: Committing changes to git -[2014-08-30 18:56:43 BST] Pusher: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 6924eb5..a13c0cd git-annex -> synced/git-annex - 5f56a47..972c8da annex/direct/master -> synced/master -fatal: Run with no arguments or with -c cmd -git-annex-shell: git-shell failed -[2014-08-30 18:56:50 BST] RemoteControl: warning Remote apollo needs its git-annex upgraded to 5.20140405 or newer -[2014-08-30 19:56:40 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 6924eb5..a13c0cd git-annex -> apollo/git-annex -To lizzie@apollo.aylett.co.uk:Annex/Family - 04e7150..9095d13 annex/direct/master -> synced/master -error: duplicate parent 9095d132bb1bd6f03ba4494bcccec6973a322f1c ignored -[2014-08-30 20:56:42 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 5f56a47..9095d13 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 9095d13..1a1d324 annex/direct/master -> synced/master -error: duplicate parent 1a1d32492a093c00c7386de55be3fc25a9a56187 ignored -[2014-08-30 21:56:43 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 9095d13..1a1d324 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 1a1d324..225e820 annex/direct/master -> synced/master -error: duplicate parent 225e820c9e27db3d278101519932dc5c8b62b64e ignored -[2014-08-30 22:56:58 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 1a1d324..225e820 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 225e820..205376f annex/direct/master -> synced/master -error: duplicate parent 205376fa7f5027653ae3a0bd177562b033b2c06a ignored -[2014-08-30 23:57:05 BST] NetWatcherFallback: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - 225e820..205376f master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-30 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-30 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-30 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-30 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-30 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 00:00:00 BST] Cronner: Consistency check in progress -[2014-08-31 00:27:29 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 205376f..b74eb7b annex/direct/master -> synced/master -error: duplicate parent b74eb7b1ecc520850efdb304ba995b14b124692c ignored -[2014-08-31 00:57:29 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 205376f..b74eb7b master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - b74eb7b..cb1254d annex/direct/master -> synced/master -error: duplicate parent cb1254d5ab344a250675fbdaf5dec942636f6026 ignored -[2014-08-31 01:57:31 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - b74eb7b..cb1254d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - cb1254d..8ad18dc annex/direct/master -> synced/master -error: duplicate parent 8ad18dcdf634a6c2aae224575b232c99c5b92a7c ignored -[2014-08-31 02:57:33 BST] NetWatcherFallback: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - cb1254d..8ad18dc master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 03:27:55 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 8ad18dc..868ab0f annex/direct/master -> synced/master -error: duplicate parent 868ab0f36977fb70ac2c8ddda86391289b6b0a3c ignored -[2014-08-31 03:57:55 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 8ad18dc..868ab0f master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 868ab0f..1eea08e annex/direct/master -> synced/master -error: duplicate parent 1eea08ee2340ccceb7554f8dd8fbae28edd0ee49 ignored -[2014-08-31 04:57:56 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 868ab0f..1eea08e master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 1eea08e..b542ca6 annex/direct/master -> synced/master -error: duplicate parent b542ca6756ba13377efa8884453c82eba71e27e6 ignored -[2014-08-31 05:57:59 BST] NetWatcherFallback: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - 1eea08e..b542ca6 master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 06:28:01 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - b542ca6..0de348c annex/direct/master -> synced/master -error: duplicate parent 0de348caffaa453ce30e72ba2e240d8bbba34337 ignored -[2014-08-31 06:58:01 BST] NetWatcherFallback: Syncing with apollo -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -gpg: Signature made Mon 18 Aug 2014 20:14:04 BST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -From apollo.aylett.co.uk:Annex/Family - b542ca6..0de348c master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 0de348c..8467b09 annex/direct/master -> synced/master -error: duplicate parent 8467b0948d5e6e3dfb8375c4e84e7770ff9798e2 ignored -[2014-08-31 07:58:04 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 0de348c..8467b09 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 8467b09..3a56258 annex/direct/master -> synced/master -error: duplicate parent 3a56258c6b5b9551a61756c97c563720c87bf692 ignored -[2014-08-31 08:58:07 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 8467b09..3a56258 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 3a56258..122eb0d annex/direct/master -> synced/master -error: duplicate parent 122eb0dbc0e863d4f044a5e0c6eccd4f39dc6599 ignored -[2014-08-31 09:58:10 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 3a56258..122eb0d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 122eb0d..46fbb4e annex/direct/master -> synced/master -error: duplicate parent 46fbb4e5a9d330cbf2fe68c329cb9f10bbba38d6 ignored -[2014-08-31 10:58:12 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 122eb0d..46fbb4e master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 46fbb4e..cca5e72 annex/direct/master -> synced/master -error: duplicate parent cca5e72784496181ade94e702533aa5c8e741309 ignored -[2014-08-31 11:58:14 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 46fbb4e..cca5e72 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - cca5e72..20f0c9d annex/direct/master -> synced/master -error: duplicate parent 20f0c9da173562c13c4bf109333c9f9787f3a23b ignored -[2014-08-31 12:58:17 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - cca5e72..20f0c9d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 20f0c9d..3c9eb47 annex/direct/master -> synced/master -error: duplicate parent 3c9eb47d6ff77f1f7949b64e10d0378220ea95b7 ignored -[2014-08-31 13:58:19 BST] NetWatcherFallback: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - 20f0c9d..3c9eb47 master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 14:28:21 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 3c9eb47..87cbe02 annex/direct/master -> synced/master -error: duplicate parent 87cbe029cf1b65809cadf6067e9cdbd4ba695118 ignored -[2014-08-31 14:58:21 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 3c9eb47..87cbe02 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 87cbe02..71238f0 annex/direct/master -> synced/master -error: duplicate parent 71238f04ff0429c64d3f3bb24116860e0cc80129 ignored -[2014-08-31 15:58:23 BST] NetWatcherFallback: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - 87cbe02..71238f0 master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 16:28:31 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 71238f0..600343d annex/direct/master -> synced/master -error: duplicate parent 600343d16d98bb7dd84ffbb1e2c8f27a49bd0bfe ignored -[2014-08-31 16:58:31 BST] NetWatcherFallback: Syncing with apollo -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 17:28:38 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 600343d..50a6288 annex/direct/master -> synced/master -error: duplicate parent 50a6288026156f5956291ad1100bd420fdde564c ignored -[2014-08-31 17:58:38 BST] NetWatcherFallback: Syncing with apollo -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 18:28:40 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 50a6288..5b1813a annex/direct/master -> synced/master -error: duplicate parent 5b1813a8dbbd7ea4b17e230e927419f1d3230534 ignored -[2014-08-31 18:56:40 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok. -unused . (checking for unused data...) (checking HEAD...) (checking master...) (checking apollo/master...) (checking apollo/synced/master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s1103321--51418dc7fc654ebbeb9173bff598b4031d07d3c5cf651bd18a18ca6af9f7f1f7.jpg - 2 SHA256E-s3754--39631a60a771a00e88ef5ab011ab3f56fa8e539619b06aa68e66f2c71f252f9f.png - 3 SHA256E-s628641--2eeef2179787270c6307e1070678b6b27cbf0fe12cce71c136e0a89e1df78565.jpg - 4 SHA256E-s848--66e696444c6e570fc00d79f6651018d7e6549585e587394b933dcb0d74d8c214.js - 5 SHA256E-s21214--f26fa07b51fe0f4c5bc0d746f8b23e50115116bbcd80db057740bccb9841e4b6.png - 6 SHA256E-s852198--9fcc545c030c268d660381fd33d66b06605f7c5df16dca0b3fbe4eddfbf6b339.jpg - 7 SHA256E-s1334033--d6e722f76229c10ea6a1ff8dce2814ee42c92b643a19ec3f4d72222e1891c210.jpg - 8 SHA256E-s664656--85aaeced38501abfec6d23591edb07d7ab98bbe303b98eb07cfa0577ec8309b2.jpg - 9 SHA256E-s3213396--90e4ec9054de04c2b2c60a49b812582ba15c8da00208c9fc74acbc69b83182dc.JPG - 10 SHA256E-s820026--c1fc64d12cc74f60f8d17302a95217978782ea99758bce99ea2233709be60a6d.jpg - 11 SHA256E-s622679--5e8412b3955db206c6836fbd5731b0ab835aa325fc75bc7d75d4511ddbf67644.jpg - 12 SHA256E-s917793--7f2ecba64196449b9d7f1ea79e07f496d90d59c59d12472d058566a0881a5c6c.jpg - 13 SHA256E-s3493204--7ce9ad40b32b5cd1237e5efbb8f6885f7d734f8af65da8d0e92dc2de13162e07.JPG - 14 SHA256E-s910114--be8d66d9261108572efe0266ae386fefa653cea4ef43be9fbd10f7e2fe8d1c4c.jpg - 15 SHA256E-s636389--07b609b0cbf827a45cff2ca92367f3c5bf9a9527d4b3cb43961487bca8068ffd.jpg - 16 SHA256E-s823401--4cf12d87a9034d34a3019b5002000c92512f901a82f1081705c12e73b5870bad.jpg - 17 SHA256E-s1880--add7e1d7d7d98ff96afaec27bb066d6747551358e025176265a31b2b0f74bec0.log - 18 SHA256E-s8784--e28377207d41b4fef538b2fcbbd25c05275103a299e74966a88dce53ad5f50c0 - 19 SHA256E-s8694--490b9f2f9c4c826b68bad68a50cf672ec36c58acb9e24fd46e84abaddec19b9b - 20 SHA256E-s2656--96dd5f3d5f8e87ce1552798dd5fe4c8dedab6268c0df9e391a202ffdc4b8fa71.log - 21 SHA256E-s459593--b68a62596f7524b6f877d8bd3dbbe49f4de02310e9dd6d5134bbdabfcd5d957a.jpg - 22 SHA256E-s11931--5ce30bd4424d544ed954e4722d7ed590a5be46a267c5045953e034309d942a8f.odp - 23 SHA256E-s1249581--d834f2dc34ded72086e26c32784e693597be011f28398635286394c7e8b5ded7.jpg - 24 SHA256E-s335736--9638a3225f1adbdb736a2cacc476f8eb5201c8124b83dab887a26c6d3a0e5899.jpg - 25 SHA256E-s6339776--f42083be1dba62acf81ad5ee8bccad47f267e2ce34c9e73e9aaafe3c69b462bd.pdf - 26 SHA256E-s582899--858ad02a9e5f58a6f5ea509865831acd540c290837beb87b37cb36bb62a7b982.jpg - 27 SHA256E-s2475657--d3fa5e460a2b164e849213d0417790704d1b4a2df9af5f6b281ac17dbacad30b.jpg - 28 SHA256E-s637475--68315445dd9477f07a695cb9fd12bb2c95f3117d949665ec2690184ded6b1ee6.jpg - 29 SHA256E-s77771--484ed3d8cc44de2db74c5680659c5c23ccb29ed5e99d0fb4b470a2c130c64c79.pdf - 30 SHA256E-s2343639--a7fccfe9a2c8de20ce8df10048b075758c445e5f4c9d9b78368db179e74e9a47.jpg - 31 SHA256E-s2282836--66e945f3a37651e1c88c58ff42b4dba9c6c5d822dc59f3e59895c336a0428c3d.jpg - 32 SHA256E-s5902--da66d622f9ed0987a0466c2c05c2aea56572e2f991c542b1120d564fb7459e7b.log - 33 SHA256E-s61410--4d3f0160bc92d0095a824baa17a08499dc748d06648029051802d24a772ba75d.css - 34 SHA256E-s1958077--1717f3036e7ca6b61fe8eeb3ce319de728b9bea10fd814108b9e13397a336db5.jpg - 35 SHA256E-s80930--f9b79963053221a10e32c4061b9da3622e89ce56aeed26c58f23bb70a2a57496.jpg - 36 SHA256E-s4956--a05854e0d26affdbb3e171c8e9ca3f663c8bc930f6402d9a370104e239bc2601.log - 37 SHA256E-s202851--3689503ce6f780d04e659fc85e4e7978c3c445afbd103f3ac118e1c6f3a4b738.jpg - 38 SHA256E-s5258--a243d289f629eb2e321c7232aa59c65d10ec79e70d07f25758ac04c0b9ff3f79.log - 39 SHA256E-s5406--dc07212d5aaaf5a320b3f9d710a72b68f7112140c76b43b7c0b4bb71f91e823f.log - 40 SHA256E-s8427--439c4f2144c9ea726b739494565b05dc47b59a8835e24e9a083171efc0834fc1 - 41 SHA256E-s46--ca4a766fadecf16bbc25afbd805e2befbfb4cb270f122b0de813fbcfc933c1a2 - 42 SHA256E-s839129--921ddf15c906a0353cb18bdd0b321bd5a37dfe653edbffc8e3b6b47996d54d8f.jpg - 43 SHA256E-s2922183--3aa5d5b22a980a11cee928ba701ffd389542db84fe96219442de1b33a64f840c.JPG - 44 SHA256E-s1305363--0b14938c28492e288d35a62334d6436ba8edfb7f65a066dbd9587478f157ab99.jpg - 45 SHA256E-s8602--819b18ca30f477f66e558ba1488a06e438a5f0b9c8f6987f68daad039d8020ca.png - 46 SHA256E-s6205--14691e198b05dd68b5fe3ed39eb8739182f4f5e75dc43dd7ecb252f01978c7ed.png - 47 SHA256E-s5070994--d0c5367647750b1f0b54c9fea7c7c9e1a0f7a0a7f61c92a688887538df3abf7f.m4v - 48 SHA256E-s134807--7100078e84c39a2123c0ea7d713e3361c7174f21fb72d39dac2a99a4844f89b7.jpg - 49 SHA256E-s535905--f317f11e4e0536ea8172e7827369bd9a3c887fcef2586b8eeda28b2dd36a791c.jpg - 50 SHA256E-s6420--72622a4453f4ea48acc0337bb1b288e0fb034d1ee1aa74f98eb9062066c025b5 - 51 SHA256E-s51483--c9fba5eb0b29216afd9b6f13dd2f351367b7bcd0c8eb93fa0a1b6a0ce4535d57.sla - 52 SHA256E-s1957447--c3eddff4df50e1b0c5dc93f85e39acd24723013dd9b27b7b8a407eb5e55f1903.jpg - 53 SHA256E-s5345--ee879c6bc3c3ac59f449a9d9f92ec9cc2d15dced1f166805a179b6874d190c25.png - 54 SHA256E-s153751--c3fd0000f94ff9c44fef856ee440837fa4c228918ae70d0813d1635d50e6d4a0.odt - 55 SHA256E-s682324--33a6a1b34570f9abe0516d9abceefe14aae4cdacc41dc3f30ca92222d545631f.jpg - 56 SHA256E-s370109--a00b1c78753de6ae1d64a01d457b53a3572a9324a0facda4ec39a149d9adb37b.jpg - 57 SHA256E-s310217--aa0c575a44cac4957e06cd8ed0b058a16454a7be7f32ec8e79c815be6057bfbd.jpg - 58 SHA256E-s5798--61852a3ad168d4f27fe0f0e924e7418e838ae4363d85a64ebea80c9154e0c9a0.gif - 59 SHA256E-s47071--f1a74e5f9a20776adbe88ac3092e5a20a69d254905c0f93aa0b95a1ad0a5ed00.sla - 60 SHA256E-s988--b1f5fb3d38001b8bcf214158c6c7571f5aadb03093d2c307970a728edcb8012b - 61 SHA256E-s1397011--b67c04c6c99ccc208734dd39e18d4304a4963ef36600d4adc5827df21bfcc260.jpg - 62 SHA256E-s2124--1c64d2a60a40242432550ab3292e1ee38072481c36b8f028f75e3b4ea52fec29.log - 63 SHA256E-s1640512--ccb4940713e190a9242b34e18896156733f36df909c7e399bfdfe36299bfa748.jpg - 64 SHA256E-s484856--55f146177198dcd03069703c7b8bdf5c10cd7750aaf4b6f9af1946d72a9f9d23.jpg - 65 SHA256E-s7031--88bedea3e75aff77858c63a6c30bb06180bd9167fd380d94f132486d6ffeddf4 - 66 SHA256E-s10100--1df9143f4c02f877ec891262bcbc407a9d4b960dd80c6826d5c1078012dc2614.js - 67 SHA256E-s2454--778574fe7cae3bfc2a49cbe3be18ed313b049b6e0bc333cea80723ae2136f9c3.log - 68 SHA256E-s63103--474c29d016927bd7dc42d992fc07c353148d393cfbd7c3e8193df91c3bb2d805.jpg - 69 SHA256E-s245481--ba0e9ed8876970e0aad7e22aeaf4f7403e1ef6fca474e0b4e90837381c0b810f.js - 70 SHA256E-s708--ab8f3c450c5c8944d6d91c35258b9da5ff4564b9b05b1e09ebbaa9b740d14aa4.log - 71 SHA256E-s582241--fb565e6fa923f3265a9406abf566d5de7a8e062b1d9ccb8ba7ec61a902ea277e.jpg - 72 SHA256E-s601517--fd4a4effd6c6b064be34910b36f1de8011bb3949d0f883a57ed4ca60eff6a642.jpg - 73 SHA256E-s613354--0d78d51b5047055d9bd2727e01a7c73ec25bcb99925be26550f3b921054e336b.jpg - 74 SHA256E-s20794--0ba2f6756001669bdf934f9d79e8fd1ccf2028130c33a0510279581ec9dfd73a.js - 75 SHA256E-s654750--be05edd69e61fb5ebecbddc8c39ae9ebdbca5e94ee395f604bbd73910a7e40f9.jpg - 76 SHA256E-s440--4e8500857e2b6a08a6922ca852ff4c9702e2397843011a14dee43d6e20c4f787.log - 77 SHA256E-s72381--a170eff1ba771b3e4e769ab2974b8fb1f66cff07bf8b19561a97f9d7767b565a.jpg - 78 SHA256E-s344661--21564a2da0f6b1ea6c4a39f4a96ba02680facb9d8a084d4fffa28b0e527c9fc8.jpg - 79 SHA256E-s51248--f940d364ad2583a9ae3c0f777fd61406914daa1837ed8dd78f3461760c4ca747.sla - 80 SHA256E-s502234--251053730579880833dc12058a6c689ba074f0a981331ec7eb685b69f08e292c.pdf - 81 SHA256E-s3682--f75a95ae16e2f8a8e0a607782cf332dc34c1e317d473023cbd7f9915fa400d62 - 82 SHA256E-s3544--9b40beb44b624520a74057a82ae5e6adb18601e6c1fc7d8496bdd59e3b248945 - 83 SHA256E-s355156--7056bee290696e681cd3538e2ff2e740842bce032effe509f0919e888cc03ee4.jpg - 84 SHA256E-s879539--12cc34616b2dda153890db0a724290fa01bd9dd664061a05c8d2c1039cd4cc3c.odg - 85 SHA256E-s2051310--69387e84897ed700b6dd7c418fc3a7884a1e6e16a4267297b3effb95b02a7bc7.jpg - 86 SHA256E-s620--eb69406700a3a6122cb532614f4ae6899d97409d76259820176f7ae77158684b.png - 87 SHA256E-s693427--e20c50c86937800b14e2773d79eb63d13c0300781f8e71ee3947fb5a2fe98fe5.jpg - 88 SHA256E-s87985--b89b279ca5dede3643e8a48402e9b112b1e1fdc14b3326c98cbdb32f9f7fa2cc.jpg - 89 SHA256E-s35739--378d1bcb19c2742b8d344459a74f9b4ea44287c4e5cf046b80a46b209ea1ebbb.sla - 90 SHA256E-s51515--d4805b60c6e0ea396dc157ca0e399ba355482f2a9696f31fdcf819aa176ea3e7.sla - 91 SHA256E-s396738--5e18be640581ced943a676323c80dc283b15d3caf37b2bc2d0b05ceee1d178e5.jpg - 92 SHA256E-s334295--7f97df9f93e42a2db9e9efb0aa34a2a9a6b9af49846e6a73f320ee151d535eed.jpg - 93 SHA256E-s425513--0f6228a7466c12d1d0e4beda9825f17442b15286a5639e3a894a36d33497c77a.jpg - 94 SHA256E-s114076--6a1822942964efa5531de2cae48d3fd69e71baca7ade38b7cbe23964637d4478.jpg - 95 SHA256E-s118034--a8b1e6f81534106e9f4563dfe3f288e9425284fbaa74247065cf80448cdb216f.jpg - 96 SHA256E-s639--4b491df2b47c2fd4dcfbb99b50ec1367e138c61216704490ada08cddd0d32fda.css - 97 SHA256E-s734079--0602d1c85bca8508010ed03c2b1c26c88a8c759783f49d7f7b282b30837c6b32.jpg - 98 SHA256E-s130889--751d2fa73ac74e17d2e82fc9a89b3d393028197790657aa075effc7c16b8f528.js - 99 SHA256E-s485283--63716cdb8953a9318eb28953af25db2afa02251e6f152d487f5ab05f1d27930e.jpg - 100 SHA256E-s59518--6a80f10665ad39dc27ee3a5727ebeee321a289dbc958916f9e6eda01f2703d25.jpg - 101 SHA256E-s194--4c0fc707f629bcb314433fc700c6090c970d343adbb921f46084bdb08f99cf6e - 102 SHA256E-s303--07ae4fec1962f2f83808ec861e477d5669dd71ff1089cb25a0e1da7b3ec9a5a6.css - 103 SHA256E-s24519--3f3cba473c1818b2ce46a034fc323d528df85dd88d3f2ed411ad644a08ff9132 - 104 SHA256E-s316292--691e653f57643e579c261a827441e63ee3d8cf1f9ed5cdc43d861cf340510d34.pdf - 105 SHA256E-s11916--88e5b1e2f5bd0f5c458abb41589028ef35dc75872abd7e04eee4a12ae7bfef38 - 106 SHA256E-s733240--fe7b7c77712b866c932d391f8305560d488d0e5515f3d9c890ddd11c96ff6069.odt - 107 SHA256E-s4323950--c71e34a9fa2d1f54934d3caf829e4b5330811c2937d523f856d43cf5d92b7275.m4v - 108 SHA256E-s475740--e2d4880b8561167dd91b57a666f3eba68931ae3546231d102469c76d341f560a.jpg - 109 SHA256E-s574--5d1bd8763457376e0ff677895456f9aad26b6d85e15648696e9f4c77af104fee.png - 110 SHA256E-s11608--f815f1bad38a05f27b1f7cd416236148fa79554ed2546a014afe148c0e427839.log - 111 SHA256E-s3300--7164c4d91218528eedb0310af14927d4ce483889b53da24fdcc01fadae107fbd - 112 SHA256E-s962958--9a81dba98b0b910641d035bf662b847fb4785ef2378bef7b2ae6713b1fbd903c.jpg - 113 SHA256E-s845627--09f3e811c372a7ee936064d4c48c8b4f36db519a49a0b274f69e3da12a0e2ffe.jpg - 114 SHA256E-s2380622--05725288b66460ff1befda38280dea4d05c5dff42818de7d64e619e12aebeaa0.jpg - 115 SHA256E-s62795--a32762ee80e176ca1d7869cd5f68e7442327e1a861ed70290f2256179ebd844c.js - 116 SHA256E-s3486--f148d21e252ab05ff7039fa276ee309e6d16d2ba7444043acc148b9986164162.log - 117 SHA256E-s2393747--1ba6fc7f4d47ced145ceab80128e3ceaf8cfe8f2155b5e33e9273c736a81b910.jpg - 118 SHA256E-s4611--bbc334899e27d8fe781f61e06be1c28852e618d1e2bd8b98de0aed7fb6106ad8.js - 119 SHA256E-s826134--426211e056784356538d3ac80838e197e2cdf29742cd31db6a386ce7c05aa052.jpg - 120 SHA256E-s1072403--87da8298b8c3c76bdfb8c96ac7dcb11349763067056eb0e1fadf5241fc134141.jpg - 121 SHA256E-s51028--d6d044282ee1d1d8fc02130ac42ab1d7ee3a6a7e2987b78bb1062529019cf3e5.sla - 122 SHA256E-s45783--35b9963b4a8bc3dbee5bbe827c2e18c795b8fce86bb1eb87c6b3b09327380f1f.js - 123 SHA256E-s999195--c0fa3d678c9ebe118ea3fb1b664a2f63ccc792a7578fe921d0c299adf40d97f3.jpg - 124 SHA256E-s96828--c5ebf871d1c98e5f49d15dc22131e483b514754ad86c6293c69b6d5aa3d44cf9.jpg - 125 SHA256E-s159835--47a9ba3de62d6a4b11dd59a60b0047d3d377c224ceac85bfb6a81a972f25fff9.css - 126 SHA256E-s9629--588e723593992acb553dd4f2c76a6993135b4f49e674358fae63ff06e145f07a - 127 SHA256E-s39867--6e96f4658811bba2f27f930f764111501e438135d793e28fe7eacb6b10866e0d.js - 128 SHA256E-s62332730--a2c804ddc66d8175fb5e187d17c904954f1e2cae634c4604ac363eb97d78f7e1.odt - 129 SHA256E-s1711933--dd49df68da23021d3e9cc775e86bd5341dda6ba71714c8287872deb9416e051a.jpg - 130 SHA256E-s290639--0803de7a02e9a4a1caca69b2a7b2c948e7faf2e4ef2bf3bcdaec148c0f26b842.pdf - 131 SHA256E-s5799--fa90e9a478760bc12c2707962f2ea6b9ab213bc7d4b158f28f6739727ffe05e7.log - 132 SHA256E-s11156--17ca703a57e9f02ebd71251ca8bdb6d82b71fa586deb034cd384b21a3818035a - 133 SHA256E-s16171--47a7946e6364fa5ad3dc595105c79a4946f18cbef0818e72682d9304625ceab9.odt - 134 SHA256E-s1962015--2eae4dfa79e014bf4468141bfac8c0065d1b05f2532758c6e68deedd297f22ee.jpg - 135 SHA256E-s31268--560829df213299f5db9aeb0b31b40044300c34e92818680f422d0ddfe7602f2c.axd - 136 SHA256E-s145407--c34c44643d9d0f7114cce8b31f3442a7b6392c4687af9ab97995bd30ddd3167c.pdf - 137 SHA256E-s1773--8417f863ffa4a076dd2d8b5a63170bb0c5b83cf275d72245a79c31d94358fd20.log - 138 SHA256E-s701838--3d7abfd8b091e4da1bb61881155c299b78ed693f128f1c693c7970bcbce4e8e0.jpg - 139 SHA256E-s2089502--f4c9ec5dce63924cba6f77efd5e20b17cfc0f3c9ae45dce7bb0ecc5a10986205.jpg - 140 SHA256E-s1085890--0346c7a329e7b80c7f93b8aa7de039bf322070ebac33cee6ade6fcc4a4f296be.jpg - 141 SHA256E-s3998--e38f3a315b698a0e8ccfa395431393af757f882413cea8b4879b5b5993543f86.js - 142 SHA256E-s7372--181699a3ca4be8bb0e9913fd96dc5c44ed8a790ea6ef2bb0fb285e741f2c46ab - 143 SHA256E-s864279--364b4a4d0a30ddbf1164d5d3ded0702a4b016ffc27d26eb6005d96e68aa4f77f.jpg - 144 SHA256E-s2941--7ca4f001618fda61146802286daf472c5daaaded2471e356a752b6a69834e7f7.log - 145 SHA256E-s153049--5805df5cecdaa15a549bf7751b1d66f7455e71e2243709d9799f839e42d082f2.jpg - 146 SHA256E-s542959--5823d605d7258bd813d09712fd124fd7c63f2cbdf46a9b52c3eb67eb7bb538bc.jpg - 147 SHA256E-s45282--b20a77431de35f8e70867cfe520503528fb948d63f724ed90fc249994875b77a.jpg - 148 SHA256E-s19556--e5bdba04d2a9d805c491778a742744d3007d38a23c9dc11cf8f6eab7b2dd0a1d.log - 149 SHA256E-s392108--c9c76c131588fc29d588afed12d98b6b3a6aa0a9971ad368112bc0c2a603e70c.pdf - 150 SHA256E-s8275--ff63b5b012ea62b178310424d817a8a77fb31151dd697659f85f23a6298cf28d - 151 SHA256E-s1769251--7d0a2ec1652f1287884f6bd4e0df14106af271e81fc38cae5aac1357966ea672.pdf - 152 SHA256E-s464748--aa63c72a4b064f91083228395e1391d970873ad1370900a468db154ed266d475.jpg - 153 SHA256E-s6130263--3521b18281dba779713e600fde1a4d15568328baad6baf43cba1530df7165c5d.JPG - 154 SHA256E-s494260--aeb91b314f3dee3580093e9610dacd5917265794b49acea9d80dfca83d56b88d.odt - 155 SHA256E-s3362329--05fde815df42455fdc1b563ce41bf13d585135da628d01c5ffc9ca627c008225.jpg - 156 SHA256E-s489239--d2ab01a94808613489205b7aa5d666cccfeac0a28b5a76ab18fc9fd9435dcabc.jpg - 157 SHA256E-s482249--e4979b950d4633515316102d934115b1981c8adf5a14ea80bfda87e623af7989.jpg - 158 SHA256E-s93506--3f44779fc3ce611f607c9cde2c114f6f038775485a677e17bcb6bb034e6ac888.jpg - 159 SHA256E-s818--66d21ef5da07cc00768b23bb711ccc8e18b91c99ccad2084ec309f51e6c52db6.log - 160 SHA256E-s171892--33f34e7d16851c2291d7495754505d391be4668883b43e4b9e587126c693b1d2.png - 161 SHA256E-s278132--fca8b8bbcc0f9fe8addb57994c69a9c511b206c27424491809ab31aef86f21b4.jpg - 162 SHA256E-s2418631--deb0aadf97aa49010ac3cab5f5299e2d68eeb5ecb4dd5de93316f23a714734f6.jpg - 163 SHA256E-s125121--2b2cc905b8c05d4c7253a9c2b45a961df545842e4ce9d17e5248aa6240e77557.pdf - 164 SHA256E-s199793--615ac75e6766d637d17159ebe3d48eedf27096e93b83efc159431da4d032e21b.axd - 165 SHA256E-s223221--ca5f5160688546f422cf7d041e58f07d5d90e8359666e523a5af515baf0b2980.jpg - 166 SHA256E-s1959724--2e44ed4b10ab3c1655b16335b901547713ac8d5c38d4ed3735bcbabb272242b5.jpg - 167 SHA256E-s11609--df8dcf81585eccae95b7c4f0a0ba8c6fc4cfe90ebbf9657bd6a10320f7195e61 - 168 SHA256E-s483419--96cfd3b43e5b7bb1d6a5bc3f78d33e873fa36ee6e53c9f1de083f279c19c5f70.jpg - 169 SHA256E-s560766--96f47b698f6502bc758e6d8b9b538368f8085d040306388bfd42d3026c465ff5.jpg - 170 SHA256E-s3848--4d18299f8d8ef1bfbd7b206d419ef6f65cbd09a3ae999f3c7cc8496051b34080 - 171 SHA256E-s1141493--80b7a82ee4edc420c538c4a2a37fc9d80cce4c321f5a9a7fa7e66df0c9e3693c.jpg - 172 SHA256E-s9726--14b5e76da3417f5f25f48c2a793aa50da9c920451495af7612b76d3c052d3f13.odt - 173 SHA256E-s939529--43d05562e75f2477aa6d412d8a672ce7b6cf2890d4e1578bf88692aabfd0e70d.jpg - 174 SHA256E-s888147--948ca59b827f77f75ea981b149a72df976aea360cd263d0f7c03275375a47232.jpg - 175 SHA256E-s740710--f1e98c032815161aff44c8ccbb882af5cb234f91c4430cf91d01115649bc9aa5.jpg - 176 SHA256E-s961257--e6b21901e268f6d0f3a38b43e5a06d8ad9ec0901f4c9639954da7ecf2ee4a666.jpg - 177 SHA256E-s616645--bd10a26926e6cd0fd0ee6cf72692c92134b183927280a00a74e869bbeae8bde6.jpg - 178 SHA256E-s47996--f862cbc7bea6fe4b5fe3a3af2b393973220a34975dd36a9d5f92b30d1db80acc.sla - 179 SHA256E-s2396909--2e6d435cf96f81a3f3247f2d35b01701f8a46977e813745324ca5b40717fdea9.jpg - 180 SHA256E-s180605--66c6df69bba4602100148ffd0f0a0ba0a14b74eaefb3b27708c6792d2b5cd09c.jpg - 181 SHA256E-s721289--159f9398adde99e23b05c8c8c99aadd98b6a3a80afe5e3745ff37b0668fe4a24.jpg - 182 SHA256E-s95559--0d932a11d465d523f85b17803d44fb0748459771b2cd843dbcfd677248abb0f5.jpg - 183 SHA256E-s368166--98be96450123c166cf11f1763aa25040ffb1674f7267a4041cc1a4fbe8e433a1.jpg - 184 SHA256E-s846--b3c9f5697bee76715237040d6ba5ff9f657dee2d882e36d818ed2ff50e8e0835.log - 185 SHA256E-s581051--217882c3f655c62dd323afe0689c9485d0d09430d5356a63105632cce08ea88e.jpg - 186 SHA256E-s586436--006bfd4f9697d8b64be920876bd8c0a40967b253806072ec09d2a630909826e4.jpg - 187 SHA256E-s398620--1ab7d488bafe19941f33155959c1bbec199a86ef2334c08b75b450bc9f36a16b.jpg - 188 SHA256E-s10457--0be429c323998556486e8f9977ccc980be3ba3920d5cc3bf16a6c7bb57b0fe3c - 189 SHA256E-s83789--c286b21f977391efd38b5a5a341f9dbec4da611a16bc1d17d8ca71d49ad64d30.jpg - 190 SHA256E-s321943--5e3983f4b43ae782b6f41c4f899027f1d55f78347e2106bc4c96e7f65c652918.jpg - 191 SHA256E-s7518--be582d1ce8295d8c47e261eb7bd78a0e720e78dd58805808e9bf64ddfc3c4fe4 - 192 SHA256E-s6118--3ca5d8ca6cda3acc6c07c604f6880c017e6faa7dad4ba61e9aa956a9fa8b4b0d - 193 SHA256E-s1086965--e170514a3651dda3313f4dcfdb9490f039a825b8349f74957a17313bdbcd7e8d.jpg - 194 SHA256E-s10504--a57d3172d4a009a1a0d38993ea6dbe03fab6aa1ec429aa4aab563465b0dc43bd.js - 195 SHA256E-s530445--7c8e603a03e17bb0c6440df6b695e557357527bc081871b51d0b5a61222dd674.jpg - 196 SHA256E-s37480--ba3a0b04e4325bf0853c6201ecf7bb0fc08a0a13f5fdf0a4477c6a1f0cc82559.js - 197 SHA256E-s394333--77f7debb969fd22698b60339ed0a0e98d9c43b8c74203528a02f6a185784e808.jpg - 198 SHA256E-s568976--43c009e20c1b4b28d651c64ac1faa9ebd5e704bb975e2fb65ece83f4cb8867d2.jpg - 199 SHA256E-s13813--4b4db06a82938c002539bc21d9285d63387e1a6241932c111c4f3992fa093092.axd - 200 SHA256E-s2735--f73ac06c4be021a97a8c40f5371f0e62fd7094d863d9679407784c09c13ddd5b.log - 201 SHA256E-s25176948--4493a4fd3160627db1fdd24c2a6bd402b544c495565815007c2d0d5093478d2a.odt - 202 SHA256E-s596273--de2ec9fe99774ea6ce0a746a66888b71cfd744d3d97084439d054e58adebe709.jpg - 203 SHA256E-s947995--956f7ec6d1c0c931c40e055fe21c2cfde8ef135f816052147406cb0c3ed0f948.jpg - 204 SHA256E-s5283--5fbb8a58b8bf48ea0511c26b1b319f737df54e8e35f13b5d851dc7c0ce662458.png - 205 SHA256E-s777575--c9fea606bc2e419967c550c43b5345bf7b08b43a81d0cdc561e048b94d536e10.jpg - 206 SHA256E-s51496--36143df60284eae68573cb266a34a25f3c042bfd8314bdf0730c03a4fb81bb38.sla - 207 SHA256E-s3013379--4f47c51193c043d2e81aa0bf46927a5f5c305625a09ac9034f9cb6e25ea2c6bc.jpg - 208 SHA256E-s592379--4cea82764a163f6da9c6e63f553f82f119d5188d187c0747ee467a337f81446e.jpg - 209 SHA256E-s8402--5b400d459743a01405d2d1ffc4d07651c36712caf9030e2a091e48f97c58a2bb.png - 210 SHA256E-s662301--f0cf51849e330e861513bee59063450d14759055c67986e8a31dbbde0907a254.jpg - 211 SHA256E-s1371822--0c85f348595f845e0076e52157fbb772a9d72a4821310c187b183370d7bb1b4c.jpg - 212 SHA256E-s13445--460f9e3ea4f8a260af278d81c59faa45f16b2069b10030a8a253cd852f2e8e34.log - 213 SHA256E-s19780--3f513b835cc3299a15178dae45cc523f1b06a1c13bd0e1c29f958027d3f5dc8a.axd - 214 SHA256E-s311438--00b3cbd6de31a75e3a017c452099991f1ec09327efe9c6450012f6015eb6e1a4.jpg - 215 SHA256E-s8942--e267fde4da4719de2c454d82f907796167f425510ea84098a39b425b69d2df5e - 216 SHA256E-s845884--58974bcab0e36d65d606c1acf57e34e2e6f89872fbab65b9abf5250c632967a5.jpg - 217 SHA256E-s331598--de52b228ad93c774d4dd1d41556ff27f7f03802378747807f324a9604e32ed66.jpg - 218 SHA256E-s201837--d3f750f64687f347f0254d3c602a010ef71636a85f37954690d20bb6548437b1.jpg - 219 SHA256E-s537652--aeaa479c57d39b3618006162c80e1c0eaa2cfa0b2a9a2c069a3d601bfe5b0706.jpg - 220 SHA256E-s1174974--1d506c737c2dbde4aa286a2a25b22412c83edc5e55c3cc94fa38fb224677cf01.jpg - 221 SHA256E-s7068886--945cfae8e22db1c96ec4cfa7b7de021c6bfe4d9e4961eeb2860716d6c8a57354.m4v - 222 SHA256E-s684839--02293539aa97de6ab57e9caaec6998f4e64a08967d9f5f2c44581fb1df0acdd0.jpg - 223 SHA256E-s371333--36110b44ea216b0166b023d09b52d0d32c3bdd01dafa857ed62e7c806be93193.jpg - 224 SHA256E-s195249--21a08a5510bc88e85db2b5da660c61320ccd101a4b86cf3558618bbf37d659f0.jpg - 225 SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.xcf - 226 SHA256E-s26368--302de7e36ca407cf1441ab2d3fa855192c9d8b2e6a7ec04638d19db7056b7f2a.png - 227 SHA256E-s965404--fd61bc28b2adfd4d2f175e02c662b7a71dc4b09880c8198795994e70f156c46d.jpg - 228 SHA256E-s7254--2fcb58c8f60caadcb3e2d9e38921a49e470a9d854a55c89cb9c80f6ed0334669.csv - 229 SHA256E-s482912--24330dbfb1d90882bf3f42e96c236f818913c343fd828992cd03ca84a3b9b2f5.jpg - 230 SHA256E-s641334--bb06cea748a2feefa1a608635b83ed4311da1990275e32a9fd4549048c91a453.jpg - 231 SHA256E-s1239159--2d15a6bf658d588697c5b3c2b1d1382450a40517779c32d435ff672e45539a5c.jpg - 232 SHA256E-s2125768--a04f47c1fa5136fa397897bc907b6754a9598b37d34920250b8f70a87aaaa0b8.jpg - 233 SHA256E-s3968--f4147a07111527be5bc7e9a5c83e3fd7ed871937167fc6d20fb7ee4d7059aa69.js - 234 SHA256E-s462918--aa97a7f50f004dffdf444bb7f69e09c650c8987f52b5f4a0164c6acdeb4a8b28.jpg - 235 SHA256E-s29501--67fa8330853830c4b29e05f96e6e3b6369ab908238e425e8faff4ac57e12bdb0.log - 236 SHA256E-s158417--4058a56c1350032d640519f3aeb94ba27cd8e8b5afceb6d65e746af4f94777e0.pdf - 237 SHA256E-s3437070--12a5bafa210aa79e9abb86c21032003c30c3a1eb5fce45a31488b6ff08db084d.jpg - 238 SHA256E-s4373--12f64c274107733ae44f8ea9dc92e3ecf15400d98b3d76f9cc7e11527e4ed81a - 239 SHA256E-s51497--218e86c2eb9ded51b764b5296cfff76bae4dca82e07a1602c9c597a1c34e98d7.sla - 240 SHA256E-s4372--20e4d3e47c5fd381ffc31e6effbeb29eda97d6def773a3e42596501c6beb6317 - 241 SHA256E-s317548--cb605575ca9fab16501f2819b000d11bb06fbb2ad1f300cfba3d011e3e8e2ffc.pdf - 242 SHA256E-s4960--c10e8c25e9b66e3ef77723373beae89e2fab1010c8b36ca329a3e9da20cbdc7e.log - 243 SHA256E-s517805--9c14fd5e5da48efd9951b086c25c04a7c5427111ef2829543497e707f93fce99.jpg - 244 SHA256E-s1857451--616661a96876b89472a69d32bd567aeeb95fa7da19ba4c3aa6a0ab237e2dcec3.jpg - 245 SHA256E-s2760813--63d375f82234356889c6222a0162bdba3b7f5a1a0cb31e24c2c209f43fc2f37e.jpg - 246 SHA256E-s832772--530816bf7c52c72e9b951289b5a35da753c66726d4e7bb2c2267faec6c8c263c.jpg - 247 SHA256E-s4660164--2832a896d7af11fc35e1dd7ab527b0fdfeedf7ffe93bcce147381a8739c81298.JPG - 248 SHA256E-s688782--71733ec7ffd2077ecf2973a739e4928be5824ad92034f64446a216cf513a1f29.jpg - 249 SHA256E-s2876462--92eb9385b333bf9eb8ad56de86e46d1ba9b21c1166814e6f16e50e4a769936fc.odt - 250 SHA256E-s496541--80d2e40f680dbd998b487e0ee8d479cb92741ec9c3e1f9d1d1d6d2f21a8cd795.jpg - 251 SHA256E-s69339--97fe05a5b2c230c5b1fde5d18555aca13d12a35940d7d8c15249e7e80629aed6.jpg - 252 SHA256E-s169446--5e1e9e262a58c5692f0d3c428fb71c0980311a88b474ffee95a5ea8cb5d5bf15.jpg - 253 SHA256E-s2678100--a347450551a9055011016920280dd0a63dfc541f4f52f8ee78ef2b7a09afd46a.jpg - 254 SHA256E-s87--5c2582459e3550daa4889fae41e3c8f6f4ad26dfa670502e4f516749aeac4113.png - 255 SHA256E-s5798--c7167ef62bc21326b00d78b47d672bc25026eb6c7f3919fa47db2e7db8855ba9.gif - 256 SHA256E-s53033--80840b2105a7a316a010ec3c3775031bef7fbdabbb7d3f6b7ece1a6253ef1b59.jpg - 257 SHA256E-s7407--8ec4462ca6a05614378729bb20bb33c3b892bc943fd698389e44d959c4506843.log - 258 SHA256E-s1189946--d23ba452e6e267d93f6233e885bd6f9e15b8ad1aea4c3d2368d901428df78970.jpg - 259 SHA256E-s3447000--61a3bd3f7dda48544b67040012d6cd5999499d25e75dc34b82d11955d0fc9b6a.jpg - 260 SHA256E-s3263208--69ad68aaad7058af8d14f7e4c03e5b52c9a78dbac7ffd33bd7bc5220c847d6bb.JPG - 261 SHA256E-s1226280--d372b699459664c382f607ff56294df49e6d8d0fcab90b509337c347943357cf.jpg - 262 SHA256E-s16890--12861c187e68e3591ccd5f708b935cc43bf25f5672daf50913e152c1c55e510c.png - 263 SHA256E-s1092669--8e7f7431c487c6cff11ee9f7c8a87aa0d057b518e60bd2b92fd677e5c9a88313.jpg - 264 SHA256E-s307511--5fad92167d8f9a7ed4076909a1540388cdae89df956e6011065526bfb10564a4.jpg - 265 SHA256E-s8334--212df98aca1ee3d4f10539a786ad746f3856c2715e23d5cb816a2374b5e6c43c.png - 266 SHA256E-s3375--2b403c31d4934895cccbe05556b0134bd4b78d4b873193d2b12a8893ab170681.txt - 267 SHA256E-s691014--470d607465715a4c0735d74da75a5aafb5f6707b9d10a9a6a8c002f095f447e2.jpg - 268 SHA256E-s680701--133c1dc67e394103d9f900cbf80ef508c7d7818edb23406c5f67f027a38093a4.jpg - 269 SHA256E-s4024--b5d3e2bb6d51ff8ceb54f501035a5feebe7d5178d35b98abe9e41531bd2abd22 - 270 SHA256E-s1117--b7c94c25be8e78468071e78481641927450d754fd1bbd8d0d751f116d02b9ab3 - 271 SHA256E-s476926--ea981873de3e0ca8156ff710429894abbd8a51384b210cc142b074ec9b2c9ba0.jpg - 272 SHA256E-s56655--7df6526b49b7aa986070db456b6a3a378c8aaaee8cb7c8892c154eecf401002a.com.htm - 273 SHA256E-s2963--4fc53b3029a595b3b7f1f201eb4b7c2df78afc7e083abccd070c8e6fae79a661.txt - 274 SHA256E-s761655--486ef18d41898ba80505d7630170305c4b58fa647786bd5447f20045bd6f3b2e.jpg - 275 SHA256E-s1389414--3599c1a4da6a3b61cbc4dc431c436af9bf201b634fde2f99ddf54eae8c3590d5.jpg - 276 SHA256E-s39678--bea819324e10bc288c75650e2196bebd5339952ce33574625ae5091ad749b63c.jpg - 277 SHA256E-s47531--a91ecea2694b4b5c8daab84aa25c675f2f73dbfaa8ccfd581d6868b1e2568b7a.jpg - 278 SHA256E-s4923--2f1b9afef156e9c7f4994106eda088868a992d92e66a5d601f77980fea80f777 - 279 SHA256E-s84101--bca6a8a9640b1ebfa8a2ba01b3a0f7ed20ad77fa5cbb5588d46ce75949fc38db.jpg - 280 SHA256E-s1245742--d547d4a18279ec671be7869896c0b3e763cf8499c4dc28a62a49cd657fdf4200.jpg - 281 SHA256E-s655461--f9b43d2794fe757d7cb61a704a01c85bc09eb20d70a1550d6934dec12f46f0bf.jpg - 282 SHA256E-s137484--51fbe9bc815e41dfe22b9f9d4ed8f3ca98a8cb5cc7b81522b296d45b0279a413.jpg - 283 SHA256E-s607392--ead4548b66ac3ab5c930cd89bd60de480184a4f23ffce9b5da24f9269b796283.jpg - 284 SHA256E-s6888--405748982bbb3340eea34acbe45085ea62c80767866f0c76c355e4f94b969c7c.png - 285 SHA256E-s4327767--eef5840e2f4294a125aaa3ed33f8ccc96c5c2c3e31cbee356013de354e628df9.pdf - 286 SHA256E-s411064--4e5e5d477ccc542f78649e4b4ee6aa132bf79ae9aeb64a46cb45a7ee133eb2f7.pdf - 287 SHA256E-s224149--204dbb62c5d5352c9b5baead124ecf52c6fffd49120343cc21bb10343353934e.jpg - 288 SHA256E-s1333719--9d9ac54db47723755ee0d19731c0b2f4b40074d946da4a1e283a4904feea4534.jpg - 289 SHA256E-s1889687--07b79ce21bf5ffe2d80f9878d338fcd63ddc92c5381eb3c290639c3e73a7b927.jpg - 290 SHA256E-s686131--93ba1a21ff8cc7d9baa61a2af8407ccc8c1b22705a191e9f0a393d14ec95e232.jpg - 291 SHA256E-s619954--3d900d39d16eca00287a0c4bbe20b46767867b5065260a4a1fa8444081998e25.jpg - 292 SHA256E-s828309--f1d702dcb350cff7a3229fe62c4f0f4beb5f95ad2f00a6fd1bfb82549cd08129.jpg - 293 SHA256E-s516404--0ca06e98fd119847c99bee56264a31ac99b36ae71136624018d308ff8c6a2e3d.jpg - 294 SHA256E-s783842--0618e7c3ebc7ff8fcdff82b9fd227e8b83f491e8e1b96c2d0e566fc7fbea27ea.jpg - 295 SHA256E-s20748--df0711c99c30b5fdcbfdd109c093f02f6a7f5196e7ffbc8e291bb2780c5735c0.css - 296 SHA256E-s61739--387a27967c79b09e21d93f8a8b969dda930e8d26e9ce379c1d71718d4cc5a1df.jpg - 297 SHA256E-s1461106--37222c3cd7a3af846c8aaed3a174a0a7e6f775ea4c08c4e2f792c6da724812b9.jpg - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -[2014-08-31 18:58:39 BST] NetWatcherFallback: Syncing with apollo -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -gpg: Signature made Mon 18 Aug 2014 20:14:04 BST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-08-31 19:28:42 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 5b1813a..68b2827 annex/direct/master -> synced/master -error: duplicate parent 68b28274ba1f0451a2e93ef4c2757ab795b920e6 ignored -[2014-08-31 19:58:41 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 71238f0..68b2827 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 68b2827..16f040e annex/direct/master -> synced/master -error: duplicate parent 16f040e9cd0bd085dd42e8869cc99d6982f8ea9c ignored -[2014-08-31 20:58:43 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 68b2827..16f040e master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 16f040e..e8ecdba annex/direct/master -> synced/master -error: duplicate parent e8ecdbace26ba300e7bf3f4b8237f8cf4d825955 ignored -[2014-08-31 21:58:46 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 16f040e..e8ecdba master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - e8ecdba..82f1c3d annex/direct/master -> synced/master -error: duplicate parent 82f1c3da446ea356933e764e4ab0f6533d8688f7 ignored -[2014-08-31 22:58:47 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - e8ecdba..82f1c3d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 82f1c3d..1d82f6d annex/direct/master -> synced/master -error: duplicate parent 1d82f6dc915ff33c86f9001c50b7c60f212b80a4 ignored -[2014-08-31 23:58:50 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 82f1c3d..1d82f6d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 1d82f6d..e6f51b1 annex/direct/master -> synced/master -error: duplicate parent e6f51b190fc3412b8c10988c2dd9f281014802f0 ignored -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-08-31 23:59:59 BST] Cronner: Consistency check in progress -[2014-09-01 00:00:00 BST] Cronner: Consistency check in progress -[2014-09-01 00:58:52 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 1d82f6d..e6f51b1 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - e6f51b1..e6d090c annex/direct/master -> synced/master -error: duplicate parent e6d090c41e0226cfb58bec304c1205b2fb2a738d ignored -[2014-09-01 01:58:54 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - e6f51b1..e6d090c master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - e6d090c..e21ddb1 annex/direct/master -> synced/master -error: duplicate parent e21ddb1bf0530ae415419ae15edeb1287ef6d9af ignored -[2014-09-01 02:58:57 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - e6d090c..e21ddb1 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - e21ddb1..03a2d0f annex/direct/master -> synced/master -error: duplicate parent 03a2d0fea214ae4a6acad0837587f5539f06efd8 ignored -[2014-09-01 03:58:59 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - e21ddb1..03a2d0f master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 03a2d0f..f062d0b annex/direct/master -> synced/master -error: duplicate parent f062d0ba684347871b780a4f0d5ff3e203329cdd ignored -[2014-09-01 04:59:01 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 03a2d0f..f062d0b master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - f062d0b..a695f4d annex/direct/master -> synced/master -error: duplicate parent a695f4dc83028907d2c9272f8cf8ec88d38049d6 ignored -[2014-09-01 05:59:03 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - f062d0b..a695f4d master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - a695f4d..7706c3b annex/direct/master -> synced/master -error: duplicate parent 7706c3bf24b8529bd248c7a4bfe817573bfa0368 ignored -[2014-09-01 06:59:05 BST] NetWatcherFallback: Syncing with apollo -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -gpg: Signature made Sun 31 Aug 2014 21:52:56 BST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - a695f4d..7706c3b master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-09-01 07:29:09 BST] PushRetrier: Syncing with apollo -To lizzie@apollo.aylett.co.uk:Annex/Family - 7706c3b..6936dd7 annex/direct/master -> synced/master -error: duplicate parent 6936dd71b925b08dac26890cec58186fe0f5da89 ignored -[2014-09-01 07:59:09 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 7706c3b..6936dd7 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 6936dd7..dc51bb1 annex/direct/master -> synced/master -error: duplicate parent dc51bb1571c950330650a2881d443449bae64db1 ignored -[2014-09-01 18:38:55 BST] NetWatcher: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 6936dd7..dc51bb1 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - dc51bb1..8f55d1c annex/direct/master -> synced/master -error: duplicate parent 8f55d1ccbb0ee6d44e3176006abf71d76f80376d ignored -[2014-09-01 19:15:05 BST] NetWatcherFallback: Syncing with apollo -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -gpg: Signature made Sun 31 Aug 2014 21:52:56 BST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -From apollo.aylett.co.uk:Annex/Family - dc51bb1..8f55d1c master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 8f55d1c..6cfcfe7 annex/direct/master -> synced/master -error: duplicate parent 6cfcfe7d46e622dd1e28d7c0d182e8c5082d88df ignored -[2014-09-01 20:15:07 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 8f55d1c..6cfcfe7 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 6cfcfe7..0048860 annex/direct/master -> synced/master -error: duplicate parent 0048860fa55502c1c58d3e4d55d3a687a5fee1cb ignored -[2014-09-01 21:15:09 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 6cfcfe7..0048860 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 0048860..3092f0e annex/direct/master -> synced/master -error: duplicate parent 3092f0e9d36cfb780bf0eb4a667bfe6a8a7b3ba4 ignored -[2014-09-01 22:15:11 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 0048860..3092f0e master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 3092f0e..c2d3665 annex/direct/master -> synced/master -error: duplicate parent c2d3665970d928b3eb4b93c0a69f4f1533a01c84 ignored -[2014-09-01 23:15:13 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 3092f0e..c2d3665 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - c2d3665..0966032 annex/direct/master -> synced/master -error: duplicate parent 09660328b05c3eb55e78e5ec38d9d043cd6aa78a ignored -[2014-09-02 00:15:15 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - c2d3665..0966032 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 0966032..b4bd0aa annex/direct/master -> synced/master -error: duplicate parent b4bd0aae9a45c024247c5ea120970ede21d52b34 ignored -[2014-09-02 01:15:17 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 0966032..b4bd0aa master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - b4bd0aa..dff7898 annex/direct/master -> synced/master -error: duplicate parent dff789833ff9f83324c35d1892fb271e7f59b6f4 ignored -[2014-09-02 02:15:18 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - b4bd0aa..dff7898 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - dff7898..628cc98 annex/direct/master -> synced/master -error: duplicate parent 628cc98b8f571d27b1b7f671992d884be9bb776a ignored -[2014-09-02 03:15:20 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - dff7898..628cc98 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 628cc98..11f0e77 annex/direct/master -> synced/master -error: duplicate parent 11f0e7756811654bee5ab1ae57068ad4cfebe698 ignored -[2014-09-02 04:15:22 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 628cc98..11f0e77 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 11f0e77..fb4d2b8 annex/direct/master -> synced/master -error: duplicate parent fb4d2b8eda7b2a194d98cf841c63374bf46cc2e0 ignored -[2014-09-02 05:12:34 BST] SanityCheckerDaily: Running daily sanity check to make sure everything is ok. -unused . (checking for unused data...) (checking HEAD...) (checking master...) (checking apollo/master...) (checking apollo/synced/master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s1103321--51418dc7fc654ebbeb9173bff598b4031d07d3c5cf651bd18a18ca6af9f7f1f7.jpg - 2 SHA256E-s3754--39631a60a771a00e88ef5ab011ab3f56fa8e539619b06aa68e66f2c71f252f9f.png - 3 SHA256E-s628641--2eeef2179787270c6307e1070678b6b27cbf0fe12cce71c136e0a89e1df78565.jpg - 4 SHA256E-s848--66e696444c6e570fc00d79f6651018d7e6549585e587394b933dcb0d74d8c214.js - 5 SHA256E-s21214--f26fa07b51fe0f4c5bc0d746f8b23e50115116bbcd80db057740bccb9841e4b6.png - 6 SHA256E-s852198--9fcc545c030c268d660381fd33d66b06605f7c5df16dca0b3fbe4eddfbf6b339.jpg - 7 SHA256E-s1334033--d6e722f76229c10ea6a1ff8dce2814ee42c92b643a19ec3f4d72222e1891c210.jpg - 8 SHA256E-s664656--85aaeced38501abfec6d23591edb07d7ab98bbe303b98eb07cfa0577ec8309b2.jpg - 9 SHA256E-s3213396--90e4ec9054de04c2b2c60a49b812582ba15c8da00208c9fc74acbc69b83182dc.JPG - 10 SHA256E-s820026--c1fc64d12cc74f60f8d17302a95217978782ea99758bce99ea2233709be60a6d.jpg - 11 SHA256E-s622679--5e8412b3955db206c6836fbd5731b0ab835aa325fc75bc7d75d4511ddbf67644.jpg - 12 SHA256E-s917793--7f2ecba64196449b9d7f1ea79e07f496d90d59c59d12472d058566a0881a5c6c.jpg - 13 SHA256E-s3493204--7ce9ad40b32b5cd1237e5efbb8f6885f7d734f8af65da8d0e92dc2de13162e07.JPG - 14 SHA256E-s910114--be8d66d9261108572efe0266ae386fefa653cea4ef43be9fbd10f7e2fe8d1c4c.jpg - 15 SHA256E-s636389--07b609b0cbf827a45cff2ca92367f3c5bf9a9527d4b3cb43961487bca8068ffd.jpg - 16 SHA256E-s823401--4cf12d87a9034d34a3019b5002000c92512f901a82f1081705c12e73b5870bad.jpg - 17 SHA256E-s1880--add7e1d7d7d98ff96afaec27bb066d6747551358e025176265a31b2b0f74bec0.log - 18 SHA256E-s8784--e28377207d41b4fef538b2fcbbd25c05275103a299e74966a88dce53ad5f50c0 - 19 SHA256E-s8694--490b9f2f9c4c826b68bad68a50cf672ec36c58acb9e24fd46e84abaddec19b9b - 20 SHA256E-s2656--96dd5f3d5f8e87ce1552798dd5fe4c8dedab6268c0df9e391a202ffdc4b8fa71.log - 21 SHA256E-s459593--b68a62596f7524b6f877d8bd3dbbe49f4de02310e9dd6d5134bbdabfcd5d957a.jpg - 22 SHA256E-s11931--5ce30bd4424d544ed954e4722d7ed590a5be46a267c5045953e034309d942a8f.odp - 23 SHA256E-s1249581--d834f2dc34ded72086e26c32784e693597be011f28398635286394c7e8b5ded7.jpg - 24 SHA256E-s335736--9638a3225f1adbdb736a2cacc476f8eb5201c8124b83dab887a26c6d3a0e5899.jpg - 25 SHA256E-s6339776--f42083be1dba62acf81ad5ee8bccad47f267e2ce34c9e73e9aaafe3c69b462bd.pdf - 26 SHA256E-s582899--858ad02a9e5f58a6f5ea509865831acd540c290837beb87b37cb36bb62a7b982.jpg - 27 SHA256E-s2475657--d3fa5e460a2b164e849213d0417790704d1b4a2df9af5f6b281ac17dbacad30b.jpg - 28 SHA256E-s637475--68315445dd9477f07a695cb9fd12bb2c95f3117d949665ec2690184ded6b1ee6.jpg - 29 SHA256E-s77771--484ed3d8cc44de2db74c5680659c5c23ccb29ed5e99d0fb4b470a2c130c64c79.pdf - 30 SHA256E-s2343639--a7fccfe9a2c8de20ce8df10048b075758c445e5f4c9d9b78368db179e74e9a47.jpg - 31 SHA256E-s2282836--66e945f3a37651e1c88c58ff42b4dba9c6c5d822dc59f3e59895c336a0428c3d.jpg - 32 SHA256E-s5902--da66d622f9ed0987a0466c2c05c2aea56572e2f991c542b1120d564fb7459e7b.log - 33 SHA256E-s61410--4d3f0160bc92d0095a824baa17a08499dc748d06648029051802d24a772ba75d.css - 34 SHA256E-s1958077--1717f3036e7ca6b61fe8eeb3ce319de728b9bea10fd814108b9e13397a336db5.jpg - 35 SHA256E-s80930--f9b79963053221a10e32c4061b9da3622e89ce56aeed26c58f23bb70a2a57496.jpg - 36 SHA256E-s4956--a05854e0d26affdbb3e171c8e9ca3f663c8bc930f6402d9a370104e239bc2601.log - 37 SHA256E-s202851--3689503ce6f780d04e659fc85e4e7978c3c445afbd103f3ac118e1c6f3a4b738.jpg - 38 SHA256E-s5258--a243d289f629eb2e321c7232aa59c65d10ec79e70d07f25758ac04c0b9ff3f79.log - 39 SHA256E-s5406--dc07212d5aaaf5a320b3f9d710a72b68f7112140c76b43b7c0b4bb71f91e823f.log - 40 SHA256E-s8427--439c4f2144c9ea726b739494565b05dc47b59a8835e24e9a083171efc0834fc1 - 41 SHA256E-s46--ca4a766fadecf16bbc25afbd805e2befbfb4cb270f122b0de813fbcfc933c1a2 - 42 SHA256E-s839129--921ddf15c906a0353cb18bdd0b321bd5a37dfe653edbffc8e3b6b47996d54d8f.jpg - 43 SHA256E-s2922183--3aa5d5b22a980a11cee928ba701ffd389542db84fe96219442de1b33a64f840c.JPG - 44 SHA256E-s1305363--0b14938c28492e288d35a62334d6436ba8edfb7f65a066dbd9587478f157ab99.jpg - 45 SHA256E-s8602--819b18ca30f477f66e558ba1488a06e438a5f0b9c8f6987f68daad039d8020ca.png - 46 SHA256E-s6205--14691e198b05dd68b5fe3ed39eb8739182f4f5e75dc43dd7ecb252f01978c7ed.png - 47 SHA256E-s5070994--d0c5367647750b1f0b54c9fea7c7c9e1a0f7a0a7f61c92a688887538df3abf7f.m4v - 48 SHA256E-s134807--7100078e84c39a2123c0ea7d713e3361c7174f21fb72d39dac2a99a4844f89b7.jpg - 49 SHA256E-s535905--f317f11e4e0536ea8172e7827369bd9a3c887fcef2586b8eeda28b2dd36a791c.jpg - 50 SHA256E-s6420--72622a4453f4ea48acc0337bb1b288e0fb034d1ee1aa74f98eb9062066c025b5 - 51 SHA256E-s51483--c9fba5eb0b29216afd9b6f13dd2f351367b7bcd0c8eb93fa0a1b6a0ce4535d57.sla - 52 SHA256E-s1957447--c3eddff4df50e1b0c5dc93f85e39acd24723013dd9b27b7b8a407eb5e55f1903.jpg - 53 SHA256E-s5345--ee879c6bc3c3ac59f449a9d9f92ec9cc2d15dced1f166805a179b6874d190c25.png - 54 SHA256E-s153751--c3fd0000f94ff9c44fef856ee440837fa4c228918ae70d0813d1635d50e6d4a0.odt - 55 SHA256E-s682324--33a6a1b34570f9abe0516d9abceefe14aae4cdacc41dc3f30ca92222d545631f.jpg - 56 SHA256E-s370109--a00b1c78753de6ae1d64a01d457b53a3572a9324a0facda4ec39a149d9adb37b.jpg - 57 SHA256E-s310217--aa0c575a44cac4957e06cd8ed0b058a16454a7be7f32ec8e79c815be6057bfbd.jpg - 58 SHA256E-s5798--61852a3ad168d4f27fe0f0e924e7418e838ae4363d85a64ebea80c9154e0c9a0.gif - 59 SHA256E-s47071--f1a74e5f9a20776adbe88ac3092e5a20a69d254905c0f93aa0b95a1ad0a5ed00.sla - 60 SHA256E-s988--b1f5fb3d38001b8bcf214158c6c7571f5aadb03093d2c307970a728edcb8012b - 61 SHA256E-s1397011--b67c04c6c99ccc208734dd39e18d4304a4963ef36600d4adc5827df21bfcc260.jpg - 62 SHA256E-s2124--1c64d2a60a40242432550ab3292e1ee38072481c36b8f028f75e3b4ea52fec29.log - 63 SHA256E-s1640512--ccb4940713e190a9242b34e18896156733f36df909c7e399bfdfe36299bfa748.jpg - 64 SHA256E-s484856--55f146177198dcd03069703c7b8bdf5c10cd7750aaf4b6f9af1946d72a9f9d23.jpg - 65 SHA256E-s7031--88bedea3e75aff77858c63a6c30bb06180bd9167fd380d94f132486d6ffeddf4 - 66 SHA256E-s10100--1df9143f4c02f877ec891262bcbc407a9d4b960dd80c6826d5c1078012dc2614.js - 67 SHA256E-s2454--778574fe7cae3bfc2a49cbe3be18ed313b049b6e0bc333cea80723ae2136f9c3.log - 68 SHA256E-s63103--474c29d016927bd7dc42d992fc07c353148d393cfbd7c3e8193df91c3bb2d805.jpg - 69 SHA256E-s245481--ba0e9ed8876970e0aad7e22aeaf4f7403e1ef6fca474e0b4e90837381c0b810f.js - 70 SHA256E-s708--ab8f3c450c5c8944d6d91c35258b9da5ff4564b9b05b1e09ebbaa9b740d14aa4.log - 71 SHA256E-s582241--fb565e6fa923f3265a9406abf566d5de7a8e062b1d9ccb8ba7ec61a902ea277e.jpg - 72 SHA256E-s601517--fd4a4effd6c6b064be34910b36f1de8011bb3949d0f883a57ed4ca60eff6a642.jpg - 73 SHA256E-s613354--0d78d51b5047055d9bd2727e01a7c73ec25bcb99925be26550f3b921054e336b.jpg - 74 SHA256E-s20794--0ba2f6756001669bdf934f9d79e8fd1ccf2028130c33a0510279581ec9dfd73a.js - 75 SHA256E-s654750--be05edd69e61fb5ebecbddc8c39ae9ebdbca5e94ee395f604bbd73910a7e40f9.jpg - 76 SHA256E-s440--4e8500857e2b6a08a6922ca852ff4c9702e2397843011a14dee43d6e20c4f787.log - 77 SHA256E-s72381--a170eff1ba771b3e4e769ab2974b8fb1f66cff07bf8b19561a97f9d7767b565a.jpg - 78 SHA256E-s344661--21564a2da0f6b1ea6c4a39f4a96ba02680facb9d8a084d4fffa28b0e527c9fc8.jpg - 79 SHA256E-s51248--f940d364ad2583a9ae3c0f777fd61406914daa1837ed8dd78f3461760c4ca747.sla - 80 SHA256E-s502234--251053730579880833dc12058a6c689ba074f0a981331ec7eb685b69f08e292c.pdf - 81 SHA256E-s3682--f75a95ae16e2f8a8e0a607782cf332dc34c1e317d473023cbd7f9915fa400d62 - 82 SHA256E-s3544--9b40beb44b624520a74057a82ae5e6adb18601e6c1fc7d8496bdd59e3b248945 - 83 SHA256E-s355156--7056bee290696e681cd3538e2ff2e740842bce032effe509f0919e888cc03ee4.jpg - 84 SHA256E-s879539--12cc34616b2dda153890db0a724290fa01bd9dd664061a05c8d2c1039cd4cc3c.odg - 85 SHA256E-s2051310--69387e84897ed700b6dd7c418fc3a7884a1e6e16a4267297b3effb95b02a7bc7.jpg - 86 SHA256E-s620--eb69406700a3a6122cb532614f4ae6899d97409d76259820176f7ae77158684b.png - 87 SHA256E-s693427--e20c50c86937800b14e2773d79eb63d13c0300781f8e71ee3947fb5a2fe98fe5.jpg - 88 SHA256E-s87985--b89b279ca5dede3643e8a48402e9b112b1e1fdc14b3326c98cbdb32f9f7fa2cc.jpg - 89 SHA256E-s35739--378d1bcb19c2742b8d344459a74f9b4ea44287c4e5cf046b80a46b209ea1ebbb.sla - 90 SHA256E-s51515--d4805b60c6e0ea396dc157ca0e399ba355482f2a9696f31fdcf819aa176ea3e7.sla - 91 SHA256E-s396738--5e18be640581ced943a676323c80dc283b15d3caf37b2bc2d0b05ceee1d178e5.jpg - 92 SHA256E-s334295--7f97df9f93e42a2db9e9efb0aa34a2a9a6b9af49846e6a73f320ee151d535eed.jpg - 93 SHA256E-s425513--0f6228a7466c12d1d0e4beda9825f17442b15286a5639e3a894a36d33497c77a.jpg - 94 SHA256E-s114076--6a1822942964efa5531de2cae48d3fd69e71baca7ade38b7cbe23964637d4478.jpg - 95 SHA256E-s118034--a8b1e6f81534106e9f4563dfe3f288e9425284fbaa74247065cf80448cdb216f.jpg - 96 SHA256E-s639--4b491df2b47c2fd4dcfbb99b50ec1367e138c61216704490ada08cddd0d32fda.css - 97 SHA256E-s734079--0602d1c85bca8508010ed03c2b1c26c88a8c759783f49d7f7b282b30837c6b32.jpg - 98 SHA256E-s130889--751d2fa73ac74e17d2e82fc9a89b3d393028197790657aa075effc7c16b8f528.js - 99 SHA256E-s485283--63716cdb8953a9318eb28953af25db2afa02251e6f152d487f5ab05f1d27930e.jpg - 100 SHA256E-s59518--6a80f10665ad39dc27ee3a5727ebeee321a289dbc958916f9e6eda01f2703d25.jpg - 101 SHA256E-s194--4c0fc707f629bcb314433fc700c6090c970d343adbb921f46084bdb08f99cf6e - 102 SHA256E-s303--07ae4fec1962f2f83808ec861e477d5669dd71ff1089cb25a0e1da7b3ec9a5a6.css - 103 SHA256E-s24519--3f3cba473c1818b2ce46a034fc323d528df85dd88d3f2ed411ad644a08ff9132 - 104 SHA256E-s316292--691e653f57643e579c261a827441e63ee3d8cf1f9ed5cdc43d861cf340510d34.pdf - 105 SHA256E-s11916--88e5b1e2f5bd0f5c458abb41589028ef35dc75872abd7e04eee4a12ae7bfef38 - 106 SHA256E-s733240--fe7b7c77712b866c932d391f8305560d488d0e5515f3d9c890ddd11c96ff6069.odt - 107 SHA256E-s4323950--c71e34a9fa2d1f54934d3caf829e4b5330811c2937d523f856d43cf5d92b7275.m4v - 108 SHA256E-s475740--e2d4880b8561167dd91b57a666f3eba68931ae3546231d102469c76d341f560a.jpg - 109 SHA256E-s574--5d1bd8763457376e0ff677895456f9aad26b6d85e15648696e9f4c77af104fee.png - 110 SHA256E-s11608--f815f1bad38a05f27b1f7cd416236148fa79554ed2546a014afe148c0e427839.log - 111 SHA256E-s3300--7164c4d91218528eedb0310af14927d4ce483889b53da24fdcc01fadae107fbd - 112 SHA256E-s962958--9a81dba98b0b910641d035bf662b847fb4785ef2378bef7b2ae6713b1fbd903c.jpg - 113 SHA256E-s845627--09f3e811c372a7ee936064d4c48c8b4f36db519a49a0b274f69e3da12a0e2ffe.jpg - 114 SHA256E-s2380622--05725288b66460ff1befda38280dea4d05c5dff42818de7d64e619e12aebeaa0.jpg - 115 SHA256E-s62795--a32762ee80e176ca1d7869cd5f68e7442327e1a861ed70290f2256179ebd844c.js - 116 SHA256E-s3486--f148d21e252ab05ff7039fa276ee309e6d16d2ba7444043acc148b9986164162.log - 117 SHA256E-s2393747--1ba6fc7f4d47ced145ceab80128e3ceaf8cfe8f2155b5e33e9273c736a81b910.jpg - 118 SHA256E-s4611--bbc334899e27d8fe781f61e06be1c28852e618d1e2bd8b98de0aed7fb6106ad8.js - 119 SHA256E-s826134--426211e056784356538d3ac80838e197e2cdf29742cd31db6a386ce7c05aa052.jpg - 120 SHA256E-s1072403--87da8298b8c3c76bdfb8c96ac7dcb11349763067056eb0e1fadf5241fc134141.jpg - 121 SHA256E-s51028--d6d044282ee1d1d8fc02130ac42ab1d7ee3a6a7e2987b78bb1062529019cf3e5.sla - 122 SHA256E-s45783--35b9963b4a8bc3dbee5bbe827c2e18c795b8fce86bb1eb87c6b3b09327380f1f.js - 123 SHA256E-s999195--c0fa3d678c9ebe118ea3fb1b664a2f63ccc792a7578fe921d0c299adf40d97f3.jpg - 124 SHA256E-s96828--c5ebf871d1c98e5f49d15dc22131e483b514754ad86c6293c69b6d5aa3d44cf9.jpg - 125 SHA256E-s159835--47a9ba3de62d6a4b11dd59a60b0047d3d377c224ceac85bfb6a81a972f25fff9.css - 126 SHA256E-s9629--588e723593992acb553dd4f2c76a6993135b4f49e674358fae63ff06e145f07a - 127 SHA256E-s39867--6e96f4658811bba2f27f930f764111501e438135d793e28fe7eacb6b10866e0d.js - 128 SHA256E-s62332730--a2c804ddc66d8175fb5e187d17c904954f1e2cae634c4604ac363eb97d78f7e1.odt - 129 SHA256E-s1711933--dd49df68da23021d3e9cc775e86bd5341dda6ba71714c8287872deb9416e051a.jpg - 130 SHA256E-s290639--0803de7a02e9a4a1caca69b2a7b2c948e7faf2e4ef2bf3bcdaec148c0f26b842.pdf - 131 SHA256E-s5799--fa90e9a478760bc12c2707962f2ea6b9ab213bc7d4b158f28f6739727ffe05e7.log - 132 SHA256E-s11156--17ca703a57e9f02ebd71251ca8bdb6d82b71fa586deb034cd384b21a3818035a - 133 SHA256E-s16171--47a7946e6364fa5ad3dc595105c79a4946f18cbef0818e72682d9304625ceab9.odt - 134 SHA256E-s1962015--2eae4dfa79e014bf4468141bfac8c0065d1b05f2532758c6e68deedd297f22ee.jpg - 135 SHA256E-s31268--560829df213299f5db9aeb0b31b40044300c34e92818680f422d0ddfe7602f2c.axd - 136 SHA256E-s145407--c34c44643d9d0f7114cce8b31f3442a7b6392c4687af9ab97995bd30ddd3167c.pdf - 137 SHA256E-s1773--8417f863ffa4a076dd2d8b5a63170bb0c5b83cf275d72245a79c31d94358fd20.log - 138 SHA256E-s701838--3d7abfd8b091e4da1bb61881155c299b78ed693f128f1c693c7970bcbce4e8e0.jpg - 139 SHA256E-s2089502--f4c9ec5dce63924cba6f77efd5e20b17cfc0f3c9ae45dce7bb0ecc5a10986205.jpg - 140 SHA256E-s1085890--0346c7a329e7b80c7f93b8aa7de039bf322070ebac33cee6ade6fcc4a4f296be.jpg - 141 SHA256E-s3998--e38f3a315b698a0e8ccfa395431393af757f882413cea8b4879b5b5993543f86.js - 142 SHA256E-s7372--181699a3ca4be8bb0e9913fd96dc5c44ed8a790ea6ef2bb0fb285e741f2c46ab - 143 SHA256E-s864279--364b4a4d0a30ddbf1164d5d3ded0702a4b016ffc27d26eb6005d96e68aa4f77f.jpg - 144 SHA256E-s2941--7ca4f001618fda61146802286daf472c5daaaded2471e356a752b6a69834e7f7.log - 145 SHA256E-s153049--5805df5cecdaa15a549bf7751b1d66f7455e71e2243709d9799f839e42d082f2.jpg - 146 SHA256E-s542959--5823d605d7258bd813d09712fd124fd7c63f2cbdf46a9b52c3eb67eb7bb538bc.jpg - 147 SHA256E-s45282--b20a77431de35f8e70867cfe520503528fb948d63f724ed90fc249994875b77a.jpg - 148 SHA256E-s19556--e5bdba04d2a9d805c491778a742744d3007d38a23c9dc11cf8f6eab7b2dd0a1d.log - 149 SHA256E-s392108--c9c76c131588fc29d588afed12d98b6b3a6aa0a9971ad368112bc0c2a603e70c.pdf - 150 SHA256E-s8275--ff63b5b012ea62b178310424d817a8a77fb31151dd697659f85f23a6298cf28d - 151 SHA256E-s1769251--7d0a2ec1652f1287884f6bd4e0df14106af271e81fc38cae5aac1357966ea672.pdf - 152 SHA256E-s464748--aa63c72a4b064f91083228395e1391d970873ad1370900a468db154ed266d475.jpg - 153 SHA256E-s6130263--3521b18281dba779713e600fde1a4d15568328baad6baf43cba1530df7165c5d.JPG - 154 SHA256E-s494260--aeb91b314f3dee3580093e9610dacd5917265794b49acea9d80dfca83d56b88d.odt - 155 SHA256E-s3362329--05fde815df42455fdc1b563ce41bf13d585135da628d01c5ffc9ca627c008225.jpg - 156 SHA256E-s489239--d2ab01a94808613489205b7aa5d666cccfeac0a28b5a76ab18fc9fd9435dcabc.jpg - 157 SHA256E-s482249--e4979b950d4633515316102d934115b1981c8adf5a14ea80bfda87e623af7989.jpg - 158 SHA256E-s93506--3f44779fc3ce611f607c9cde2c114f6f038775485a677e17bcb6bb034e6ac888.jpg - 159 SHA256E-s818--66d21ef5da07cc00768b23bb711ccc8e18b91c99ccad2084ec309f51e6c52db6.log - 160 SHA256E-s171892--33f34e7d16851c2291d7495754505d391be4668883b43e4b9e587126c693b1d2.png - 161 SHA256E-s278132--fca8b8bbcc0f9fe8addb57994c69a9c511b206c27424491809ab31aef86f21b4.jpg - 162 SHA256E-s2418631--deb0aadf97aa49010ac3cab5f5299e2d68eeb5ecb4dd5de93316f23a714734f6.jpg - 163 SHA256E-s125121--2b2cc905b8c05d4c7253a9c2b45a961df545842e4ce9d17e5248aa6240e77557.pdf - 164 SHA256E-s199793--615ac75e6766d637d17159ebe3d48eedf27096e93b83efc159431da4d032e21b.axd - 165 SHA256E-s223221--ca5f5160688546f422cf7d041e58f07d5d90e8359666e523a5af515baf0b2980.jpg - 166 SHA256E-s1959724--2e44ed4b10ab3c1655b16335b901547713ac8d5c38d4ed3735bcbabb272242b5.jpg - 167 SHA256E-s11609--df8dcf81585eccae95b7c4f0a0ba8c6fc4cfe90ebbf9657bd6a10320f7195e61 - 168 SHA256E-s483419--96cfd3b43e5b7bb1d6a5bc3f78d33e873fa36ee6e53c9f1de083f279c19c5f70.jpg - 169 SHA256E-s560766--96f47b698f6502bc758e6d8b9b538368f8085d040306388bfd42d3026c465ff5.jpg - 170 SHA256E-s3848--4d18299f8d8ef1bfbd7b206d419ef6f65cbd09a3ae999f3c7cc8496051b34080 - 171 SHA256E-s1141493--80b7a82ee4edc420c538c4a2a37fc9d80cce4c321f5a9a7fa7e66df0c9e3693c.jpg - 172 SHA256E-s9726--14b5e76da3417f5f25f48c2a793aa50da9c920451495af7612b76d3c052d3f13.odt - 173 SHA256E-s939529--43d05562e75f2477aa6d412d8a672ce7b6cf2890d4e1578bf88692aabfd0e70d.jpg - 174 SHA256E-s888147--948ca59b827f77f75ea981b149a72df976aea360cd263d0f7c03275375a47232.jpg - 175 SHA256E-s740710--f1e98c032815161aff44c8ccbb882af5cb234f91c4430cf91d01115649bc9aa5.jpg - 176 SHA256E-s961257--e6b21901e268f6d0f3a38b43e5a06d8ad9ec0901f4c9639954da7ecf2ee4a666.jpg - 177 SHA256E-s616645--bd10a26926e6cd0fd0ee6cf72692c92134b183927280a00a74e869bbeae8bde6.jpg - 178 SHA256E-s47996--f862cbc7bea6fe4b5fe3a3af2b393973220a34975dd36a9d5f92b30d1db80acc.sla - 179 SHA256E-s2396909--2e6d435cf96f81a3f3247f2d35b01701f8a46977e813745324ca5b40717fdea9.jpg - 180 SHA256E-s180605--66c6df69bba4602100148ffd0f0a0ba0a14b74eaefb3b27708c6792d2b5cd09c.jpg - 181 SHA256E-s721289--159f9398adde99e23b05c8c8c99aadd98b6a3a80afe5e3745ff37b0668fe4a24.jpg - 182 SHA256E-s95559--0d932a11d465d523f85b17803d44fb0748459771b2cd843dbcfd677248abb0f5.jpg - 183 SHA256E-s368166--98be96450123c166cf11f1763aa25040ffb1674f7267a4041cc1a4fbe8e433a1.jpg - 184 SHA256E-s846--b3c9f5697bee76715237040d6ba5ff9f657dee2d882e36d818ed2ff50e8e0835.log - 185 SHA256E-s581051--217882c3f655c62dd323afe0689c9485d0d09430d5356a63105632cce08ea88e.jpg - 186 SHA256E-s586436--006bfd4f9697d8b64be920876bd8c0a40967b253806072ec09d2a630909826e4.jpg - 187 SHA256E-s398620--1ab7d488bafe19941f33155959c1bbec199a86ef2334c08b75b450bc9f36a16b.jpg - 188 SHA256E-s10457--0be429c323998556486e8f9977ccc980be3ba3920d5cc3bf16a6c7bb57b0fe3c - 189 SHA256E-s83789--c286b21f977391efd38b5a5a341f9dbec4da611a16bc1d17d8ca71d49ad64d30.jpg - 190 SHA256E-s321943--5e3983f4b43ae782b6f41c4f899027f1d55f78347e2106bc4c96e7f65c652918.jpg - 191 SHA256E-s7518--be582d1ce8295d8c47e261eb7bd78a0e720e78dd58805808e9bf64ddfc3c4fe4 - 192 SHA256E-s6118--3ca5d8ca6cda3acc6c07c604f6880c017e6faa7dad4ba61e9aa956a9fa8b4b0d - 193 SHA256E-s1086965--e170514a3651dda3313f4dcfdb9490f039a825b8349f74957a17313bdbcd7e8d.jpg - 194 SHA256E-s10504--a57d3172d4a009a1a0d38993ea6dbe03fab6aa1ec429aa4aab563465b0dc43bd.js - 195 SHA256E-s530445--7c8e603a03e17bb0c6440df6b695e557357527bc081871b51d0b5a61222dd674.jpg - 196 SHA256E-s37480--ba3a0b04e4325bf0853c6201ecf7bb0fc08a0a13f5fdf0a4477c6a1f0cc82559.js - 197 SHA256E-s394333--77f7debb969fd22698b60339ed0a0e98d9c43b8c74203528a02f6a185784e808.jpg - 198 SHA256E-s568976--43c009e20c1b4b28d651c64ac1faa9ebd5e704bb975e2fb65ece83f4cb8867d2.jpg - 199 SHA256E-s13813--4b4db06a82938c002539bc21d9285d63387e1a6241932c111c4f3992fa093092.axd - 200 SHA256E-s2735--f73ac06c4be021a97a8c40f5371f0e62fd7094d863d9679407784c09c13ddd5b.log - 201 SHA256E-s25176948--4493a4fd3160627db1fdd24c2a6bd402b544c495565815007c2d0d5093478d2a.odt - 202 SHA256E-s596273--de2ec9fe99774ea6ce0a746a66888b71cfd744d3d97084439d054e58adebe709.jpg - 203 SHA256E-s947995--956f7ec6d1c0c931c40e055fe21c2cfde8ef135f816052147406cb0c3ed0f948.jpg - 204 SHA256E-s5283--5fbb8a58b8bf48ea0511c26b1b319f737df54e8e35f13b5d851dc7c0ce662458.png - 205 SHA256E-s777575--c9fea606bc2e419967c550c43b5345bf7b08b43a81d0cdc561e048b94d536e10.jpg - 206 SHA256E-s51496--36143df60284eae68573cb266a34a25f3c042bfd8314bdf0730c03a4fb81bb38.sla - 207 SHA256E-s3013379--4f47c51193c043d2e81aa0bf46927a5f5c305625a09ac9034f9cb6e25ea2c6bc.jpg - 208 SHA256E-s592379--4cea82764a163f6da9c6e63f553f82f119d5188d187c0747ee467a337f81446e.jpg - 209 SHA256E-s8402--5b400d459743a01405d2d1ffc4d07651c36712caf9030e2a091e48f97c58a2bb.png - 210 SHA256E-s662301--f0cf51849e330e861513bee59063450d14759055c67986e8a31dbbde0907a254.jpg - 211 SHA256E-s1371822--0c85f348595f845e0076e52157fbb772a9d72a4821310c187b183370d7bb1b4c.jpg - 212 SHA256E-s13445--460f9e3ea4f8a260af278d81c59faa45f16b2069b10030a8a253cd852f2e8e34.log - 213 SHA256E-s19780--3f513b835cc3299a15178dae45cc523f1b06a1c13bd0e1c29f958027d3f5dc8a.axd - 214 SHA256E-s311438--00b3cbd6de31a75e3a017c452099991f1ec09327efe9c6450012f6015eb6e1a4.jpg - 215 SHA256E-s8942--e267fde4da4719de2c454d82f907796167f425510ea84098a39b425b69d2df5e - 216 SHA256E-s845884--58974bcab0e36d65d606c1acf57e34e2e6f89872fbab65b9abf5250c632967a5.jpg - 217 SHA256E-s331598--de52b228ad93c774d4dd1d41556ff27f7f03802378747807f324a9604e32ed66.jpg - 218 SHA256E-s201837--d3f750f64687f347f0254d3c602a010ef71636a85f37954690d20bb6548437b1.jpg - 219 SHA256E-s537652--aeaa479c57d39b3618006162c80e1c0eaa2cfa0b2a9a2c069a3d601bfe5b0706.jpg - 220 SHA256E-s1174974--1d506c737c2dbde4aa286a2a25b22412c83edc5e55c3cc94fa38fb224677cf01.jpg - 221 SHA256E-s7068886--945cfae8e22db1c96ec4cfa7b7de021c6bfe4d9e4961eeb2860716d6c8a57354.m4v - 222 SHA256E-s684839--02293539aa97de6ab57e9caaec6998f4e64a08967d9f5f2c44581fb1df0acdd0.jpg - 223 SHA256E-s371333--36110b44ea216b0166b023d09b52d0d32c3bdd01dafa857ed62e7c806be93193.jpg - 224 SHA256E-s195249--21a08a5510bc88e85db2b5da660c61320ccd101a4b86cf3558618bbf37d659f0.jpg - 225 SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.xcf - 226 SHA256E-s26368--302de7e36ca407cf1441ab2d3fa855192c9d8b2e6a7ec04638d19db7056b7f2a.png - 227 SHA256E-s965404--fd61bc28b2adfd4d2f175e02c662b7a71dc4b09880c8198795994e70f156c46d.jpg - 228 SHA256E-s7254--2fcb58c8f60caadcb3e2d9e38921a49e470a9d854a55c89cb9c80f6ed0334669.csv - 229 SHA256E-s482912--24330dbfb1d90882bf3f42e96c236f818913c343fd828992cd03ca84a3b9b2f5.jpg - 230 SHA256E-s641334--bb06cea748a2feefa1a608635b83ed4311da1990275e32a9fd4549048c91a453.jpg - 231 SHA256E-s1239159--2d15a6bf658d588697c5b3c2b1d1382450a40517779c32d435ff672e45539a5c.jpg - 232 SHA256E-s2125768--a04f47c1fa5136fa397897bc907b6754a9598b37d34920250b8f70a87aaaa0b8.jpg - 233 SHA256E-s3968--f4147a07111527be5bc7e9a5c83e3fd7ed871937167fc6d20fb7ee4d7059aa69.js - 234 SHA256E-s462918--aa97a7f50f004dffdf444bb7f69e09c650c8987f52b5f4a0164c6acdeb4a8b28.jpg - 235 SHA256E-s29501--67fa8330853830c4b29e05f96e6e3b6369ab908238e425e8faff4ac57e12bdb0.log - 236 SHA256E-s158417--4058a56c1350032d640519f3aeb94ba27cd8e8b5afceb6d65e746af4f94777e0.pdf - 237 SHA256E-s3437070--12a5bafa210aa79e9abb86c21032003c30c3a1eb5fce45a31488b6ff08db084d.jpg - 238 SHA256E-s4373--12f64c274107733ae44f8ea9dc92e3ecf15400d98b3d76f9cc7e11527e4ed81a - 239 SHA256E-s51497--218e86c2eb9ded51b764b5296cfff76bae4dca82e07a1602c9c597a1c34e98d7.sla - 240 SHA256E-s4372--20e4d3e47c5fd381ffc31e6effbeb29eda97d6def773a3e42596501c6beb6317 - 241 SHA256E-s317548--cb605575ca9fab16501f2819b000d11bb06fbb2ad1f300cfba3d011e3e8e2ffc.pdf - 242 SHA256E-s4960--c10e8c25e9b66e3ef77723373beae89e2fab1010c8b36ca329a3e9da20cbdc7e.log - 243 SHA256E-s517805--9c14fd5e5da48efd9951b086c25c04a7c5427111ef2829543497e707f93fce99.jpg - 244 SHA256E-s1857451--616661a96876b89472a69d32bd567aeeb95fa7da19ba4c3aa6a0ab237e2dcec3.jpg - 245 SHA256E-s2760813--63d375f82234356889c6222a0162bdba3b7f5a1a0cb31e24c2c209f43fc2f37e.jpg - 246 SHA256E-s832772--530816bf7c52c72e9b951289b5a35da753c66726d4e7bb2c2267faec6c8c263c.jpg - 247 SHA256E-s4660164--2832a896d7af11fc35e1dd7ab527b0fdfeedf7ffe93bcce147381a8739c81298.JPG - 248 SHA256E-s688782--71733ec7ffd2077ecf2973a739e4928be5824ad92034f64446a216cf513a1f29.jpg - 249 SHA256E-s2876462--92eb9385b333bf9eb8ad56de86e46d1ba9b21c1166814e6f16e50e4a769936fc.odt - 250 SHA256E-s496541--80d2e40f680dbd998b487e0ee8d479cb92741ec9c3e1f9d1d1d6d2f21a8cd795.jpg - 251 SHA256E-s69339--97fe05a5b2c230c5b1fde5d18555aca13d12a35940d7d8c15249e7e80629aed6.jpg - 252 SHA256E-s169446--5e1e9e262a58c5692f0d3c428fb71c0980311a88b474ffee95a5ea8cb5d5bf15.jpg - 253 SHA256E-s2678100--a347450551a9055011016920280dd0a63dfc541f4f52f8ee78ef2b7a09afd46a.jpg - 254 SHA256E-s87--5c2582459e3550daa4889fae41e3c8f6f4ad26dfa670502e4f516749aeac4113.png - 255 SHA256E-s5798--c7167ef62bc21326b00d78b47d672bc25026eb6c7f3919fa47db2e7db8855ba9.gif - 256 SHA256E-s53033--80840b2105a7a316a010ec3c3775031bef7fbdabbb7d3f6b7ece1a6253ef1b59.jpg - 257 SHA256E-s7407--8ec4462ca6a05614378729bb20bb33c3b892bc943fd698389e44d959c4506843.log - 258 SHA256E-s1189946--d23ba452e6e267d93f6233e885bd6f9e15b8ad1aea4c3d2368d901428df78970.jpg - 259 SHA256E-s3447000--61a3bd3f7dda48544b67040012d6cd5999499d25e75dc34b82d11955d0fc9b6a.jpg - 260 SHA256E-s3263208--69ad68aaad7058af8d14f7e4c03e5b52c9a78dbac7ffd33bd7bc5220c847d6bb.JPG - 261 SHA256E-s1226280--d372b699459664c382f607ff56294df49e6d8d0fcab90b509337c347943357cf.jpg - 262 SHA256E-s16890--12861c187e68e3591ccd5f708b935cc43bf25f5672daf50913e152c1c55e510c.png - 263 SHA256E-s1092669--8e7f7431c487c6cff11ee9f7c8a87aa0d057b518e60bd2b92fd677e5c9a88313.jpg - 264 SHA256E-s307511--5fad92167d8f9a7ed4076909a1540388cdae89df956e6011065526bfb10564a4.jpg - 265 SHA256E-s8334--212df98aca1ee3d4f10539a786ad746f3856c2715e23d5cb816a2374b5e6c43c.png - 266 SHA256E-s3375--2b403c31d4934895cccbe05556b0134bd4b78d4b873193d2b12a8893ab170681.txt - 267 SHA256E-s691014--470d607465715a4c0735d74da75a5aafb5f6707b9d10a9a6a8c002f095f447e2.jpg - 268 SHA256E-s680701--133c1dc67e394103d9f900cbf80ef508c7d7818edb23406c5f67f027a38093a4.jpg - 269 SHA256E-s4024--b5d3e2bb6d51ff8ceb54f501035a5feebe7d5178d35b98abe9e41531bd2abd22 - 270 SHA256E-s1117--b7c94c25be8e78468071e78481641927450d754fd1bbd8d0d751f116d02b9ab3 - 271 SHA256E-s476926--ea981873de3e0ca8156ff710429894abbd8a51384b210cc142b074ec9b2c9ba0.jpg - 272 SHA256E-s56655--7df6526b49b7aa986070db456b6a3a378c8aaaee8cb7c8892c154eecf401002a.com.htm - 273 SHA256E-s2963--4fc53b3029a595b3b7f1f201eb4b7c2df78afc7e083abccd070c8e6fae79a661.txt - 274 SHA256E-s761655--486ef18d41898ba80505d7630170305c4b58fa647786bd5447f20045bd6f3b2e.jpg - 275 SHA256E-s1389414--3599c1a4da6a3b61cbc4dc431c436af9bf201b634fde2f99ddf54eae8c3590d5.jpg - 276 SHA256E-s39678--bea819324e10bc288c75650e2196bebd5339952ce33574625ae5091ad749b63c.jpg - 277 SHA256E-s47531--a91ecea2694b4b5c8daab84aa25c675f2f73dbfaa8ccfd581d6868b1e2568b7a.jpg - 278 SHA256E-s4923--2f1b9afef156e9c7f4994106eda088868a992d92e66a5d601f77980fea80f777 - 279 SHA256E-s84101--bca6a8a9640b1ebfa8a2ba01b3a0f7ed20ad77fa5cbb5588d46ce75949fc38db.jpg - 280 SHA256E-s1245742--d547d4a18279ec671be7869896c0b3e763cf8499c4dc28a62a49cd657fdf4200.jpg - 281 SHA256E-s655461--f9b43d2794fe757d7cb61a704a01c85bc09eb20d70a1550d6934dec12f46f0bf.jpg - 282 SHA256E-s137484--51fbe9bc815e41dfe22b9f9d4ed8f3ca98a8cb5cc7b81522b296d45b0279a413.jpg - 283 SHA256E-s607392--ead4548b66ac3ab5c930cd89bd60de480184a4f23ffce9b5da24f9269b796283.jpg - 284 SHA256E-s6888--405748982bbb3340eea34acbe45085ea62c80767866f0c76c355e4f94b969c7c.png - 285 SHA256E-s4327767--eef5840e2f4294a125aaa3ed33f8ccc96c5c2c3e31cbee356013de354e628df9.pdf - 286 SHA256E-s411064--4e5e5d477ccc542f78649e4b4ee6aa132bf79ae9aeb64a46cb45a7ee133eb2f7.pdf - 287 SHA256E-s224149--204dbb62c5d5352c9b5baead124ecf52c6fffd49120343cc21bb10343353934e.jpg - 288 SHA256E-s1333719--9d9ac54db47723755ee0d19731c0b2f4b40074d946da4a1e283a4904feea4534.jpg - 289 SHA256E-s1889687--07b79ce21bf5ffe2d80f9878d338fcd63ddc92c5381eb3c290639c3e73a7b927.jpg - 290 SHA256E-s686131--93ba1a21ff8cc7d9baa61a2af8407ccc8c1b22705a191e9f0a393d14ec95e232.jpg - 291 SHA256E-s619954--3d900d39d16eca00287a0c4bbe20b46767867b5065260a4a1fa8444081998e25.jpg - 292 SHA256E-s828309--f1d702dcb350cff7a3229fe62c4f0f4beb5f95ad2f00a6fd1bfb82549cd08129.jpg - 293 SHA256E-s516404--0ca06e98fd119847c99bee56264a31ac99b36ae71136624018d308ff8c6a2e3d.jpg - 294 SHA256E-s783842--0618e7c3ebc7ff8fcdff82b9fd227e8b83f491e8e1b96c2d0e566fc7fbea27ea.jpg - 295 SHA256E-s20748--df0711c99c30b5fdcbfdd109c093f02f6a7f5196e7ffbc8e291bb2780c5735c0.css - 296 SHA256E-s61739--387a27967c79b09e21d93f8a8b969dda930e8d26e9ce379c1d71718d4cc5a1df.jpg - 297 SHA256E-s1461106--37222c3cd7a3af846c8aaed3a174a0a7e6f775ea4c08c4e2f792c6da724812b9.jpg - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -[2014-09-02 05:15:23 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - 11f0e77..fb4d2b8 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - fb4d2b8..490e8d4 annex/direct/master -> synced/master -error: duplicate parent 490e8d462bf7572cf44bf4fb6a820ed38d471a54 ignored -[2014-09-02 06:15:25 BST] NetWatcherFallback: Syncing with apollo -From apollo.aylett.co.uk:Annex/Family - fb4d2b8..490e8d4 master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 490e8d4..08b6a0a annex/direct/master -> synced/master -error: duplicate parent 08b6a0ab11b225b34261a4cd5962a6630eed4495 ignored -[2014-09-02 07:15:27 BST] NetWatcherFallback: Syncing with apollo -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory -gpg: Signature made Sun 31 Aug 2014 21:52:56 BST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -From apollo.aylett.co.uk:Annex/Family - 490e8d4..08b6a0a master -> apollo/master -To lizzie@apollo.aylett.co.uk:Annex/Family - 08b6a0a..69244bb annex/direct/master -> synced/master -error: duplicate parent 69244bbcf029c21782995b78cdfbff789c0d198e ignored -[2014-09-02 12:19:20 BST] NetWatcher: Syncing with apollo -ControlSocket /run/user/1000/ssh-apollo.aylett.co.uk-22-lizzie already exists, disabling multiplexing -From apollo.aylett.co.uk:Annex/Family - 08b6a0a..69244bb master -> apollo/master -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-09-02 12:20:01 BST] UpgradeWatcher: Upgrading git-annex -error: refs/heads/synced/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/heads/synced/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/heads/synced/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/heads/synced/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/git-annex does not point to a valid object! -error: refs/synced/5879379e-5514-11e3-b428-a79c7bfa61c8/master does not point to a valid object! -[2014-09-02 12:21:36 BST] NetWatcherFallback: Syncing with apollo -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -git-annex-shell: Only allowed to access ~/Music not ~/Annex/Family -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -"""]] - -> This is due to using an old and buggy version of git-annex. This bug was -> fixed 3 full months ago, in version 5.20140709. [[done]] --[[Joey]] diff --git a/doc/bugs/Assistant_removed_all_references_to_files/comment_1_1f7da19ea99c263d56db6331d4b1e346._comment b/doc/bugs/Assistant_removed_all_references_to_files/comment_1_1f7da19ea99c263d56db6331d4b1e346._comment deleted file mode 100644 index f3cfbaabe..000000000 --- a/doc/bugs/Assistant_removed_all_references_to_files/comment_1_1f7da19ea99c263d56db6331d4b1e346._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 1" - date="2014-09-11T17:45:31Z" - content=""" -Unfortunately, the old version of git-annex you have been using is exactly the wrong version, so you ran into this horrible bug, which is fixed in newer versions. - -<http://git-annex.branchable.com/bugs/bad_merge_commit_deleting_all_files/> - -That page has details, including instructions on how to recover your data. - -I hope that you were not using that old version because it's included in some distribution somewhere still? -"""]] diff --git a/doc/bugs/Assistant_removed_all_references_to_files/comment_2_0dbb8df1ad267d1c502646a7131a99f1._comment b/doc/bugs/Assistant_removed_all_references_to_files/comment_2_0dbb8df1ad267d1c502646a7131a99f1._comment deleted file mode 100644 index 932a88471..000000000 --- a/doc/bugs/Assistant_removed_all_references_to_files/comment_2_0dbb8df1ad267d1c502646a7131a99f1._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://andrew.aylett.co.uk/" - nickname="andrew" - subject="comment 2" - date="2014-09-11T19:03:07Z" - content=""" -Unfortunately, that bug involves merges while I'm seeing regular commits so I don't think it's identical. - -As to why I'm on that version, it appears that the updater and something in my environment conspired against me, leaving an old version in my path. I'll fix that now and let you know if I see the issue again. -"""]] diff --git a/doc/bugs/Bloom_filter_capacity_too_large_to_represent.mdwn b/doc/bugs/Bloom_filter_capacity_too_large_to_represent.mdwn deleted file mode 100644 index 56d3d8f8c..000000000 --- a/doc/bugs/Bloom_filter_capacity_too_large_to_represent.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. -When running git-annex info I get an error when it tries to show the bloom filter size - -### What steps will reproduce the problem? -git-annex info in my Photos repo - - -### What version of git-annex are you using? On what operating system? -[[!format sh """ -$ git-annex version -git-annex version: 5.20140814-g9b89b5c -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -"""]] - -### Please provide any additional information below. - -[[!format sh """ -$ git-annex info -repository mode: direct -trusted repositories: 2 - c0e4106e-2631-11e2-9749-1bfa37a61069 -- [rose] - ca735977-973c-44bc-9257-915b2c875e39 -- synology [here] -semitrusted repositories: 3 - 00000000-0000-0000-0000-000000000001 -- web - 7e5c0010-2634-4a5e-bc7b-6fea84b8b947 -- [glacier] - d7e01abc-d74b-40e2-8607-3d41ce8bc4bd -- seagate3 -untrusted repositories: 1 - c1fe5922-43f1-11e2-b146-33530f7fa6cc -- x200s -transfers in progress: none -available local disk space: 928.4 gigabytes (+1 megabyte reserved) -local annex keys: 34758 -local annex size: 186.78 gigabytes -annexed files in working tree: 35300 -size of annexed files in working tree: 193.76 gigabytes -bloom filter size: git-annex: Data.BloomFilter.Util.suggestSizing: capacity too large to represent -"""]] - -> I've worked around this problem in the arm autobuilder (only build -> affected), so [[done]] --[[Joey]] diff --git a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_1_43c824a3b843faa2377bfd78158c72fe._comment b/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_1_43c824a3b843faa2377bfd78158c72fe._comment deleted file mode 100644 index 0bf00d7d5..000000000 --- a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_1_43c824a3b843faa2377bfd78158c72fe._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 1" - date="2014-09-12T16:03:09Z" - content=""" -It seems you must have tweaked the annex.bloomcapacity and/or annex.bloomaccuracy settings, probably to some quite large values. - -For example capacity of 50000000 and accuracy of 10000000000 will fail this way. - -This happens when it runs out of Double floating point precision to calculate the requested bloom filter size. I think that a bloom filter can be built that has this capacity/accuracy, it's just that Data.BloomFilter.Easy.safeSuggestSizing falls over trying to find the bloom filter size. Also, such a bloom filter may use rather a lot of memory.. - - -"""]] diff --git a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_2_9b74457549e2739ae45dccd128de946f._comment b/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_2_9b74457549e2739ae45dccd128de946f._comment deleted file mode 100644 index 803465e01..000000000 --- a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_2_9b74457549e2739ae45dccd128de946f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 2" - date="2014-09-12T16:34:56Z" - content=""" -However, in Greg's case he had no such configuration. Instead, I think something is broken with the use of floating point or bit math that bloomfilter uses, on the NAS where he's using git-annex. - -I have made git-annex not crash when this happens, just show a warning and fall back to a reasonable default bloom filter size. If the problem is with the bit math, then the bloom filter may not work either, which would probably show up as false negatives, so `git annex unused` not finding things that are unused. - -I need to update the armel build with this so Greg can test it.. -"""]] diff --git a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_3_5790bbbe347e1806062ccb60fcad046a._comment b/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_3_5790bbbe347e1806062ccb60fcad046a._comment deleted file mode 100644 index a11d0efc7..000000000 --- a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_3_5790bbbe347e1806062ccb60fcad046a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 3" - date="2014-09-12T16:38:47Z" - content=""" -I have reproduced the bug, using the standalone build on an arm box (turtle). - -On the same box, the debian git-annex build works ok. - -Suggests to me the problem is related to the cross-compiling method used for the standalone arm build. -"""]] diff --git a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_4_9fb9fdbc6218d6b86b0921f411f78891._comment b/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_4_9fb9fdbc6218d6b86b0921f411f78891._comment deleted file mode 100644 index 77097e07c..000000000 --- a/doc/bugs/Bloom_filter_capacity_too_large_to_represent/comment_4_9fb9fdbc6218d6b86b0921f411f78891._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="turns out to be an upstream bug already filed" - date="2014-09-12T17:46:23Z" - content=""" -It seems that this is a bug on bloomfilter 2.0.0.0 on armel generally. It's also preventing this newer version from building on armel currently: - -<http://bugs.debian.org/756801> - -The git-annex standalone arm autobuilder installed it with cabal, so ended up with the newer, broken version. -"""]] diff --git a/doc/bugs/Box.com_ReposnseTimeout.mdwn b/doc/bugs/Box.com_ReposnseTimeout.mdwn deleted file mode 100644 index 4beb6999c..000000000 --- a/doc/bugs/Box.com_ReposnseTimeout.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -Box.com is still not working properly in version 5.20140227 (I'm using it in Debian testing and sid). - -I created a new clean repository and configured Box.com (everything from the webapp). At first it seamed to work, files where being uploaded and the logs where fine. Then I created another clean repository in another computer and started syncing. Downloading files worked properly, but when trying to upload a file from the second computer I got this: - - copy my_file (gpg) (checking box.com...) (to box.com...) - 100% 0.0 B/s 0sResponseTimeout - failed - git-annex: copy: 1 failed - -When I got back to the first computer I saw the same behavior, uploading files wasn't working any more. - -> [[duplicate|done]] --[[Joey]] diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_1_4ac0bf61fb4b2ac335a8a1f29e9d882d._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_1_4ac0bf61fb4b2ac335a8a1f29e9d882d._comment deleted file mode 100644 index 062fbfac6..000000000 --- a/doc/bugs/Box.com_ReposnseTimeout/comment_1_4ac0bf61fb4b2ac335a8a1f29e9d882d._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8" - nickname="Jon Ander" - subject="comment 1" - date="2014-03-01T11:23:05Z" - content=""" -I have another error log: - - 29% 653.2KB/s 1m49sgpg: [stdout]: write error: Broken pipe - gpg: DBG: deflate: iobuf_write failed - gpg: build_packet failed: file write error - gpg: [stdout]: write error: Broken pipe - gpg: iobuf_flush failed on close: file write error - gpg: symmetric encryption of `[stdin]' failed: file write error - ResponseTimeout - git-annex: fd:96: hPutBuf: resource vanished (Broken pipe) - ResponseTimeout - -Some files (very few) are being uploaded properly, so the error is not always reproducible. -"""]] diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_2_29d8a9fa8d385a08fa70337baaba462c._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_2_29d8a9fa8d385a08fa70337baaba462c._comment deleted file mode 100644 index 864731a47..000000000 --- a/doc/bugs/Box.com_ReposnseTimeout/comment_2_29d8a9fa8d385a08fa70337baaba462c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 2" - date="2014-03-05T03:15:43Z" - content=""" -I suspect this is just box.com's webdav support being flakey. - -It's possible there's a timeout that's too aggressive in the http library. I have had some trouble with that when trying to use DAV over a slow connection. -"""]] diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment deleted file mode 100644 index e6585b6a2..000000000 --- a/doc/bugs/Box.com_ReposnseTimeout/comment_3_b73450b3a9728ac6f34f0e63255f6fa9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!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. -"""]] diff --git a/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment b/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment deleted file mode 100644 index c95d3ceb4..000000000 --- a/doc/bugs/Box.com_ReposnseTimeout/comment_4_0bd9eb5947a21d0657e79cf276923bb5._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!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.]] -"""]] diff --git a/doc/bugs/Bug_Report_doesn__39__t_work.mdwn b/doc/bugs/Bug_Report_doesn__39__t_work.mdwn deleted file mode 100644 index cbf4a481d..000000000 --- a/doc/bugs/Bug_Report_doesn__39__t_work.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -### Please describe the problem. -Bug Report doesn't work - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -[[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Build_error_when_S3_is_disabled.mdwn b/doc/bugs/Build_error_when_S3_is_disabled.mdwn deleted file mode 100644 index 2ae38659d..000000000 --- a/doc/bugs/Build_error_when_S3_is_disabled.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -With release 5.20141203, I'm getting the following build error. - - Remote/Helper/AWS.hs:15:18: - Could not find module ‘Aws’ - Use -v to see a list of the files searched for. - - Remote/Helper/AWS.hs:16:18: - Could not find module ‘Aws.S3’ - Use -v to see a list of the files searched for. - -I'm installing dependencies with cabal but have disabled S3 support -('-f-S3'). This setup has worked for previous releases (I'm on a machine running Arch Linux). - - _features=(-f-Android - -f-Assistant - -fDbus - -fDNS - -fInotify - -fPairing - -fProduction - -f-S3 - -fTestSuite - -fTDFA - -f-Webapp - -f-WebDAV - -fXMPP - -fFeed - -fQuvi - -fCryptoHash) - - cabal update - cabal install c2hs - - cabal install --user --force-reinstalls --only-dependencies "${_features[@]}" - cabal configure "${_features[@]}" - - make - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Build_error_with_Yesod_1.4.mdwn b/doc/bugs/Build_error_with_Yesod_1.4.mdwn deleted file mode 100644 index dbee2654e..000000000 --- a/doc/bugs/Build_error_with_Yesod_1.4.mdwn +++ /dev/null @@ -1,287 +0,0 @@ -### Please describe the problem. -I have problems building with yesod 1.4 - -### What steps will reproduce the problem? -Building git annex in a clean sandbox. - -### What version of git-annex are you using? On what operating system? -5.20140927 on OS X i.e. Trying to upgrade the homebrew recipe to the most recent version of git-annex - -### Please provide any additional information below. -Error messages below are discussed in the following SO-thread: -https://stackoverflow.com/questions/26225991/illegal-view-pattern-frompathpiece-just-dyn-abdd-when-using-parameters-on - - -[[!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 -[310 of 470] Compiling Assistant.WebApp.Types ( Assistant/WebApp/Types.hs, dist/dist-sandbox-52ca649e/build/git-annex/git-annex-tmp/Assistant/WebApp/Types.o ) - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_aceZO - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_aceZW - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf02 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0c - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0e - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0f - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0h - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0j - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0l - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0n - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0p - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0r - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0u - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0w - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0y - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0z - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0C - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0D - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0F - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0H - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0J - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0L - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0M - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0O - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0R - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0T - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf0U - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf11 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf13 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf18 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1a - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1c - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1e - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1g - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1i - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1k - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1m - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1o - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1q - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1s - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1v - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1x - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1z - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1B - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1D - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1G - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1I - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1J - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1L - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1M - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1O - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1R - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1U - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1X - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf1Y - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf20 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf22 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf25 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf27 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf28 - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf2b - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf2d - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf2f - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf2h - Use ViewPatterns to enable view patterns - -Assistant/WebApp/Types.hs:40:1: - Illegal view pattern: fromPathPiece -> Just dyn_acf2j - Use ViewPatterns to enable view patterns -cabal: Error: some packages failed to install: -git-annex-5.20140927 - - -# End of transcript or log. -"""]] - -> You're not building the most recent version of git-annex; this was -> already fixed in version 5.20141013. [[done]] --[[Joey]] diff --git a/doc/bugs/Build_error_with_Yesod_1.4/comment_1_42fe9d62c9dcc55deea35d16b67177e6._comment b/doc/bugs/Build_error_with_Yesod_1.4/comment_1_42fe9d62c9dcc55deea35d16b67177e6._comment deleted file mode 100644 index 145b5b1ea..000000000 --- a/doc/bugs/Build_error_with_Yesod_1.4/comment_1_42fe9d62c9dcc55deea35d16b67177e6._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw" - nickname="Carl" - subject="Not on hackage" - date="2014-10-15T15:34:02Z" - content=""" -I stand corrected, but it seems this release is not on hackage? -"""]] diff --git a/doc/bugs/Build_error_with_Yesod_1.4/comment_2_05f6fb19f2527f6dd72ab0e2f87c021a._comment b/doc/bugs/Build_error_with_Yesod_1.4/comment_2_05f6fb19f2527f6dd72ab0e2f87c021a._comment deleted file mode 100644 index 4f671d0b4..000000000 --- a/doc/bugs/Build_error_with_Yesod_1.4/comment_2_05f6fb19f2527f6dd72ab0e2f87c021a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.111" - subject="comment 2" - date="2014-10-15T17:30:45Z" - content=""" -Hmm, yeah, it seems the upload to hackage failed, because hackage still rejects cabal files mentioning the legal os(gnu). Sigh. Fixed now. -"""]] diff --git a/doc/bugs/Build_fails_when_no_wget_avalible.mdwn b/doc/bugs/Build_fails_when_no_wget_avalible.mdwn deleted file mode 100644 index 565060518..000000000 --- a/doc/bugs/Build_fails_when_no_wget_avalible.mdwn +++ /dev/null @@ -1,46 +0,0 @@ -### Please describe the problem. - -When trying to build git-annex 5.21050113 in a clean cabal sandbox on OSX and not having wget avalible, breaks the configure step of the build. See excerpt of build log below. - -I am not sure if it is a bug or not, from the debian dependencies it seems that wget is required, but from reading various pieces of the documentation it seems to only be recommended. Installing wget makes it build. - -### What steps will reproduce the problem? - - - -### What version of git-annex are you using? On what operating system? - -5.20150113 on OSX Yosemite. - -### Please provide any additional information below. - -[[!format sh """ - checking version...fatal: Not a git repository (or any of the parent directories): .git - 5.20150113 - checking UPGRADE_LOCATION... not available - checking git... yes - checking git version... 2.2.1 - checking cp -a... yes - checking cp -p... yes - checking cp --preserve=timestamps... no - checking cp --reflink=auto... no - checking xargs -0... yes - checking rsync... yes - checking curl... yes - checking wget... no - checking wget supports -q --show-progress...setup: wget: does not exist -cabal: Error: some packages failed to install: -git-annex-5.20150113 failed during the configure step. The exception was: -ExitFailure 1 - - -# End of transcript or log. -"""]] - --- Carl - -> wget is not intended to be a hard build dependency. The Debian package -> should always be built with wget, so it's a build-dependency there. -> -> I've fixed the configure script to not crash in this situation. -> [[done]]. --[[Joey]] diff --git a/doc/bugs/Build_fails_when_no_wget_avalible/comment_1_c40db66d48d69d03847d73154faf3f59._comment b/doc/bugs/Build_fails_when_no_wget_avalible/comment_1_c40db66d48d69d03847d73154faf3f59._comment deleted file mode 100644 index 02888728a..000000000 --- a/doc/bugs/Build_fails_when_no_wget_avalible/comment_1_c40db66d48d69d03847d73154faf3f59._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw" - nickname="Carl" - subject="Thanks and question" - date="2015-01-16T20:14:32Z" - content=""" -Thanks for the quick fix. - -Is there any advantage in using wget over curl, for git-annex (when it comes to progress bars etc or are they just as good? -"""]] diff --git a/doc/bugs/Build_fails_when_no_wget_avalible/comment_2_f98ce0d40c60ea37f6174117bb7cef9f._comment b/doc/bugs/Build_fails_when_no_wget_avalible/comment_2_f98ce0d40c60ea37f6174117bb7cef9f._comment deleted file mode 100644 index a7eafe197..000000000 --- a/doc/bugs/Build_fails_when_no_wget_avalible/comment_2_f98ce0d40c60ea37f6174117bb7cef9f._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 2" - date="2015-01-16T20:38:57Z" - content=""" -git-annex defaults to wget when both are available, but curl works equally well. -"""]] diff --git a/doc/bugs/Build_failure_at_commit_1efe4f3.mdwn b/doc/bugs/Build_failure_at_commit_1efe4f3.mdwn deleted file mode 100644 index ba87b1191..000000000 --- a/doc/bugs/Build_failure_at_commit_1efe4f3.mdwn +++ /dev/null @@ -1,45 +0,0 @@ -Applying this - -<pre> -laplace:git-annex jtang$ git diff -diff --git a/Assistant/WebApp/Configurators.hs b/Assistant/WebApp/Configurators.hs -index b9630b1..bf36e59 100644 ---- a/Assistant/WebApp/Configurators.hs -+++ b/Assistant/WebApp/Configurators.hs -@@ -101,7 +101,7 @@ checkRepositoryPath p = do - - - - If run in another directory, the user probably wants to put it there. -} - defaultRepositoryPath :: Bool -> IO FilePath --defaultRepositoryPath firstrun = do -+defaultRepositoryPath firstRun = do - cwd <- liftIO $ getCurrentDirectory - home <- myHomeDir - if home == cwd && firstRun -</pre> - -Causes this to occur, - -<pre> -Assistant/WebApp/Configurators.hs:114:17: - Couldn't match expected type `Control.Monad.Trans.RWS.Lazy.RWST - (Maybe (Env, FileEnv), WebApp, [Yesod.Form.Types.Lang]) - Enctype - Ints - (GHandler WebApp WebApp) - t0' - with actual type `Text' - Expected type: String - -> Control.Monad.Trans.RWS.Lazy.RWST - (Maybe (Env, FileEnv), WebApp, [Yesod.Form.Types.Lang]) - Enctype - Ints - (GHandler WebApp WebApp) - t0 - Actual type: String -> Text - In the first argument of `(.)', namely `T.pack' - In the first argument of `(<$>)', namely - `T.pack . addTrailingPathSeparator' -make: *** [git-annex] Error 1 -</pre> - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Build_failures_with_7.10.mdwn b/doc/bugs/Build_failures_with_7.10.mdwn deleted file mode 100644 index e733ad1a7..000000000 --- a/doc/bugs/Build_failures_with_7.10.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -git-annex fails to build in the NixOS builder - -### What steps will reproduce the problem? - -cabal build - -### What version of git-annex are you using? On what operating system? - -5.20150812 - -### Please provide any additional information below. - -[The build log](http://hydra.cryp.to/build/1099681/nixlog/1/raw) has a full transcript of the build from one of the build machines, though I have reproduced this locally. - -The pertinent bit of the log (which is *not* at the end, though I think that's just a capture-both-stderr-and-stdin thing, since it was at the end when I repro'd it: - -[[!format sh """ -Assistant/WebApp/Types.hs:39:1: ‘WebApp’ is not in scope at a reify -"""]] - -If I'm reading things correctly (you can do some diffing of the inputs from [the page for the build](http://hydra.cryp.to/build/1099681)), I'm going to guess that it was the upgrade to yesod-1.4.14. - -I'll continue to look into it, but it would seem to touch on TH and Yesod stuff with which I am largely unfamiliar. - -> Fixed with mdorman's patch, [[done]] (will push a release in a day or 2) --[[Joey]] diff --git a/doc/bugs/Build_failures_with_7.10/comment_1_3ef2d6bcc66d57140777e6262467a40a._comment b/doc/bugs/Build_failures_with_7.10/comment_1_3ef2d6bcc66d57140777e6262467a40a._comment deleted file mode 100644 index 38652d880..000000000 --- a/doc/bugs/Build_failures_with_7.10/comment_1_3ef2d6bcc66d57140777e6262467a40a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="mdorman@ddbe259e8f6e03351350a04515c67f7957abf736" - nickname="mdorman" - subject="In fact, the problem *is* the yesod update" - date="2015-08-22T10:37:20Z" - content=""" -Per https://github.com/yesodweb/yesod/issues/1059, it would appear that all you would need to do is reorder some declarations---though that was my first thought and I thought I tried it and it failed, perhaps I got something else wrong in doing so. I'll report back when I have more info. -"""]] diff --git a/doc/bugs/Build_failures_with_7.10/comment_2_d3b68bbf83d9e83f93fc10a588e127f5._comment b/doc/bugs/Build_failures_with_7.10/comment_2_d3b68bbf83d9e83f93fc10a588e127f5._comment deleted file mode 100644 index dde4b4f94..000000000 --- a/doc/bugs/Build_failures_with_7.10/comment_2_d3b68bbf83d9e83f93fc10a588e127f5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="mdorman@ddbe259e8f6e03351350a04515c67f7957abf736" - nickname="mdorman" - subject="Fix for this issue" - date="2015-08-23T17:26:34Z" - content=""" -[My yesod-core-fix branch](https://github.com/mdorman/git-annex/tree/yesod-core-fix) has as its HEAD the (super-simplistic) fix for this issue. -"""]] diff --git a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them.mdwn b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them.mdwn deleted file mode 100644 index c3da3f5c1..000000000 --- a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -### Please describe the problem. -Some filenames in doc have a colon `(:)` in them and it seems it's not allowed on Windows. - -There's no hurry with this since I was able to clone the repo by doing a fork on Github and removing `doc/`. - -### What steps will reproduce the problem? - -[[!format sh """ -D:\tmp> git clone git://git-annex.branchable.com/ -Cloning into 'git-annex.branchable.com'... -remote: Counting objects: 72064, done. -remote: Compressing objects: 100% (18759/18759), done. -remote: Total 72064 (delta 52959), reused 72032 (delta 52944) -Receiving objects: 100% (72064/72064), 18.05 MiB | 2.39 MiB/s, done. -Resolving deltas: 100% (52959/52959), done. -fatal: cannot create directory at 'doc/bugs/3.20121112:_build_error_in_assistant': Invalid argument -D:\tmp> -"""]] - -> [[wontfix|done]] --[[Joey]] diff --git a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_1_5fc1347f4bcc13c9f8dbc5ecd4847fc7._comment b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_1_5fc1347f4bcc13c9f8dbc5ecd4847fc7._comment deleted file mode 100644 index 59bfd629b..000000000 --- a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_1_5fc1347f4bcc13c9f8dbc5ecd4847fc7._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-06-10T16:22:00Z" - content=""" -IMHO this is a bug in msysgit. It should support git repositories containing any legal filenames. - -Luckily, there is another git for Windows that does. It comes with Cygwin. You need Cygwin to build git-annex on Windows, anyway. - -So, I do not plan to do anything in git-annex to address this. -"""]] diff --git a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_2_38696178e658d1d32deec37dbea66a3d._comment b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_2_38696178e658d1d32deec37dbea66a3d._comment deleted file mode 100644 index fa9bd3dd3..000000000 --- a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_2_38696178e658d1d32deec37dbea66a3d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXm4VZC7ekVOXHGKjBObojiHB2E1kmMgA" - nickname="Leonardo" - subject="comment 2" - date="2013-08-11T21:21:56Z" - content=""" -Files with colon are not allowed in windows, they are interpreted as absolute path. The fact that you can checkout them \"fine\" (actually, their name get truncated to whatever was before the colon) using cygwin's GIT implementation is to be interpreted as a bug in cygwin's GIT in my opinion. I suggest renaming them before cygwin get fixed. -"""]] diff --git a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_3_f34d996827f5e7662bec409cbcce961b._comment b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_3_f34d996827f5e7662bec409cbcce961b._comment deleted file mode 100644 index 14cfa2686..000000000 --- a/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_3_f34d996827f5e7662bec409cbcce961b._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.63" - subject="comment 3" - date="2013-08-24T19:27:57Z" - content=""" -Leonardo, you made me boot up my windows machine just to check if cygwin git truncated files at the colon. It does not. - -AFAIK, Cygwin transliterates colons to another unicode character or something like that. I would be highly surprised if the Cygwin people consider this feature to be a bug. - -Since you need Cygwin to build git-annex on Windows anyway (though not to run it!), this remains WONTFIX. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library.mdwn b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library.mdwn deleted file mode 100644 index 5f7e490ca..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -### Please describe the problem. -I have lots of content stored in Amazon S3. Using git-annex from before commit 911ba8d972e4e7b151385d30c198598e1a0dfaca, I am able to ``git annex get`` from S3 and files are downloaded. -Using a more recent version (eg that commit, or the current master, or release 20150409), I am unable to download the content. - -I'm not sure if my repo or remote is somehow misconfigured, or if there's something else going on here. - ---Walter - -### What steps will reproduce the problem? -Use a version of git-annex with s3-aws - -### What version of git-annex are you using? On what operating system? -Debian, versions as above - -### 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 - -git annex get . --from cloud --debug -[2015-04-19 22:23:37 BST] read: git ["--git-dir=../../../.git","--work-tree=../../..","--literal-pathspecs","show-ref","git-annex"] -[2015-04-19 22:23:37 BST] read: git ["--git-dir=../../../.git","--work-tree=../../..","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] -[2015-04-19 22:23:37 BST] read: git ["--git-dir=../../../.git","--work-tree=../../..","--literal-pathspecs","log","refs/heads/git-annex..a51a912223d3d86f19762e387e3eae23c3024d2c","-n1","--pretty=%H"] -[2015-04-19 22:23:37 BST] chat: git ["--git-dir=../../../.git","--work-tree=../../..","--literal-pathspecs","cat-file","--batch"] -[2015-04-19 22:23:37 BST] read: git ["--git-dir=../../../.git","--work-tree=../../..","--literal-pathspecs","ls-files","--cached","-z","--","."] -get IMG_7079.JPG (from cloud...) [2015-04-19 22:23:37 BST] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--decrypt"] - -failed -get IMG_7080.JPG (from cloud...) -failed - - - -git annex info cloud -remote: cloud -description: [cloud] -uuid: be992080-b1db-11e1-8f79-1b10bb4092ef -trust: semitrusted -cost: 250.0 -type: S3 -creds: embedded in git repository (gpg encrypted) -bucket: ffffffffffffffffffffffffff -partsize: unlimited -encryption: encrypted (to gpg keys: FFFFFFFFFFFF) (hybrid mode) -chunking: none -remote annex keys: 0 -remote annex size: 0 bytes - - -git annex fsck -f cloud -fsck IMG_6876.JPG (checking cloud...) (StatusCodeException (Status {statusCode = 301, statusMessage = "Moved Permanently"}) [("x-amz-request-id","275ADF5B1B77D514"),("x-amz-id-2","flWGBHOZYEZAohygAzBIZAYd7nBGkm3HpSMfJuhgRp3txXx20yJz7S4yRlNLwCs1cHUMyWc9JbA="),("Content-Type","application/xml"),("Transfer-Encoding","chunked"),("Date","Sun, 19 Apr 2015 22:23:15 GMT"),("Server","AmazonS3")] (CJ {expose = []})) failed - - - -# End of transcript or log. -"""]] - -> I think I've made all the git-annex improvements that are going to come -> from this bug report. There's still the open bug on the aws library to better -> follow these redirects. Anyway, I think it makes sense to call this -> bug [[done]]. --[[Joey]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_11_f30f86482d48ff8d658a4ee74d4c8586._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_11_f30f86482d48ff8d658a4ee74d4c8586._comment deleted file mode 100644 index 2f2a3f0c6..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_11_f30f86482d48ff8d658a4ee74d4c8586._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 11" - date="2015-04-23T20:29:17Z" - content=""" -I think I may have not been entirely clear previously; the file \"GPGHMACSHA1--417830f4c50a2887674917abd2c18c522853255a\" was not in the bucket, but git annex said it was. That is, the upload failed, but git annex thought it succeeded. - -Similarly, all the files I recently added we not actually uploaded, but git annex thought they were. I ``git annex fsck``ed them, which was fast because it failed to download any of them. fscking other files is slow, as it has to download them of course. - -Maybe to reproduce this, you could try: - -[[!format sh \"\"\" -git annex initremote cloud datacenter=ap-southeast-1 -git annex add file -git annex copy --to cloud file -git annex drop file -git annex enableremote could dataceter=ap-southeast-2 -git annex get file -\"\"\"]] -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_1ba3271a62b8ce8088c67e4741ecf385._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_1ba3271a62b8ce8088c67e4741ecf385._comment deleted file mode 100644 index 3b416f09b..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_1ba3271a62b8ce8088c67e4741ecf385._comment +++ /dev/null @@ -1,32 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""fully reproduced""" - date="2015-04-24T16:33:02Z" - content=""" -I was able to fully reproduce this bug! I installed the old version of -git-annex that used the S3 library, and made a remote: - - joey@darkstar:~/tmp/rrold>git annex initremote S3 type=S3 encryption=none datacenter=ap-southeast-1 - initremote S3 (checking bucket...) (creating bucket in ap-southeast-1...) ok - joey@darkstar:~/tmp/rrold>git annex move me --to S3 - move me (checking S3...) (to S3...) - ok - -Retrieval then failed using current git-annex. - -Also, a remote made with the old git-annex with datacenter=ap-southeast-2 -fails with the new git-annex. - -Hypothesis: Either the new or the old S3 library must be confusing between -ap-southeast-1/2. My guess is the old library was just creating and using -buckets in the wrong place, at least when told to use ap-southeast-*. - ---- - -I cannot reproduce anything about "the upload failed, but git annex thought it succeeded", -nor do I see any indications in comments 11 or 12 that git-annex's location -log is failing in any way. The sequence of commands in comment 11 ends with the -get failing, as it should, since the remote has been switched to a different -datacenter. I don't understand what you're seeing in comment #12 at all; -it seems to just show it getting a file successfully. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_a208344e552bfe6b8d9f409560c9a515._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_a208344e552bfe6b8d9f409560c9a515._comment deleted file mode 100644 index 030e82d9d..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_12_a208344e552bfe6b8d9f409560c9a515._comment +++ /dev/null @@ -1,61 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 12" - date="2015-04-23T21:03:36Z" - content=""" -For completeness, here is the output when I get a file that *is* properly in the bucket (and you could use for any further testing you need to do). - -While this may have been caused by some misconfiguration on my part (though I'm not entirely sure how that could happen, strangely it would be easier to muck up now enableremote doesn't create a new bucket), I feel the potential harm here (the location information being wrong) is quite serious. (I'm sure this point does not escape you). - -[[!format sh \"\"\" ->git annex get --force --debug file.jpg --from cloud -[2015-04-23 21:52:41 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-23 21:52:41 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-23 21:52:41 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..cb0f954d09e3ea28171434e0e7499c84d1722fce\",\"-n1\",\"--pretty=%H\"] -[2015-04-23 21:52:41 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..573f75e01681e9bf2b513bc85e18fc250298a4d3\",\"-n1\",\"--pretty=%H\"] -[2015-04-23 21:52:41 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-23 21:52:41 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"file.jpg\"] -[2015-04-23 21:52:41 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] -(checking cloud...) [2015-04-23 21:52:42 BST] String to sign: \"HEAD\n\n\nThu, 23 Apr 2015 20:52:42 GMT\n/BUCKET/GPGHMACSHA1--08b3dee71059819e3558ac9ef8b82ad87e2d8951\" -[2015-04-23 21:52:42 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-23 21:52:42 BST] Path: \"/GPGHMACSHA1--08b3dee71059819e3558ac9ef8b82ad87e2d8951\" -[2015-04-23 21:52:42 BST] Query string: \"\" -[2015-04-23 21:52:42 BST] Response status: Status {statusCode = 200, statusMessage = \"OK\"} -[2015-04-23 21:52:42 BST] Response header 'x-amz-id-2': 'f8bEclNud1KNHevvGPVHutG3V0TH/ixnMSuu3NBhEKRrWaUYtENbKyA5PyxCdSrz0REgq/Bgu1w=' -[2015-04-23 21:52:42 BST] Response header 'x-amz-request-id': '7A344C3C3A27308E' -[2015-04-23 21:52:42 BST] Response header 'Date': 'Thu, 23 Apr 2015 20:52:43 GMT' -[2015-04-23 21:52:42 BST] Response header 'Last-Modified': 'Fri, 31 Oct 2014 07:03:03 GMT' -[2015-04-23 21:52:42 BST] Response header 'ETag': '\"66a85b0007a52d82e5bd29192ebdb510\"' -[2015-04-23 21:52:42 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-23 21:52:42 BST] Response header 'Content-Type': '' -[2015-04-23 21:52:42 BST] Response header 'Content-Length': '46058' -[2015-04-23 21:52:42 BST] Response header 'Server': 'AmazonS3' -[2015-04-23 21:52:42 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> -get file.jpg (from cloud...) -[2015-04-23 21:52:42 BST] String to sign: \"GET\n\n\nThu, 23 Apr 2015 20:52:42 GMT\n/BUCKET/GPGHMACSHA1--08b3dee71059819e3558ac9ef8b82ad87e2d8951\" -[2015-04-23 21:52:42 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-23 21:52:42 BST] Path: \"/GPGHMACSHA1--08b3dee71059819e3558ac9ef8b82ad87e2d8951\" -[2015-04-23 21:52:42 BST] Query string: \"\" -[2015-04-23 21:52:43 BST] Response status: Status {statusCode = 200, statusMessage = \"OK\"} -[2015-04-23 21:52:43 BST] Response header 'x-amz-id-2': 'LRDMgQAj+F81m3UqDebJ5CoZdyM/c2tMaFUvhjn8kjqq3x2Evy7O+wgLUiwE7lqascd0yrHR+xA=' -[2015-04-23 21:52:43 BST] Response header 'x-amz-request-id': '068D946E995E7473' -[2015-04-23 21:52:43 BST] Response header 'Date': 'Thu, 23 Apr 2015 20:52:44 GMT' -[2015-04-23 21:52:43 BST] Response header 'Last-Modified': 'Fri, 31 Oct 2014 07:03:03 GMT' -[2015-04-23 21:52:43 BST] Response header 'ETag': '\"66a85b0007a52d82e5bd29192ebdb510\"' -[2015-04-23 21:52:43 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-23 21:52:43 BST] Response header 'Content-Type': '' -[2015-04-23 21:52:43 BST] Response header 'Content-Length': '46058' -[2015-04-23 21:52:43 BST] Response header 'Server': 'AmazonS3' -[2015-04-23 21:52:43 BST] Response metadata: S3: request ID=068D946E995E7473, x-amz-id-2=LRDMgQAj+F81m3UqDebJ5CoZdyM/c2tMaFUvhjn8kjqq3x2Evy7O+wgLUiwE7lqascd0yrHR+xA= -99% 22.5KB/s 0s[2015-04-23 21:52:44 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--batch\",\"--passphrase-fd\",\"14\",\"--decrypt\"] -ok -[2015-04-23 21:52:44 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"hash-object\",\"-w\",\"--stdin-paths\",\"--no-filters\"] -[2015-04-23 21:52:44 BST] feed: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"update-index\",\"-z\",\"--index-info\"] -[2015-04-23 21:52:44 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -(recording state in git...) -[2015-04-23 21:52:44 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"write-tree\"] -[2015-04-23 21:52:44 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"commit-tree\",\"444e504a0ab73d01df08ef731e691205cfd485f5\",\"--no-gpg-sign\",\"-p\",\"refs/heads/git-annex\"] -[2015-04-23 21:52:44 BST] call: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"update-ref\",\"refs/heads/git-annex\",\"6e57ed008525cd58641c54a5ac6f07a960a7dc5c\"] -\"\"\"]] -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_14_035a933289f95c365ce2c851f6946181._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_14_035a933289f95c365ce2c851f6946181._comment deleted file mode 100644 index 96d212a39..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_14_035a933289f95c365ce2c851f6946181._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 14" - date="2015-04-24T20:13:31Z" - content=""" -Playing around with it, I also can't reproduce it (using new or old versions of git-annex; it may be, as you allude, a problem in an old version of the s3 library). - -Anyway, I'm happy that it's working now. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_16_2f16c63e539e51d9d1c0f85605e6d1e8._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_16_2f16c63e539e51d9d1c0f85605e6d1e8._comment deleted file mode 100644 index e5141a30b..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_16_2f16c63e539e51d9d1c0f85605e6d1e8._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 16""" - date="2015-04-25T01:18:51Z" - content=""" -Investigating further, when I create a bucket with the AWS library -in ap-southeast-2, `s3cmd info` shows it is located there. - -When I create a bucket with hS3 in ap-southeast-2, I get this -interesting output: - - joey@darkstar:~>s3cmd info s3://s3-43302240-076c-4420-8099-f2ef0b517e5f - s3://s3-43302240-076c-4420-8099-f2ef0b517e5f/ (bucket): - Location: ap-southeast-2 - WARNING: Redirected to: s3-43302240-076c-4420-8099-f2ef0b517e5f.s3-ap-southeast-2.amazonaws.com - Expiration Rule: none - policy: none - ACL: joeyhess: FULL_CONTROL - -So, it's apparently in the datacenter I asked for when making it, -but here's a redirect again. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_1_533c4a26200501486a9ec103e1301391._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_1_533c4a26200501486a9ec103e1301391._comment deleted file mode 100644 index 8921214a9..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_1_533c4a26200501486a9ec103e1301391._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-21T19:23:18Z" - content=""" -So the http 301 redirect seems to be the relevant clue. - -Perhaps the old S3 library followed such redirects and the new aws library -does not. Although AFAICS, http-client should follow redirects by default. - -Are you able to store new files in this remote and get them back out? - -Which Amazon datacenter is the bucket at? - -I've added some more debugging to the S3 remote; --debug will now -have it log the http requests and responses. Perhaps this will give us -more clues to the problem. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_2_24224679a1516e2852b43624c787f639._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_2_24224679a1516e2852b43624c787f639._comment deleted file mode 100644 index 2bafdf7ea..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_2_24224679a1516e2852b43624c787f639._comment +++ /dev/null @@ -1,63 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 2" - date="2015-04-21T22:53:21Z" - content=""" -It's in bucket ap-southeast-2, which conflicts with the info in the log below. I'm not sure why they disagree. - -This was a new file, which I also \"uploaded\" with a ``git annex copy --to cloud test_file``, and ``git annex whereis`` says is in cloud. However, using ``s3cmd`` to retrieve it (using the info from the log below), it claims it doesn't exist (404). So, I don't think it got uploaded correctly. I don't seem to get any useful logs when forcing an upload with ``--debug`` (as in no S3-related logs, but I've included that at the very bottom). - -[[!format sh \"\"\" -> git annex get test_file -get test_file (from cloud...) - - Unable to access these remotes: cloud - - Try making some of these repositories available: - be992080-b1db-11e1-8f79-1b10bb4092ef -- [cloud] - - (Note that these git remotes have annex-ignore set: origin) -failed -git-annex: get: 1 failed -walter@kronos:~/NewPics$ git annex get test_file --debug -[2015-04-21 23:39:57 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"test_file\"] -get test_file [2015-04-21 23:39:57 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-21 23:39:57 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-21 23:39:57 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..347f154f5dfa9e41dc459eda328421741e1e90a6\",\"-n1\",\"--pretty=%H\"] -[2015-04-21 23:39:57 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..83793925a571a3228cc64e204598f8c54203b1f7\",\"-n1\",\"--pretty=%H\"] -[2015-04-21 23:39:57 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -(from cloud...) [2015-04-21 23:39:57 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] - -[2015-04-21 23:39:57 BST] String to sign: \"GET\n\n\nTue, 21 Apr 2015 22:39:57 GMT\n/BUCKETID/GPGHMACSHA1--417830f4c50a2887674917abd2c18c522853255a\" -[2015-04-21 23:39:57 BST] Host: \"BUCKETID.s3-ap-southeast-1.amazonaws.com\" -[2015-04-21 23:39:57 BST] Path: \"/GPGHMACSHA1--417830f4c50a2887674917abd2c18c522853255a\" -[2015-04-21 23:39:57 BST] Query string: \"\" -[2015-04-21 23:39:57 BST] Response status: Status {statusCode = 301, statusMessage = \"Moved Permanently\"} -[2015-04-21 23:39:57 BST] Response header 'x-amz-request-id': 'C2825FBB20ED22B4' -[2015-04-21 23:39:57 BST] Response header 'x-amz-id-2': 'I93feDTHOrPR+bwVqoMBuEEwYQAN7ZfjOq0jdIJ6ywzOPYYxTfqZg9OR+M0L+MFdilHKRJ+CEv8=' -[2015-04-21 23:39:57 BST] Response header 'Content-Type': 'application/xml' -[2015-04-21 23:39:57 BST] Response header 'Transfer-Encoding': 'chunked' -[2015-04-21 23:39:57 BST] Response header 'Date': 'Tue, 21 Apr 2015 22:39:56 GMT' -[2015-04-21 23:39:57 BST] Response header 'Server': 'AmazonS3' -[2015-04-21 23:39:57 BST] Response metadata: S3: request ID=C2825FBB20ED22B4, x-amz-id-2=I93feDTHOrPR+bwVqoMBuEEwYQAN7ZfjOq0jdIJ6ywzOPYYxTfqZg9OR+M0L+MFdilHKRJ+CEv8= - - Unable to access these remotes: cloud - - Try making some of these repositories available: - be992080-b1db-11e1-8f79-1b10bb4092ef -- [cloud] - - (Note that these git remotes have annex-ignore set: origin) -failed -git-annex: get: 1 failed - -> git annex copy --to cloud --force --debug test_file -[2015-04-21 23:47:24 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-21 23:47:24 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-21 23:47:24 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..347f154f5dfa9e41dc459eda328421741e1e90a6\",\"-n1\",\"--pretty=%H\"] -[2015-04-21 23:47:24 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..83793925a571a3228cc64e204598f8c54203b1f7\",\"-n1\",\"--pretty=%H\"] -[2015-04-21 23:47:24 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-21 23:47:24 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"test_file\"] - -\"\"\"]] -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_3_9665a868f786afa445f5e3b0fbd20011._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_3_9665a868f786afa445f5e3b0fbd20011._comment deleted file mode 100644 index 8b92ca305..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_3_9665a868f786afa445f5e3b0fbd20011._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-04-23T17:00:20Z" - content=""" -ap-southeast-2 vs ap-southeast-1 must have something to do with this -problem. - -I tried making a S3 remote with datacenter=ap-southeast-2 and it didn't -have this problem, and used s3-ap-southeast-2.amazonaws.com, so doesn't -seem that git-annex is getting the mapping to endpoints wrong. - -I also tried forcing git-annex to use ap-southeast-1 instead of the right -datacenter, and I don't get a redirect, getting a file just fails in that -misconfiguration. - -So, it seems there is something special about your bucket; git-annex thinks -it's in ap-southeast-1, S3 apparently redirects to somewhere else. Sounds -like the AWS interface shows you the bucket is located in ap-southeast-2? - -This is looking more like a bug with the haskell-AWS library. If AWS can -send redirects here, it ought to follow them. It would be really helpful if -I had a way to reproduce the problem. Since your remote is encrypted -anyway, is there any chance you could generate AWS creds that I could use -to access that bucket to try to get files from it? - -(The `copy --to cloud` didn't do anything because git-annex already thinks -the file is there (--force has no effect on copy --to).) -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_b70a0075e61565e4501f0b5b143b222d._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_b70a0075e61565e4501f0b5b143b222d._comment deleted file mode 100644 index 2f862c560..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_b70a0075e61565e4501f0b5b143b222d._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-04-23T18:17:23Z" - content=""" -I agree, enableremote should not create the bucket. Made that change. Also, -`git annex info $s3remote` will show some more info about it, including its -endpoint. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_d37d9b008e2e8f570af86e620ad6064f._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_d37d9b008e2e8f570af86e620ad6064f._comment deleted file mode 100644 index b79f5812d..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_4_d37d9b008e2e8f570af86e620ad6064f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 4" - date="2015-04-23T17:58:14Z" - content=""" -I've sent an email regarding this. - -One comment, it seems that it's not possible to change the configuration of an S3 remote, as ``enableremote`` causes git-annex to try to create a new bucket (which fails, as the name is already used). Otherwise, I could try to tell git-annex it has the region wrong. Perhaps an option ``use-existing-bucket`` or something would work? -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_6_7caef30897eabf04faab12f4b4a16916._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_6_7caef30897eabf04faab12f4b4a16916._comment deleted file mode 100644 index fd55b5134..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_6_7caef30897eabf04faab12f4b4a16916._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-04-23T18:44:02Z" - content=""" -I reproduced the problem using the creds, and a modified version of -GetObject.hs from haskell-aws. - -I had to upgrade from aws-0.9.2 to 0.11.4 to see the 301 redirect in the -debug mesages, but both versions seemed to fail the same way, it's just the -newer version added more debugging output. - -There's an exception, which git-annex obscured: - - Response metadata: S3: request ID=5B5B9AE39E0C9729, x-amz-id-2=t6xToNbirPnwgEhTdbFr+Ncq5cGr3fMCRNq5WlFLjEk3ZJtan5aCotcsCS3GMTMgjsP/MNcOWUw= - GetObject: HeaderException {headerErrorMessage = "ETag missing"} - -I've seen this "ETag missing" before when an object was genuinely missing, but -I'm not sure what it indicates in this case. - -This was using s3-ap-southeast-1.amazonaws.com. If I use southeast-2, it -just fails with "NoSuchKey". So I think that the 1-vs-2 was a red herring; -git-annex is using the right endpoint. - -I have forwarded this bug report to: <https://github.com/aristidb/aws/issues/160> - -It might be good to get in touch with the haskell-aws maintainer and provide the -creds so they can reproduce it too. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_7_cd943597e319c94e91b17f24346be456._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_7_cd943597e319c94e91b17f24346be456._comment deleted file mode 100644 index 171b2b371..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_7_cd943597e319c94e91b17f24346be456._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 7""" - date="2015-04-23T18:59:10Z" - content=""" -Hrm, I get an identical error message if I try to request a file that -is certianly not there! - -So maybe the 301 is a red herring? -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_13f862524d4aa503fc998ede41617942._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_13f862524d4aa503fc998ede41617942._comment deleted file mode 100644 index 531e8c79d..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_13f862524d4aa503fc998ede41617942._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 8" - date="2015-04-23T19:02:18Z" - content=""" -Ok, so I did ``git annex enableremote cloud datacenter=ap-southeast-2``, and can now get files properly. So from that point of view it now works. And I guess that provides an easy way to reproduce (just set a working S3 remote to the wrong datacenter). I'm prepared to accept that this was something I did somehow (at some point I manually moved files from one S3 bucket (actually account) to another, but it seems that git-annex would have created the bucket, so I'm not sure how the datacenter could be wrong.) - -In any case, now I'm not sure exactly which files did get uploaded properly, so will run a ``fsck``. I guess it would be good to either return an error when this happens, or follow the redirect. - -Also, I really appreciate the quick response you have to bugs! -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_44915e2b9e871c16861223e1e2a0827b._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_44915e2b9e871c16861223e1e2a0827b._comment deleted file mode 100644 index dd6f2f7a6..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_8_44915e2b9e871c16861223e1e2a0827b._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 8""" - date="2015-04-23T19:06:02Z" - content=""" -Glad that resolved it, but I'm still confused why I can't seem to get the -test file when I have my test program use ap-southeast-2. (But maybe those -creds you gave me just don't let me or something..) - -If you're up for some sleuthing, you could check out the git-annex branch -and look through `git blame remotes.log`. And changes that git-annex ever -made to the config of the remote will be in the history of that file. -"""]] diff --git a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_9_769de1e47221dfb6c810665e3704bbb2._comment b/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_9_769de1e47221dfb6c810665e3704bbb2._comment deleted file mode 100644 index 788ccf7ed..000000000 --- a/doc/bugs/Can__39__t_get_content_from_S3_with_s3-aws_library/comment_9_769de1e47221dfb6c810665e3704bbb2._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 9" - date="2015-04-23T19:07:56Z" - content=""" -Is it possible to do a fast ``fsck`` on an S3 remote? Because I don't want to download all the files again, it would be nice to just have the option to check it it exists. - -I get a ``failed to download file from remote`` error when I try it. -"""]] diff --git a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote.mdwn b/doc/bugs/Can__39__t_initialize_Tahoe_special_remote.mdwn deleted file mode 100644 index 874ba5ba2..000000000 --- a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. - -I tried to add a Tahoe special remote as follows- -git annex initremote tahoe type=tahoe embedcreds=yes - -However, this fails and gives me an error saying that tahoe create-client failed because .tahoe is not empty (even when .tahoe did not previously exist). It seems like git-annex is creating a .tahoe/git-annex directory (which is empty) and then trying to run tahoe create-client, which fails because the .tahoe directory was already created by git-annex. - -### What steps will reproduce the problem? -1. Install tahoe and setup a plain git annex repo -2. export TAHOE_FURL=tahoe introducer url here -3. git annex initremote tahoe type=tahoe embedcreds=yes - - -### What version of git-annex are you using? On what operating system? -5.20141024~bpo70+1 on Tails 1.2.1 (Debian Wheezy 32-bit) - - -### 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 -$ git annex initremote tahoe type=tahoe embedcreds=yes - -initremote tahoe The base directory '/home/amnesia/.tahoe' is not empty. -To avoid clobbering anything, I am going to quit now. -Please use a different directory, or empty this one. -git-annex: tahoe create-client failed - -# End of transcript or log. -"""]] - -> So this was caused by an old version of tahoe-lafs. Might as -> well support older versions if we can easily, I suppose. -> -> I have gone ahead and changed git-annex to use ~/.tahoe-git-annex/ -> instead of ~/.tahoe/git-annex/ when setting up new remotes. -> Existing remote's configs will be unchanged. -> -> So, [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_1_b3733fd117aef7e80a4342492388af82._comment b/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_1_b3733fd117aef7e80a4342492388af82._comment deleted file mode 100644 index 9d6ef522c..000000000 --- a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_1_b3733fd117aef7e80a4342492388af82._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="zooko@0afad0e8b0168f9c2e504a0200ae2ccc1dcea7fe" - nickname="zooko" - subject="ticket to track this in the Tahoe-LAFS issue tracker" - date="2015-05-28T21:58:41Z" - content=""" -Here's a ticket in the Tahoe-LAFS issue tracker for us to track this issue: - -https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2437 -"""]] diff --git a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_2_31cde69bfff097f7c59e64abb973c3c8._comment b/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_2_31cde69bfff097f7c59e64abb973c3c8._comment deleted file mode 100644 index 0b2880934..000000000 --- a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_2_31cde69bfff097f7c59e64abb973c3c8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="zooko@0afad0e8b0168f9c2e504a0200ae2ccc1dcea7fe" - nickname="zooko" - subject="ticket to track this in the Ubuntu issue tracker" - date="2015-05-28T22:01:23Z" - content=""" -Here's a ticket in the Ubuntu issue tracker: https://bugs.launchpad.net/tahoe-lafs/+bug/1459847 -"""]] diff --git a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_3_5d4404f32f86ddabde31b5aed6fa1fd8._comment b/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_3_5d4404f32f86ddabde31b5aed6fa1fd8._comment deleted file mode 100644 index 955604777..000000000 --- a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_3_5d4404f32f86ddabde31b5aed6fa1fd8._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-06-02T19:19:26Z" - content=""" -I don't seem to have this problem using tahoe-lafs 1.10.0. What version do -you have, 1.9.2? - - joey@kite:~>tahoe -d .tahoe/git-annex/foo create-client --introducer FURL - Node created in '/home/joey/.tahoe/git-annex/foo' - Please set [node]nickname= in tahoe.cfg -"""]] diff --git a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_4_499d68e03431a8bd88405dc86bc92b84._comment b/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_4_499d68e03431a8bd88405dc86bc92b84._comment deleted file mode 100644 index e1578dac3..000000000 --- a/doc/bugs/Can__39__t_initialize_Tahoe_special_remote/comment_4_499d68e03431a8bd88405dc86bc92b84._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="shidash@f577ed77e11dcfd714258ba6b25aaf670515222b" - nickname="shidash" - subject="comment 4" - date="2015-06-05T12:25:01Z" - content=""" -Yeah, I'm using tahoe-lafs version 1.9.2 -"""]] diff --git a/doc/bugs/Can__39__t_start_on_Cyanogenmod_10.2_nightly.mdwn b/doc/bugs/Can__39__t_start_on_Cyanogenmod_10.2_nightly.mdwn deleted file mode 100644 index c28794622..000000000 --- a/doc/bugs/Can__39__t_start_on_Cyanogenmod_10.2_nightly.mdwn +++ /dev/null @@ -1,158 +0,0 @@ -### Please describe the problem. -The android app won't start on Cyanogenmod 10.2. Not sure if this is cyanogenmod specific or if it is because the underlying android is now version 4.3 - -### What steps will reproduce the problem? -Install the apk and start the program - -### What version of git-annex are you using? On what operating system? -A 7 day old nightly as of this post(can't get specific number since it won't run) - -### Please provide any additional information below. - -Tested this on both a samsung galaxy S and a samsung galaxy note 2. With different nightlies of cyanogenmod 10.2 - -[[!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 - -Falling back to hardcoded app location; cannot find expected files in /data/app-lib -git annex webapp -u0_a115@android:/sdcard/git-annex.home $ git annex webapp -CANNOT LINK EXECUTABLE: git-annex invalid R_ARM_COPY relocation against DT_SYMBOLIC shared library libc.so (built with -Bsymbolic?) -1|u0_a115@android:/sdcard/git-annex.home $ - ---- - - -cat git-annex-install.log - -Installation starting to /data/data/ga.androidterm -34c88243533e9b0a725ebe33533d990e628dc44b -installing busybox -installing git-annex -installing git-shell -installing git-upload-pack -installing git -installing gpg -installing rsync -installing ssh -installing ssh-keygen -linking ./libexec/git-core/git-config to git -linking ./libexec/git-core/git-fetch to git -linking ./libexec/git-core/git-fsck to git -linking ./libexec/git-core/git-unpack-file to git -linking ./libexec/git-core/git-get-tar-commit-id to git -linking ./libexec/git-core/git-fmt-merge-msg to git -linking ./libexec/git-core/git-push to git -linking ./libexec/git-core/git-for-each-ref to git -linking ./libexec/git-core/git-pack-redundant to git -linking ./libexec/git-core/git-mv to git -linking ./libexec/git-core/git-ls-remote to git -linking ./libexec/git-core/git-prune-packed to git -linking ./libexec/git-core/git-apply to git -linking ./libexec/git-core/git-check-ignore to git -linking ./libexec/git-core/git-log to git -linking ./libexec/git-core/git-cherry-pick to git -linking ./libexec/git-core/git-diff-files to git -linking ./libexec/git-core/git-commit-tree to git -linking ./libexec/git-core/git-index-pack to git -linking ./libexec/git-core/git-reflog to git -linking ./libexec/git-core/git-merge-index to git -linking ./libexec/git-core/git-column to git -linking ./libexec/git-core/git-checkout-index to git -linking ./libexec/git-core/git-diff-index to git -linking ./libexec/git-core/git-count-objects to git -linking ./libexec/git-core/git-fast-export to git -linking ./libexec/git-core/git-fetch-pack to git -linking ./libexec/git-core/git-merge-file to git -linking ./libexec/git-core/git-init to git -linking ./libexec/git-core/git-remote to git -linking ./libexec/git-core/git-init-db to git -linking ./libexec/git-core/git-ls-tree to git -linking ./libexec/git-core/git-merge-subtree to git -linking ./libexec/git-core/git-rev-parse to git -linking ./libexec/git-core/git-bundle to git -linking ./libexec/git-core/git-prune to git -linking ./libexec/git-core/git-peek-remote to git -linking ./libexec/git-core/git-tar-tree to git -linking ./libexec/git-core/git-describe to git -linking ./libexec/git-core/git-update-index to git -linking ./libexec/git-core/git to git -linking ./libexec/git-core/git-revert to git -linking ./libexec/git-core/git-show-ref to git -linking ./libexec/git-core/git-upload-archive to git -linking ./libexec/git-core/git-add to git -linking ./libexec/git-core/git-verify-tag to git -linking ./libexec/git-core/git-format-patch to git -linking ./libexec/git-core/git-show-branch to git -linking ./libexec/git-core/git-remote-fd to git -linking ./libexec/git-core/git-pack-refs to git -linking ./libexec/git-core/git-replace to git -linking ./libexec/git-core/git-pack-objects to git -linking ./libexec/git-core/git-notes to git -linking ./libexec/git-core/git-tag to git -linking ./libexec/git-core/git-var to git -linking ./libexec/git-core/git-help to git -linking ./libexec/git-core/git-gc to git -linking ./libexec/git-core/git-check-ref-format to git -linking ./libexec/git-core/git-shortlog to git -linking ./libexec/git-core/git-stage to git -linking ./libexec/git-core/git-mktree to git -linking ./libexec/git-core/git-merge-recursive to git -linking ./libexec/git-core/git-grep to git -linking ./libexec/git-core/git-clean to git -linking ./libexec/git-core/git-merge-base to git -linking ./libexec/git-core/git-repo-config to git -linking ./libexec/git-core/git-hash-object to git -linking ./libexec/git-core/git-read-tree to git -linking ./libexec/git-core/git-rm to git -linking ./libexec/git-core/git-fsck-objects to git -linking ./libexec/git-core/git-ls-files to git -linking ./libexec/git-core/git-mktag to git -linking ./libexec/git-core/git-stripspace to git -linking ./libexec/git-core/git-mailsplit to git -linking ./libexec/git-core/git-diff-tree to git -linking ./libexec/git-core/git-merge-ours to git -linking ./libexec/git-core/git-cherry to git -linking ./libexec/git-core/git-checkout to git -linking ./libexec/git-core/git-rev-list to git -linking ./libexec/git-core/git-write-tree to git -linking ./libexec/git-core/git-update-ref to git -linking ./libexec/git-core/git-blame to git -linking ./libexec/git-core/git-archive to git -linking ./libexec/git-core/git-update-server-info to git -linking ./libexec/git-core/git-merge-tree to git -linking ./libexec/git-core/git-show to git -linking ./libexec/git-core/git-remote-ext to git -linking ./libexec/git-core/git-merge to git -linking ./libexec/git-core/git-name-rev to git -linking ./libexec/git-core/git-bisect--helper to git -linking ./libexec/git-core/git-clone to git -linking ./libexec/git-core/git-symbolic-ref to git -linking ./libexec/git-core/git-send-pack to git -linking ./libexec/git-core/git-commit to git -linking ./libexec/git-core/git-mailinfo to git -linking ./libexec/git-core/git-credential to git -linking ./libexec/git-core/git-diff to git -linking ./libexec/git-core/git-patch-id to git -linking ./libexec/git-core/git-rerere to git -linking ./libexec/git-core/git-branch to git -linking ./libexec/git-core/git-reset to git -linking ./libexec/git-core/git-receive-pack to git -linking ./libexec/git-core/git-verify-pack to git -linking ./libexec/git-core/git-unpack-objects to git -linking ./libexec/git-core/git-check-attr to git -linking ./libexec/git-core/git-whatchanged to git -linking ./libexec/git-core/git-status to git -linking ./libexec/git-core/git-cat-file to git -linking ./libexec/git-core/git-annotate to git -linking ./bin/git-upload-archive to git -linking ./bin/git-receive-pack to git -linking ./libexec/git-core/git-shell to git-shell -linking ./libexec/git-core/git-upload-pack to git-upload-pack -Installation complete - -# End of transcript or log. -"""]] - -> [[dup|done]] of [[git-annex_broken_on_Android_4.3]].--[[Joey]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces.mdwn b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces.mdwn deleted file mode 100644 index c40a90feb..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -I have a repository at rsync.net, even though following files are shown as unused I can not drop them. - -Running unused, - - git annex unused --from cloud - unused cloud (checking for unused data...) (checking annex/direct/master...) - Some annexed data on cloud is not used by any files: - NUMBER KEY - 1 SHA256E-s4189547--43aef42540e7f50fc454ab3a2ce4aa28a13b57cccff725359cea0470eb88704b. Bir.mp3 - 2 SHA256E-s853765--c0964d3af493d78b7b8393a2aefdd8c290390a03c8cb5cccdcac4647c0fc52a0. 1.jpg - 3 SHA256E-s8706267--e34988b70048a512ad0f431a2a91fa7dd553f96c2bd6caca0bcef928bdfafb93. 3.mp3 - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused --from cloud NUMBER - -show these then running, - - git annex dropunused 1-3 --force - -reports ok for each drop operation but rerunning git annex unused --from cloud still shows these three files as unused. I am using git-annex on mac os x (current dmg) on a direct repo. I have similar problems dropping files on the current repo even though I drop unused they still show up as unused. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_1_b909ed9f474601587b2adad7ad4f674d._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_1_b909ed9f474601587b2adad7ad4f674d._comment deleted file mode 100644 index fa41b59a7..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_1_b909ed9f474601587b2adad7ad4f674d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.163" - subject="doubt this has anything to do with spaces" - date="2014-02-08T17:44:45Z" - content=""" -If you want to drop the files from the remote, you need to also pass the --from option to dropunused. Otherwise, it defaults to dropping any of the unused files that are present in the local repository. -"""]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_2_b2735a6e03db3f77a87a0f7d87347685._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_2_b2735a6e03db3f77a87a0f7d87347685._comment deleted file mode 100644 index 5f5694c00..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_2_b2735a6e03db3f77a87a0f7d87347685._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" - nickname="Hamza" - subject="comment 2" - date="2014-02-08T18:30:47Z" - content=""" -I tried with/without --from still does not drop the files. - - git annex dropunused --from cloud 1-3 --force - dropunused 1 (from cloud...) (gpg) ok - dropunused 2 (from cloud...) ok - dropunused 3 (from cloud...) ok - (Recording state in git...) - -still running unused shows the files as unused. -"""]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_3_dd82a0cd698b0688ff08f0462af0275f._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_3_dd82a0cd698b0688ff08f0462af0275f._comment deleted file mode 100644 index 86e3bd2c1..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_3_dd82a0cd698b0688ff08f0462af0275f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.163" - subject="comment 3" - date="2014-02-08T19:17:46Z" - content=""" -Ok, you're right and this *does* involve spaces. Some bug in the unused log parser. -"""]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_4_bbebb1d0dc5fbc1f6a0bb75b47bd4986._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_4_bbebb1d0dc5fbc1f6a0bb75b47bd4986._comment deleted file mode 100644 index 6459ee8d7..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_4_bbebb1d0dc5fbc1f6a0bb75b47bd4986._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.163" - subject="comment 4" - date="2014-02-08T19:28:18Z" - content=""" -Fixed in git. -"""]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_5_106c271d5174342055910bf57c0a34c5._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_5_106c271d5174342055910bf57c0a34c5._comment deleted file mode 100644 index 4ad4d6f8b..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_5_106c271d5174342055910bf57c0a34c5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" - nickname="Hamza" - subject="comment 5" - date="2014-02-08T19:46:49Z" - content=""" -Are the files dropped on the rsync repo? Or are they gonna be dropped when fix propagates to dmg build? -"""]] diff --git a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_6_3a2d3cc3e018beaf2eb44b86ce7e1a7f._comment b/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_6_3a2d3cc3e018beaf2eb44b86ce7e1a7f._comment deleted file mode 100644 index fbd9ed55c..000000000 --- a/doc/bugs/Can_not_Drop_Unused_Files_With_Spaces/comment_6_3a2d3cc3e018beaf2eb44b86ce7e1a7f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.163" - subject="comment 6" - date="2014-02-08T19:49:11Z" - content=""" -You will need to upgrade git-annex to the next autobuild or an upcoming release to get the fix. -"""]] diff --git a/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree.mdwn b/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree.mdwn deleted file mode 100644 index 1a71ecf38..000000000 --- a/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -### Please describe the problem. -I am trying to switch to direct mode with the git work tree in a different directory than default much like described in http://git-annex.branchable.com/forum/Detached_git_work_tree__63__/ - - -### What steps will reproduce the problem? -- Create a new git repo with the GIT_WORK_TREE and GIT_DIR set. -- git annex init test -- git annex direct - - -### What version of git-annex are you using? On what operating system? -5.20141125 package in Debian unstable - - -### Please provide any additional information below. - -[[!format sh """ -+dbn@loaner:~/annex $ mkdir -p test/worktree -+dbn@loaner:~/annex $ cd test/ -+dbn@loaner:~/annex/test $ git init -Initialized empty Git repository in /home/dbn/annex/test/.git/ -+dbn@loaner:~/annex/test $ git annex init test -init test ok -(Recording state in git...) -+dbn@loaner:~/annex/test $ git annex direct --debug -commit -[2014-12-08 03:05:45 PST] call: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","commit","-a","-m","commit before switching to direct mode"] -On branch master - -Initial commit - -nothing to commit -ok -[2014-12-08 03:05:45 PST] read: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","ls-files","--cached","-z","--","/home/dbn/annex/test/worktree"] -direct [2014-12-08 03:05:45 PST] read: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","symbolic-ref","HEAD"] -[2014-12-08 03:05:45 PST] read: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","show-ref","--hash","refs/heads/master"] -[2014-12-08 03:05:45 PST] call: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","checkout","-q","-B","annex/direct/master"] -[2014-12-08 03:05:45 PST] call: git ["--git-dir=/home/dbn/annex/test/.git","--work-tree=/home/dbn/annex/test/worktree","config","core.bare","true"] -[2014-12-08 03:05:45 PST] read: git ["config","--null","--list"] -fatal: core.bare and core.worktree do not make sense - -git-annex: user error (git ["config","--null","--list"] exited 128) -failed -git-annex: direct: 1 failed -"""]] - -> [[done]] per my comment --[[Joey]] diff --git a/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree/comment_1_40ec252a4801fa56bcdc8db4af8343fc._comment b/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree/comment_1_40ec252a4801fa56bcdc8db4af8343fc._comment deleted file mode 100644 index 33f7696cf..000000000 --- a/doc/bugs/Cannot_set_direct_mode_with_non_default_worktree/comment_1_40ec252a4801fa56bcdc8db4af8343fc._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-06T19:52:12Z" - content=""" -I cannot reproduce this problem with git-annex version 5.20150706. -I don't remember any bug fixes in this area though. - -Note that "fatal: core.bare and core.worktree do not make sense" is -not a git-annex error message. It is a git error message. I conclude -you didn't configure them right, and since git-annex works in my testing -with the two variables set correctly, I'm going to close this bug report. -"""]] diff --git a/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox.mdwn b/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox.mdwn deleted file mode 100644 index 425831a12..000000000 --- a/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. -[[!format sh """ -cabal install -O2 -j1 -f-webdav -f-s3 git-annex -Resolving dependencies... -Configuring dns-1.2.0... -Building dns-1.2.0... -Preprocessing library dns-1.2.0... - -Network/DNS/Decode.hs:15:8: - Could not find module `Data.Conduit.Network' - It is a member of the hidden package `conduit-extra-1.1.0'. - Perhaps you need to add `conduit-extra' to the build-depends in your .cabal file. - Use -v to see a list of the files searched for. -Failed to install dns-1.2.0 -cabal: Error: some packages failed to install: -dns-1.2.0 failed during the building phase. The exception was: -ExitFailure 1 -git-annex-5.20140402 depends on dns-1.2.0 which failed to install. -"""]] - -### What steps will reproduce the problem? - -[[!format sh """ -cabal update -mkdir -p ~/haskell/git-annex -cd ~/haskell/git-annex -cabal sandbox init -cabal install -O2 -j1 -f-webdav -f-s3 c2hs git-annex -"""]] -### What version of git-annex are you using? On what operating system? - -5.20140402, Gentoo Linux - -### Please provide any additional information below. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox/comment_1_bd830cadaeffda0366b3ae46b34c0c55._comment b/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox/comment_1_bd830cadaeffda0366b3ae46b34c0c55._comment deleted file mode 100644 index 8ac4f017f..000000000 --- a/doc/bugs/Compilation_error_when_building_version_5.20140402_in_cabal_sandbox/comment_1_bd830cadaeffda0366b3ae46b34c0c55._comment +++ /dev/null @@ -1,39 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl1D_4vD5ueaDw8gRsIYPO3UHRKEpFfg9I" - nickname="Dmitry" - subject="comment 1" - date="2014-04-04T06:40:21Z" - content=""" -Author of \"dns\" library already fixed this issue. - -Next error is: -[[!format sh \"\"\" -Preprocessing executable 'git-annex' for git-annex-5.20140402... - -Utility/Yesod.hs:36:8: - Could not find module `Text.Hamlet' - It is a member of the hidden package `shakespeare-2.0.0.1'. - Perhaps you need to add `shakespeare' to the build-depends in your .cabal file. - Use -v to see a list of the files searched for. -cabal: Error: some packages failed to install: -\"\"\"]] - -Here is the fix: - - -[[!format diff \"\"\" -Index: git-annex/git-annex.cabal -=================================================================== ---- git-annex.orig/git-annex.cabal -+++ git-annex/git-annex.cabal -@@ -101,7 +101,7 @@ Executable git-annex - base (>= 4.5 && < 4.9), monad-control, MonadCatchIO-transformers, - IfElse, text, QuickCheck >= 2.1, bloomfilter, edit-distance, process, - SafeSemaphore, uuid, random, dlist, unix-compat, async, stm (>= 2.3), -- data-default, case-insensitive -+ data-default, case-insensitive, shakespeare - CC-Options: -Wall - GHC-Options: -Wall - Extensions: PackageImports -\"\"\"]] -"""]] diff --git a/doc/bugs/Creating_a_WebDAV_repo_under_OpenBSD.mdwn b/doc/bugs/Creating_a_WebDAV_repo_under_OpenBSD.mdwn deleted file mode 100644 index f82f914ff..000000000 --- a/doc/bugs/Creating_a_WebDAV_repo_under_OpenBSD.mdwn +++ /dev/null @@ -1,53 +0,0 @@ -### Please describe the problem. -When creating a https webdav repository under openbsd it complains that /etc/ssl/certs doesn't exist. This is true considering all certs are stored in /etc/ssl/cert.pem. -After /etc/ssl/certs is created it complains about that the certificate has an unknown CA, for obvious reasons. - -A workaround is to symlink /etc/ssl/cert.pem in /etc/ssl/certs - -### What steps will reproduce the problem? -See below - -### What version of git-annex are you using? On what operating system? -5.20140129 under OpenBSD 5.4 - -### 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 -WEBDAV_USERNAME=<username> WEBDAV_PASSWORD=<password> git annex initremote box.com type=webdav url=https://dav.box.com/dav/Documents chunksize=100mb encryption=hybrid keyid=<key> mac=HMACSHA512 -initremote box.com (encryption setup) (hybrid cipher with gpg key <key>) (testing WebDAV server...) - -git-annex: WebDAV failed to write file: /etc/ssl/certs/: getDirectoryContents: does not exist (No such file or directory): user error -failed -git-annex: initremote: 1 failed - - -# End of transcript or log. -"""]] - -> This needs to be fixed in the haskell certificate library. -> I have filed a bug there: -> <https://github.com/vincenthz/hs-certificate/issues/26> -> -> Patch would probably be pretty simple. Based on description, something like -> this: - -[[!format patch """ -diff --git a/System/Certificate/X509/Unix.hs b/System/Certificate/X509/Unix.hs -index 8463465..74316e9 100644 ---- a/System/Certificate/X509/Unix.hs -+++ b/System/Certificate/X509/Unix.hs -@@ -50,7 +50,7 @@ listDirectoryCerts path = (map (path </>) . filter isCert <$> getDirectoryConten - isCert x = (not $ isPrefixOf "." x) && (not $ isHashedFile x) - - getSystemCertificateStore :: IO CertificateStore --getSystemCertificateStore = makeCertificateStore . concat <$> (getSystemPath >>= listDirectoryCerts >>= mapM readCertificates) -+getSystemCertificateStore = makeCertificateStore <$> readCertificates "/etc/ssl/cert.pem" - - getSystemPath :: IO FilePath - getSystemPath = E.catch (getEnv envPathOverride) inDefault -"""]] - -> -> [[closing|done]] as no changes to git-annex can fix this. --[[Joey]] diff --git a/doc/bugs/Creating_a_remote_located_in___34____126____47__wherever__34___works_incorrectly.mdwn b/doc/bugs/Creating_a_remote_located_in___34____126____47__wherever__34___works_incorrectly.mdwn deleted file mode 100644 index 7d100929d..000000000 --- a/doc/bugs/Creating_a_remote_located_in___34____126____47__wherever__34___works_incorrectly.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -When creating a new remote with the webapp (on Windows) and setting the remote repository directory as "~/wherever", everything seems to be going well up until pressing the button to create an unencrypted repository. There is no output from either the terminal or error messages displayed in the browser. - -On the remote server, it turns out that it is creating a directory named ~ within $HOME so that there is a $HOME/~/wherever directory. - -Omitting the leading ~/ correctly creates $HOME/wherever and the setup proceeds as it should. - -### What steps will reproduce the problem? - -Try to create a remote repository with directory "~/wherever". - -### What version of git-annex are you using? On what operating system? - -OS: Windows 7 - -Output of git annex version: - -git-annex version: 5.20140517-gee56d21 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feed -s Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SH -A256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar ho -ok external - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Creating_second_repository_leads_to_wrong_ip___40__using_git-annex_webapp_--listen__41__.mdwn b/doc/bugs/Creating_second_repository_leads_to_wrong_ip___40__using_git-annex_webapp_--listen__41__.mdwn deleted file mode 100644 index 28b74bd98..000000000 --- a/doc/bugs/Creating_second_repository_leads_to_wrong_ip___40__using_git-annex_webapp_--listen__41__.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. -Using the git-annex webapp in remote mode will forward to the wrong IP (localhost) when creating the second repository - -### What steps will reproduce the problem? -Needs two computers (C1, C2) - -- C1: run "git-annex webapp --listen=[IP of C1] -- C2: use a browser to go to the address you just got on C1 (should contain IP of C1) -- C2: create an repository as prompted (should work fine) -- C2: In the dropdown on the top right select "Add another repository", choose desired location, select keep separate -- C2: Browser forwards to new address, but instead of the IP of C1, 127.0.0.1 is used (which obviously fails) - -### What version of git-annex are you using? On what operating system? - -[[!format sh """ -$ git-annex version -git-annex version: 4.20130802 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP -$ lsb_release -d -Description: Ubuntu 13.04 -$ uname -a -Linux nas 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:19:35 UTC 2013 i686 i686 i686 GNU/Linux -"""]] - -### 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. -"""]] - -> This is a different effect of the same bug in [[Hangs on creating repository when using --listen]]. Closing as [[dup|done]] --[[Joey]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share.mdwn b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share.mdwn deleted file mode 100644 index 64ae859e2..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -### Please describe the problem. -If have a directory - mounted CIF share (windows server with domain). -If i run "git annex assistant" or "git annex watch" daemon starts fine and works at first, but then after some time stops doing anything: no messages in .git/annex/daemon.log, process hangs in ps aux. - -If i try to "cat .git/annex/daemon.pid" I get "permission denied". And permission is denied for everyone: root, from other windows machines, etc. - -If i then kill daemon process and start daemon again everything repeats. - -### What version of git-annex are you using? On what operating system? -Standalone git-annex 5.20140421-g515d251 on CentOS 6.5 - -> [[done]] --[[Joey]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_1_2a5fb522cbf6e2cefbee0a5fc48287d0._comment b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_1_2a5fb522cbf6e2cefbee0a5fc48287d0._comment deleted file mode 100644 index d247667c4..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_1_2a5fb522cbf6e2cefbee0a5fc48287d0._comment +++ /dev/null @@ -1,45 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmaB2n9HFclAvyMyDzvTPaifh5OrlF51Co" - nickname="VS7" - subject="comment 1" - date="2014-05-21T07:17:44Z" - content=""" -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ ps aux | grep assistant -filesync 27036 0.0 0.0 103244 864 pts/0 S+ 11:13 0:00 grep assistant -\"\"\"]] -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ git annex assistant -\"\"\"]] -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ cat .git/annex/daemon.log -[2014-05-21 11:14:06 MSK] main: starting assistant version 5.20140421-g515d251 -[2014-05-21 11:14:07 MSK] Cronner: You should enable consistency checking to protect your data. -failed to add watch on directory /home/filesync/.config/git-annex (/home/filesync/.config/git-annex: getDirectoryContents: does not exist (No such file or directory)) - - dbus failed; falling back to mtab polling (ClientError {clientErrorMessage = \"runClient: unable to determine DBUS address\", clientErrorFatal = True}) -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory - - No known network monitor available through dbus; falling back to polling -[2014-05-21 11:14:09 MSK] Upgrader: An upgrade of git-annex is available. (version 5.20140517) - -Already up-to-date. -(scanning...) [2014-05-21 11:14:09 MSK] Watcher: Performing startup scan -\"\"\"]] -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ git annex assistant --stop - -git-annex: /home/filesync/manuals/.git/annex/daemon.pid: hGetContents: permission denied (Permission denied) -failed -git-annex: assistant: 1 failed -\"\"\"]] -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ cat .git/annex/daemon.pid -cat: .git/annex/daemon.pid: Permission denied -\"\"\"]] -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ ps aux | grep assistant -filesync 27060 6.2 0.5 566372 41808 ? Sl 11:14 0:04 /home/filesync/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /home/filesync/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/home/filesync/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/home/filesync/git-annex.linux//etc/ld.so.conf.d:/home/filesync/git-annex.linux//usr/lib:/home/filesync/git-annex.linux//usr/lib/x86_64-linux-gnu:/home/filesync/git-annex.linux//lib64:/home/filesync/git-annex.linux//lib/x86_64-linux-gnu: /home/filesync/git-annex.linux/shimmed/git-annex/git-annex assistant -filesync 27115 0.0 0.0 103244 864 pts/0 S+ 11:15 0:00 grep assistant -\"\"\"]] -"""]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_2_6b8d35d464e248c29764e3adbc1c9bae._comment b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_2_6b8d35d464e248c29764e3adbc1c9bae._comment deleted file mode 100644 index 9f0687c62..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_2_6b8d35d464e248c29764e3adbc1c9bae._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.3" - subject="comment 2" - date="2014-05-21T17:11:27Z" - content=""" -It seems to me that your filesystem is broken. -"""]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_3_e134ba74ec996a419d6f9903871b9b03._comment b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_3_e134ba74ec996a419d6f9903871b9b03._comment deleted file mode 100644 index a4b6d8740..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_3_e134ba74ec996a419d6f9903871b9b03._comment +++ /dev/null @@ -1,47 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmaB2n9HFclAvyMyDzvTPaifh5OrlF51Co" - nickname="VS7" - subject="comment 3" - date="2014-05-22T07:23:23Z" - content=""" -*1. Windows Server 2012, deduplication is on.* -[[!format sh \"\"\" -[filesync@ServiceVM00001 manuals]$ ps aux | grep assist -filesync 1222 0.0 0.0 103244 860 pts/0 S+ 11:20 0:00 grep assist -[filesync@ServiceVM00001 manuals]$ git annex assistant -[filesync@ServiceVM00001 manuals]$ cat .git/annex/daemon.pid -1250[filesync@ServiceVM00001 manuals]$ git annex assistant - -git-annex: /home/filesync/manuals/.git/annex/daemon.pid: hGetContents: permission denied (Permission denied) -failed -git-annex: assistant: 1 failed -[filesync@ServiceVM00001 manuals]$ cat .git/annex/daemon.pid -cat: .git/annex/daemon.pid: Permission denied -\"\"\"]] - -*2. Windows 7 Pro, no deduplication.* -[[!format sh \"\"\" -[filesync@ServiceVM00001 test]$ ps aux | grep assistant -filesync 655 0.0 0.0 103244 856 pts/0 S+ 11:18 0:00 grep assistant -[filesync@ServiceVM00001 test]$ git annex assistant -[filesync@ServiceVM00001 test]$ cat .git/annex/daemon.pid -cat: .git/annex/daemon.pid: Permission denied -[filesync@ServiceVM00001 test]$ git annex assistant - -git-annex: /home/filesync/test/.git/annex/daemon.pid: hGetContents: permission denied (Permission denied) -failed -git-annex: assistant: 1 failed -\"\"\"]] - -*3. Local directory. Normal behavior* -[[!format sh \"\"\" -[filesync@ServiceVM00001 test1]$ ps aux | grep assist -filesync 1315 0.0 0.0 103244 856 pts/0 R+ 11:23 0:00 grep assist -[filesync@ServiceVM00001 test1]$ git annex assistant -[filesync@ServiceVM00001 test1]$ cat .git/annex/daemon.pid -1338[filesync@ServiceVM00001 test1]$ git annex assistant -git-annex: Daemon is already running. -[filesync@ServiceVM00001 test1]$ cat .git/annex/daemon.pid -1338 -\"\"\"]] -"""]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_4_2ad592d92dda2d1e78235bad5764f5d9._comment b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_4_2ad592d92dda2d1e78235bad5764f5d9._comment deleted file mode 100644 index ad225a9a8..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_4_2ad592d92dda2d1e78235bad5764f5d9._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmaB2n9HFclAvyMyDzvTPaifh5OrlF51Co" - nickname="VS7" - subject="comment 4" - date="2014-05-22T09:44:33Z" - content=""" -Now i begin to suspect that daemon doesn't work with CIF mounted directories at all. - - mkdir ~/test-container - mkdir ~/test-container/test - mount -t cifs -o user=test_user,uid=502,gid=502 //srv/test ~/test-container/test - cd ~/test-container - git init - git annex init - git annex direct - git annex add - git annex sync - git annex assistant - -Then if i place any file in ~/test-container then git-annex sees changes and processes it almost immediately. But if i do anything inside mounted ~/test-container/test daemon ignores it. -\"git annex status\" says that yes there are changes inside \"~/test-container/test\" and i can commit them via \"git annex add\" & \"git annex sync\", but daemon ignores. -"""]] diff --git a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_5_42ad8c7944c210ac1be812e463e03d7c._comment b/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_5_42ad8c7944c210ac1be812e463e03d7c._comment deleted file mode 100644 index 6061f7d7b..000000000 --- a/doc/bugs/Daemon_stops_working_on_mounted_CIF_share/comment_5_42ad8c7944c210ac1be812e463e03d7c._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="24.159.78.125" - subject="comment 5" - date="2014-05-23T14:34:34Z" - content=""" -My point is that if the filesystem is rejecting all attempts to access it with \"permission denied\", it's hardly surprising that git-annex doesn't work, since nothing works. If running the assistant somehow causes the filesystem to get into this strange broken state, then you have a nice repoducible bug to report on the filesystem, I suppose. I don't see how it could be a bug in git-annex, since it is using only standard posix filesystem system calls, plus inotify. - -Based on this, samba/CIFS does not support inotify: <http://stackoverflow.com/questions/8124617/getting-file-create-notifications-for-cifs-mount-in-linux> -Thus, the assistant won't work on it. - -If I were you, I'd set up git-annex repositories on local filesystems, and let it take care of the syncronosation, rather than using a networked filesystem. -"""]] diff --git a/doc/bugs/Data_loss_when_doing___96__git_annex_import_--force__96__.mdwn b/doc/bugs/Data_loss_when_doing___96__git_annex_import_--force__96__.mdwn deleted file mode 100644 index 60e04fc14..000000000 --- a/doc/bugs/Data_loss_when_doing___96__git_annex_import_--force__96__.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -### Please describe the problem. - -Calling `git annex import --force file-in-working-copy` removes `file-in-working-copy` from disk. - -My workflow is: - -1) copy the CR2 files from a card to the desired directory structure using a tool of my choice, -2) import the created directory layout to git-annex - -### What version of git-annex are you using? On what operating system? - -[[!format sh """ -$ git-annex version -git-annex version: 5.20150327 -build flags: Pairing Testsuite S3 DBus DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -"""]] - -### How to reproduce: - -[[!format sh """ -jkt@svist ~/temp $ mkdir annex-add-force-data-loss -jkt@svist ~/temp $ cd annex-add-force-data-loss/ -jkt@svist ~/temp/annex-add-force-data-loss $ git init -Initialized empty Git repository in /home/jkt/temp/annex-add-force-data-loss/.git/ -jkt@svist ~/temp/annex-add-force-data-loss $ echo 1234 > foo -jkt@svist ~/temp/annex-add-force-data-loss $ ls -al -total 16K -drwxr-xr-x 3 jkt jkt 27 May 8 13:54 . -drwx------ 55 jkt jkt 8.0K May 8 13:54 .. -drwxr-xr-x 6 jkt jkt 96 May 8 13:54 .git --rw-r--r-- 1 jkt jkt 5 May 8 13:54 foo -jkt@svist ~/temp/annex-add-force-data-loss $ git annex import --force foo -git-annex: First run: git-annex init -jkt@svist ~/temp/annex-add-force-data-loss $ git annex init -init ok -(recording state in git...) -jkt@svist ~/temp/annex-add-force-data-loss $ ls -al -total 16K -drwxr-xr-x 3 jkt jkt 27 May 8 13:54 . -drwx------ 55 jkt jkt 8.0K May 8 13:54 .. -drwxr-xr-x 8 jkt jkt 119 May 8 13:54 .git --rw-r--r-- 1 jkt jkt 5 May 8 13:54 foo -jkt@svist ~/temp/annex-add-force-data-loss $ git annex import --force foo -import foo -git-annex: foo: rename: does not exist (No such file or directory) -failed -git-annex: import: 1 failed -jkt@svist ~/temp/annex-add-force-data-loss $ ls -al -total 12K -drwxr-xr-x 3 jkt jkt 17 May 8 13:55 . -drwx------ 55 jkt jkt 8.0K May 8 13:54 .. -drwxr-xr-x 8 jkt jkt 119 May 8 13:55 .git -"""]] -...and the file is gone :(. - -> You should use `git annex add` in this case, not import. -> I've made import refuse to run in this case. [[done]] --[[Joey]] diff --git a/doc/bugs/Deleted_files_during_merge.mdwn b/doc/bugs/Deleted_files_during_merge.mdwn deleted file mode 100644 index 63ef1de7d..000000000 --- a/doc/bugs/Deleted_files_during_merge.mdwn +++ /dev/null @@ -1,2138 +0,0 @@ -### Please describe the problem. - -I edited a file on one machine (firefly), which then synced with another (browncoats). browncoats then deleted the changed file and comitted that with the message «git-annex in browncoats». During this time the file was only ever touched on one machine (firefly), never on browncoats (which I turned on after the two commits on firefly had been made, with git annex assistant running). The result is that the file has disappeared and I have to dig through the log and get it from a backup repository. Both machines are running the assistant in direct mode. Both on ext4 in case that matters. - -I've included the daemon.log from browncoats (with filenames redacted). - -### What steps will reproduce the problem? - -Unknown. - -### What version of git-annex are you using? On what operating system? - -Both are Archlinux 64bit, both running git-annex version 5.20150219-g52daae5 from the standalone 64bit build. - -### Please provide any additional information below. - -First commit: -[[!format text """ -Date: Thu Mar 5 13:24:30 2015 +0100 - - git-annex in firefly - -diff --git a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods b/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -index 5a18c1e..e579681 120000 ---- a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -+++ b/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -@@ -1 +1 @@ --../../../../.git/annex/objects/Kg/v0/SHA256E-s39322--ca7a6d4d84b59d49a699e921438ace0d6c326c9db218a7c99b0b6626cae4b976.ods/SHA256E-s39322--ca7a6d4d84b59d49a699e921438ace0d6c326c9db218a7c99b0b6626cae4b976.ods -\ No newline at end of file -+../../../../.git/annex/objects/V8/7z/SHA256E-s39378--dfbc693d94beb76e1556ff2aefd87b5b6678b93f03bcb0113e1249872c6f7c71.ods/SHA256E-s39378--dfbc693d94beb76e1556ff2aefd87b5b6678b93f03bcb0113e1249872c6f7c71.ods -\ No newline at end of file -"""]] - -Second commit: -[[!format text """ -Date: Thu Mar 5 13:27:21 2015 +0100 - - git-annex in firefly - -diff --git a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods b/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -index e579681..f7fbb69 120000 ---- a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -+++ b/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -@@ -1 +1 @@ --../../../../.git/annex/objects/V8/7z/SHA256E-s39378--dfbc693d94beb76e1556ff2aefd87b5b6678b93f03bcb0113e1249872c6f7c71.ods/SHA256E-s39378--dfbc693d94beb76e1556ff2aefd87b5b6678b93f03bcb0113e1249872c6f7c71.ods -\ No newline at end of file -+../../../../.git/annex/objects/0v/kG/SHA256E-s39498--d962b697df05df77275572bc03f18995b47d013708e6b775c700b3092028c54f.ods/SHA256E-s39498--d962b697df05df77275572bc03f18995b47d013708e6b775c700b3092028c54f.ods -\ No newline at end of file -"""]] - -The final commit, now on the remote: - -[[!format text """ -Date: Thu Mar 5 13:34:47 2015 +0100 - - git-annex in browncoats - -diff --git a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods b/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -deleted file mode 120000 -index f7fbb69..0000000 ---- a/Dokument/Dokument/Skule/Sjukepleie-s4/leseliste.ods -+++ /dev/null -@@ -1 +0,0 @@ --../../../../.git/annex/objects/0v/kG/SHA256E-s39498--d962b697df05df77275572bc03f18995b47d013708e6b775c700b3092028c54f.ods/SHA256E-s39498--d962b697df05df77275572bc03f18995b47d013708e6b775c700b3092028c54f.ods -\ No newline at end of file -"""]] - -[[!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 -[2015-03-05 13:32:49 CET] main: starting assistant version 5.20150219-g52daae5 -[2015-03-05 13:32:51 CET] Cronner: Consistency check in progress -[2015-03-05 13:34:40 CET] TransferScanner: Syncing with firefly, serenity, zoe, river -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: Ingen slik fil eller filkatalog -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: Ingen slik fil eller filkatalog -Warning: the ECDSA host key for 'firefly' differs from the key for the IP address '10.0.0.17' -Offending key for IP in /home/zerodogg/.ssh/known_hosts:103 -Matching host key in /home/zerodogg/.ssh/known_hosts:148 -X11 forwarding request failed -Warning: the ECDSA host key for 'firefly' differs from the key for the IP address '10.0.0.17' -Offending key for IP in /home/zerodogg/.ssh/known_hosts:103 -Matching host key in /home/zerodogg/.ssh/known_hosts:148 -X11 forwarding request failed on channel 0 -(scanning...) [2015-03-05 13:34:41 CET] Watcher: Performing startup scan -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aep11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: Ingen slik fil eller filkatalog -p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: Ingen slik fil eller filkatalog -gpg: Signature made to. 19. feb. 2015 kl. 23.44 +0100 CET using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -ssh: connect to host river port 22: No route to host -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -From firefly:Documents/annexed - 66ab32c..decb072 annex/direct/master -> firefly/annex/direct/master - 7a45b9c..66cf859 git-annex -> firefly/git-annex - 94362e9..decb072 master -> firefly/master - 66ab32c..decb072 synced/master -> firefly/synced/master -(checksum...) -ok -fsck FILENAME (merging firefly/git-annex into git-annex...) -(started...) (checksum...) -ok -fsck FILENAME From serenity:/home/zerodogg/Documents/annexed - 7a45b9c..66cf859 synced/git-annex -> serenity/synced/git-annex - 66ab32c..decb072 synced/master -> serenity/synced/master -Automatic merge went well; stopped before committing as requested -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -(checksum...) -ok -fsck FILENAME [2015-03-05 13:34:47 CET] Committer: Committing changes to git -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME [2015-03-05 13:34:47 CET] Pusher: Syncing with firefly, serenity, zoe, river -Warning: the ECDSA host key for 'firefly' differs from the key for the IP address '10.0.0.17' -Offending key for IP in /home/zerodogg/.ssh/known_hosts:103 -Matching host key in /home/zerodogg/.ssh/known_hosts:148 -(checksum...) -ok -fsck FILENAME X11 forwarding request failed on channel 0 -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME To zerodogg@firefly:Documents/annexed - 7a45b9c..510e591 git-annex -> synced/git-annex - decb072..0f076c0 annex/direct/master -> synced/master -(checksum...) -ok -fsck FILENAME To serenity:/home/zerodogg/Documents/annexed - 66cf859..510e591 git-annex -> synced/git-annex - decb072..0f076c0 annex/direct/master -> synced/master -(checksum...) -ok -fsck FILENAME [2015-03-05 13:34:49 CET] RemoteControl: Syncing with firefly -X11 forwarding request failed -(checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ssh: connect to host river port 22: No route to host -ssh: connect to host rivefatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -r port 22: No route to host -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -(checksum...) -ok -fsck FILENAME From firefly:Documents/annexed - decb072..0f076c0 annex/direct/master -> firefly/annex/direct/master - 66cf859..1de4042 git-annex -> firefly/git-annex -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME Warning: the ECDSA host key for 'firefly' differs from the key for the IP address '10.0.0.17' -Offending key for IP in /home/zerodogg/.ssh/known_hosts:103 -Matching host key in /home/zerodogg/.ssh/known_hosts:148 -(checksum...) -ok -fsck FILENAME X11 forwarding request failed on channel 0 -To zerodogg@firefly:Documents/annexed - 510e591..1de4042 git-annex -> synced/git-annex -(checksum...) -ok -fsck FILENAME Everything up-to-date -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -ssh: connect to host river port 22: Nfatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -(checksum...) -ok -fsck FILENAME git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME fatal: Unable to create '/home/zerodogg/Documents/annexed/.git/refs/heads/synced/git-annex.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: The remote end hung up unexpectedly -fatal: The remote end hung up unexpectedly -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME From zoe:Documents/annexed - 61b7ec9..1de4042 synced/git-annex -> zoe/synced/git-annex - e3b0e2e..0f076c0 synced/master -> zoe/synced/master -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME fra 2013-02-15 00:05:43.png Everything up-to-date -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -ssh: connect to hofatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -st river port 22: No route to host -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME To zerodogg@zoe:Documents/annexed - 61b7ec9..1de4042 git-annex -> synced/git-annex - e3b0e2e..0f076c0 annex/direct/master -> synced/master -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME Dragonfall/ShadowrunEditor.ini (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME s(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -(checksum...) -ok -fsck FILENAME ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. -git-annex-shell: expected repository UUID b158aa97-4b68-4c37-a109-f3df91480185 but found UUID 2a6ccda4-f94c-484f-aefe-ce49c1767eab -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (2).pdf (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ONSDAG.ret (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ONSDAG.ret (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME M_HAVREGRYN.ret (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -(checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME (checksum...) -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok -fsck FILENAME ok - - Time limit (5m) reached! -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] -ssh: connect to host river port 22: No route to host -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.1] - -# End of transcript or log. -"""]] - -> This seems very like the problem described in -> [[git_annex_still_deleting_content_when_merging]]. Without a way to -> reproduce it, I can't tell for sure, but the circumstances of both seem -> the same. I'm going to close this as a duplicate, and have updated the -> other bug report to point to it as more evidence of the bug. [[done]] - -[[!meta title="Assistant deleted modified file during merge"]] diff --git a/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file.mdwn b/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file.mdwn deleted file mode 100644 index 21c7af19b..000000000 --- a/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file.mdwn +++ /dev/null @@ -1,60 +0,0 @@ -### Please describe the problem. - -On Windows, a 10GB file of mine is successfully indexed (``git annex add``'ed), but ``git annex sync --content`` always fails with rsync, saying "recvkey: received key with wrong size". This is the largest file I've tested so far, and the only one that's failed. - -### What steps will reproduce the problem? - -1. Copy a 10GB file to a working copy (mine is ''PNG_Sequence.rar'', 10 361 629 980 bytes). -2. Run ``git annex add`` -3. Run ``git annex sync --content`` - -### What version of git-annex are you using? On what operating system? - -Windows 7 x64 with: - - git-annex version: 5.20141128-g70f997e - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feed - s Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SH - A256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar ho - ok external - -### 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 - -commit (Recording state in git...) -ok -pull origin -ok -copy Art/PlanetPioneers/PNG_Sequence.rar copy Art/PlanetPioneers/PNG_Sequence.ra -r (checking origin...) (to origin...) - recvkey: received key with wrong size; discarding - -sent 39 bytes received 12 bytes 102.00 bytes/sec -rsync error: syntax or usage error (code 1) at /home/lapo/package/rsync-3.0.9-1/ -src/rsync-3.0.9/main.c(1052) [sender=3.0.9]total size is 10361629980 speedup is - 203169215.29 - rsync failed -- run git annex again to resume file transfer -failed -pull origin -ok -push origin -Counting objects: 24, done. -Delta compression using up to 8 threads. -Compressing objects: 100% (11/11), done. -Writing objects: 100% (13/13), 1.06 KiB | 0 bytes/s, done. -Total 13 (delta 7), reused 0 (delta 0) -To ssh://gitannex@serv-gitannex:/home/gitannex/git-annex-test.git - f8f70de..41bec92 git-annex -> synced/git-annex - 090ca15..e9e842b annex/direct/master -> synced/master -ok -git-annex: sync: 1 failed - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file/comment_1_cb9e9dada7baf4e48725a9483b3b448a._comment b/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file/comment_1_cb9e9dada7baf4e48725a9483b3b448a._comment deleted file mode 100644 index 42acf9f64..000000000 --- a/doc/bugs/Direct_mode_sync_fails_to_transfer_a_10GB_file/comment_1_cb9e9dada7baf4e48725a9483b3b448a._comment +++ /dev/null @@ -1,25 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-01-20T19:41:44Z" - content=""" -In my own test, I made a 10 gb file, and the key git-annex came up with had -a size of -2147483648 which is clearly screwed up.. But that's what -getFileStatus reports the size as. This was in an 32 bit XP VM. - -Hmm, unix-compat's getFileStatus calls getFileSize, which yields a -FileOffset. The maxBound of that on linux is a nice large -9223372036854775807, but on Windows, it appears to be 2147483647. - -Compare with using hFileSize, which yields an Integer. So, -getFileSize and fileSize are unsafe on Windows due to FileOffset being so -small on Windows. - -I have now corrected all places in git-annex that used the unsafe fileSize. -It will behave correctly on Windows now. - -However, if you still have the repo with the big file, it's key still has -the wrong size. To fix, you can "git annex unannex" the file, and then "git -annex add" it back, after upgrading to the current daily build, or the next -release of git-annex. -"""]] diff --git a/doc/bugs/Drop_--from_always_trusts_local_repository.mdwn b/doc/bugs/Drop_--from_always_trusts_local_repository.mdwn deleted file mode 100644 index 53bdda332..000000000 --- a/doc/bugs/Drop_--from_always_trusts_local_repository.mdwn +++ /dev/null @@ -1,46 +0,0 @@ -### Please describe the problem. - -The command `git annex drop --from` always trusts the local repository, even if -it is marked as untrusted. - - -### What steps will reproduce the problem? -[[!format sh """ -mkdir t u; cd t; git init; git commit --allow-empty -m "Initial commit"; git annex init "Trusted"; date > file; git annex add file; git commit -m "Add file"; cd ../u; git init; git remote add t ../t; git fetch t; git merge t/master; git annex init "Untrusted"; git annex untrust .; git annex get file; cd ../t; git remote add u ../u; git fetch u; cd .. -"""]] - -Create two repositories, *t* (trusted) and *u* (untrusted). A file is in both -repositories. When performing `git annex drop file` in repository *t*, `git -annex` will abort because there are not enough copies. But when performing `git -annex drop --from t file` in *u*, git annex will delete the copy. - - -### What version of git-annex are you using? On what operating system? - -Bug was introduced with 6c31e3a8 and still exists in current master (d955cfe7). - - -### Please provide any additional information below. - -The following change seems to solve the problem. (First time working with -Haskell, please excuse the crude code.) - -[[!format diff """ -diff --git a/Command/Drop.hs b/Command/Drop.hs -index 269c4c2..09ea99a 100644 ---- a/Command/Drop.hs -+++ b/Command/Drop.hs -@@ -82,8 +82,9 @@ performRemote key afile numcopies remote = lockContent key $ do - (remotes, trusteduuids) <- Remote.keyPossibilitiesTrusted key - present <- inAnnex key - u <- getUUID -+ level <- lookupTrust u - let have = filter (/= uuid) $ -- if present then u:trusteduuids else trusteduuids -+ if present && level <= SemiTrusted then u:trusteduuids else trusteduuids - untrusteduuids <- trustGet UnTrusted - let tocheck = filter (/= remote) $ - Remote.remotesWithoutUUID remotes (have++untrusteduuids) -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Drop_files_with_the_same_checksum..mdwn b/doc/bugs/Drop_files_with_the_same_checksum..mdwn deleted file mode 100644 index 0dcae20c7..000000000 --- a/doc/bugs/Drop_files_with_the_same_checksum..mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. -When two identical files are annexed and one of them is dropped, both files are gone (one dangling symlink is left). This may be intentional (the checksums are the same after all), but then is there a way to drop one of the files? - -### What steps will reproduce the problem? - - mkdir annex - cd annex - git init - git annex init - mkdir a b - dd if=/dev/urandom of=a/data.bin count=2048 - cp a/data.bin b - git annex add a/data.bin b/data.bin - git commit -m "Added raw data." - git annex drop --force a/data.bin - file b/data.bin - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140831+b1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 - -Distributor ID: Debian -Description: Debian GNU/Linux testing (jessie) -Release: testing -Codename: jessie - -> If you don't want git-annex to de-duplicate files you can use a backend -> such as WORM. Here it's behaving as expected, so [[done]]. --[[Joey]] diff --git a/doc/bugs/Endless_SSH_password_prompts.mdwn b/doc/bugs/Endless_SSH_password_prompts.mdwn deleted file mode 100644 index 6a180f274..000000000 --- a/doc/bugs/Endless_SSH_password_prompts.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -### Please describe the problem. -Yesterday I installed git-annex on two computers and paired their repos. Today I logged back in to one of them, and as soon as the webapp loaded (autostarted in the background), it popped up an OpenSSH prompt wanting my key's password. I typed it in, and it popped up another. This went on several times. When I hit Cancel instead, it popped up a prompt wanting the password for the user account on my other computer. Even with that, once wasn't enough. - -This is bad enough, but worse is that the password prompt captures the keyboard input so I can't even open my Yakuake console to kill git-annex. Well, it's difficult and requires hitting Escape rapidly over and over until I can squeeze in a keystroke to the rest of the system. - -I don't understand why this is happening. - -1. Shouldn't git-annex have installed a passwordless key on my paired system? It did that for my remote repo. - -2. The prompt it's using has no option to remember the pasword. I use ssh-agent, but usually by running ssh-add in a terminal. Maybe if it would use a prompt that works with the agent it wouldn't ask for the password multiple times. - -3. I think it's opening multiple SSH connections at once, before I've entered the password even once, so even after I enter the password, it will keep asking for it until I've entered it for every SSH process that was already started. - -### What version of git-annex are you using? On what operating system? -1 Nov 2013 Linux tarball on Ubuntu Raring 13.04 - -> [[fixed|done]]; assistant now sets `StrictHostKeyChecking yes` -> when creating ssh remotes. It also fixes up any ssh remotes it already -> created to have that setting (unless StrictHostKeyChecking is already -> being set). -> -> So, when the host key changes, syncing with the remote will now fail, -> rather than letting ssh prompt for the y/n response. In the local -> pairing case, this is completely right, when on a different lan -> and it tries to communicate with the wrong host there. OTOH, if the ssh -> key of a ssh server has really changed, the assistant does not currently -> help dealing with that. -> -> Any ssh remotes not set up by the assistant are left as-is, so this -> could still happen if the ssh host key of such a ssh remote changes. -> I'll assume that if someone can set up their ssh remotes at the command -> line, they can also read the dialog box ssh pops up, ignore the -> misleading "passphrase request" in the title, and see that it's actually -> prompting about a host key change. --[[Joey]] -> -> Update: See [[bugs/kill_git-annex_assistant_on_logout]] -- the fact that -> it happened after logging back in suggests that was the actual cause of -> this problem. --[[Joey]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment b/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment deleted file mode 100644 index b1ea71526..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 1" - date="2013-11-03T00:29:14Z" - content=""" -Pairing sets up the same kind of dedicated passwordless ssh key that is used when adding a ssh server. - -It's not clear from your description what program is asking for the password, or even if it's asking for the password for a ssh key. You need to provide more details. -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_2_0a1fc4b4580d8be4c37064e0a16de99b._comment b/doc/bugs/Endless_SSH_password_prompts/comment_2_0a1fc4b4580d8be4c37064e0a16de99b._comment deleted file mode 100644 index fec729ddb..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_2_0a1fc4b4580d8be4c37064e0a16de99b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" - nickname="Adam" - subject="comment 2" - date="2013-11-03T00:39:38Z" - content=""" -I'm not sure which program is doing the asking either. The title bar says \"OpenSSH\". It is asking for the SSH key password, but if I dismiss the dialog without entering the password, it will open another dialog asking for the user account's password, e.g. me@laptop, indicating it's SSH falling back to password auth. -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_3_46210f7745b8c7c237fc8b08309390fe._comment b/doc/bugs/Endless_SSH_password_prompts/comment_3_46210f7745b8c7c237fc8b08309390fe._comment deleted file mode 100644 index aacf1cc01..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_3_46210f7745b8c7c237fc8b08309390fe._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlHNJ7FpiXJNwSmojlwKwXhhF5QvwpNPmI" - nickname="Colin" - subject="Confirmed" - date="2013-11-14T17:57:23Z" - content=""" -I am seeing the same problem. It happened on a machine running git-annex on Debian Testing some weeks ago, and I eventually disabled the offending repository for my sanity (incidentally - it seems to have vanished so I don't know how to re-enable it apart from adding it again). - -It has just very recently (some days) started on this machine running Debian Unstable. - -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_4_bf311301063db06bcfa8ce8d7db54028._comment b/doc/bugs/Endless_SSH_password_prompts/comment_4_bf311301063db06bcfa8ce8d7db54028._comment deleted file mode 100644 index 0a182f310..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_4_bf311301063db06bcfa8ce8d7db54028._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="similar" - date="2013-12-02T01:39:36Z" - content=""" -I am having a similar issue here. The problem is that the assistant is started along with my regular session, but the SSH keys required for the assistant to sync are prompted during my session startup. So I actually get lots of prompts, because the assistant is started before I have time to enter the password for my SSH key. -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_5_7490ca530d4e7d49eaa264eb5880dd17._comment b/doc/bugs/Endless_SSH_password_prompts/comment_5_7490ca530d4e7d49eaa264eb5880dd17._comment deleted file mode 100644 index 7990d0ff2..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_5_7490ca530d4e7d49eaa264eb5880dd17._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkdiXn5s1wX2Zncy1S7_h-yPTv2gt0bmmY" - nickname="Jacob" - subject="Same problem on ubuntu" - date="2013-12-15T14:22:55Z" - content=""" -Same problem, I even manually setup ssh keys between the two servers but it just loops and keeps asking for a password every sync. -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_6_57952f91c8d55558cce18b229398f70c._comment b/doc/bugs/Endless_SSH_password_prompts/comment_6_57952f91c8d55558cce18b229398f70c._comment deleted file mode 100644 index 863756a00..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_6_57952f91c8d55558cce18b229398f70c._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 6" - date="2013-12-19T16:36:55Z" - content=""" -Taking a screenshot, and running `ps -fax` to find what programs are -running, seem like the logical first steps to get anywhere on this -problem. - -"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_7_6d6a131fda398840cfe00c52ad560ed2._comment b/doc/bugs/Endless_SSH_password_prompts/comment_7_6d6a131fda398840cfe00c52ad560ed2._comment deleted file mode 100644 index c135989b0..000000000 --- a/doc/bugs/Endless_SSH_password_prompts/comment_7_6d6a131fda398840cfe00c52ad560ed2._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 7" - date="2013-12-19T17:54:33Z" - content=""" -Seems likely that this is ssh prompting that the host key has changed. The dialog box has \"password\" at the top, but if you actually read it, it's prompting for a yes/no response to a host key change. - -So, I probably need to turn on StrictHostKeyChecking. -"""]] diff --git a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX.mdwn b/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX.mdwn deleted file mode 100644 index 67dfae11d..000000000 --- a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -What steps will reproduce the problem? - -1. Click "Remote server: Set up a repository on a remote server using ssh." -2. Enter hostname and different username than currently logged in user -3. Click check this server - - -What is the expected output? - -> I expected to see the next step in the remote repo creration process. - -What do you see instead? - - -> Failed to ssh to the server. Transcript: ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory Permission denied, please try again. ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory Permission denied, please try again. ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory Permission denied (publickey,password). - - -What version of git-annex are you using? - -> git-annex: Version: 3.20130114 - - -On what operating system? - -> OSX: 10.8.2 - - - -Please provide any additional information below. - -> I mentioned "with a different username" because the assistant will allow me to create a remote repository on the same target machine when I use my normal username. I think this is most likely because I have a ssh-key setup for the account on the remote machine. However I do not want to assume anything and send you down the wrong OSX rabbit hole. - -> After a little research it seems that OSX does not have a ssh-askpass - -[[!tag /design/assistant/OSX]] -[[!meta title="ssh-askpass not available on OSX"]] - -> [[fixed|done]]; the webapp now handles ssh password prompting on its own, -> ssh-askpass is not needed. --[[Joey]] diff --git a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_1_559555934d79ae6be383063abcaae22e._comment b/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_1_559555934d79ae6be383063abcaae22e._comment deleted file mode 100644 index 8b701250c..000000000 --- a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_1_559555934d79ae6be383063abcaae22e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.3.125" - subject="comment 1" - date="2013-02-05T19:45:24Z" - content=""" -It should be possible to use SSHPassKey as described here: <http://benno.id.au/docs/ssh_macosx.pml> - -However, this all seems pretty crummy, and so perhaps it would be worth it for the webapp to do its own ssh password prompting when setting up a remote. -"""]] diff --git a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_2_a9f4f9db042ab6f6c15d6954651971b2._comment b/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_2_a9f4f9db042ab6f6c15d6954651971b2._comment deleted file mode 100644 index f0d25d778..000000000 --- a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_2_a9f4f9db042ab6f6c15d6954651971b2._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="Peng" - ip="171.37.79.254" - subject="Found an easy solution" - date="2013-06-15T03:34:52Z" - content=""" -Just install this script on OS X, and you'll get the ssh-askpass command. - -https://github.com/markcarver/mac-ssh-askpass - -Tested working successfully on OS X 10.8.3. -"""]] diff --git a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_3_55a496d0a0be80ba723b17bf9faa3bc0._comment b/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_3_55a496d0a0be80ba723b17bf9faa3bc0._comment deleted file mode 100644 index e22ca1ff9..000000000 --- a/doc/bugs/Error_creating_remote_repository_using_ssh_on_OSX/comment_3_55a496d0a0be80ba723b17bf9faa3bc0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnb4NsPsSSHTniueRuVnBzTLrDiDqBZIfY" - nickname="Doug" - subject="Same problem but still does not work with askpass installed" - date="2013-07-24T18:19:25Z" - content=""" -So, I got askpass installed and I'm still getting the same error as everybody else. It's a strange thing as I have my public key dumped on the remote server and I can log in fine manually. It's an empty passphrase so there shouldn't be any prompting going on. -"""]] diff --git a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars.mdwn b/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars.mdwn deleted file mode 100644 index 3c00472d7..000000000 --- a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. -I’ve noticed that daemon.log will sometimes contain error messages arising from logging a file name during transfer. Additionally, I’ve occasionally noticed that certain files get «stuck» after being added to the objects store, i. e., they will never be committed by the assistant and have to be staged manually; it appears there is a correlation between files where the logger errors out and files getting stuck. - -I can reproduce this using the en-dash (U+2013). - -### What steps will reproduce the problem? -1. Create a file named «Behold – the majestic en-dash» in a repository where the assistant is running. -2. Observe file has not been added by the assistant and daemon.log contains no message pertaining to new file. -3. Restart assistant. -4. Observe in daemon.log that the logger has errored out with «hPutChar: invalid argument» and gives the Unicode replacement character thrice for each en-dash. -5. Observe that file is added to object store, but the symlink is not staged or committed by the assistant. - -### What version of git-annex are you using? On what operating system? -git-annex 5.20150731 -Linux 4.0.9 - -### Please provide any additional information below. -[[!format sh """ -# After restarting the assistant. -[2015-07-28 14:24:58 CEST] Committer: Adding 978Error writing log message: <stderr>: hPutChar: invalid argument (invalid character) (original message: [2015-07-28 14:24:58 CEST] Committer: Adding 978\65533\65533\655330\65533\65533..1\65533\65533\655330.pdf) -[2015-07-28 14:24:59 CEST] Transferrer: Uploaded 978Error writing log message: <stderr>: hPutChar: invalid argument (invalid character) (original message: [2015-07-28 14:24:59 CEST] Transferrer: Uploaded 978\65533\65533\655330\65533\65533..1\65533\65533\655330.pdf) -"""]] - -> Closing this because the main bug is fixed in hinotify git and will -> percolate to the git-annex builds eventually. [[done]] --[[Joey]] diff --git a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_1_8a8f3722a0ed6ad030195cf32532e386._comment b/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_1_8a8f3722a0ed6ad030195cf32532e386._comment deleted file mode 100644 index 7e91c7709..000000000 --- a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_1_8a8f3722a0ed6ad030195cf32532e386._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 1" - date="2015-08-03T08:37:18Z" - content=""" -BTW this was with LANG=en_US.utf8 -"""]] diff --git a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_2_1be17780fd4244053c504383ad56969b._comment b/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_2_1be17780fd4244053c504383ad56969b._comment deleted file mode 100644 index fabe85a3a..000000000 --- a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_2_1be17780fd4244053c504383ad56969b._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-08-03T14:33:38Z" - content=""" -I was able to reproduce this, but only once I started the assistant with -LANG=C. I suspect that the bug reporter's locale in the shell is not -the locale the assistant was started with. - -(Also, I included the French quotes in the filename, which wasn't very -clear in the bug report.) - -The failure to output a debug message is not actually fatal. The file -still gets added and committed if it exists when the assistant starts up, -despite this "error". What actually seems to be failing is the -inotify code. Creating the file while the assistant is running with LANG=C -results in no inotify event being received for it. AFAICS, the -inotify library is falling over on the filename, before git-annex ever gets -to see the file. - -Hmm, it looks like the inotify library is generating events with -filenames that have high bit characters stripped out when run in the C -locale! So, git-annex gets an event for a file that's not present, and -ignores it. This sure seems like a bug in the inotify library to me. Bug -filed: <https://github.com/kolmodin/hinotify/issues/13>. -"""]] diff --git a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_3_eb14f37daebccca05c413acd3112e5a0._comment b/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_3_eb14f37daebccca05c413acd3112e5a0._comment deleted file mode 100644 index db3513b48..000000000 --- a/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_3_eb14f37daebccca05c413acd3112e5a0._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-08-03T15:28:00Z" - content=""" -I've developed a patch to hinotify that fixes the problem. Hopefully it will -be accepted upstream soon. (Update: It's merged and will be in the next -release of hinotify.) Verified that with it, the assistant can add -these files even when run in LANG=C. - -The debug logger still shows the error message, but it's not actually fatal, -and I'm inclined to not do anything about it since it only shows up when -debugging is enabled. Actually, I'm not sure what to do about it; it's -writing to stderr, which has fileEncoding set on it, so I don't understand -why it's having the problem -- when git-annex writes filenames to stderr it -works ok, but when System.Log.Handler.Simple does, it fails like this -weird. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work.mdwn b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work.mdwn deleted file mode 100644 index ee007b3f6..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work.mdwn +++ /dev/null @@ -1,145 +0,0 @@ -### Please describe the problem. - -In the external special remote protocol, SETURLPRESENT (and SETURIPRESENT) doesn't seem to work. My expectation is that it will add a public URL for a file, as with `git annex addurl`, so that clones can retrieve it without enabling the special remote. Instead, the specified URL doesn't show up under `git annex whereis` and isn't used when fetching the file in a clone. Am I misunderstanding how SETURLPRESENT is supposed to work? - -### What steps will reproduce the problem? - -See transcript below. I'm seeing this with [gcsannex](https://github.com/bgilbert/gcsannex), my external special remote. - -### What version of git-annex are you using? On what operating system? - -5.20150809-ga52b65a on Fedora 22 x86_64. - -### Please provide any additional information below. - -[[!format sh """ -# First, set up git-annex repository - -$ mkdir t -$ cd t -$ git init -Initialized empty Git repository in /home/bgilbert/tmp/t/.git/ -$ git annex init -init ok -(recording state in git...) -$ cp ~/sample.jpg . -$ git annex add sample.jpg -add sample.jpg ok -(recording state in git...) -$ git commit -m 'sample' -[master (root-commit) 692e208] sample - 1 file changed, 1 insertion(+) - create mode 120000 sample.jpg -$ GOOGLE_APPLICATION_CREDENTIALS=../credentials.json git annex initremote test1 type=external externaltype=gcs encryption=none project=my-project public=yes -initremote test1 ok -(recording state in git...) - - -# Copy file to special remote. Note the SETURLPRESENT. - -$ git annex whereis sample.jpg -whereis sample.jpg (1 copy) - d2ed9d95-3005-40cc-a743-227c38e0242a -- bgilbert@trumpeter:~/tmp/t [here] -ok -$ git annex copy -t test1 sample.jpg --debug -[2015-08-09 19:20:28 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"] -[2015-08-09 19:20:28 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] -[2015-08-09 19:20:28 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","log","refs/heads/git-annex..a2e464a88d86394ef071cdc1af3f36856b91b0e1","-n1","--pretty=%H"] -[2015-08-09 19:20:28 EDT] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"] -[2015-08-09 19:20:28 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","ls-files","--cached","-z","--","sample.jpg"] -copy sample.jpg [2015-08-09 19:20:28 EDT] chat: git-annex-remote-gcs [] -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> VERSION 1 -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- PREPARE -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETUUID -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE e49a874a-5480-4e48-aa51-c6e34ee5991c -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG project -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE my-project -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG location -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG storageclass -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG name -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE test1 -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG bucket -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG public -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE yes -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG fileprefix -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCONFIG encryption -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- VALUE none -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs --> GETCREDS e49a874a-5480-4e48-aa51-c6e34ee5991c-creds-v1 -[2015-08-09 19:20:28 EDT] git-annex-remote-gcs <-- CREDS [elided] -[2015-08-09 19:20:29 EDT] git-annex-remote-gcs --> PREPARE-SUCCESS -[2015-08-09 19:20:29 EDT] git-annex-remote-gcs <-- CHECKPRESENT SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -[2015-08-09 19:20:30 EDT] git-annex-remote-gcs --> SETURLMISSING SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg https://storage-download.googleapis.com/test1-e49a874a-5480-4e48-aa51-c6e34ee5991c/SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -[2015-08-09 19:20:30 EDT] git-annex-remote-gcs --> CHECKPRESENT-FAILURE SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -(to test1...) -[2015-08-09 19:20:30 EDT] git-annex-remote-gcs <-- TRANSFER STORE SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg .git/annex/objects/K2/7X/SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg/SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -[2015-08-09 19:20:32 EDT] git-annex-remote-gcs --> SETURLPRESENT SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg https://storage-download.googleapis.com/test1-e49a874a-5480-4e48-aa51-c6e34ee5991c/SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -[2015-08-09 19:20:32 EDT] git-annex-remote-gcs --> TRANSFER-SUCCESS STORE SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg -ok -[2015-08-09 19:20:32 EDT] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","hash-object","-w","--stdin-paths","--no-filters"] -[2015-08-09 19:20:32 EDT] feed: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","update-index","-z","--index-info"] -[2015-08-09 19:20:32 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] -(recording state in git...) -[2015-08-09 19:20:32 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","write-tree"] -[2015-08-09 19:20:32 EDT] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","commit-tree","ed61e5bed8cac36eef5e3feb72c0e4165947c746","--no-gpg-sign","-p","refs/heads/git-annex"] -[2015-08-09 19:20:32 EDT] call: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","update-ref","refs/heads/git-annex","6885483c56c1fc394b4ca518c6c5377147d4931c"] - - -# The URL is not shown in whereis, but does exist (HEAD returns 200). - -$ git annex whereis sample.jpg -whereis sample.jpg (2 copies) - d2ed9d95-3005-40cc-a743-227c38e0242a -- bgilbert@trumpeter:~/tmp/t [here] - e49a874a-5480-4e48-aa51-c6e34ee5991c -- [test1] -ok -$ curl -I 'https://storage-download.googleapis.com/test1-e49a874a-5480-4e48-aa51-c6e34ee5991c/SHA256E-s380682--"0494a188e8cb9feda674b983dc294b7992512fe56fadd040708d22b388d3c38d".jpg' | head -n 1 -HTTP/1.1 200 OK - - -# If I drop the file from this repository, make a new clone, and then -# try to get the file in the clone without enabling the test1 remote, -# git-annex does not fetch from the URL. - -$ git annex drop sample.jpg -drop sample.jpg ok -(recording state in git...) -$ cd .. -$ git clone t t2 -Cloning into 't2'... -done. -$ cd t2 -$ git annex init -init (merging origin/git-annex into git-annex...) -(recording state in git...) -ok -(recording state in git...) -$ git annex sync -commit ok -pull origin -ok -push origin -Counting objects: 6, done. -Delta compression using up to 4 threads. -Compressing objects: 100% (5/5), done. -Writing objects: 100% (6/6), 699 bytes | 0 bytes/s, done. -Total 6 (delta 2), reused 0 (delta 0) -To /home/bgilbert/tmp/t - * [new branch] git-annex -> synced/git-annex - * [new branch] master -> synced/master -ok -$ git annex whereis sample.jpg -whereis sample.jpg (1 copy) - e49a874a-5480-4e48-aa51-c6e34ee5991c -- test1 -ok -$ git annex get sample.jpg -get sample.jpg (not available) - Try making some of these repositories available: - e49a874a-5480-4e48-aa51-c6e34ee5991c -- test1 -failed -git-annex: get: 1 failed -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_1_af8bfacc1cc98719199e7bc57eaca5b4._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_1_af8bfacc1cc98719199e7bc57eaca5b4._comment deleted file mode 100644 index d2b578943..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_1_af8bfacc1cc98719199e7bc57eaca5b4._comment +++ /dev/null @@ -1,48 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-08-11T16:14:22Z" - content=""" -This is the first I've heard of your gcsannex. Thanks for working on it. - -I am pretty sure that the url is being recorded in the git-annex branch, -and that if you look at the history of the branch, you'll see that. The -reason whereis doesn't show it, and `git annex get` doesn't use it is that -the location tracking info doesn't list the web as one of the locations of -the key. - -Looking at the code, SETURLPRESENT causes the url to be recorded, and the -location tracking info for the special remote (not the web) is updated to -say it has the key. - -IIRC, my original use case for this was things like *.torrent urls, where -it makes sense for the bittorrent special remote to add an url to the -torrent, but we don't want the torrent to be downloaded as if it were the -content of the file. However.. I don't know if any external special remotes -actually use SETURLPRESENT this way. The SETUR*I*PRESENT varient seems to -be the one really used, and/or CLAIMURL. - -So, SETURLPRESENT is feeling a bit like an unused appendix that doesn't do -quite you want. And could be changed to do what you want quite easily -- by -making it set the location tracking for the web. But, it's hard for me to -tell if the current behavior is really unused. I suppose you could work -around this by having your external special remote run "git annex -setpresentkey" with the uuid used for the web -(00000000-0000-0000-0000-000000000001). - -On the third hand, does it really make sense for a key, upon being uploaded -to google drive, to appear to be in two remotes; both google drive and the -web? If the web is not untrusted, it will count as another copy of the -file, when there's not really another copy as such (google drive redundancy -aside). - -What I did in the similar case of uploading a file to a public S3 -bucket is to not make that file be present in the web remote, and indeed -not record the url in the git-annex branch at all. Instead, the S3 remote -uses the `whereisKey` interface to add the url to the `whereis` output, and -if the S3 API keys are not available, it will download files from the public -url, instead of using the S3 protocol. An external special remote could also -take this approach, although the internal `whereisKey` interface is not -currently exposed. If you want to go this route, I'll see about adding -that and any other necessary missing bits. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_2_899b154cfe0385de0fec249f5e9a3f00._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_2_899b154cfe0385de0fec249f5e9a3f00._comment deleted file mode 100644 index cfc7af00c..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_2_899b154cfe0385de0fec249f5e9a3f00._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="bgilbert@a0c64716cf22216de5eeb15a5ca4f009164c8fb3" - nickname="bgilbert" - subject="comment 2" - date="2015-08-12T04:51:53Z" - content=""" -Well, gcsannex didn't exist until last weekend. I hope people find it useful. - -You're correct about what is happening, and I agree that the public URL shouldn't appear to be another copy of the file. I was hoping to avoid requiring `enableremote` in a clone, but I see that the S3 remote [does also](https://git-annex.branchable.com/tips/public_Amazon_S3_remote/). - -I'll look at supporting unauthenticated reads through gcsannex directly. I'll add support for `whereisKey` if you decide to expose it; AFAICS it's only used in the output of `git annex whereis`, which is convenient but doesn't seem to be critical. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_3_6e856db0eb3bb3e7674649857d53cc11._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_3_6e856db0eb3bb3e7674649857d53cc11._comment deleted file mode 100644 index 35108ee82..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_3_6e856db0eb3bb3e7674649857d53cc11._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-08-13T20:47:28Z" - content=""" -Needing enableremote is a trifle annoying, but I don't see a way to avoid -it and it's symmetric with needing to add a git remote to a repo before -accessing it. And of course, the user has to install your external special -remote's implementation too. Which is perhaps more annoying in this use case -where the file is only being retrieved with a dumb http call in the end. - -Instead of the current approach, I could have had special remotes -use SETURLPRESENT to record the public urls for keys. Then git-annex -would have something that notices if a special remote is not enabled, but -supports public urls, and perhaps auto-enables the special remote in -readonly mode, not using the normal implementation of the special remote, -but a standin implementation that just uses the public urls. That seems a -little complicated, especially with the auto-enabling, and it bloats the -git-annex branch with public urls. IIRC those are the reasons I decided not -to go that route. - -I've added WHEREIS to the protocol. It is only used for `whereis` -display. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment deleted file mode 100644 index 7bb2d0ef0..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_4_109c33f4ed1230a54e410842de7779f7._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-08-13T23:50:58Z" - content=""" -Thinking some more, getting the external special remote program installed -may be the real pain point here. - -I could easily add support for enableremote with readonly=yes, and have it -not use the external program at all, just hit the urls previously registered -with SETURLPRESENT. - -The git-annex branch would bloat some if a remote works this way, but if -the urls consist mostly of some fixed strings, and the key, then git should -pack those pretty efficiently. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_5_5cd42f34ccdb665193960abb6e6248a1._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_5_5cd42f34ccdb665193960abb6e6248a1._comment deleted file mode 100644 index 457485614..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_5_5cd42f34ccdb665193960abb6e6248a1._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-08-17T15:36:49Z" - content=""" -I've gone ahead and implemented my last comment, see -<http://git-annex.branchable.com/design/external_special_remote_protocol/#index9h2> -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_6_34aecee25295477c51650ece94fda113._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_6_34aecee25295477c51650ece94fda113._comment deleted file mode 100644 index 39e447787..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_6_34aecee25295477c51650ece94fda113._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="bgilbert@a0c64716cf22216de5eeb15a5ca4f009164c8fb3" - nickname="bgilbert" - subject="comment 6" - date="2015-08-18T06:13:28Z" - content=""" -`readonly` seems to work in my early tests. Thanks for doing that. - -For consistency, shouldn't it be `readonly=yes` rather than `readonly=true`? -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_7_f3c26c061fdc6dcd181f998c73450525._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_7_f3c26c061fdc6dcd181f998c73450525._comment deleted file mode 100644 index 45130b41f..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_7_f3c26c061fdc6dcd181f998c73450525._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="bgilbert@a0c64716cf22216de5eeb15a5ca4f009164c8fb3" - nickname="bgilbert" - subject="comment 7" - date="2015-08-19T05:49:12Z" - content=""" -It seems that with encrypted remotes, `WHEREIS` passes the non-HMAC version of the `Key`. Thus, the URL returned by the external special remote won't actually point to the remote object. I'm not sure whether it's even useful to display URLs for encrypted files, but the current situation seems actively misleading. -"""]] diff --git a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_8_44ae52059790e105442067c311a7ec8b._comment b/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_8_44ae52059790e105442067c311a7ec8b._comment deleted file mode 100644 index 25c1ae81e..000000000 --- a/doc/bugs/External_special_remote_SETURLPRESENT_doesn__39__t_seem_to_work/comment_8_44ae52059790e105442067c311a7ec8b._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 8""" - date="2015-08-19T18:03:22Z" - content=""" -I chose readonly=true to be consistent with the annex.readonly git config -values. This is inconsistent with some other initremote stuff that uses -foo=yes. - -I should probably make everything accept everything, which seems to be -approximately what git-config does, but too much bother for now. - ----- - -Indeed, WHEREIS is not useful for encrypted (or chunked) special remotes. -I've made it not be used in those cases. -"""]] diff --git a/doc/bugs/Fails_to_add_files_with_a_newline_in_their_name___59____41__.mdwn b/doc/bugs/Fails_to_add_files_with_a_newline_in_their_name___59____41__.mdwn deleted file mode 100644 index f096a1532..000000000 --- a/doc/bugs/Fails_to_add_files_with_a_newline_in_their_name___59____41__.mdwn +++ /dev/null @@ -1,71 +0,0 @@ -### Please describe the problem. - -I know that it is actually a problem with my script and that some might treat it as a feature ;) but -- apparently I can have such filenames, git also manages to add it no problem (see below) - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - -5.20141024~bpo70+1 - -### 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 -$> cd 1000genomes/ -total 352 - 4 20131219.populations.tsv? 4 CHANGELOG? 4 phase1/ 4 README.crams? 4 README.sequence_data? - 4 20131219.superpopulations.tsv? 124 changelog_details/ 4 pilot_data/ 4 README.ebi_aspera_info? 4 release/ - 4 alignment.index? 0 complete_genomics_indices/ 4 README.alignment_data? 4 README.ftp_structure? 4 sequence.index? - 4 alignment_indices/ 128 data/ 4 README.analysis_history? 4 README.pilot_data? 16 sequence_indices/ - 4 analysis.sequence.index? 4 exome.alignment.index? 4 README.complete_genomics_data? 4 README.populations? 4 technical/ -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#9 !5130 [0].....................................:Wed Nov 26 11:40:13:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -$> git annex add 20131219.* -add 20131219.populations.tsv - git-annex: unknown response from git cat-file ("HEAD:./20131219.populations.tsv missing","HEAD:./20131219.populations.tsv\n") -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#10 !5131 [0].....................................:Wed Nov 26 11:40:36:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -*$> git annex add '20131219.populations.tsv -' -add 20131219.populations.tsv - git-annex: unknown response from git cat-file ("HEAD:./20131219.populations.tsv missing","HEAD:./20131219.populations.tsv\n") -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#11 !5132 [0].....................................:Wed Nov 26 11:41:07:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -$> ls -ld '20131219.populations.tsv -' -4 -r-------- 2 yoh yoh 91 Nov 26 10:44 20131219.populations.tsv? -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#12 !5133 [0].....................................:Wed Nov 26 11:41:15:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -$> acpolicy git-annex -git-annex: - Installed: 5.20141024~bpo70+1 - Candidate: 5.20141024~bpo70+1 - Version table: - *** 5.20141024~bpo70+1 0 - 100 http://debproxy/debian/ wheezy-backports/main amd64 Packages - 100 /var/lib/dpkg/status - 3.20120629 0 - 500 http://debproxy/debian/ wheezy/main amd64 Packages -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#13 !5134 [0].....................................:Wed Nov 26 11:41:31:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -*$> git add '20131219.populations.tsv -' -(git)/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124:1000genomes[master] -#14 !5135 [0].....................................:Wed Nov 26 11:42:58:. -head2:/backup/users/yoh/tmp/nobackup_1000genome-ls.20141124/1000genomes -$> - - -# End of transcript or log. -"""]] - -> [[dup|done]] of -> [[git_annex_import_fails_on_filenames_with_newlines_in_them]] --[[Joey]] diff --git a/doc/bugs/File_that_are_in_two_place_can_be_sequentially_copy_then_dropped.mdwn b/doc/bugs/File_that_are_in_two_place_can_be_sequentially_copy_then_dropped.mdwn deleted file mode 100644 index b794e6a3f..000000000 --- a/doc/bugs/File_that_are_in_two_place_can_be_sequentially_copy_then_dropped.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -### Please describe the problem. -I've a repository with a prefered content of "exclude=cours/vieux/* and ( include=cours/* or include=Programmes/* or include=Stage/* )", but there is a repository that has a (identical) copy both in cours/vieux and in Stage/ so git annex sync --content will -- get the content in Stage/ -- then drop it because it is in cours/vieux/ - -And again, and again... - -### What version of git-annex are you using? On what operating system? -git-annex 5.20140127 in debian/sid - -> This is actually a duplicate of -> [[Handling_of_files_inside_and_outside_archive_directory_at_the_same_time]]. -> As noted in that bug report, this should already be fixed in direct mode, -> but still happens in indirect mode when the full scan is done (at -> startup, and occasionally at other times). -> -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn b/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn deleted file mode 100644 index 7a96ff6c7..000000000 --- a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -### Please describe the problem. - -A special remote for Google cloud storage would appear to send the developer keys in the clear. -Obviously the content itself can be secured with the encryption but sending the auth keys in -the clear permits anybody listening (i.e. at a public WiFi access point) to gain r/w access to -the user's GCS store. - -### What steps will reproduce the problem? - -Setup a new special remote: - - git annex initremote gcs type=S3 chunk=2MiB encryption=none host=storage.googleapis.com bucket=gitannex - ... - git move --to=gcs blah - -Capture packets. Watch the developer keys go by in the headers. And in this case, see the content too because there's no -encryption turned on. But I believe that I know how to fix this. - -I tried to persuade `git annex` to use a SSL connection but without encouraging results: - - git annex initremote gcs type=S3 chunk=2MiB port=443 host=storage.googleapis.com bucket=gitannex - initremote gcs (checking bucket...) git-annex: ErrorClosed - - -### What version of git-annex are you using? On what operating system? - -Debian wheezy, git-annex version: 5.20141024~bpo70+1 - -### Please provide any additional information below. - -> [[done]]; port=443 supported since 5.20141203. --[[Joey]] diff --git a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_1_93183de95cc5c99a15eacbade19873ef._comment b/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_1_93183de95cc5c99a15eacbade19873ef._comment deleted file mode 100644 index 66856a32d..000000000 --- a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_1_93183de95cc5c99a15eacbade19873ef._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" - nickname="Rob" - subject="Proposed resolution" - date="2015-01-24T17:18:14Z" - content=""" -see [my other bug](https://git-annex.branchable.com/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/) for a proposed resolution: a GCS-optimized external special remote -"""]] diff --git a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_2_c01a47b9df3167c9af8e5e43ec138401._comment b/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_2_c01a47b9df3167c9af8e5e43ec138401._comment deleted file mode 100644 index 9006486df..000000000 --- a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_2_c01a47b9df3167c9af8e5e43ec138401._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-02-04T18:55:50Z" - content=""" -You need to upgrade to git-annex 5.20141203. With that version, -you can pass port=443 to git-annex initremote and it will then use -https. - -The old version you're using does not support this. - -Also, AFAIK, S3 does not send passwords over the wire; it uses a -challange-response, which proves to the S3 server that you possess the -access keys. This would not be susceptable to attackers in the way you -think it is. -"""]] diff --git a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided.mdwn b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided.mdwn deleted file mode 100644 index fe1bc1611..000000000 --- a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -docs say -GETURLS Key Prefix -Gets the recorded urls where a Key can be downloaded from. Only urls that start with the Prefix will be returned. The Prefix may be empty to get all urls. (git-annex replies one or more times with VALUE for each url. The final VALUE has an empty value, indicating the end of the url list. - -but when I am trying with a prefix -- doesn't return any... expected that one which is present and returned if I don't provide any prefix - -### What steps will reproduce the problem? - -git clone git://github.com/yarikoptic/datalad -b nf-custom-remotes -cd datalad -# there are requirements in requirements.txt, which you might need to install... or just do on smaug -git checkout 5b9cfd5008151c515f8bccadf39451055ab61b4b -DATALAD_LOGLEVEL=1 DATALAD_LOGTARGET=stderr tools/testing/make_test_repo archive r1 - -### What version of git-annex are you using? On what operating system? -5.20150302~nd80+1 now tried also with 5.20150318+yoh20150323+1~nd80+1 (ie snapshot from march 23) with the same success - -### 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 - -2015-03-26 15:56:05,612 [Level 1] Sending 'GETURLS SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat' (base.py:120) -2015-03-26 15:56:05,613 [Level 1] Received ['VALUE', 'dl+archive:SHA256E-s153--f378a42b6ff4d90091a7dfa37ebe1fe2fc5926eafd12cde1f2ba5fd1bcbf5e1e.tar.gz/d/test.dat'] (base.py:120) -2015-03-26 15:56:05,613 [Level 1] Received ['VALUE'] (base.py:120) - - -2015-03-26 15:57:37,389 [Level 1] Sending 'GETURLS SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat dl+archive:' (base.py:120) -2015-03-26 15:57:37,391 [Level 1] Received ['VALUE'] (base.py:120) - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_1_48f4cce32de8da1f2c8b3c29dc1a50a0._comment b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_1_48f4cce32de8da1f2c8b3c29dc1a50a0._comment deleted file mode 100644 index baa30f7ef..000000000 --- a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_1_48f4cce32de8da1f2c8b3c29dc1a50a0._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-27T17:37:14Z" - content=""" -This seems very unlikely, because the *indentical* code path is running -in both cases. In both cases it filters the list of urls to those prefixed with -the specified prefix; when no prefix is specified it uses "" as the -prefix. - -Also, when I test it myself using my own test code, it works as expected: - -<pre> -[2015-03-27 13:49:30 JEST] git-annex-remote-test --> GETURLS SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 dl+archive: -[2015-03-27 13:49:30 JEST] git-annex-remote-test <-- VALUE dl+archive:foo-bar-baz -[2015-03-27 13:49:30 JEST] git-annex-remote-test <-- VALUE -</pre> - -Are you sure that your test machinery has actually set any urls in the -second case? -"""]] diff --git a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment deleted file mode 100644 index 26815a6a5..000000000 --- a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="comment 2" - date="2015-03-27T20:04:23Z" - content=""" -could you try on your end with as obscure URL as mine? i.e. -'dl+archive:SHA256E-s153--f378a42b6ff4d90091a7dfa37ebe1fe2fc5926eafd12cde1f2ba5fd1bcbf5e1e.tar.gz/d/test.dat' -may be something to do with the / in the url name? -as posted on IRC, here are two runs protocols with all the details, where I don't spot any related difference in runs -http://www.onerussian.com/tmp/run-bad.txt_ http://www.onerussian.com/tmp/run-good.txt_ -"""]] diff --git a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_3_98b2b1915c50bca599f6d48fe117b213._comment b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_3_98b2b1915c50bca599f6d48fe117b213._comment deleted file mode 100644 index a137aac32..000000000 --- a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_3_98b2b1915c50bca599f6d48fe117b213._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="comment 3" - date="2015-03-27T22:33:52Z" - content=""" -[[!format sh \"\"\" -18:28 @yoh: joeyh: ok -- at least figured out where f.ck up is although yet not sure whose fault it is ;) -18:29 @yoh: looking into git-annex branch, -$> cat 738/f2b/SHA256E-s3--a665a45920422f9d417e4867efdc4fb8a04a1f3fff1fa07e998e86f7f7a27ae3.dat.log.web -1427495230.649621s 1 :dl+archive:SHA256E-s163--91440757454fb3eed74dcaadb9720b9b4c8b570daf5b31e125d035316e7e2faa.tar.gz/a/d/test.dat -18:29 @yoh: so there is \":\" before the url. If I prefix the prefix I send with \":\" I am getting correct replies (without any : prefixed) -\"\"\"]] - -so what could it be? -"""]] diff --git a/doc/bugs/GIT_DIR_support_incomplete.mdwn b/doc/bugs/GIT_DIR_support_incomplete.mdwn deleted file mode 100644 index 1b9738c4f..000000000 --- a/doc/bugs/GIT_DIR_support_incomplete.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -`GIT_DIR` support isn't right. Git does not look for `GIT_DIR/.git`; -git-annex does. - -Also, to support this scenario, support for core.worktree needs to be added -as well: - - mkdir repo workdir - git --work-tree=$PWD/workdir --git-dir=$PWD/repo init - export GIT_DIR=$PWD/repo - git status - # ok - git annex init "new repo" - # fail - ---[[Joey]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__.mdwn b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__.mdwn deleted file mode 100644 index bf7f4f391..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. -When I try to create a megaannex remote with pubkey encryption GPG complains about not finding the public key. - -### What steps will reproduce the problem? -See below - - -### What version of git-annex are you using? On what operating system? -5.20140129 under OSX. - - -### Please provide any additional information below. - -[[!format sh """ -% USERNAME="<username>" PASSWORD='<password>' git annex -vd initremote mega type=external externaltype=mega encryption=pubkey keyid=X folder=Documents mac=HMACSHA512 -[2014-02-06 11:39:14 CET] read: git ["--git-dir=/Users/dxtr/Documents/.git","--work-tree=/Users/dxtr/Documents","show-ref","git-annex"] -[2014-02-06 11:39:14 CET] read: git ["--git-dir=/Users/dxtr/Documents/.git","--work-tree=/Users/dxtr/Documents","show-ref","--hash","refs/heads/git-annex"] -[2014-02-06 11:39:14 CET] read: git ["--git-dir=/Users/dxtr/Documents/.git","--work-tree=/Users/dxtr/Documents","log","refs/heads/git-annex..62dc22cced06268fa5adcf54992eb1169c6ca1aa","--oneline","-n1"] -[2014-02-06 11:39:14 CET] chat: git ["--git-dir=/Users/dxtr/Documents/.git","--work-tree=/Users/dxtr/Documents","cat-file","--batch"] -initremote mega (encryption setup) [2014-02-06 11:39:14 CET] read: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--with-colons","--list-public-keys","46726B9A"] -[2014-02-06 11:39:14 CET] read: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","2","256"] -[2014-02-06 11:39:14 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--recipient","X","--encrypt","--no-encrypt-to","--no-default-recipient","--force-mdc","--no-textmode"] -(pubkey crypto with gpg key X) [2014-02-06 11:39:15 CET] chat: git-annex-remote-mega [] -[2014-02-06 11:39:15 CET] git-annex-remote-mega --> VERSION 1 -[2014-02-06 11:39:15 CET] git-annex-remote-mega <-- INITREMOTE -[2014-02-06 11:39:15 CET] git-annex-remote-mega --> GETCONFIG encryption -[2014-02-06 11:39:15 CET] git-annex-remote-mega <-- VALUE pubkey -[2014-02-06 11:39:15 CET] git-annex-remote-mega --> GETCONFIG folder -[2014-02-06 11:39:15 CET] git-annex-remote-mega <-- VALUE Documents -[2014-02-06 11:39:15 CET] git-annex-remote-mega --> SETCREDS mycreds <username> <password> -(gpg) [2014-02-06 11:39:15 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--decrypt"] -[2014-02-06 11:39:15 CET] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--encrypt","--no-encrypt-to","--no-default-recipient","--force-mdc","--no-textmode"] -gpg: no valid addressees -gpg: [stdin]: encryption failed: no such user id - -git-annex: user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--encrypt","--no-encrypt-to","--no-default-recipient","--force-mdc","--no-textmode"] exited 2) -failed -git-annex: initremote: 1 failed - - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_1_ac3631024abf372e6f578a472b86d792._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_1_ac3631024abf372e6f578a472b86d792._comment deleted file mode 100644 index 1d71eebf4..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_1_ac3631024abf372e6f578a472b86d792._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw" - nickname="dxtrish" - subject="comment 1" - date="2014-02-06T11:00:49Z" - content=""" -I just confirmed it works with encryption=hybrid -"""]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_980c149d7f9040f5e71e662d95a5fbf1._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_980c149d7f9040f5e71e662d95a5fbf1._comment deleted file mode 100644 index 2c5bdc120..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_980c149d7f9040f5e71e662d95a5fbf1._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="71.80.94.56" - subject="comment 3" - date="2014-02-06T21:53:23Z" - content=""" -I can reproduce this, but only when using the hook special remote, so it's some problem with it. -directory special remote works ok. -"""]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_c279f5cc3f96910287e72bf59120d02b._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_c279f5cc3f96910287e72bf59120d02b._comment deleted file mode 100644 index b5e9c3c21..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_3_c279f5cc3f96910287e72bf59120d02b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="71.80.94.56" - subject="comment 3" - date="2014-02-06T22:07:55Z" - content=""" -Actually, it seems to affect also S3 and other remotes that call setCreds. -"""]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_4_ec6abe7074f767f866e9618d65a4a900._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_4_ec6abe7074f767f866e9618d65a4a900._comment deleted file mode 100644 index b61b0626a..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_4_ec6abe7074f767f866e9618d65a4a900._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw" - nickname="dxtrish" - subject="comment 4" - date="2014-02-07T11:11:23Z" - content=""" -Could it be some general issue with setCreds? - -The reason I'm wondering is that megaannex isn't really working. It doesn't seem to (properly) get the credentials so it's acting funny and getting an Invalid Argument exception where, according to what I understand from the documentation, it shouldn't be possible to get an Invalid Argument exception. - -Ofcourse I have contacted the maintainer of megaannex (TobiasTheViking on github) too. I've also started looking in to it myself. -"""]] diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_5_44f80d89360a5620f919f8bc7c1c2879._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_5_44f80d89360a5620f919f8bc7c1c2879._comment deleted file mode 100644 index b5495e454..000000000 --- a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_5_44f80d89360a5620f919f8bc7c1c2879._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkzwmw_zyMpZC9_J7ey--woeYPoZkAOgGw" - nickname="dxtrish" - subject="comment 5" - date="2014-02-07T11:12:24Z" - content=""" -Oh, sorry. I didn't see that you had already fixed it. -"""]] diff --git a/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn b/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn deleted file mode 100644 index eef705e69..000000000 --- a/doc/bugs/Git-Annex_requires_all_repositories_to_repair.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -I recently had my git-annex repository die and it needed to be repaired. Two of my repositories are external hard drives. When I tried to use git-annex repair, it would churn for some hours, then error because the external hard drives were not plugged in. When I brought the two hard drives home from the various places that they are (safely) stored, it all worked fine, but it would have been great if git-annex repair could somehow do what it could with what was connected and do the rest as and when the other drives are plugged in. This must only become more of a problem as git-annex is used for longer, as one may have a handful of USB keys storing a little on each. - -[[!taglink moreinfo]] - -> With the lack of an error message or any followup, it's hard to take -> this bug seriously, so [[done]] --[[Joey]] diff --git a/doc/bugs/Git-Annex_requires_all_repositories_to_repair/comment_1_dff1424e48835d7d3eb8653fc59de18a._comment b/doc/bugs/Git-Annex_requires_all_repositories_to_repair/comment_1_dff1424e48835d7d3eb8653fc59de18a._comment deleted file mode 100644 index d44c30f32..000000000 --- a/doc/bugs/Git-Annex_requires_all_repositories_to_repair/comment_1_dff1424e48835d7d3eb8653fc59de18a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.244" - subject="comment 1" - date="2014-04-07T19:25:25Z" - content=""" -Repair does not require access to remotes, but it will certianly yield a better result to have one remote available. Otherwise, information that cannot be repaired will be missing from the repository. Repair will still successfully complete in this situation though. - -If you have an error message, please paste it. -"""]] diff --git a/doc/bugs/Git_annex_add_._dies_when_you_add_too_much.mdwn b/doc/bugs/Git_annex_add_._dies_when_you_add_too_much.mdwn deleted file mode 100644 index 9443a4fbd..000000000 --- a/doc/bugs/Git_annex_add_._dies_when_you_add_too_much.mdwn +++ /dev/null @@ -1,58 +0,0 @@ -### Please describe the problem. - -I was playing around thinking to try out git-annex, and bup - -I sucessfully added 6GB of images in subdirectories in ~/Pictures, so decided to push over another dir full - - -more than 30GB more... - -sven@quad:~/Pictures$ git annex add . -.... -add 2012/01/10/20120110-024457/IMG_1830.JPG -git-annex: <file descriptor: 7>: hFlush: resource vanished (Broken pipe) -failed -add 2012/01/10/20120110-024457/IMG_1831.JPG -git-annex: <file descriptor: 7>: hFlush: resource vanis -sven@quad:~/Pictures$ -sven@quad:~/Pictures$ git annex add . -Stack space overflow: current size 8388608 bytes. -Use `+RTS -Ksize -RTS' to increase it. -sven@quad:~/Pictures$ git git commit -a -m added -git: 'git' is not a git command. See 'git --help'. - -Did you mean this? - init -sven@quad:~/Pictures$ git commit -a -m added -Bus error (core dumped) - - - -### What steps will reproduce the problem? -see above - -### What version of git-annex are you using? On what operating system? -sven@quad:~/Pictures$ git annex version -git-annex version: 3.20120406 -local repository version: 3 -default repository version: 3 -supported repository versions: 3 -upgrade supported from repository versions: 0 1 2 -sven@quad:~/Pictures$ uname -a -Linux quad 3.8.0-34-generic #49~precise1-Ubuntu SMP Wed Nov 13 18:05:00 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux - - -### 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. -"""]] - -> Ancient git-annex version. Doubt it affects current version. [[!tag moreinfo]] --[[Joey]] - ->> Actually, this is a dup of [[runs_of_of_memory_adding_2_million_files]] so [[done]] --[[Joey]] diff --git a/doc/bugs/Git_annex_add_._dies_when_you_add_too_much/comment_1_a99b96c38bba3af54e0152cc3730c16c._comment b/doc/bugs/Git_annex_add_._dies_when_you_add_too_much/comment_1_a99b96c38bba3af54e0152cc3730c16c._comment deleted file mode 100644 index de4928b3a..000000000 --- a/doc/bugs/Git_annex_add_._dies_when_you_add_too_much/comment_1_a99b96c38bba3af54e0152cc3730c16c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 1" - date="2014-01-13T19:22:12Z" - content=""" -It looks like git-annex was leaking memory, and so ran out and died. - -But, you're using an ancient version of git-annex from 2012. Upgrade to a current version and write back if it still has a memory leak. I doubt it does. -"""]] diff --git a/doc/bugs/Git_annex_for_Windows_keyboard_shortcut.mdwn b/doc/bugs/Git_annex_for_Windows_keyboard_shortcut.mdwn deleted file mode 100644 index 4d48078a2..000000000 --- a/doc/bugs/Git_annex_for_Windows_keyboard_shortcut.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. -After git annex been installed, I cannot any longer (with no hacks) use my right ALT+A shortcut creating special char. -After installing git annex for Windows it overtook this shortcut and redirects my browser to a weird localhost server with a weird port. - -### What steps will reproduce the problem? -Installing git annex for Windows and tapping rAlt+A. :) - -### What version of git-annex are you using? On what operating system? -The newest version, Windows 8. - -### 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. -"""]] - -> Seems I misunderstood, I thought that would only apply in the start menu. -> Removed the shortcut. [[done]] --[[Joey]] diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn deleted file mode 100644 index 11040e301..000000000 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn +++ /dev/null @@ -1,71 +0,0 @@ -Hi, -I already have told about that in a comment here <http://git-annex.branchable.com/bugs/submodule_path_problem/#comment-e86330d15b714a41a07b6548fbc79bb2>, but I am not sure it will be seen. - -Then here is an official bug report. -### Please describe the problem. - -I have a problem with submodules when the git repository is not a submodule everywhere. - -For instance, if A is a git annexed repository and B another git repository. If B adds A as submodules. The symlinks added in A as submodule won't work in the original A. - -### What steps will reproduce the problem? - - # creating the master repository - mkdir annex_master - cd annex_master/ - git init - # hack: adding a file to create the master branch - touch start - git add start - git commit -m "start" - cd .. - # create another repository - mkdir annex_sub - cd annex_sub/ - git init - # hack: adding a file to create the master branch - touch start - git add start - git commit -m "start" - # it is a annexed repository - git annex init sub - # add the other repository as submodule of the master one - cd ../annex_master/ - git submodule add ../annex_sub/ module - cd module/ - git annex init sub_module - git annex sync origin - # add an annexed file - echo test > test - git annex add - git annex sync - # go back to the origin repository - cd ../../annex_sub/ - git annex sync - ls -l -This returns test -> ../.git/modules/module/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2 - -Actually, the file committed is correct. But the fact it points to '../.git/modules/module/...' makes the link work only if the repository is also a submodule and if this submodule is also located in the modules folder in the parent git repository. - -I tried playing with making the repository direct and then indirect, hoping that would fix the symlinks, but it did not work. -### What version of git-annex are you using? On what operating system? - - $ git-annex version - git-annex version: 4.20130802 - ... - - $ git --version - git version 1.8.3.2 - - $ uname -a - Linux konixwork 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux - -### Please provide any additional information below. - -[[!tag confirmed]] - -> [[fixed|done]] -- with a current version of git, git-annex now supports -> [[/submodules]]. NB: Filesystem must support symlinks, or this won't -> work. -> -> -- [[Joey]] diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_1_b3197993dbdfaf2db5e4651ac54a896e._comment b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_1_b3197993dbdfaf2db5e4651ac54a896e._comment deleted file mode 100644 index 8ff232159..000000000 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_1_b3197993dbdfaf2db5e4651ac54a896e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.63" - subject="comment 1" - date="2013-08-24T18:49:18Z" - content=""" -git-annex assumes that it can make a stable symlink from a file in the working tree to a file in the .git directory. There are several ways to break this. One, as noted, is sometimes using a repository as a submodule, and sometimes not. Another would be to play around with `GIT_DIR`. - -I don't see a way git-annex can support those use cases, at least in indirect mode. - -It does seem like, in direct mode, it should just work. git-annex will commit various symlinks to git, but these symlinks will never be followed to get at the content of a file, since direct mode arranges for the content to be directly present in the working tree. -"""]] diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_2_1fbbd02e61ef524597dafd69460b00b4._comment b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_2_1fbbd02e61ef524597dafd69460b00b4._comment deleted file mode 100644 index b7aa61f17..000000000 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_2_1fbbd02e61ef524597dafd69460b00b4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="konubinix" - ip="82.243.233.186" - subject="Thanks" - date="2013-08-26T06:25:19Z" - content=""" -Thanks for the reply. - -Also thanks for this great tool (Though I am not sure I truelly realize the true power of git annex yet). -"""]] diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_3_c63b4a86b84c1e4077ddf10858ef5761._comment b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_3_c63b4a86b84c1e4077ddf10858ef5761._comment deleted file mode 100644 index 0f3d22325..000000000 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_3_c63b4a86b84c1e4077ddf10858ef5761._comment +++ /dev/null @@ -1,34 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-02-27T19:45:27Z" - content=""" -One way that seems to work to use submodules with git-annex: - -* Replace the submodule's .git file with a symlink to the location the - contents of the file pointed at. (Eg, ../.git/modules/$whatever) -* Unset core.worktree in the submodule's .git/config, which will - normally be set by git when checking out a submodule. - -With this configuration, git seems to work ok (although it's hard to tell -if there might be some code path that requires .git to be a file and not a -directory.. seems unlikely though!). And, git-annex works fine, because -it uses paths relative to the .git symlink, so -".git/annex/objects/xx/yy/sha/sha" is in the symlink target like usual. - -Converting .git to a symlink also means that the same repo that is used -as a submodule can be moved to a different "mount point" in the parent -repo, or used standalone, and the git-annex object links in it will -continue to work. - -Looking at the git code, it would be a problem if a code path called -read_gitfile without also checking is_git_directory or similar. Auditing -the code, I have found a lot of places that are careful to check both -possibilities, and none that are a problem with a .git directory; -although I don't understand all the git code so not 100% sure. - -Since a submodule will have core.worktree set, git-annex -could cheaply check that with nearly no overhead as a first pass to -detect a submodule, and then do whatever might be appropriate to support -submodules -- such as replacing .git with a symlink. -"""]] diff --git a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_4_7dae2920926e7556de442952c4a318d9._comment b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_4_7dae2920926e7556de442952c4a318d9._comment deleted file mode 100644 index 70d24cb38..000000000 --- a/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_4_7dae2920926e7556de442952c4a318d9._comment +++ /dev/null @@ -1,35 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-02-27T20:00:54Z" - content=""" -Also, git has only used gitfiles for submodules since git 1.7.8. - -So, repos using submodules that were cloned with an older version of git -would use a .git directory. And, if some part of git only supports -gitfiles, it wouldn't work with such repositories. Which would probably be -considered a bug since git doesn't break support for existing checkouts. - -git-mv and git-rm man pages have a SUBMODULES section documenting that. -Including the behavior when using git-rm to try to delete a submodule that -uses a .git directory, instead of a gitfile: - -> Only submodules using a gitfile (which means they were cloned -> with a Git version 1.7.8 or newer) will be removed from the work -> tree, as their repository lives inside the .git directory of the -> superproject. If a submodule (or one of those nested inside it) -> still uses a .git directory, `git rm` will fail - no matter if forced -> or not - to protect the submodule's history. - -So, I doubt that git is going to break support for .git directory (or symlink) -in a submodule. But, using that might prevent a few things, particularly -git-rm of a submodule. - -<pre> -joey@darkstar:~/tmp/r2>git rm module -error: the following submodule (or one of its nested submodules) -uses a .git directory: - module -(use 'rm -rf' if you really want to remove it including all of its history) -</pre> -"""]] diff --git a/doc/bugs/Glacier_remote_doesn__39__t_pass_the_--region_parameter_to_glacier-cli_on_hasKey.mdwn b/doc/bugs/Glacier_remote_doesn__39__t_pass_the_--region_parameter_to_glacier-cli_on_hasKey.mdwn deleted file mode 100644 index 7756db866..000000000 --- a/doc/bugs/Glacier_remote_doesn__39__t_pass_the_--region_parameter_to_glacier-cli_on_hasKey.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -### Please describe the problem. -hasKey check fails when using a Glacier special remote with a non-default region setting. - -### What steps will reproduce the problem? -1. Configure a Glacier special remote with a region other than us-east-1 -2. Move some files to the remote -3. Somehow let galcier-cli cache expire. In my case this was waiting for more than 60 hours. -4. Try to copy the file to the glacier remote again. - -### What version of git-annex are you using? On what operating system? -5.20140227 on Ubuntu 12.04 - -### Please provide any additional information below. - -[[!format sh """ -user@server:$ git annex copy my_file.txt --to glacier -copy my_file.txt (checking glacier...) Traceback (most recent call last): - File "/bin/glacier", line 730, in <module> - App().main() - File "/bin/glacier", line 716, in main - self.args.func() - File "/bin/glacier", line 620, in archive_checkpresent - wait=self.args.wait) - File "/bin/glacier", line 442, in _vault_sync - vault = self.connection.get_vault(vault_name) - File "/usr/local/lib/python2.7/dist-packages/boto/glacier/layer2.py", line 82, in get_vault - response_data = self.layer1.describe_vault(name) - File "/usr/local/lib/python2.7/dist-packages/boto/glacier/layer1.py", line 195, in describe_vault - return self.make_request('GET', uri) - File "/usr/local/lib/python2.7/dist-packages/boto/glacier/layer1.py", line 118, in make_request - raise UnexpectedHTTPResponseError(ok_responses, response) -boto.glacier.exceptions.UnexpectedHTTPResponseError: Expected 200, got (404, code=ResourceNotFoundException, message=Vault not found for ARN: arn:aws:glacier:us-east-1:111111111111:vaults/myvault) -(user error (glacier ["archive","checkpresent","myvault","--quiet","SHA256E-s1111111--aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.JPG"] exited 1)) failed -git-annex: copy: 1 failed -"""]] - -> [[fixed|done]]; made it use the same glacierParams as everything else. -> --[[Joey]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates.mdwn b/doc/bugs/Glacier_remote_uploads_duplicates.mdwn deleted file mode 100644 index 75014a5e0..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -Other references: - -https://github.com/basak/glacier-cli/pull/19 -http://git-annex.branchable.com/special_remotes/glacier/#comment-a2b05b8dc2d640ee498d90398f02931c - -#### Background - - * Glacier doesn't support keys that the client selects, unlike S3. If you upload to Glacier, Glacier assigns a unique ID, not the client. - * Glacier does support an "archive description" which is immutable. It also provides this "archive description" in an inventory listing, together with the unique IDs. - * An "archive description" is not a unique key. It's perfectly possible to upload multiple archives to Glacier with the same "archive description". - * glacier-cli uses the "archive description" field as an upload identifier, since the unique IDs are unfriendly to users. However, since they are potentially ambiguous identifiers, it also supports disambiguation using the ID itself. See "Addressing Archives" in README.md for details. - -#### The Problem - -This what I believe is happening in the two reports referenced above. When git-annex is used without `--trust-glacier`, it can end up uploading the same data multiple times. From git-annex's point of view, it cannot verify that the data is already in Glacier, so it uploads again, expecting an overwrite operation if the key is already in Glacier. Since glacier-cli maps the key to an "archive description" that can be duplicated, this is not what happens. Instead, a second archive is uploaded. - -When git-annex later does a "checkpresent" operation, glacier-cli fails. This is because the request is ambiguous, since there are two archives in Glacier with the same "key". The error message could be better here, but I believe that the behaviour is correct. - -#### Discussion - -glacier-cli can find out what data Glacier claims to have using an inventory retrieval. However, this retrieval takes about four hours and can be out of date (eg. if someone else recently deleted the archive from another client). Thus, I can understand git-annex's desire not to trust this data or a cache of it. - -However, whatever we do, it is impossible to map an "upload or overwrite on key X" type command to Glacier. We'll always end up with duplicates. Even if git-annex stored the Glacier archive IDs, there is no API to replace an existing archive with the same ID, and inventories are out of date even before we retrieve them. - -#### Workaround - -If the problem is as I think it is, always applying `--trust-glacier` should prevent the problem from occurring in most cases, since git-annex will run "checkpresent" and glacier-cli will confirm that the archive exists. - -To fix the problem after it has occurred, it should be sufficient to delete duplicates using glacier-cli, since they _should_ be identical to each other. Some enhancement of the `glacier-cli archive list` command would help here. - -Update 10 June 2013: I've pushed a `glacier-cli` update and helper script in commit `b68835`. This adds a `--force-ids` option to `glacier archive list`, with which the helper script `glacier-list-duplicates.sh` uses to identify duplicates that can be removed. If you're affected by this issue, I suggest that you use this helper to identify and fix your problem by removing the duplicates. Please do so carefully by checking that the output of the helper is correct before you use it to delete the duplicates. See the comments at the top of the helper script for usage information. - -> [[fixed|done]], at least for the only well-working case for glacier, where -> only one repository can access glacier directly. --[[Joey]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_1_8aef582a0f0d0c7f764b425fc45de3b4._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_1_8aef582a0f0d0c7f764b425fc45de3b4._comment deleted file mode 100644 index 9e42d4cae..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_1_8aef582a0f0d0c7f764b425fc45de3b4._comment +++ /dev/null @@ -1,25 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-05-23T15:55:16Z" - content=""" -Please beware of the warning on the man page when using --trust-glacier-inventory: - -> Be careful using this, especially if you or someone else might -> have recently removed a file from Glacier. If you try to drop -> the only other copy of the file, and this switch is enabled, you -> could lose data! - -While I'm inclined to want git-annex to store the necessary mappings from keys to glacier IDs in the git-annex branch, which would allow uploads/downloads from multiple repositories to the same glacier repository, it will not help with this problem. The git-annex branch can be out of date too. - -It seems that what's needed is a separate form of the checkpresent hook, that's used when deciding whether to copy data to glacier. -We want this to trust the glacier inventory. But we don't want to trust the glacier inventory when moving data to glacier, or when running `git annex drop`! (unless --trust-glacier-inventory is specified). I think this would be easy to add. If you're up for testing a patch, I could do it today. - -BTW, there does seem to be a workaround that avoids duplicate copies to glacier: - - git annex copy --to glacier --not --in glacier - -While normally copy checks the inventory to see if a key has been sent to glacier, and so will re-send, the `--not --in glacier` -trusts the location tracking information, so if git-annex has sent the key before, it will skip the copy. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment deleted file mode 100644 index 859377308..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_2_150ce8b7c4424a83c4b1760da5a89d27._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 2" - date="2013-05-23T15:57:08Z" - content=""" -I suppose another way to fix it along similar lines would be to make `git annex copy` always trust location tracking information when deciding whether to copy. I'm not sure how I feel about this though -- it might make things less robust in situations where `git annex copy` is run as a backup, and location tracking could have gotten out of date. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_3_718af5048c5f894eee134547a2e0a644._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_3_718af5048c5f894eee134547a2e0a644._comment deleted file mode 100644 index 4091e258c..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_3_718af5048c5f894eee134547a2e0a644._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 3" - date="2013-05-23T15:59:37Z" - content=""" -It's also worth noting that the assistant always trusts the location log when deciding whether to send a key to a remote. So I think it will not trigger this bug. It seems only `git annex copy` will. (Well, maybe `git annex move` too in an edge case.) -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_4_184ad0f8c2847309632f8c18b918cd42._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_4_184ad0f8c2847309632f8c18b918cd42._comment deleted file mode 100644 index 415103a01..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_4_184ad0f8c2847309632f8c18b918cd42._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 4" - date="2013-05-27T22:24:44Z" - content=""" -> If you're up for testing a patch, I could do it today. - -I'm happy to test a patch. I haven't successfully compiled git-annex on my Mac, which is the only computer I have for the next month or so, but it wasn't too hard to get it to work on my Linux box. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_5_6980a912d3582c2f2511e4827e9e76b3._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_5_6980a912d3582c2f2511e4827e9e76b3._comment deleted file mode 100644 index 1d4bbf1fd..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_5_6980a912d3582c2f2511e4827e9e76b3._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 5" - date="2013-05-29T17:54:11Z" - content=""" -I started to make a branch with the change I suggested, but then I had another idea. - -The checkpresent hook can return either True or, False, or fail with a message if it cannot successfully check the remote. Currently for glacier, when --trust-glacier is not set, it always returns False. Crucially, in the case when a file is in glacier, this is telling git-annex it's not there, so copy re-uploads it. What if it instead, when the glacier inventory is missing a file, it returns False. And when the glacier inventory has a file, unless --trust-glacier is set, it *fails*. - -The result would be: - -* `git annex copy --to glacier` would only send things not listed in inventory. If a file is listed in the inventory, `copy` - would complain that --trust-glacier` is not set, and not re-upload the file. -* `git annex drop` would only trust that glacier has a file when --trust-glacier is set. Behavior unchanged. -* `git annex move --to glacier`, when the file is not listed in inventory, would send the file, and delete it locally. Behavior unchanged. -* `git annex move --to glacier`, when the file is listed in inventory, would only trust that glacier has the file when --trust-glacier is set -* `git annex copy --from glacier` / `git annex get`, when the file is located in glacier, would trust the location log, and attempt to get the file from glacier. - -This seems like it should do the right thing in all cases, but I have not tested it. I've pushed a `glacier` branch with this change. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment deleted file mode 100644 index 2a140eb49..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkexhIpGcYa22aPQtLm-StpHiF-MHYPh5w" - nickname="Robie" - subject="comment 6" - date="2013-06-10T17:24:34Z" - content=""" -This seems reasonable to me. - -One other possibility that you could end up with a duplicate: if `glacier-cli`'s cache is not up to date. For example: hosts A and B both have (the same) annex with the same Glacier special remote defined. Host A copies a file to Glacier. On host B, the `glacier-cli` cache doesn't know about the file, and so a copy to Glacier on host B also succeeds. When the cache is later brought up to date `glacier vault sync`, then the duplicate appears. - -I'm not sure what we can do about this. Perhaps we need to accept that duplicates will occur, and handle them more gracefully. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_7_e96187bad3dae2f5f95118f6df87a1ec._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_7_e96187bad3dae2f5f95118f6df87a1ec._comment deleted file mode 100644 index 26cbb5a47..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_7_e96187bad3dae2f5f95118f6df87a1ec._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 7" - date="2013-06-11T14:38:19Z" - content=""" -Ok, I've merged the glacier branch into master. I would still be happy to see some testing of this before my next release (in a week). - -I guess I'll close this bug report. There are certainly still problems that can happen if there are multiple repositories all writing to glacier independently. Seems to me that one good way to deal with this is to set up a single remote that is configured to be a gateway to glacier. -"""]] diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_8_34216b514a6fca788cfacb8579ce5311._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_8_34216b514a6fca788cfacb8579ce5311._comment deleted file mode 100644 index 67fd5354b..000000000 --- a/doc/bugs/Glacier_remote_uploads_duplicates/comment_8_34216b514a6fca788cfacb8579ce5311._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="For those on Mac OS X" - date="2013-11-18T00:00:32Z" - content=""" -The duplicates script fails because the BSD/MacOS version of uniq doesn't support the -D option. - -You can work around this by installing the GNU version using Homebrew ('brew install coreutils') and then replacing the 'uniq' in the script with 'guniq' (Homebrew prefixes the coreutils with \"g\" by default). - -I seem to still be running in to this bug using git annex version 4.20131106 and 'git annex copy --to glacier' without the '--not --in glacier' flags. It's not a problem to use the extra flags but I wasn't originally aware of this issue and the duplicates don't seem to always occur. I'll do some more testing and see whether I can reliably predict what will create duplicates and what won't. -"""]] diff --git a/doc/bugs/Google_Cloud_Storage_Nearline.mdwn b/doc/bugs/Google_Cloud_Storage_Nearline.mdwn deleted file mode 100644 index 4aadc85d7..000000000 --- a/doc/bugs/Google_Cloud_Storage_Nearline.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -### Please describe the problem. - -Google's Nearline Storage does not work with git-annex. - -### What steps will reproduce the problem? - -Create a remote on google cloud storage. AFAIK there is no way to tell annex to create a nearline bucket so what I did was to let it create a regular bucket. At this point everything works I can store retrieve files from the remote. Then I download the buckets content delete the bucket and recreate a nearline bucket with the same name as the old one and re-upload the content. With the new nearline bucket trying to put files there results in a 400 bad request error. - - -### What version of git-annex are you using? On what operating system? - -Mac OS X, git-annex version: 5.20150219-g52daae5 - -### 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. -"""]] - -> This is a dup of [[todo/Nearline_support]] ; [[done]] --[[Joey]] diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__.mdwn b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__.mdwn deleted file mode 100644 index a5bb5cb33..000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -Git annex's special S3 remote doesn't seem to work with DRA buckets in Google cloud storage. - -### What steps will reproduce the problem? - -I created a DRA-style bucket in Google cloud storage: - - gsutil mb gs://gitannex-dra - -Then followed [this hint](https://gist.github.com/jterrace/4576324) to -set up use of GCS. Except that it didn't work: - - git annex initremote gcs type=S3 encryption=none host=storage.googleapis.com port=80 bucket=gitannex-dra - initremote gcs (checking bucket...) git-annex: Invalid argument. - -### What version of git-annex are you using? On what operating system? - -Wheezy, git-annex version: 5.20141024~bpo70+1 - -### Please provide any additional information below. - -There didn't seem to be any extra logs and `--debug` didn't seem to add anything useful. - -> Closing, as it seems others have gotten this to work with a more recent -> version of git-annex. Please followup if it doesn't work. [[done]] -> --[[Joey]] diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_71e3fb544914c1924f8517173371c205._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_71e3fb544914c1924f8517173371c205._comment deleted file mode 100644 index 2d9161264..000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_71e3fb544914c1924f8517173371c205._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" - nickname="Rob" - subject="proposed resolution" - date="2015-01-24T17:10:20Z" - content=""" -I believe that I could write an external special remote to enable a full GCS feature set to resolve this. I'll do this. If someone has already done so, please add to the comments. -"""]] diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment deleted file mode 100644 index 2420e3d0c..000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" - nickname="Rob" - subject="Additional experiment" - date="2015-01-22T18:26:17Z" - content=""" -I tried unuccessfully on GCS DRA bucket gitannex-dra: - - git annex initremote gcs type=S3 chunk=2MiB encryption=none host=storage.googleapis.com bucket=gitannex-dra storageclass=DURABLE_REDUCED_AVAILABILITY - initremote gcs (checking bucket...) git-annex: Invalid argument. - - -"""]] diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_70c3d9014f5be74e225a241ae7bea95a._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_70c3d9014f5be74e225a241ae7bea95a._comment deleted file mode 100644 index 69251c1f0..000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_70c3d9014f5be74e225a241ae7bea95a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="bgilbert@a0c64716cf22216de5eeb15a5ca4f009164c8fb3" - nickname="bgilbert" - subject="External special remote" - date="2015-08-09T23:05:04Z" - content=""" -Rob, I have now [done so](https://github.com/bgilbert/gcsannex). Feedback welcome. -"""]] diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_e13eac28bd05f09210018a29c13aa73c._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_e13eac28bd05f09210018a29c13aa73c._comment deleted file mode 100644 index 00243b5e4..000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_4_e13eac28bd05f09210018a29c13aa73c._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-02-04T18:46:32Z" - content=""" -The first thing to try is going to be a current version of git-annex, -not the wheezy backport, which uses an old and not very good S3 library. - -So, upgrade to git-annex 5.20141203 or newer. -The new aws library used by that version will probably work -- it's -presumably what was used to make <https://gist.github.com/jterrace/4576324> - -Even if it fails, will probably fail in a more useful way than throwing -an "Invalid argument" exception. -"""]] diff --git a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status.mdwn b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status.mdwn deleted file mode 100644 index 07d6f3eb3..000000000 --- a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status.mdwn +++ /dev/null @@ -1,69 +0,0 @@ -### Please describe the problem. - -[[!tag moreinfo]] - -I added a lot of files to my annex in direct mode. Now I want to switch to indirect mode. git-annex status and indirect create an out-of-memory error. - -### What steps will reproduce the problem? - -I am not really sure, I added a lot of files to the annex, almost 3TB. -Then either git-annex status or git-annex indirect cause a similar error (see below). - - -### What version of git-annex are you using? On what operating system? - -git-annex version: 4.20130501-g4a5bfb3 -local repository version: 4 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP - -Ubuntu precise -3.2.0-26-generic - - -### 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/debug.log -git-annex status -supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL -supported remote types: git S3 bup directory rsync web webdav glacier hook -repository mode: direct -trusted repositories: 0 -semitrusted repositories: 7 - 00000000-0000-0000-0000-000000000001 -- web - 0b8e6666-80d5-11e2-adf3-6f4d3d6ef0aa -- marek@x4:~/tmp/annex - 65c057c6-6027-11e2-84b0-b77d71696e49 -- here (.) - 96b31c5e-6524-11e2-b136-fbd1a03b2799 -- BackupOnGlacier - b509c388-629a-11e2-be5f-d376e201ad86 -- marek@x201:~/AllData - c636e33c-6e31-11e2-a9c4-a3c5546d69d9 -- desktop - fbaa1c3a-60d7-11e2-842f-9348368d2f4c -- . -untrusted repositories: 0 -dead repositories: 0 -transfers in progress: none -available local disk space: 81 gigabytes (+1 megabyte reserved) -temporary directory size: 9 megabytes (clean up with git-annex unused) -local annex keys: 61396 -local annex size: 3 terabytes -known annex keys: git-annex: out of memory (requested 985661440 bytes) - -OR - -git-annex indirect -commit git-annex: out of memory (requested 985661440 bytes) - - - - - -# End of transcript or log. -"""]] - -> [[fixed|done]]. However, if you saw this behavior, -> you have large files checked directly into git. You may -> want to examine your repository and use git filter-branch to clean -> it up. -> --[[Joey]] diff --git a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_1_94c678e1348280a96f11d7456c240d3a._comment b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_1_94c678e1348280a96f11d7456c240d3a._comment deleted file mode 100644 index 06b56c47f..000000000 --- a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_1_94c678e1348280a96f11d7456c240d3a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="Marek" - subject="comment 1" - date="2013-05-03T21:12:39Z" - content=""" -I have not yet commited after git-annex add. -"""]] diff --git a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_2_09450d58df2373174a1f0d90b08e9eb3._comment b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_2_09450d58df2373174a1f0d90b08e9eb3._comment deleted file mode 100644 index b0e5bb5c2..000000000 --- a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_2_09450d58df2373174a1f0d90b08e9eb3._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 2" - date="2013-05-06T15:59:00Z" - content=""" -Looks like you have around 61396 files, which is not really very many. Is that guess accurate? - -I have repositories with that many files, that do not run out of memory, or even use much memory at all when running `git annex status`. Just tried and it needed 15 mb, not 900. - -Since you're using Ubuntu precise with a current version of git-annex, I'll bet you installed from fmarier's PPA. Is that right? - -In case this is a problem only with the build in the PPA, can you please download the [[/install/Linux_standalone]] tarball, and try the same command using the git-annex from there? -"""]] diff --git a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_3_a07105226ef3488b97731db004651976._comment b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_3_a07105226ef3488b97731db004651976._comment deleted file mode 100644 index e4795e5a8..000000000 --- a/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_3_a07105226ef3488b97731db004651976._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.153.14.105" - subject="comment 3" - date="2013-09-19T18:59:42Z" - content=""" -It turns out that if you are using direct mode and you manually `git commit some-file` that is really big, that file is checked directly into git. Which is why direct mode's docs say not to do that. - -Once you've got an enormous file in git, either on purpose on by mistake, it turns out that git-annex tries to buffer the whole file content in some situations. I am in the process of fixing those memory leaks. -"""]] diff --git a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__.mdwn b/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__.mdwn deleted file mode 100644 index 9b5d52220..000000000 --- a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. -Incorrect merge of direct repos. - -### What steps will reproduce the problem? - -[[!format sh """ -# setting up stuff -test/a$ git init -test/a$ git annex init -test/a$ git annex direct -test/a$ touch firstfile -test/a$ git annex add firstfile -$ git clone test/a -$ mv a test/b -test/b$ git annex direct - -# actual scenario -test/b$ echo bbbb > f -test/b$ git annex add f -test/b$ git annex sync -test/a$ mkdir f -test/a$ echo aaaa > f/f -test/a$ git annex add f/f -test/a$ git annex sync -test/b$ git annex sync -test/b$ rm f -test/b$ git annex sync -test/b$ ls -test/b$ firstfile -test/b$ f.variant-SHA256E-s5--4551db5fd4d56e27be71a8a943070cfaa4342b8e960a326e2d6427b3aa0a5a48.variant-43f5 -test/a$ git annex sync # A's f/f is no longer to be found -"""]] - -### What version of git-annex are you using? On what operating system? -[[!format sh """ -git-annex version: 4.20131031-g7d99d14 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - -Linux ceilingcat 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64 GNU/Linux -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_1_15c354c4841d364e78882d2b46a0a764._comment b/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_1_15c354c4841d364e78882d2b46a0a764._comment deleted file mode 100644 index 53c9f7915..000000000 --- a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_1_15c354c4841d364e78882d2b46a0a764._comment +++ /dev/null @@ -1,66 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 1" - date="2013-11-14T17:06:50Z" - content=""" -I verify this bug. And it's specific to direct mode as you say. Here is a shell script which automates the proccess: - -[[!format sh \"\"\" -#!/bin/sh -set -e -mkdir test -cd test -git init a - -cd a -git annex init -git annex direct -touch firstfile -git annex add firstfile -git annex sync # think this was left out of recipe - -cd .. - -git clone a b -cd b -git annex direct -echo bbbb > f -git annex add f -git annex sync || true -cd .. -cd a -mkdir f -echo aaaa > f/f -git annex add f/f -git annex sync || true -cd .. -cd b -git annex sync -echo \"after merge:\" -ls -\"\"\"]] - -At this point, b only has the file version of f; the directory form has been removed. (Syncing to a of course then does the same thing there.) - -And from the trascript, we can see what's going on: - -<pre> -Adding f/f -CONFLICT (directory/file): There is a directory with name f in HEAD. Adding f as f~refs_heads_synced_master -Automatic merge failed; fix conflicts and then commit the result. -(Recording state in git...) -f: needs merge -[master 0600854] git-annex automatic merge conflict fix - - Merge conflict was automatically resolved; you may want to examine the result. -</pre> - -The problem seems to be that direct mode merge does not find the `f~refs_heads_synced_master` created by the merge, so fails to copy it from the temp merge tree into the work tree. - -`Command.Sync.cleanConflictCruft` is relevant, but was only made to work in indirect mode, it seems. - ----- - -Obviously, if someone runs into this bug and seems to lose data, they can get the data back by reverting the changes from the automatic merge. Direct mode does preserve file contents when removing them from the work tree in a merge. -"""]] diff --git a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_2_8bc496226a977dbeeb1ce3f06122f1c2._comment b/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_2_8bc496226a977dbeeb1ce3f06122f1c2._comment deleted file mode 100644 index f9d3c7ffe..000000000 --- a/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_2_8bc496226a977dbeeb1ce3f06122f1c2._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 2" - date="2013-11-15T17:39:37Z" - content=""" -My initial guess was wrong.. This is not actually a bug in conflicted merge resolution at all. - -The bug is that in direct mode, it diffs the old and new tree when doing a normal merge, so see what files in the work tree need to be changed. This was written to go through the diff and replay the deletes and adds. In this case, since f/f and f are different items, they can appear in either order in the diff But the code only worked when f was first deleted, and f/f was then added. And it turns out that in this case, the diff had the two items the other way around. - -So, I think it needs to do 2 passes, first deleting and then adding. -"""]] diff --git a/doc/bugs/Incorrect_merge___40__a_special_case__41__.mdwn b/doc/bugs/Incorrect_merge___40__a_special_case__41__.mdwn deleted file mode 100644 index 8e25ed6cb..000000000 --- a/doc/bugs/Incorrect_merge___40__a_special_case__41__.mdwn +++ /dev/null @@ -1,48 +0,0 @@ -### Please describe the problem. -(Minor issue.) - -Incorrect merge of direct repos in the special case where at repo A a symlink to a file whose contents aren't yet available, are overwritten, while at repo B the file is deleted. - -Result: file is deleted on both side. - -Expected: B.f is gone, A.f is still present - -### What steps will reproduce the problem? - -[[!format sh """ -# setting up stuff -test/a$ git init -test/a$ git annex init -test/a$ git annex direct -test/a$ touch firstfile -test/a$ git annex add firstfile -$ git clone test/a -$ mv a test/b -test/b$ git annex direct - -# actual scenario -test/b$ echo bbbb > f -test/b$ git annex add f -test/b$ git annex sync -test/a$ git annex sync -test/a$ echo aaaa > f -test/a$ git annex add f -test/a$ git annex sync -test/b$ rm f -test/b$ git annex sync -test/a$ git annex sync -# test/a/f is now gone, lost -"""]] - -### What version of git-annex are you using? On what operating system? -[[!format sh """ -git-annex version: 4.20131031-g7d99d14 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - -Linux ceilingcat 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64 GNU/Linux -"""]] - -> [[fixed|done]]; direct mode now freezes the content directory as indirect -> mode already did. fsck will fix up the permissions too. --[[Joey]] diff --git a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_1_c80418d76b501c688e3a9fb4831520fd._comment b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_1_c80418d76b501c688e3a9fb4831520fd._comment deleted file mode 100644 index 0594ddabe..000000000 --- a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_1_c80418d76b501c688e3a9fb4831520fd._comment +++ /dev/null @@ -1,41 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 1" - date="2013-11-14T17:10:55Z" - content=""" -I suspect this might be the same underlying problem as [[bugs/Incorrect merge, direct repos (2)]]. However, I cannot reproduce it using the recipe given.. perhaps something was left out? - -I wrote this shell script to try to codify the recipe in a runnable form: - -[[!format sh \"\"\" -#!/bin/sh -set -e -mkdir test -cd test -git init a - -cd a -git annex init -git annex direct -touch firstfile -git annex add firstfile -git annex sync # think this was left out of recipe - -cd .. - -git clone a b -cd b -git annex direct -echo bbbb > f -git annex add f -git annex sync || true -cd .. -cd a -echo aaaa > f -git annex add f -git annex sync -\"\"\"]] - -At this point, a has 2 variants of f, and no amount of syncing in either repo will cause either variant to go away. -"""]] diff --git a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_2_8b2a188696f46819f6e3f0e9660362d2._comment b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_2_8b2a188696f46819f6e3f0e9660362d2._comment deleted file mode 100644 index 39bb90877..000000000 --- a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_2_8b2a188696f46819f6e3f0e9660362d2._comment +++ /dev/null @@ -1,45 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" - nickname="Tim" - subject="comment 2" - date="2013-11-14T18:06:55Z" - content=""" -You were missing a: test/a$ git annex sync - -This did the trick on my system -[[!format sh \"\"\" -#!/bin/sh -set -e -mkdir test -cd test -git init a - -cd a -git annex init -git annex direct -touch firstfile -git annex add firstfile -git annex sync # think this was left out of recipe # indeed it was - -cd .. - -git clone a b -cd b -git annex direct -echo bbbb > f -git annex add f -git annex sync || true # why add a || true? -cd ../a -git annex sync -echo aaaa > f -git annex add f -git annex sync -cd ../b -rm f -git annex sync -ls -cd ../a -git annex sync -ls -\"\"\"]] -"""]] diff --git a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_3_8cdbb1fda506b9e53a0e9ab88b2569c1._comment b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_3_8cdbb1fda506b9e53a0e9ab88b2569c1._comment deleted file mode 100644 index ce5c144e1..000000000 --- a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_3_8cdbb1fda506b9e53a0e9ab88b2569c1._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 3" - date="2013-11-15T17:48:42Z" - content=""" -Hmm. In your script, when you run `git annex sync` in a and then `echo aaaa > f`, f already exists at that point as a symlink. This actually ends up following the link and writing to .git/annex/objects. (fsck will detect that junk has been written there) - -That's a bug on its own; seems like direct mode is neglecting to lock down the .git/annex/objects directories to prevent writing to them like this. - ----- - -However, this means that your script does not demonstrate the bug you originally reported. -You remove b/f and sync, and since a/f has not been changed, the deleting is correctly synced to a, removing a/f. -"""]] diff --git a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_4_9d74e2854a5d77f0f793f56fa0cff9e2._comment b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_4_9d74e2854a5d77f0f793f56fa0cff9e2._comment deleted file mode 100644 index c7bb02765..000000000 --- a/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_4_9d74e2854a5d77f0f793f56fa0cff9e2._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 4" - date="2013-11-15T17:52:38Z" - content=""" -Looking back at the original bug description: - -\"repo A a symlink to a file whose contents aren't yet available, are overwritten, while at repo B the file is deleted.\" - -I think the \"overwritten\" is key. I suspect you were always doing echo > f where f was a symlink, and this does not actually overwrite the symlink, it just puts data (that fsck will reject) into the annex. - -So, proceeding as if the real bug here is the ability to write through symlink in direct mode, unless told otherwise.. -"""]] diff --git a/doc/bugs/Incorrect_version_of_Git_Annex___40__1.0.52__41___as_seen_by_Android.mdwn b/doc/bugs/Incorrect_version_of_Git_Annex___40__1.0.52__41___as_seen_by_Android.mdwn deleted file mode 100644 index 95db65e25..000000000 --- a/doc/bugs/Incorrect_version_of_Git_Annex___40__1.0.52__41___as_seen_by_Android.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -### Please describe the problem. - -Git Annex is listed as of version 1.0.52 if you check out its entry in the list of applications in the Android configuration. I guess that one is of the terminal app which kickstarts the annex. - -### What steps will reproduce the problem? - -install apk - -### What version of git-annex are you using? On what operating system? - -android -5.2013whatever - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Installation_on_ArchLinux_fails.mdwn b/doc/bugs/Installation_on_ArchLinux_fails.mdwn deleted file mode 100644 index 54c671847..000000000 --- a/doc/bugs/Installation_on_ArchLinux_fails.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. -The packages provided on AUR fail to install. I've tried git-annex, git-annex-bin and git-annex-git. - -### What steps will reproduce the problem? - - yaourt -S git-annex - -or - - yaourt -S git-annex-bin - -or - - yaourt -S git-annex-git - -### What version of git-annex are you using? On what operating system? - -None, on an up-to-date ArchLinux (Kernel 4.0.5-1) - -### Please provide any additional information below. - - -The git-annex-bin package has outdated checksums. When updating these, yaourt fails with - - rm: cannot remove ‘/tmp/yaourt-tmp-foo/aur-git-annex-bin/pkg/git-annex-bin/opt/git-annex.linux/usr/lib/x86_64-linux-gnu/libcurl.so.4’: No such file or directory - -Both git-annex and git-annex-git fail with - - error: target not found: haskell-edit-distance - error: target not found: haskell-ifelse - error: target not found: haskell-hs3 - -as these packages are not available on AUR. - -> I have updated the arch documentation to replace the failing package with -> the haskell-core one. [[done]] --[[Joey]] diff --git a/doc/bugs/Installation_on_ArchLinux_fails/comment_1_17821bd94b52c8231059e4934b4131e4._comment b/doc/bugs/Installation_on_ArchLinux_fails/comment_1_17821bd94b52c8231059e4934b4131e4._comment deleted file mode 100644 index 8823790c0..000000000 --- a/doc/bugs/Installation_on_ArchLinux_fails/comment_1_17821bd94b52c8231059e4934b4131e4._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="tommi" - subject="comment 1" - date="2015-06-23T21:24:35Z" - content=""" -As a workaround, installing git-annex from the haskell-core repository works (see https://wiki.archlinux.org/index.php/ArchHaskell) -"""]] diff --git a/doc/bugs/Installation_on_ArchLinux_fails/comment_2_ff058ac51ee3bdd2b65a903716ea0d66._comment b/doc/bugs/Installation_on_ArchLinux_fails/comment_2_ff058ac51ee3bdd2b65a903716ea0d66._comment deleted file mode 100644 index 408922840..000000000 --- a/doc/bugs/Installation_on_ArchLinux_fails/comment_2_ff058ac51ee3bdd2b65a903716ea0d66._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 2" - date="2015-06-24T07:33:20Z" - content=""" -The AUR package isn't \"official\", so it isn't supported. - -It has an outdated checksum because there is some issue related to changes to curl which apparently causes problems if you use the webapp (which I don't, so I just deleted that bit and it seems to work fine). -"""]] diff --git a/doc/bugs/Installation_on_ArchLinux_fails/comment_3_848fcafc5a3ffcc6641aa2dc3bd8286f._comment b/doc/bugs/Installation_on_ArchLinux_fails/comment_3_848fcafc5a3ffcc6641aa2dc3bd8286f._comment deleted file mode 100644 index 53298bf41..000000000 --- a/doc/bugs/Installation_on_ArchLinux_fails/comment_3_848fcafc5a3ffcc6641aa2dc3bd8286f._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-02T16:38:51Z" - content=""" -Not a whole lot I can do about this.. We can update install/ArchLinux -and that's about it. Probably more productive to get in touch with the -maintainer of the AUR package if it needs fixed. - -But, ArchHaskell seems promising. Much better than the hacks used to build -the git-annex-bin AUR, IMHO. Since I'm not an Arch user, and don't -understand the distro (on a number of levels it seems very puzzling to -me..), I am reluctant to update the documentation myself to say to use it, but -if it makes sense to point users at haskell-core, by all means update the -docs to do so. - -(Any details about the curl thing?) -"""]] diff --git a/doc/bugs/Installation_on_ArchLinux_fails/comment_4_be3a6b3955354fb56eec0371b8f32f6a._comment b/doc/bugs/Installation_on_ArchLinux_fails/comment_4_be3a6b3955354fb56eec0371b8f32f6a._comment deleted file mode 100644 index c88b405c1..000000000 --- a/doc/bugs/Installation_on_ArchLinux_fails/comment_4_be3a6b3955354fb56eec0371b8f32f6a._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 4" - date="2015-07-03T08:11:08Z" - content=""" -I'll try to replicate the curl problem in a VM over the weekend. -"""]] diff --git a/doc/bugs/Internal_Server_Error_unknown_UUID__59___cannot_modify.mdwn b/doc/bugs/Internal_Server_Error_unknown_UUID__59___cannot_modify.mdwn deleted file mode 100644 index 7767b83e2..000000000 --- a/doc/bugs/Internal_Server_Error_unknown_UUID__59___cannot_modify.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -### Please describe the problem. -I was trying to use "Local Computer" option to sync up two machines on my local network. I was having some firewall issues and it failed on one machine. -It still created a repository without a name in the web ui and i get that Error unknown UUID when trying to edit or delete it. - -### What steps will reproduce the problem? -Machine A initiates pairing. Machine B accepts pairing. Machine A has a firewall blocking outgoing connections. -Machine B times out. Machine A accepts outgoing connections for vnetd. Machine A starts syncing with Machine B. -Machine B gets files but have a broken web ui. - - -### What version of git-annex are you using? On what operating system? - -4.20130601-g2b6c3f2 -OSX 10.7.5 on both Machine A and B - -### 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. -"""]] - -> [[dup|done]] of [[Internal_Server_Error:_Unknown_UUID]] --[[Joey]] diff --git a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows.mdwn b/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows.mdwn deleted file mode 100644 index 76a88808e..000000000 --- a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. -The web app fails with an Internal server error while adding a remote server on Windows. -ssh: createProcess: does not exist (No such file or directory) - -### What steps will reproduce the problem? -Start the webapp, click add repository, select remote server, click check. - -### What version of git-annex are you using? On what operating system? -Latest (as of 20141104) on Windows. - -### 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 - -[2014-11-04 12:42:27 ora solare Europa occidentale] main: starting assistant version 5.20141031-gbfac20c -Launching web browser on file://C:\Users\ltaglialegne\Documents\Annex\.git\annex\webapp.html -[2014-11-04 12:42:27 ora solare Europa occidentale] Cronner: You should enable consistency checking to protect your data. -(scanning...) [2014-11-04 12:42:27 ora solare Europa occidentale] Watcher: Performing startup scan -(started...) recv: failed (No error) -recv: failed (No error) -recv: failed (No error) -recv: failed (No error) -04/Nov/2014:12:44:30 +0100 [Error#yesod-core] ssh: createProcess: does not exist (No such file or directory) @(yesod-core-1.2.19:Yesod.Core.Class.Yesod .\Yesod\Core\Class\Yesod.hs:503:5) -04/Nov/2014:12:44:50 +0100 [Error#yesod-core] ssh: createProcess: does not exist (No such file or directory) @(yesod-core-1.2.19:Yesod.Core.Class.Yesod .\Yesod\Core\Class\Yesod.hs:503:5) - -# End of transcript or log. -"""]] - -> [[fixed|done]]; git-annex's ssh is now installed to Git/cmd, -> so it will be in the PATH as long as the instructions are followed to let -> msysgit add git to the PATH. --[[Joey]] diff --git a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_1_af5df473e49a149701b30accb63643a9._comment b/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_1_af5df473e49a149701b30accb63643a9._comment deleted file mode 100644 index 32eb8b0a2..000000000 --- a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_1_af5df473e49a149701b30accb63643a9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-11-06T19:48:44Z" - content=""" -This looks like it's failing to find the ssh command. How did you install -git-annex on your windows computer? Can you use ssh from a terminal? -"""]] diff --git a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_2_e7ab75a3c4cd6db900bc2b786bda4e8d._comment b/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_2_e7ab75a3c4cd6db900bc2b786bda4e8d._comment deleted file mode 100644 index 8557046d4..000000000 --- a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_2_e7ab75a3c4cd6db900bc2b786bda4e8d._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnE6kFAbud1LWrQuyX76yMYnUjHt9tR-A8" - nickname="Leonardo" - subject="comment 2" - date="2014-11-18T14:00:58Z" - content=""" -I've installed it using the installer. -I think the problem might be that recent versions of git install somewhere in %AppData% and not in %ProgramFiles%. -"""]] diff --git a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_3_0ff9b2e15904ef64b7d1937a41da5f49._comment b/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_3_0ff9b2e15904ef64b7d1937a41da5f49._comment deleted file mode 100644 index 5144abcc6..000000000 --- a/doc/bugs/Internal_server_error_while_adding_remote_server_on_Windows/comment_3_0ff9b2e15904ef64b7d1937a41da5f49._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 3" - date="2014-12-03T17:35:19Z" - content=""" -I was able to reproduce this. ssh is installed in C:\Program Files\Git\bin\, which is not in the PATH unless the msysgit installer is told to put all the unix utils in the PATH. -"""]] diff --git a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken.mdwn b/doc/bugs/Latest_64_bit_standalone_Linux_build_broken.mdwn deleted file mode 100644 index ebb55543d..000000000 --- a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken.mdwn +++ /dev/null @@ -1,18 +0,0 @@ - [0 zerodogg@firefly git-annex]$ ls - bin/ favicon.png git-annex git-annex-shell git-core/ lib/ libdirs linker README shimmed/ uninstall - etc/ gconvdir git-annex.MANIFEST git-annex-webapp install-haskell-packages lib64/ LICENSE logo.svg runshell templates/ usr/ - [0 zerodogg@firefly git-annex]$ pwd - /home/zerodogg/.local/share/git-annex - [0 zerodogg@firefly git-annex]$ ./git-annex version - /home/zerodogg/.local/share/git-annex/bin/git-annex: line 2: /home/zerodogg/.local/share/git-annex/lib64/ld-linux-x86-64.so.2: No such file or directory - [127 zerodogg@firefly git-annex]$ ls -l /home/zerodogg/.local/share/git-annex/lib64/ld-linux-x86-64.so.2 - lrwxrwxrwx. 1 zerodogg zerodogg 32 2012-12-30 16:35 /home/zerodogg/.local/share/git-annex/lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.13.so - [0 zerodogg@firefly git-annex]$ ls /lib/x86_64-linux-gnu/ld-2.13.so - ls: cannot access /lib/x86_64-linux-gnu/ld-2.13.so: No such file or directory - -This is on Fedora 20, 64bit, installed from http://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz as of Sun Dec 22 00:44:53 CET 2013. - -> [[fixed|done]]; converted ugly shell code to much nicer haskell code, -> which let me reuse relative symlink generation code from git-annex -> to fix this. Updated the amd64 build for the last release only. -> --[[Joey]] diff --git a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_1_428eba88016d50a6631fffa906815767._comment b/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_1_428eba88016d50a6631fffa906815767._comment deleted file mode 100644 index 60012d2cd..000000000 --- a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_1_428eba88016d50a6631fffa906815767._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="EskildHustvedt" - ip="80.202.194.17" - subject="32 bit standalone works (on 64 bit) however" - date="2013-12-22T11:37:24Z" - content=""" -SSIA -"""]] diff --git a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_2_87f70b3eececca8a5b7946cff53e0a2f._comment b/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_2_87f70b3eececca8a5b7946cff53e0a2f._comment deleted file mode 100644 index b9cc82a7b..000000000 --- a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_2_87f70b3eececca8a5b7946cff53e0a2f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmTlfbCC37CAjhQrS107ZWRVA_sF4s3gLU" - nickname="Juergen" - subject="Same here broken " - date="2013-12-22T12:11:57Z" - content=""" -It's broken here too. Debian testing 64bit . - - -"""]] diff --git a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_3_manually_added._comment b/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_3_manually_added._comment deleted file mode 100644 index 23ca8f72c..000000000 --- a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_3_manually_added._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://id.clacke.se/" - nickname="clacke" - subject="Workaround/Fix" - date="2013-12-22T14:23:09Z" - content=""" -Broken here on Linux Mint 13 Maya (Ubuntu 12.04 precise) too. The reason is a dangling symlink. Fix: - - clacke@acozed:~/.local/libexec/git-annex.linux.5.20131221$ ./git-annex version - Segmentation fault - clacke@acozed:~/.local/libexec/git-annex.linux.5.20131221$ rm lib64/ld-linux-x86-64.so.2 - clacke@acozed:~/.local/libexec/git-annex.linux.5.20131221$ ln -s ../lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 lib64/ - clacke@acozed:~/.local/libexec/git-annex.linux.5.20131221$ ./git-annex version - git-annex version: 5.20131221-gf8c928d - build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav glacier hook -"""]] diff --git a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_4_43947607472193e2199b98ee2192af30._comment b/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_4_43947607472193e2199b98ee2192af30._comment deleted file mode 100644 index 3a5e1947b..000000000 --- a/doc/bugs/Latest_64_bit_standalone_Linux_build_broken/comment_4_43947607472193e2199b98ee2192af30._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 4" - date="2013-12-23T16:45:23Z" - content=""" -clacke's workaround works for me, as well, on 5.20131223-gafb776f (ie: issue still present on 5.20131223-gafb776f) -"""]] diff --git a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable.mdwn b/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable.mdwn deleted file mode 100644 index e4eef758a..000000000 --- a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -### Please describe the problem. -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by git-annex) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libidn.so.11) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libgnutls.so.26) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libxml2.so.2) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libxml2.so.2) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libgmp.so.10) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libffi.so.6) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libntlm.so.0) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libkrb5.so.3) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.16' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libkrb5.so.3) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libk5crypto.so.3) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/user/bin/lib/x86_64-linux-gnu/libcom_err.so.2) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/lib/x86_64-linux-gnu/libgcrypt.so.11) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /home/user/bin/lib/x86_64-linux-gnu/libgcrypt.so.11) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libtasn1.so.3) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libp11-kit.so.0) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libstdc++.so.6) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libstdc++.so.6) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/lib/x86_64-linux-gnu/libgcc_s.so.1) -git-annex: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/user/bin/usr/lib/x86_64-linux-gnu/libkrb5support.so.0) - -### What steps will reproduce the problem? -$git-annex - -### What version of git-annex are you using? On what operating system? -v20130723, 64-bit, Debian Stable - -### 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. -"""]] - -Also note, the last build 20130709 was compatible with glibc 2.13 - -> [[fixed|done]]; builds are back to using debian stable. -> also updated the autobuilds and last release's builds. --[[Joey]] diff --git a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_1_dc7f726a0b60f64392cbbd1b4317bab5._comment b/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_1_dc7f726a0b60f64392cbbd1b4317bab5._comment deleted file mode 100644 index f50471ca0..000000000 --- a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_1_dc7f726a0b60f64392cbbd1b4317bab5._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="2001:4978:f:21a::2" - subject="comment 1" - date="2013-07-25T17:00:53Z" - content=""" -Thank you for reminding me why I was using debian stable chroots for the autobuilds. - -Unfortunately, I forgot about this problem and upgraded the chroots. Rebuilding them with all the stuff I need is going to take a while. -"""]] diff --git a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_2_4a0198d714bd3b52ba9baa68dc45f535._comment b/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_2_4a0198d714bd3b52ba9baa68dc45f535._comment deleted file mode 100644 index 1d7685bb1..000000000 --- a/doc/bugs/Linux_stand_alone_build_20130723_breaks_support_for_glibc_2.13_debian_stable/comment_2_4a0198d714bd3b52ba9baa68dc45f535._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://jamdev.myopenid.com/" - ip="117.195.168.15" - subject="well that was fast!" - date="2013-07-25T21:01:38Z" - content=""" -Hey Joey - -Confirming this as fixed, thanks. - --have a nice weekend! -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__.mdwn b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__.mdwn deleted file mode 100644 index 2875e63e4..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -### Please describe the problem. - -Creating a USB repo fails with a GPG error. - -### What steps will reproduce the problem? - - * Build git-annex and git-annex assistant using the instructions at https://gist.github.com/calmyournerves/7144127 - * Run git-annex app to launch web interface - * Create local repo using web interface - * Try to create USB repo using web interface - -### What version of git-annex are you using? On what operating system? - -git-annex version 4.20131105-g136b030 on Mac OS 10.9 Mavericks. - -### Please provide any additional information below. - -[[!format sh """ -07/Nov/2013:06:51:07 +1100 [Error#yesod-core] user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--with-colons","--list-secret-keys","--fixed-list-mode"] exited 5) @(yesod-core-1.2.4.5:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) -"""]] - -> [[fixed|done]]; it seems that this was a local build issue ad does not -> affect the autobuild. --[[Joey]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment deleted file mode 100644 index 34d8d94b1..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Updated version 4.20131105-g136b030 seems to work" - date="2013-11-07T20:28:55Z" - content=""" -I've updated to the latest version as of 12 hours ago and I was able to create a USB repo on two computers. 4.20131105-g136b030 showing on the web app but 20131106 on the command line. - -Is there an easy way of checking the repo is correctly encrypted? I didn't see anything about encrypting (now the previous error has disappeared) when creating the repo - is this what I should expect? -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_2_1cb1ef0292a3357874b461a77c13373e._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_2_1cb1ef0292a3357874b461a77c13373e._comment deleted file mode 100644 index 83e0b2317..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_2_1cb1ef0292a3357874b461a77c13373e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 2" - date="2013-11-08T17:36:53Z" - content=""" -USB repos are not set up encryption unless you explicitly request it. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment deleted file mode 100644 index 0b3a804b9..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo___40__solved__41__/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Yes, I just figured that out" - date="2013-11-08T22:09:40Z" - content=""" -I figured it out a couple of hours ago when I was able to use the existing USB repo on a new computer that doesn't have any of my private keys on it. - -I didn't see an option in the web interface to use encryption - is it command line only? -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__.mdwn b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__.mdwn deleted file mode 100644 index 5c70527fd..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -Creating a remote S3 repository using the git-annex assistant web interface fails with a GPG error. (I'm also getting a GPG error trying to create a USB repo but it's slightly different so I'll post a different bug.) - -### What steps will reproduce the problem? - - * Build git-annex and git-annex assistant using the instructions at https://gist.github.com/calmyournerves/7144127 - * Run git-annex app to launch web interface - * Create local repo using web interface - * Try to create encrypted S3 remote repo using web interface - -### What version of git-annex are you using? On what operating system? - -git-annex version 4.20131105-g136b030 on MacOS 10.9 Mavericks. - -### Please provide any additional information below. - -[[!format sh """ - -(encryption setup) dyld: Library not loaded: @rpath/libz.1.2.8.dylib - Referenced from: /Applications/git-annex.app/Contents/MacOS/bundle/gpg - Reason: image not found -07/Nov/2013:06:38:27 +1100 [Error#yesod-core] user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 5) @(yesod-core-1.2.4.5:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) - -"""]] - -> [[fixed|done]]; it seems that this was a local build issue ad does not -> affect the autobuild. --[[Joey]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment deleted file mode 100644 index 0f1e34e31..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="S3 works without encryption" - date="2013-11-06T21:09:26Z" - content=""" -Not surprisingly, S3 repos work without encryption. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_2_452a3c524974832f0742efb00df4d576._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_2_452a3c524974832f0742efb00df4d576._comment deleted file mode 100644 index 6b3ca2a0b..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_2_452a3c524974832f0742efb00df4d576._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Still fails with git-annex version 4.20131105-g136b030" - date="2013-11-07T20:32:09Z" - content=""" -Updating seems to have fixed my other problem with creating a USB repo but still fails when trying to create an encrypted S3 repo. - - (encryption setup) dyld: Library not loaded: @rpath/libz.1.2.8.dylib - Referenced from: /Applications/git-annex.app/Contents/MacOS/bundle/gpg - Reason: image not found - 08/Nov/2013:07:30:11 +1100 [Error#yesod-core] user error (gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"1\",\"512\"] exited 5) @(yesod-core-1.2.4.5:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment deleted file mode 100644 index e2ae9c3dc..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 3" - date="2013-11-08T17:38:40Z" - content=""" -Looks like it failed to include libz.1.2.8.dylib in the bundle for some reason despite gpg needing it. - -I don't really see the point in building an app bundle if you're going to install it back to the same machine you built it on. It's much easier to just `cabal install git-annex` in this case. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_4_b524649cee751532d20a4894d71c5cf3._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_4_b524649cee751532d20a4894d71c5cf3._comment deleted file mode 100644 index 8c7450ca6..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_4_b524649cee751532d20a4894d71c5cf3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Maybe I'm missing something..." - date="2013-11-08T22:12:04Z" - content=""" -But does cabal install git-annex install the assistant? On the Mac, I use the app bundle to launch the web interface from my applications folder. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_5_8312ba868ef616ec00563446c9c3464f._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_5_8312ba868ef616ec00563446c9c3464f._comment deleted file mode 100644 index f94f2d9c8..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_5_8312ba868ef616ec00563446c9c3464f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="To answer my own question - "git annex webapp"" - date="2013-11-09T00:10:28Z" - content=""" -Will open the web app from the command line. - -But now I get a different error trying to create an encrypted S3 repo. - - (encryption setup) 09/Nov/2013:11:08:56 +1100 [Error#yesod-core] user error (gpg [\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"1\",\"512\"] exited 127) @(yesod-core-1.2.4.5:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_6_1af75c691d27c97397f1901f7c2483b0._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_6_1af75c691d27c97397f1901f7c2483b0._comment deleted file mode 100644 index 19313d9a7..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_6_1af75c691d27c97397f1901f7c2483b0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="Works with git annex on command line" - date="2013-11-09T20:18:38Z" - content=""" -git annex initremote cloud type=S3 keyid=key correct creates an encrypted S3 repo and I'm able to upload files. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_7_e519df252875de87c4ef5b727f033bdf._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_7_e519df252875de87c4ef5b727f033bdf._comment deleted file mode 100644 index a67c59451..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_7_e519df252875de87c4ef5b727f033bdf._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 7" - date="2013-11-15T19:00:25Z" - content=""" -It would be useful if you could test with the 10.9 build now available in [[install/OSX]]. -"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_8_4bb959e2659991cd392853e8beacf708._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_8_4bb959e2659991cd392853e8beacf708._comment deleted file mode 100644 index cff7e9dee..000000000 --- a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo___40__solved__41__/comment_8_4bb959e2659991cd392853e8beacf708._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="comment 8" - date="2013-11-15T21:31:40Z" - content=""" -Thanks Joey - I was able to create an encrypted S3 repo using the new Mavericks build. Files are transferring across and are encrypted. -"""]] diff --git a/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp.mdwn b/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp.mdwn deleted file mode 100644 index 7401d79fb..000000000 --- a/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -Latest build for Mac OS X (both autobuild and release versions) does not contain webapp. - -git annex version for OS X, - - git-annex version: 5.20140306-g309a73c - build flags: Assistant Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN2 56 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -whereas on my Linux box build flags include webapp. On os x when I run git annex webapp it does nothing, just prints the help info. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp/comment_1_b918a741f2397b6588e7a9f1feca7e66._comment b/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp/comment_1_b918a741f2397b6588e7a9f1feca7e66._comment deleted file mode 100644 index b13eab08f..000000000 --- a/doc/bugs/Mac_OS_X_Build_doesn__39__t_include_webapp/comment_1_b918a741f2397b6588e7a9f1feca7e66._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 1" - date="2014-03-07T15:17:16Z" - content=""" -I've fixed the missing warp-tls dep on the autobuilder and updated the builds. -"""]] diff --git a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__.mdwn b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__.mdwn deleted file mode 100644 index 5de6d2aa5..000000000 --- a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -Joey, it looks like the git version wasn't updated with the latest release as is still too old to respect .gitignore files. I'm hoping that I haven't just made a silly mistake but I don't think I have... - -See http://git-annex.branchable.com/bugs/Mac_OS_git_version_too_old_to_honour_.gitignore/ for bug that was closed. - -### What steps will reproduce the problem? - -Install git-annex 5.20140209-g3a61dbe and try to use .gitignore file to exclude items from git annex. - -### What version of git-annex are you using? On what operating system? - -5.20140209-g3a61dbe on Mac OS 10.9.1. - -### Please provide any additional information below. - -[/Applications/git-annex.app/Contents/MacOS]# ./git annex version - -git-annex version: 5.20140209-g3a61dbe -build flags: Assistant Webapp Pairing S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -[/Applications/git-annex.app/Contents/MacOS]# ./git --version - -git version 1.8.3.4 (Apple Git-47) - -> Really [[fixed|done]] now. --[[Joey]] diff --git a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_1_1768ece63499c643c75085773b6d4c18._comment b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_1_1768ece63499c643c75085773b6d4c18._comment deleted file mode 100644 index afa6cc8f6..000000000 --- a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_1_1768ece63499c643c75085773b6d4c18._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 1" - date="2014-02-20T18:59:44Z" - content=""" -I thought it got upgrades, perhaps it was downgraded again? I have prodded Kevin. -"""]] diff --git a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_2_888fb193072cf05a34943db072eb7a3b._comment b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_2_888fb193072cf05a34943db072eb7a3b._comment deleted file mode 100644 index 1bd1e037e..000000000 --- a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_2_888fb193072cf05a34943db072eb7a3b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="comment 2" - date="2014-02-21T07:03:20Z" - content=""" -Thanks Joey and Kevin. Glad to have the bug really fixed and glad to know that I wasn't missing something obvious! -"""]] diff --git a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment deleted file mode 100644 index 591d4e80f..000000000 --- a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" - nickname="Jimmy" - subject="comment 3" - date="2014-02-21T22:05:06Z" - content=""" -And yep, it's fixed in 5.20140221-g1a47f5f. Thanks guys! -"""]] diff --git a/doc/bugs/Mac_OS_git_version_too_old_to_honour_.gitignore.mdwn b/doc/bugs/Mac_OS_git_version_too_old_to_honour_.gitignore.mdwn deleted file mode 100644 index 0cf61bb0f..000000000 --- a/doc/bugs/Mac_OS_git_version_too_old_to_honour_.gitignore.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -### Please describe the problem. - -Git annex assistant ignores .gitignore file due to packaged git version being too old. - -I have a locally installed version that is greater than the 1.8.4 needed to respect .gitignore but git annex doesn't use it. - -### What steps will reproduce the problem? - -- Create local repository using webapp -- Add .gitignore file to local repository -- Add files that match .gitignore patterns and watch git annex add them - -### What version of git-annex are you using? On what operating system? - -Git Annex assistant version 5.20140128-g0ac94c3 on Mac OS 10.9.1 - -### Please provide any additional information below. - -Log message is "The installed version of git is too old for .gitignores to be honored by git-annex." - -[[!format sh """ -# /Applications/git-annex.app/Contents/MacOS/git-annex version -git-annex version: 5.20140128-g0ac94c3 -build flags: Assistant Webapp Pairing S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -# /Applications/git-annex.app/Contents/MacOS/git --version -git version 1.8.3.4 (Apple Git-47) - -# which git -/usr/local/bin/git - -# /usr/local/bin/git --version -git version 1.8.5.3 -"""]] - -> [[fixed|done]]; it has been updated to 1.8.5.3 on the autobuilder. --[[Joey]] diff --git a/doc/bugs/Manual_content_mode_isn__39__t_manual.mdwn b/doc/bugs/Manual_content_mode_isn__39__t_manual.mdwn deleted file mode 100644 index cb0247766..000000000 --- a/doc/bugs/Manual_content_mode_isn__39__t_manual.mdwn +++ /dev/null @@ -1,89 +0,0 @@ -### Please describe the problem. - -The `manual` content mode doesn't follow the description provided in the help page, instead it seems to collect content. - -### What steps will reproduce the problem? - -1. Create a new git annex repository using the webapp, set the content type to `client`. -2. Create another repository, and set the content type to `manual`. -3. Copy something into the `client` repository. -4. It will be pushed/pulled into the `manual` repository. - -### What version of git-annex are you using? On what operating system? - - git-annex version: 4.20130521-g25dba9d - Ubuntu 13.04 x64. - -### Please provide any additional information below. - -I have also noticed very weird behaviour that I have been unable to replicate in testing, but I will describe the setup that it currently happens in: -I have 3x repositories, one a `client` repository, and the other two are set to `manual`. When put a new file into the `client` repository, it is pushed onto the two `manual` repositories. When these repositories have received it, the client drops the file and re-downloads it from one of the `manual` repositories. Once it's been pushed, deleted, and pulled, everything is happy... but the extra step makes no difference. - -[[!format sh """ -[2013-05-22 20:41:44 EST] main: starting assistant version 4.20130521-g25dba9d -[2013-05-22 20:41:44 EST] TransferScanner: Syncing with test3, test2 -Already up-to-date. - -(scanning...) [2013-05-22 20:41:44 EST] Watcher: Performing startup scan -Already up-to-date. -Already up-to-date. - - -(started...) From /home/valorin/workspace/tmp/test3 - f285dc2..406c20c git-annex -> test3/git-annex - cdf2ad3..508983c master -> test3/master -From /home/valorin/workspace/tmp/test2 - 1e04829..1c03533 git-annex -> test2/git-annex - 8ad4bd3..18a5408 master -> test2/master -Updating 508983c..18a5408 -Fast-forward -Already up-to-date. -To /home/valorin/workspace/tmp/test2 - 4e49293..a66ce5d git-annex -> synced/git-annex - 508983c..18a5408 master -> synced/master -To /home/valorin/workspace/tmp/test3 - 4e49293..a66ce5d git-annex -> synced/git-annex - 508983c..18a5408 master -> synced/master -Already up-to-date. -Already up-to-date. -[2013-05-22 20:42:07 EST] Committer: Adding Firefly S..acked.m4v - -(merging test3/git-annex into git-annex...) -(merging test2/git-annex into git-annex...) -(Recording state in git...) - - - - -add Firefly S01E03 Bushwhacked.m4v (checksum...) [2013-05-22 20:42:15 EST] Committer: Committing changes to git -[2013-05-22 20:42:15 EST] Pusher: Syncing with test3, test2 -Already up-to-date. -To /home/valorin/workspace/tmp/test2 - a66ce5d..a6773dd git-annex -> synced/git-annex - 18a5408..f9e7692 master -> synced/master -To /home/valorin/workspace/tmp/test3 - a66ce5d..a6773dd git-annex -> synced/git-annex - 18a5408..f9e7692 master -> synced/master -Already up-to-date. -Already up-to-date. -[2013-05-22 20:42:26 EST] Transferrer: Uploaded Firefly S..acked.m4v -[2013-05-22 20:42:26 EST] Pusher: Syncing with test3, test2 -To /home/valorin/workspace/tmp/test3 - a6773dd..c35f992 git-annex -> synced/git-annex -To /home/valorin/workspace/tmp/test2 - a6773dd..c35f992 git-annex -> synced/git-annex -[2013-05-22 20:42:35 EST] Transferrer: Uploaded Firefly S..acked.m4v -[2013-05-22 20:42:35 EST] Pusher: Syncing with test3, test2 -To /home/valorin/workspace/tmp/test3 - c35f992..9e47813 git-annex -> synced/git-annex -To /home/valorin/workspace/tmp/test2 - c35f992..9e47813 git-annex -> synced/git-annex -[2013-05-22 20:42:44 EST] Pusher: Syncing with test3, test2 -Everything up-to-date -Everything up-to-date -"""]] - -> It turns out there was a bug in the preferred content expression parser, -> that made it parse the expression for manual mode (but I think no other standard -> expression) quite wrong, as if it had parens in the wrong place. This explains -> the broken behavior. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results.mdwn b/doc/bugs/Merge_involving_symlink_yields_unexpected_results.mdwn deleted file mode 100644 index 1ebd4039b..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results.mdwn +++ /dev/null @@ -1,51 +0,0 @@ -### Please describe the problem. -When creating a symlink in repository A, and creating a regular file under the same name in repository B, syncing B will yield the result that the symlink is lost, and both the original filename and the .variant file will point to the same annex object containing the original content from B. - -Both A and B are indirect mode repos. - -### What steps will reproduce the problem? - -[[!format sh """ - -#Initial state: - -repo-A$ echo file1 -This is file 1. -repo-B$ echo file1 -This is file 1. - -#Make conflicting changes: - -repo-A$ ln -s file1 file2; git add file2; git commit -m "Add file2 as symlink." -repo-B$ echo "This is file 2." > file2; git annex add file2; git commit -m "Add file2 as regular file." - -#Sync it: - -repo-A$ git annex sync -repo-B$ git annex sync - -#Strange result in repo-B: - -repo-B$ ls -l file2* -file2 -> .git/annex/objects/$HASH1 -file2.variant1234 -> .git/annex/objects/$HASH1 -repo-B$ cat file2 file2.variantXXXX -This is file 2. -This is file 2. - -#Repo-A leaves the symlink change untouched and adds a .variant containing the new regular file data. - -repo-A$ ls -l file* -file2 -> file1 -file2.variant1234 -> .git/annex/objects/$HASH1 -repo-A$ cat file.variant1234 -This is file 2. -"""]] -### What version of git-annex are you using? On what operating system? -Linux 3.15.3 -git-annex 5.20140613 - - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_1_e8a2ea1b8573bee45b70bcc7ef7e3bed._comment b/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_1_e8a2ea1b8573bee45b70bcc7ef7e3bed._comment deleted file mode 100644 index 624b39a79..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_1_e8a2ea1b8573bee45b70bcc7ef7e3bed._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="134.147.14.84" - subject="comment 1" - date="2014-07-07T14:09:33Z" - content=""" -Sorry, the initial «echos» should have been «cat» of course. -"""]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_2_b6182038292bd72dc4711e4575510172._comment b/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_2_b6182038292bd72dc4711e4575510172._comment deleted file mode 100644 index 39f60f775..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_2_b6182038292bd72dc4711e4575510172._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-07T17:17:49Z" - content=""" -Drat, so many bug fixes and test cases and this still got through? -"""]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_3_c6ca13d475b3f846c95606c20e1a3052._comment b/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_3_c6ca13d475b3f846c95606c20e1a3052._comment deleted file mode 100644 index 292d11743..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_3_c6ca13d475b3f846c95606c20e1a3052._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 3" - date="2014-07-07T17:19:03Z" - content=""" -Ah, I see, it's explicitly because the non-git-annex symlink is involved. Whew! -"""]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_4_13179e0f72026092e48c13082818ce68._comment b/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_4_13179e0f72026092e48c13082818ce68._comment deleted file mode 100644 index 49210ee55..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_4_13179e0f72026092e48c13082818ce68._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="analysis" - date="2014-07-08T17:52:59Z" - content=""" -When resolveMerge' calls graftin to add A's file2 symlink to B's tree, it actually stages the right symlink (the non-annexed one). - -However, the work tree is left as-is, so it still has the annexed symlink in it. So git status shows file2 as modified. Later syncs will commit that. - -This is why the sync in A doesn't have the problem, as there things are the other way around, and git-annex makes the git-annex symlink, leaving the non-annexed symlink as-is in the work tree. - -So, graftin needs to update the work tree. But it's tricky because graftin is called in 3 situations: non-symlink file, directory, and non-annexed symlink. -Interestingly, in the other 2 cases, git-merge already takes care of updating the work tree -- it deletes the annexed symlink and puts in place either the non-symlink file or the directory. It's only the the case of a merge conflict involving 2 symlinks that git merge doesn't update the tree in this way. It's nice to be able to rely on git-merge in the other 2 cases, especially the directory case (avoids having to manually check out the directory). -"""]] diff --git a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_5_585c8a5a13bb17032bfe30818345f936._comment b/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_5_585c8a5a13bb17032bfe30818345f936._comment deleted file mode 100644 index 566a0aad8..000000000 --- a/doc/bugs/Merge_involving_symlink_yields_unexpected_results/comment_5_585c8a5a13bb17032bfe30818345f936._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="78.49.247.112" - subject="comment 5" - date="2014-07-08T19:17:29Z" - content=""" -Thanks for the swift fix + analysis! If I’m ever around, I’ll lend you a hand on your next truckload of firewood! ;> - -Cheers! -"""]] diff --git a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex.mdwn b/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex.mdwn deleted file mode 100644 index dc24ee18d..000000000 --- a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -### Please describe the problem. -I paired my repo running on Gentoo (git-annex 4.20130601) with Ubuntu 13.04 (git-annex 3.10121112ubuntu4). The repo on Ubuntu doesn't have uuid for the Gentoo remote, so: - -- There is no name in assistan's repo settings for it - -- Trying to access its settings gives Internal server error: Unknown UUID -15/Jun/2013:12:39:10 +0300 [Error#yesod-core] Unknown UUID @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) - -- In dashboard on Ubuntu all changes stay queued forever (although the syncing seems to work) - -### What steps will reproduce the problem? -Pair local computers with different annex versions. - -### What version of git-annex are you using? On what operating system? -Gentoo (git-annex 4.20130601) -Ubuntu 13.04 (git-annex 3.10121112ubuntu4) - -### 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. -"""]] - -> Others are reporting what seems to be the same problem here: -> [[Internal_Server_Error:_Unknown_UUID]]. -> -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_1_8229df64a872bee7590f75eb78f78c4a._comment b/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_1_8229df64a872bee7590f75eb78f78c4a._comment deleted file mode 100644 index 26881f17b..000000000 --- a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_1_8229df64a872bee7590f75eb78f78c4a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.108.193" - subject="comment 1" - date="2013-06-25T18:08:55Z" - content=""" -As far as I know, there have been no changes to the local pairing protocol that would cause a problem like this. 3.20121112 is a few months after local pairing was first developed. - -Have you tried upgrading and re-pairing? -"""]] diff --git a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_2_f37be896396915b1c85cff8811dceb4a._comment b/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_2_f37be896396915b1c85cff8811dceb4a._comment deleted file mode 100644 index d9ad17e79..000000000 --- a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_2_f37be896396915b1c85cff8811dceb4a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm01ida6POv7vqyUYtOlymEbJTbrImAIzM" - nickname="Reinis" - subject="comment 2" - date="2013-06-25T18:50:00Z" - content=""" -I have not tried to upgrade, but I fixed it using annex describe followed by assistant restart as hinted in /usr/share/doc/git-annex/html/bugs/uuid.log_trust.log_and_remote.log_merge_wackiness.html. - -From that document I understood that at worst it should use one of the two uuids (from Ubuntu or Gentoo repo), but it should not leave it without uuid and hence this report. - -I have tried it a couple of times and it is perfectly reproducible. -"""]] diff --git a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_3_df7fc1078059538a76f384a40541e91f._comment b/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_3_df7fc1078059538a76f384a40541e91f._comment deleted file mode 100644 index 75fd81d46..000000000 --- a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_3_df7fc1078059538a76f384a40541e91f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.108.193" - subject="comment 3" - date="2013-06-25T19:13:06Z" - content=""" -An old bug report that was fixed in 2011 seems very unlikely to have anything to do with your local pairing problem. - -Why don't you try upgrading? -"""]] diff --git a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_4_70c444c61f41df2f59294c10f94f0c09._comment b/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_4_70c444c61f41df2f59294c10f94f0c09._comment deleted file mode 100644 index 8e895be5f..000000000 --- a/doc/bugs/Missing_repo_uuid_after_local_pairing_with_older_annex/comment_4_70c444c61f41df2f59294c10f94f0c09._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm01ida6POv7vqyUYtOlymEbJTbrImAIzM" - nickname="Reinis" - subject="comment 4" - date="2013-06-25T19:34:12Z" - content=""" -I was expecting the version in distribution which came out two months ago to be somewhat recent, probably unfounded expectation for non-rolling release distribution. I'll add PPA and try using that one. -"""]] diff --git a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex.mdwn b/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex.mdwn deleted file mode 100644 index 8df3bde48..000000000 --- a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -My local git index got corrupted and I needed to clone and annex get all data from my main repo. - -Some files were never copied anywhere so I am stuck with symlinks to nowhere. - -I tried to copy over the symlink with a copy of the actual file, which did not work. Trying to unlock, copying over the symlink, and relock did not work, either. - -Then, I copied the annex object to the correct place in .git/annex/objects/..., set all modes, re-ran fsck and the file re-appeared. - - -Long story short, I think there should be a `git annex reinject $file` or similar which will take a file, either one replacing the symlink or with an arbitrary path, and put it into the correct place in the object store. Called normally, it should reject all reinjects where the checksum does not match. With --force, this should be overridden. For reasons of safety, WORM should always require --force. - -> [[closing|done]], seems addressed --[[Joey]] diff --git a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_1_c871605e187f539f3bfe7478433e7fb5._comment b/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_1_c871605e187f539f3bfe7478433e7fb5._comment deleted file mode 100644 index 9688012a4..000000000 --- a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_1_c871605e187f539f3bfe7478433e7fb5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2011-04-03T01:46:16Z" - content=""" -Have you seen [[walkthrough/recover_data_from_lost+found]]? The method described there will also work in this scenario. -"""]] diff --git a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_2_e6f1e9eee8b8dfb60ca10c8cfd807ac9._comment b/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_2_e6f1e9eee8b8dfb60ca10c8cfd807ac9._comment deleted file mode 100644 index c9b74d98f..000000000 --- a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_2_e6f1e9eee8b8dfb60ca10c8cfd807ac9._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 2" - date="2011-04-03T09:00:17Z" - content=""" -I did not. Thanks :) - -This still means that you can't re-inject a new version of a file unless you have the old one if you are using a SHA* backend, but that might be a corner case anyway. -"""]] diff --git a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_3_be62be5fe819acc0cb8b878802decd46._comment b/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_3_be62be5fe819acc0cb8b878802decd46._comment deleted file mode 100644 index 9c56452e5..000000000 --- a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_3_be62be5fe819acc0cb8b878802decd46._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 3" - date="2011-05-14T16:28:36Z" - content=""" -To re-inject new content for a file, you really want to get a new key for the file. Otherwise, other repos that have the old file will never get the new content. So: - -<pre> -git rm file -mv ~/newcontent file -git annex add file -</pre> -"""]] diff --git a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_4_480a4f72445a636eab1b1c0f816d365c._comment b/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_4_480a4f72445a636eab1b1c0f816d365c._comment deleted file mode 100644 index fcca0561d..000000000 --- a/doc/bugs/No_easy_way_to_re-inject_a_file_into_an_annex/comment_4_480a4f72445a636eab1b1c0f816d365c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 4" - date="2011-05-14T16:29:35Z" - content=""" -Now available as `git-annex reinject`. -"""]] diff --git a/doc/bugs/No_manual_page_on_prebuilt_linux_version.mdwn b/doc/bugs/No_manual_page_on_prebuilt_linux_version.mdwn deleted file mode 100644 index eeb96a197..000000000 --- a/doc/bugs/No_manual_page_on_prebuilt_linux_version.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -### Please describe the problem, What steps will reproduce the problem? - - $ which git-annex - ~/.local/bin/git-annex - $ git help annex - No manual entry for git-annex - $ git annex --help - No manual entry for git-annex - -(either that or it display the manual of system-installed git-annex, not the locally installed one) - -### What version of git-annex are you using? On what operating system? - -Fedora 20 - -`git-annex --version` doesn't work and the webapp tells me Version: 5.20131130-gc25be33 - -> [[fixed|done]] (OSX too) --[[Joey]] diff --git a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend.mdwn b/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend.mdwn deleted file mode 100644 index 8cf6e4f72..000000000 --- a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend.mdwn +++ /dev/null @@ -1,64 +0,0 @@ -### Please describe the problem. - -I get no such file errors when using WORM backend on files with a certain name. Doesn't like brackets? - -Default backend is fine (see output below). - -### What steps will reproduce the problem? - -See additional info - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140613-g5587055 -On Windows 8.1 -Tried with both Windows command prompt and Git Bash shell. - -### 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 - -git config --add annex.backends WORM -git annex add extras - -add extras/Extra Content - Reason Drum Takes/DT Key Map.pdf ok -add extras/Extra Content - Reason Drum Takes/DT Read Me.pdf ok -add extras/Extra Content - Reason Drum Takes/DT7 Rock - Love (136).reason ok -add extras/Extra Content - Reason Drum Takes/DT7 Rock - Peace (200).reason ok -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G06.aif -git-annex: C:\Studio\.git\annex\objects\b43\d6d\WORM-s178174-m1363015489--extras%Extra Content - Reason Drum Takes%Kit S -amples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G06.aif\WORM-s178174-m1363015489--extras%Extra Content - Reason Drum Tak -es%Kit Samples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G06.aif.cache: openFile: does not exist (No such file or directo -ry) -failed -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G09.aif -git-annex: C:\Studio\.git\annex\objects\e90\b5c\WORM-s199108-m1363015489--extras%Extra Content - Reason Drum Takes%Kit S -amples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G09.aif\WORM-s199108-m1363015489--extras%Extra Content - Reason Drum Tak -es%Kit Samples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G09.aif.cache: openFile: does not exist (No such file or directo -ry) -failed -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G14.aif -git-annex: C:\Studio\.git\annex\objects\995\4e7\WORM-s201570-m1363015489--extras%Extra Content - Reason Drum Takes%Kit S -amples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G14.aif\WORM-s201570-m1363015489--extras%Extra Content - Reason Drum Tak -es%Kit Samples%1. Bass Drum mic ,40BD,41%DT6_BD_Bd_RG_R_G14.aif.cache: openFile: does not exist (No such file or directo -ry) -failed - -git config --unset annex.backends -git annex add extras - -add extras/Extra Content - Reason Drum Takes/DT Key Map.pdf ok -add extras/Extra Content - Reason Drum Takes/DT Read Me.pdf ok -add extras/Extra Content - Reason Drum Takes/DT7 Rock - Love (136).reason ok -add extras/Extra Content - Reason Drum Takes/DT7 Rock - Peace (200).reason ok -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G06.aif ok -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G09.aif ok -add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/DT6_BD_Bd_RG_R_G14.aif ok - -# End of transcript or log. -"""]] - -> [[done]]; this is a duplicate of the bug referred to in my comment below. -> --[[Joey]] diff --git a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_1_a1db4ff3e8517d7cbe649bca1ed275d0._comment b/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_1_a1db4ff3e8517d7cbe649bca1ed275d0._comment deleted file mode 100644 index 7136cabb0..000000000 --- a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_1_a1db4ff3e8517d7cbe649bca1ed275d0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-05T21:55:46Z" - content=""" -Hmm, the filename `WORM-s178174-m1363015489--extras%Extra\ Content\ -\ Reason\ Drum\ Takes%Kit\ Samples%1.\ Bass\ Drum\ mic\ ,40BD,41%DT6_BD_Bd_RG_R_G06.aif.cach` is a legal filename on FAT at least, dunno about NTFS.. -"""]] diff --git a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_2_c5645988eaf4f7493d70b6a63f21cdaf._comment b/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_2_c5645988eaf4f7493d70b6a63f21cdaf._comment deleted file mode 100644 index 6305a4eff..000000000 --- a/doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_2_c5645988eaf4f7493d70b6a63f21cdaf._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-01-20T19:09:39Z" - content=""" -Seems this does not have to do with special characters at all. - -Instead, it's a problem with too-long filenames; windows has a crazy short -limit. All explained here: -(http://git-annex.branchable.com/bugs/__34__git-annex:_direct:_1_failed__34___on_Windows) - -You could just switch from the WORM backend to one with shorter filenames. -SHA1 might be a god choice. - -Or, install git-annex 5.20150113, which includes some changes to use shorter -relative paths to files, and may avoid the problem at least some of the -time. That version also avoids making such long WORM keys. -"""]] diff --git a/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn b/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn deleted file mode 100644 index e4a364195..000000000 --- a/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. -There are a lot of differences in the behaviour of usual commands and commans using --all. -The specific problem I found was that "git annex fsck --all" will only checksum it seems and not report back numcopies failures. -Checking if objects/old versions have propagated is not possible without it or do I miss something. - -(As additional note not sure if related. It seems that git annex fsck --all is running much faster in my tests 1/3 faster. Any reason for that? Bug related?) - - -### What steps will reproduce the problem? -compare "git annex fsck" vs "git annex fsck" (no numcopies check) - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140210-gd99db49 -Linux (Ubuntu 13.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. -"""]] - -> It's expected that --all (and --unused) make .gitattributes -> annex.numcopies settings be ignored, because with these options git-annex -> is operating on keys, it does not know or care what filename they're -> associated with, and so cannot look them up in .gitattributes. I have -> improved the documentation of .gitattributes files to mention this -> limitation. -> -> I also notice that fsck --all is not checking .git/config's -> annex.numcopies or the new global numcopies setting. It certianly makes -> sense for those numcopies settings to be paid attention to. -> [[fixed|done]] --[[Joey]] -> -> (--all is faster because it can quickly scan through .git/annex/objects -> to find everything, rather than looking at the symlink target of every -> file in the work tree.) diff --git a/doc/bugs/Numcopies_not_checked_when_running_with_--all/comment_1_63af5a11c3ae370433c4bf84de097414._comment b/doc/bugs/Numcopies_not_checked_when_running_with_--all/comment_1_63af5a11c3ae370433c4bf84de097414._comment deleted file mode 100644 index c0cbe3907..000000000 --- a/doc/bugs/Numcopies_not_checked_when_running_with_--all/comment_1_63af5a11c3ae370433c4bf84de097414._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="84.56.21.11" - subject="Some suggestions" - date="2014-02-20T21:22:21Z" - content=""" -So I think it should at least for --all look at the global numcopies setting. As this could be essential to prevent data-loss. -I agree that special working tree related numcopies don't need to be included. -"""]] diff --git a/doc/bugs/OOM_while_configuring_git-annex.mdwn b/doc/bugs/OOM_while_configuring_git-annex.mdwn deleted file mode 100644 index 07f8909af..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex.mdwn +++ /dev/null @@ -1,48 +0,0 @@ -### Please describe the problem. -When running configure, the system runs out of memory: - -[[https://kojipkgs.fedoraproject.org//work/tasks/1587/10431587/build.log]] - -built with versions from: - -[[https://kojipkgs.fedoraproject.org//work/tasks/1587/10431587/root.log]] - -### What steps will reproduce the problem? -Rebuilding on koji. Also occurs in mock. Haven't tried a naked build (yet). - -### What version of git-annex are you using? On what operating system? -Currently, 5.20141203. Newest snapshot requires deps not yet packaged in Fedora. - -### Please provide any additional information below. - -[[!format sh """ -+ ./Setup configure --prefix=/usr --libdir=/usr/lib --docdir=/usr/share/doc/git-annex '--libsubdir=$compiler/$pkgid' '--datasubdir=$pkgid' --ghc --enable-executable-dynamic '--ghc-options= -optc-O2 -optc-g -optc-pipe -optc-Wall -optc-Werror=format-security -optc-Wp,-D_FORTIFY_SOURCE=2 -optc-fexceptions -optc-fstack-protector-strong -optc--param=ssp-buffer-size=4 -optc-grecord-gcc-switches -optc-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -optc-m32 -optc-march=i686 -optc-mtune=atom -optc-fasynchronous-unwind-tables -optl-Wl,-z,relro' - checking version...fatal: Not a git repository (or any of the parent directories): .git - 5.20141203 - checking UPGRADE_LOCATION... not available - checking git... yes - checking git version... 2.4.6 - checking cp -a... yes - checking cp -p... yes - checking cp --preserve=timestamps... yes - checking cp --reflink=auto... yes - checking xargs -0... yes - checking rsync... yes - checking curl... yes - checking wget... no - checking bup... no - checking nice... yes - checking ionice... yes - checking nocache... no - checking gpg... gpg2 - checking lsof... not available - checking git-remote-gcrypt... not available - checking ssh connection caching... yes - checking sha1... sha1sum - checking sha256... sha256sum - checking sha512... sha512sum - checking sha224... sha224sum - checking sha384...Setup: out of memory (requested 1048576 bytes) -"""]] - -> forwarded to cabal && [[done]] per my comment --[[Joey]] diff --git a/doc/bugs/OOM_while_configuring_git-annex/comment_1_247c4d778766c9079024c78582a69ed4._comment b/doc/bugs/OOM_while_configuring_git-annex/comment_1_247c4d778766c9079024c78582a69ed4._comment deleted file mode 100644 index 19a52bed9..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex/comment_1_247c4d778766c9079024c78582a69ed4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-22T03:36:11Z" - content=""" -This is due to cabal's dependency resolver not finding a solution and -recursing too much. Passing -v3 will show what the dependency problem is. - -(Using stackage is a good way to avoid these kinds of dependency problems.) -"""]] diff --git a/doc/bugs/OOM_while_configuring_git-annex/comment_2_efb55be6e82d4034358b186125edafbd._comment b/doc/bugs/OOM_while_configuring_git-annex/comment_2_efb55be6e82d4034358b186125edafbd._comment deleted file mode 100644 index 161f3b068..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex/comment_2_efb55be6e82d4034358b186125edafbd._comment +++ /dev/null @@ -1,56 +0,0 @@ -[[!comment format=sh - username="siflfran@3babe1b188962ba45b5d4649e721ac59ead57b7c" - nickname="siflfran" - subject="comment 2" - date="2015-07-29T06:57:00Z" - content=""" -Running configure with -v3 does not give much additional info: - -% runhaskell Setup.hs configure --verbose=3 --prefix=/usr - checking version...fatal: Not a git repository (or any parent up to mount point /tmp) -Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). - 5.20150617 - checking UPGRADE_LOCATION... not available - checking git... yes - checking git version... 2.4.6 - checking cp -a... yes - checking cp -p... yes - checking cp --preserve=timestamps... yes - checking cp --reflink=auto... yes - checking xargs -0... yes - checking rsync... yes - checking curl... yes - checking wget... yes - checking wget supports -q --show-progress... yes - checking bup... no - checking nice... yes - checking ionice... yes - checking nocache... no - checking gpg... gpg - checking lsof... not available - checking git-remote-gcrypt... not available - checking ssh connection caching... yes - checking sha1... sha1sum - checking sha256... sha256sum - checking sha512... sha512sum - checking sha224... sha224sum - checking sha384... sha384sum -Configuring git-annex-5.20150617... -creating dist -Searching for ghc in path. -Found ghc at /usr/bin/ghc -(\"/usr/bin/ghc\",[\"--numeric-version\"]) -/usr/bin/ghc is version 7.10.1 -looking for tool ghc-pkg near compiler in /usr/bin -found ghc-pkg in /usr/bin/ghc-pkg -(\"/usr/bin/ghc-pkg\",[\"--version\"]) -/usr/bin/ghc-pkg is version 7.10.1 -(\"/usr/bin/ghc\",[\"--supported-languages\"]) -(\"/usr/bin/ghc\",[\"--info\"]) -Reading installed packages... -(\"/usr/bin/ghc-pkg\",[\"dump\",\"--global\",\"-v0\"]) -(\"/usr/bin/ghc\",[\"--print-libdir\"]) -Killed - -Any suggestions? -"""]] diff --git a/doc/bugs/OOM_while_configuring_git-annex/comment_3_e302c50d67ee09f499ab62d97f112fc1._comment b/doc/bugs/OOM_while_configuring_git-annex/comment_3_e302c50d67ee09f499ab62d97f112fc1._comment deleted file mode 100644 index 53a90b5a2..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex/comment_3_e302c50d67ee09f499ab62d97f112fc1._comment +++ /dev/null @@ -1,246 +0,0 @@ -[[!comment format=sh - username="siflfran@3babe1b188962ba45b5d4649e721ac59ead57b7c" - nickname="siflfran" - subject="comment 3" - date="2015-07-29T15:49:19Z" - content=""" -I gave it another try on a different system and it actually seems to succeed: - - % runhaskell Setup.hs configure --prefix=/usr --verbose=3 - checking version...fatal: Not a git repository (or any parent up to mount point /tmp) -Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). - 5.20150710 - checking UPGRADE_LOCATION... not available - checking git... yes - checking git version... 2.5.0 - checking cp -a... yes - checking cp -p... yes - checking cp --preserve=timestamps... yes - checking cp --reflink=auto... yes - checking xargs -0... yes - checking rsync... yes - checking curl... yes - checking wget... yes - checking wget supports -q --show-progress... yes - checking bup... no - checking nice... yes - checking ionice... yes - checking nocache... no - checking gpg... gpg - checking lsof... lsof - checking git-remote-gcrypt... not available - checking ssh connection caching... yes - checking sha1... sha1sum - checking sha256... sha256sum - checking sha512... sha512sum - checking sha224... sha224sum - checking sha384... sha384sum -Configuring git-annex-5.20150710... -creating dist -Searching for ghc in path. -Found ghc at /usr/bin/ghc -(\"/usr/bin/ghc\",[\"--numeric-version\"]) -/usr/bin/ghc is version 7.8.4 -looking for tool ghc-pkg near compiler in /usr/bin -found ghc-pkg in /usr/bin/ghc-pkg -(\"/usr/bin/ghc-pkg\",[\"--version\"]) -/usr/bin/ghc-pkg is version 7.8.4 -(\"/usr/bin/ghc\",[\"--supported-languages\"]) -(\"/usr/bin/ghc\",[\"--info\"]) -Reading installed packages... -(\"/usr/bin/ghc-pkg\",[\"dump\",\"--global\",\"-v0\"]) -(\"/usr/bin/ghc\",[\"--print-libdir\"]) -Flags chosen: new-time=False, network-uri=True, ekg=False, -asciiprogress=False, torrentparser=False, desktopnotify=False, tahoe=True, -quvi=True, feed=True, tdfa=True, testsuite=True, androidsplice=False, -android=False, production=True, dns=True, xmpp=True, pairing=True, -webapp-secure=True, webapp=True, assistant=True, dbus=True, inotify=True, -webdav=False, s3=True -Dependency IfElse -any: using IfElse-0.85 -Dependency MissingH -any: using MissingH-1.3.0.1 -Dependency QuickCheck >=2.1: using QuickCheck-2.8.1 -Dependency SafeSemaphore -any: using SafeSemaphore-0.10.1 -Dependency aeson -any: using aeson-0.9.0.1 -Dependency async -any: using async-2.0.2 -Dependency aws >=0.9.2: using aws-0.12.1 -Dependency base >=4.5 && <4.9: using base-4.7.0.2 -Dependency blaze-builder -any: using blaze-builder-0.4.0.1 -Dependency bloomfilter -any: using bloomfilter-2.0.1.0 -Dependency byteable -any: using byteable-0.1.1 -Dependency bytestring -any: using bytestring-0.10.4.0 -Dependency case-insensitive -any: using case-insensitive-1.2.0.4 -Dependency clientsession -any: using clientsession-0.9.1.1 -Dependency conduit -any: using conduit-1.2.5 -Dependency conduit-extra -any: using conduit-extra-1.1.9.1 -Dependency containers >=0.5.0.0: using containers-0.5.5.1 -Dependency crypto-api -any: using crypto-api-0.13.2 -Dependency cryptohash >=0.11.0: using cryptohash-0.11.6 -Dependency data-default -any: using data-default-0.5.3 -Dependency dbus >=0.10.7: using dbus-0.10.10 -Dependency directory -any: using directory-1.2.1.0 -Dependency dlist -any: using dlist-0.7.1.1 -Dependency dns -any: using dns-2.0.0 -Dependency edit-distance -any: using edit-distance-0.2.2.1 -Dependency esqueleto -any: using esqueleto-2.1.3 -Dependency exceptions >=0.6: using exceptions-0.8.0.2 -Dependency feed >=0.3.4: using feed-0.3.9.7 -Dependency filepath -any: using filepath-1.3.0.2 -Dependency gnutls >=0.1.4: using gnutls-0.1.6 -Dependency hinotify -any: using hinotify-0.3.7 -Dependency hslogger -any: using hslogger-1.2.9 -Dependency http-client -any: using http-client-0.4.18.1 -Dependency http-conduit -any: using http-conduit-2.1.7.1 -Dependency http-types -any: using http-types-0.8.6 -Dependency json -any: using json-0.9.1 -Dependency monad-control -any: using monad-control-1.0.0.4 -Dependency monad-logger -any: using monad-logger-0.3.13.2 -Dependency mtl >=2: using mtl-2.2.1 -Dependency network >=2.6: using network-2.6.2.1 -Dependency network-info -any: using network-info-0.2.0.7 -Dependency network-multicast -any: using network-multicast-0.0.11 -Dependency network-protocol-xmpp -any: using network-protocol-xmpp-0.4.8 -Dependency network-uri >=2.6: using network-uri-2.6.0.3 -Dependency old-locale -any: using old-locale-1.0.0.6 -Dependency optparse-applicative >=0.10: using optparse-applicative-0.11.0.2 -Dependency path-pieces >=0.1.4: using path-pieces-0.2.0 -Dependency persistent -any: using persistent-2.1.6 -Dependency persistent-sqlite -any: using persistent-sqlite-2.1.4.2 -Dependency persistent-template -any: using persistent-template-2.1.3.4 -Dependency process -any: using process-1.2.0.0 -Dependency random -any: using random-1.1 -Dependency regex-tdfa -any: using regex-tdfa-1.2.0 -Dependency resourcet -any: using resourcet-1.1.5 -Dependency sandi -any: using sandi-0.3.5 -Dependency securemem -any: using securemem-0.1.9 -Dependency shakespeare >=2.0.0: using shakespeare-2.0.5 -Dependency stm >=2.3: using stm-2.4.4 -Dependency tasty >=0.7: using tasty-0.10.1.2 -Dependency tasty-hunit -any: using tasty-hunit-0.9.2 -Dependency tasty-quickcheck -any: using tasty-quickcheck-0.8.3.2 -Dependency tasty-rerun -any: using tasty-rerun-1.1.4 -Dependency template-haskell -any: using template-haskell-2.9.0.0 -Dependency text -any: using text-1.2.1.1 -Dependency time -any: using time-1.4.2 -Dependency transformers -any: using transformers-0.4.3.0 -Dependency unix -any: using unix-2.7.0.1 -Dependency unix-compat -any: using unix-compat-0.4.1.4 -Dependency utf8-string -any: using utf8-string-1 -Dependency uuid -any: using uuid-1.3.10 -Dependency wai -any: using wai-3.0.3.0 -Dependency wai-extra -any: using wai-extra-3.0.10 -Dependency warp >=3.0.0.5: using warp-3.0.13.1 -Dependency warp-tls >=1.4: using warp-tls-3.0.4.2 -Dependency xml-types -any: using xml-types-0.3.6 -Dependency yesod >=1.2.6: using yesod-1.4.1.5 -Dependency yesod-core >=1.2.19: using yesod-core-1.4.12 -Dependency yesod-default >=1.2.0: using yesod-default-1.2.0 -Dependency yesod-form >=1.3.15: using yesod-form-1.4.4.1 -Dependency yesod-static >=1.2.4: using yesod-static-1.5.0.1 -Searching for alex in path. -Found alex at /usr/bin/alex -(\"/usr/bin/alex\",[\"--version\"]) -/usr/bin/alex is version 3.1.4 -Searching for ar in path. -Found ar at /usr/bin/ar -Searching for c2hs in path. -Found c2hs at /usr/bin/c2hs -(\"/usr/bin/c2hs\",[\"--numeric-version\"]) -/usr/bin/c2hs is version 0.25.2 -Searching for cpphs in path. -Cannot find cpphs on the path -Searching for gcc in path. -Found gcc at /usr/bin/gcc -(\"/usr/bin/gcc\",[\"-dumpversion\"]) -/usr/bin/gcc is version 4.9.3 -Searching for ghcjs in path. -Cannot find ghcjs on the path -Searching for ghcjs-pkg in path. -Cannot find ghcjs-pkg on the path -Searching for greencard in path. -Cannot find greencard on the path -Searching for haddock in path. -Cannot find haddock on the path -Searching for happy in path. -Found happy at /usr/bin/happy -(\"/usr/bin/happy\",[\"--version\"]) -/usr/bin/happy is version 1.19.5 -Searching for hmake in path. -Cannot find hmake on the path -Searching for hpc in path. -Found hpc at /usr/bin/hpc -(\"/usr/bin/hpc\",[\"version\"]) -/usr/bin/hpc is version 0.67 -looking for tool hsc2hs near compiler in /usr/bin -found hsc2hs in /usr/bin/hsc2hs -(\"/usr/bin/hsc2hs\",[\"--version\"]) -/usr/bin/hsc2hs is version 0.67 -Searching for HsColour in path. -Found HsColour at /usr/bin/HsColour -(\"/usr/bin/HsColour\",[\"-version\"]) -/usr/bin/HsColour is version 1.22 -Searching for jhc in path. -Cannot find jhc on the path -Searching for ld in path. -Found ld at /usr/bin/ld -Environment: [(\"ANT_HOME\",\"/usr/share/ant\"),(\"AWT_TOOLKIT\",\"MToolkit\"),(\"BLOCKSIZE\",\"K\"),(\"CASROOT\",\"/usr/lib64/opencascade-6.9.0/ros/lin\"),(\"CCACHE_NOCOMPRESS\",\"yes\"),(\"COLORFGBG\",\"default;default\"),(\"COLORTERM\",\"yes\"),(\"CONFIG_PROTECT\",\"/usr/share/gnupg/qualified.txt /usr/share/config /usr/lib64/libreoffice/program/sofficerc\"),(\"CONFIG_PROTECT_MASK\",\"/etc/gentoo-release /etc/sandbox.d /etc/fonts/fonts.conf /etc/gconf /etc/terminfo /etc/dconf /etc/ca-certificates.conf /etc/texmf/web2c /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/revdep-rebuild\"),(\"CSF_EXCEPTION_PROMPT\",\"1\"),(\"CSF_GraphicShr\",\"/usr/lib64/opencascade-6.9.0/ros/lin/lib64/libTKOpenGl.so\"),(\"CSF_IGESDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/XSTEPResource\"),(\"CSF_LANGUAGE\",\"us\"),(\"CSF_MDTVFontDirectory\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/FontMFT\"),(\"CSF_MDTVTexturesDirectory\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/Textures\"),(\"CSF_MIGRATION_TYPES\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/StdResource/MigrationSheet.txt\"),(\"CSF_PluginDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/StdResource\"),(\"CSF_SHMessage\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/SHMessage\"),(\"CSF_STEPDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/XSTEPResource\"),(\"CSF_StandardDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/StdResource\"),(\"CSF_StandardLiteDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/StdResource\"),(\"CSF_UnitsDefinition\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/UnitsAPI/Units.dat\"),(\"CSF_UnitsLexicon\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/UnitsAPI/Lexi_Expr.dat\"),(\"CSF_XCAFDefaults\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/StdResource\"),(\"CSF_XSMessage\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/XSMessage\"),(\"CSF_XmlOcafResource\",\"/usr/lib64/opencascade-6.9.0/ros/lin/src/XmlOcafResource\"),(\"CVS_RSH\",\"ssh\"),(\"DBUS_SESSION_BUS_ADDRESS\",\"unix:abstract=/tmp/dbus-KC1dHno8Ok,guid=22396e1b611ef7c98854252555b76fe7\"),(\"DEBEMAIL\",\"Florian.Franzmann@cs.fau.de\"),(\"DEBFULLNAME\",\"Florian Franzmann\"),(\"DIFF_TOOL\",\"kdiff3\"),(\"DISPLAY\",\":0\"),(\"EDITOR\",\"vim\"),(\"EMAIL\",\"Florian Franzmann <Florian.Franzmann@fau.de>\"),(\"EVENT_NOEPOLL\",\"1\"),(\"FLTK_DOCDIR\",\"/usr/share/doc/fltk-1.3.3-r3/html\"),(\"GCC_COLORS\",\"error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01\"),(\"GCC_SPECS\",\"\"),(\"GIT_AUTHOR_EMAIL\",\"Florian.Franzmann@fau.de\"),(\"GREP_COLOR\",\"1;31\"),(\"GSETTINGS_BACKEND\",\"dconf\"),(\"GTK_MODULES\",\"canberra-gtk-module\"),(\"GUILE_LOAD_PATH\",\"/usr/share/guile/1.8\"),(\"HACKPAGER\",\"less\"),(\"HG\",\"/usr/bin/hg\"),(\"HOME\",\"/home/franzman\"),(\"INFINALITY_FT_AUTOHINT_HORIZONTAL_STEM_DARKEN_STRENGTH\",\"10\"),(\"INFINALITY_FT_AUTOHINT_INCREASE_GLYPH_HEIGHTS\",\"true\"),(\"INFINALITY_FT_AUTOHINT_SNAP_STEM_HEIGHT\",\"100\"),(\"INFINALITY_FT_AUTOHINT_VERTICAL_STEM_DARKEN_STRENGTH\",\"25\"),(\"INFINALITY_FT_BOLD_EMBOLDEN_X_VALUE\",\"0\"),(\"INFINALITY_FT_BOLD_EMBOLDEN_Y_VALUE\",\"0\"),(\"INFINALITY_FT_BRIGHTNESS\",\"0\"),(\"INFINALITY_FT_CHROMEOS_STYLE_SHARPENING_STRENGTH\",\"0\"),(\"INFINALITY_FT_CONTRAST\",\"0\"),(\"INFINALITY_FT_FILTER_PARAMS\",\"11 22 38 22 11\"),(\"INFINALITY_FT_FRINGE_FILTER_STRENGTH\",\"0\"),(\"INFINALITY_FT_GAMMA_CORRECTION\",\"0 100\"),(\"INFINALITY_FT_GLOBAL_EMBOLDEN_X_VALUE\",\"0\"),(\"INFINALITY_FT_GLOBAL_EMBOLDEN_Y_VALUE\",\"0\"),(\"INFINALITY_FT_GRAYSCALE_FILTER_STRENGTH\",\"0\"),(\"INFINALITY_FT_STEM_ALIGNMENT_STRENGTH\",\"25\"),(\"INFINALITY_FT_STEM_FITTING_STRENGTH\",\"25\"),(\"INFINALITY_FT_STEM_SNAPPING_SLIDING_SCALE\",\"40\"),(\"INFINALITY_FT_USE_KNOWN_SETTINGS_ON_SELECTED_FONTS\",\"true\"),(\"INFINALITY_FT_USE_VARIOUS_TWEAKS\",\"true\"),(\"INFINALITY_FT_WINDOWS_STYLE_SHARPENING_STRENGTH\",\"5\"),(\"INFOPATH\",\"/usr/share/info:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3/info:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.25.1/info\"),(\"ITCL_LIBRARY\",\"/usr/lib64/itcl4.0\"),(\"ITK_LIBRARY\",\"/usr/lib64/itk4.0\"),(\"JAVAC\",\"/etc/java-config-2/current-system-vm/bin/javac\"),(\"JAVA_HOME\",\"/etc/java-config-2/current-system-vm\"),(\"JDK_HOME\",\"/etc/java-config-2/current-system-vm\"),(\"LADSPA_PATH\",\"/usr/lib/ladspa\"),(\"LANG\",\"en_US.utf8\"),(\"LC_COLLATE\",\"de_DE.utf8\"),(\"LC_CTYPE\",\"de_DE.utf8\"),(\"LC_MESSAGES\",\"\"),(\"LC_MONETARY\",\"de_DE.utf8\"),(\"LC_NUMERIC\",\"de_DE.utf8\"),(\"LC_TIME\",\"de_DE.utf8\"),(\"LESS\",\" -R \"),(\"LESSOPEN\",\"| /usr/bin/src-hilite-lesspipe.sh %s\"),(\"LESS_TERMCAP_mb\",\"\ESC[01;31m\"),(\"LESS_TERMCAP_md\",\"\ESC[01;31m\"),(\"LESS_TERMCAP_me\",\"\ESC[0m\"),(\"LESS_TERMCAP_se\",\"\ESC[0m\"),(\"LESS_TERMCAP_so\",\"\ESC[01;44;33m\"),(\"LESS_TERMCAP_ue\",\"\ESC[0m\"),(\"LESS_TERMCAP_us\",\"\ESC[01;32m\"),(\"LIBXCB_ALLOW_SLOPPY_LOCK\",\"yes\"),(\"LOGNAME\",\"franzman\"),(\"LSCOLORS\",\"Gxfxcxdxbxegedabagacad\"),(\"MAIL\",\"/var/mail/franzman\"),(\"MAKE_NJOBS\",\"4\"),(\"MANPATH\",\"/etc/java-config-2/current-system-vm/man:/usr/local/share/man:/usr/share/man:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3/man:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.25.1/man:/etc/java-config-2/current-system-vm/man/\"),(\"MINICOM\",\"-c on -o -w\"),(\"MMGT_CLEAR\",\"1\"),(\"OPENCL_PROFILE\",\"mesa\"),(\"OPENGL_PROFILE\",\"xorg-x11\"),(\"PAGER\",\"less\"),(\"PATH\",\"/home/franzman/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin\"),(\"PERL5LIB\",\"/home/franzman/perl5/lib/perl5\"),(\"PERL_LOCAL_LIB_ROOT\",\"/home/franzman/perl5\"),(\"PERL_MB_OPT\",\"--install_base \\"/home/franzman/perl5\\"\"),(\"PERL_MM_OPT\",\"INSTALL_BASE=/home/franzman/perl5\"),(\"PRELINK_PATH_MASK\",\"/usr/lib64/libfreebl3.so:/usr/lib64/libnssdbm3.so:/usr/lib64/libsoftokn3.so\"),(\"PWD\",\"/tmp/git-annex-5.20150710\"),(\"QT_GRAPHICSSYSTEM\",\"raster\"),(\"QT_PLUGIN_PATH\",\"/usr/lib64/kde4/plugins\"),(\"R_HOME\",\"/usr/lib64/R\"),(\"SHELL\",\"/bin/zsh\"),(\"SHLVL\",\"3\"),(\"SP_BASE\",\"/home/franzman/repos/sp-korrektur-ss15/V_SP/ueb\"),(\"TCLHOME\",\"/usr/bin\"),(\"TCLLIBPATH\",\"/usr/lib64\"),(\"TCL_LIBRARY\",\"/usr/lib64/tcl8.6\"),(\"TERM\",\"rxvt-unicode-256color\"),(\"TESTBASE\",\"/home/franzman/repos/sp-korrektur-ss15/V_SP/ueb/aufgaben/clash/testcase\"),(\"TEXEDIT\",\"vim\"),(\"TEXINPUTS\",\"/usr/lib64/ocaml/ocamldoc:\"),(\"TIX_LIBRARY\",\"/usr/lib64/tix8.4\"),(\"TK_LIBRARY\",\"/usr/lib64/tk8.6\"),(\"UBUNTU_MENUPROXY\",\"1\"),(\"USER\",\"franzman\"),(\"WHOIS_OPTIONS\",\"-H\"),(\"WINDOWID\",\"35651708\"),(\"WINDOWPATH\",\"7\"),(\"XDG_CONFIG_DIRS\",\"/etc/xdg\"),(\"XDG_DATA_DIRS\",\"/usr/local/share:/usr/share\"),(\"_JAVA_AWT_WM_NONREPARENTING\",\"1\")] -(\"/usr/bin/ghc\",[\"-c\",\"/tmp/16120.c\",\"-o\",\"/tmp/16120.o\"]) -(\"/usr/bin/ld\",[\"-x\",\"-r\",\"/tmp/16120.o\",\"-o\",\"/tmp/16121.o\"]) -Searching for lhc in path. -Cannot find lhc on the path -Searching for lhc-pkg in path. -Cannot find lhc-pkg on the path -Searching for pkg-config in path. -Found pkg-config at /usr/bin/pkg-config -(\"/usr/bin/pkg-config\",[\"--version\"]) -/usr/bin/pkg-config is version 0.28 -Searching for strip in path. -Found strip at /usr/bin/strip -(\"/usr/bin/strip\",[\"--version\"]) -/usr/bin/strip is version 2.25 -Searching for tar in path. -Found tar at /bin/tar -(\"/bin/tar\",[\"--help\"]) -Searching for uhc in path. -Cannot find uhc on the path -Using Cabal-1.22.4.0 compiled by ghc-7.8 -Using compiler: ghc-7.8.4 -Using install prefix: /usr -Binaries installed in: /usr/bin -Libraries installed in: /usr/lib/x86_64-linux-ghc-7.8.4/git-annex-5.20150710 -Private binaries installed in: /usr/libexec -Data files installed in: -/usr/share/x86_64-linux-ghc-7.8.4/git-annex-5.20150710 -Documentation installed in: -/usr/share/doc/x86_64-linux-ghc-7.8.4/git-annex-5.20150710 -Configuration files installed in: /usr/etc -Using alex version 3.1.4 found on system at: /usr/bin/alex -Using ar found on system at: /usr/bin/ar -Using c2hs version 0.25.2 found on system at: /usr/bin/c2hs -No cpphs found -Using gcc version 4.9.3 found on system at: /usr/bin/gcc -Using ghc version 7.8.4 found on system at: /usr/bin/ghc -Using ghc-pkg version 7.8.4 found on system at: /usr/bin/ghc-pkg -No ghcjs found -No ghcjs-pkg found -No greencard found -No haddock found -Using happy version 1.19.5 found on system at: /usr/bin/happy -Using haskell-suite found on system at: haskell-suite-dummy-location -Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location -No hmake found -Using hpc version 0.67 found on system at: /usr/bin/hpc -Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs -Using hscolour version 1.22 found on system at: /usr/bin/HsColour -No jhc found -Using ld found on system at: /usr/bin/ld -No lhc found -No lhc-pkg found -Using pkg-config version 0.28 found on system at: /usr/bin/pkg-config -Using strip version 2.25 found on system at: /usr/bin/strip -Using tar found on system at: /bin/tar -No uhc found -(\"/usr/bin/gcc\",[\"/tmp/16120.c\",\"-o\",\"/tmp/16120\",\"-D__GLASGOW_HASKELL__=708\",\"-Dlinux_BUILD_OS=1\",\"-Dx86_64_BUILD_ARCH=1\",\"-Dlinux_HOST_OS=1\",\"-Dx86_64_HOST_ARCH=1\",\"-Idist/build/autogen\",\"-IUtility\",\"-I.\",\"-DWITH_CLIBS\",\"-DWITH_TESTSUITE\",\"-DWITH_TDFA\",\"-DWITH_S3\",\"-DWITH_ASSISTANT\",\"-DWITH_INOTIFY\",\"-DWITH_DBUS\",\"-DWITH_WEBAPP\",\"-DWITH_WEBAPP_SECURE\",\"-DWITH_PAIRING\",\"-DWITH_XMPP\",\"-DWITH_DNS\",\"-DWITH_FEED\",\"-DWITH_QUVI\",\"-DWITH_TAHOE\",\"-Wall\",\"-I/usr/lib64/unix-compat-0.4.1.4/ghc-7.8.4/include\",\"-I/usr/include/libxml2\",\"-I/usr/lib64/bloomfilter-2.0.1.0/ghc-7.8.4/include\",\"-I/usr/lib64/vector-0.10.12.3/ghc-7.8.4/include\",\"-I/usr/lib64/primitive-0.5.4.0/ghc-7.8.4/include\",\"-I/usr/lib64/ghc-7.8.4/old-time-1.1.0.2/include\",\"-I/usr/lib64/ghc-7.8.4/process-1.2.0.0/include\",\"-I/usr/lib64/network-2.6.2.1/ghc-7.8.4/include\",\"-I/usr/lib64/ghc-7.8.4/directory-1.2.1.0/include\",\"-I/usr/lib64/ghc-7.8.4/unix-2.7.0.1/include\",\"-I/usr/lib64/ghc-7.8.4/bytestring-0.10.4.0/include\",\"-I/usr/lib64/ghc-7.8.4/time-1.4.2/include\",\"-I/usr/lib64/ghc-7.8.4/base-4.7.0.2/include\",\"-I/usr/lib64/ghc-7.8.4/integer-gmp-0.5.1.0/include\",\"-I/usr/lib64/ghc-7.8.4/include\",\"-I/usr/lib64/libffi-3.2.1/include\",\"-Wall\",\"-L/usr/lib64/yesod-static-1.5.0.1/ghc-7.8.4\",\"-L/usr/lib64/yesod-default-1.2.0/ghc-7.8.4\",\"-L/usr/lib64/yesod-1.4.1.5/ghc-7.8.4\",\"-L/usr/lib64/yesod-auth-1.4.6/ghc-7.8.4\",\"-L/usr/lib64/yesod-form-1.4.4.1/ghc-7.8.4\",\"-L/usr/lib64/yesod-persistent-1.4.0.3/ghc-7.8.4\",\"-L/usr/lib64/yesod-core-1.4.12/ghc-7.8.4\",\"-L/usr/lib64/yaml-0.8.12/ghc-7.8.4\",\"-L/usr/lib64/xss-sanitize-0.3.5.5/ghc-7.8.4\",\"-L/usr/lib64/warp-tls-3.0.4.2/ghc-7.8.4\",\"-L/usr/lib64/wai-app-static-3.1.1/ghc-7.8.4\",\"-L/usr/lib64/warp-3.0.13.1/ghc-7.8.4\",\"-L/usr/lib64/wai-extra-3.0.10/ghc-7.8.4\",\"-L/usr/lib64/word8-0.1.2/ghc-7.8.4\",\"-L/usr/lib64/wai-logger-2.2.4.1/ghc-7.8.4\",\"-L/usr/lib64/wai-3.0.3.0/ghc-7.8.4\",\"-L/usr/lib64/vault-0.3.0.4/ghc-7.8.4\",\"-L/usr/lib64/uuid-1.3.10/ghc-7.8.4\",\"-L/usr/lib64/uuid-types-1.0.1/ghc-7.8.4\",\"-L/usr/lib64/unix-time-0.3.5/ghc-7.8.4\",\"-L/usr/lib64/unix-compat-0.4.1.4/ghc-7.8.4\",\"-L/usr/lib64/tasty-rerun-1.1.4/ghc-7.8.4\",\"-L/usr/lib64/tasty-quickcheck-0.8.3.2/ghc-7.8.4\",\"-L/usr/lib64/tasty-hunit-0.9.2/ghc-7.8.4\",\"-L/usr/lib64/tasty-0.10.1.2/ghc-7.8.4\",\"-L/usr/lib64/unbounded-delays-0.1.0.9/ghc-7.8.4\",\"-L/usr/lib64/tagsoup-0.13.3/ghc-7.8.4\",\"-L/usr/lib64/stringsearch-0.3.6.6/ghc-7.8.4\",\"-L/usr/lib64/split-0.2.2/ghc-7.8.4\",\"-L/usr/lib64/simple-sendfile-0.2.21/ghc-7.8.4\",\"-L/usr/lib64/shakespeare-2.0.5/ghc-7.8.4\",\"-L/usr/lib64/sandi-0.3.5/ghc-7.8.4\",\"-L/usr/lib64/regex-tdfa-rc-1.1.8.3/ghc-7.8.4\",\"-L/usr/lib64/regex-tdfa-1.2.0/ghc-7.8.4\",\"-L/usr/lib64/reducers-3.10.3.2/ghc-7.8.4\",\"-L/usr/lib64/semigroupoids-5.0.0.2/ghc-7.8.4\",\"-L/usr/lib64/persistent-template-2.1.3.4/ghc-7.8.4\",\"-L/usr/lib64/persistent-sqlite-2.1.4.2/ghc-7.8.4\",\"-L/usr/lib64/optparse-applicative-0.11.0.2/ghc-7.8.4\",\"-L/usr/lib64/nonce-1.0.2/ghc-7.8.4\",\"-L/usr/lib64/network-protocol-xmpp-0.4.8/ghc-7.8.4\",\"-L/usr/lib64/network-multicast-0.0.11/ghc-7.8.4\",\"-L/usr/lib64/network-info-0.2.0.7/ghc-7.8.4\",\"-L/usr/lib64/mwc-random-0.13.3.2/ghc-7.8.4\",\"-L/usr/lib64/mime-mail-0.4.9/ghc-7.8.4\",\"-L/usr/lib64/json-0.9.1/ghc-7.8.4\",\"-L/usr/lib64/http-date-0.0.6.1/ghc-7.8.4\",\"-L/usr/lib64/hjsmin-0.1.4.7/ghc-7.8.4\",\"-L/usr/lib64/language-javascript-0.5.13.4/ghc-7.8.4\",\"-L/usr/lib64/hinotify-0.3.7/ghc-7.8.4\",\"-L/usr/lib64/gsasl-0.3.6/ghc-7.8.4\",\"-L/usr/lib64/gnutls-0.1.6/ghc-7.8.4\",\"-L/usr/lib64/monads-tf-0.1.0.2/ghc-7.8.4\",\"-L/usr/lib64/gnuidn-0.2.1/ghc-7.8.4\",\"-L/usr/lib64/fingertree-0.1.1.0/ghc-7.8.4\",\"-L/usr/lib64/file-embed-0.0.8.2/ghc-7.8.4\",\"-L/usr/lib64/feed-0.3.9.7/ghc-7.8.4\",\"-L/usr/lib64/xml-1.3.14/ghc-7.8.4\",\"-L/usr/lib64/time-locale-compat-0.1.1.0/ghc-7.8.4\",\"-L/usr/lib64/esqueleto-2.1.3/ghc-7.8.4\",\"-L/usr/lib64/persistent-2.1.6/ghc-7.8.4\",\"-L/usr/lib64/silently-1.2.5/ghc-7.8.4\",\"-L/usr/lib64/resource-pool-0.2.3.2/ghc-7.8.4\",\"-L/usr/lib64/path-pieces-0.2.0/ghc-7.8.4\",\"-L/usr/lib64/monad-logger-0.3.13.2/ghc-7.8.4\",\"-L/usr/lib64/stm-chans-3.0.0.4/ghc-7.8.4\",\"-L/usr/lib64/monad-loops-0.4.3/ghc-7.8.4\",\"-L/usr/lib64/fast-logger-2.4.0/ghc-7.8.4\",\"-L/usr/lib64/enclosed-exceptions-1.0.1.1/ghc-7.8.4\",\"-L/usr/lib64/email-validate-2.0.1/ghc-7.8.4\",\"-L/usr/lib64/edit-distance-0.2.2.1/ghc-7.8.4\",\"-L/usr/lib64/easy-file-0.2.1/ghc-7.8.4\",\"-L/usr/lib64/dns-2.0.0/ghc-7.8.4\",\"-L/usr/lib64/iproute-1.5.0/ghc-7.8.4\",\"-L/usr/lib64/dbus-0.10.10/ghc-7.8.4\",\"-L/usr/lib64/libxml-sax-0.7.5/ghc-7.8.4\",\"-L/usr/lib64/css-text-0.1.2.1/ghc-7.8.4\",\"-L/usr/lib64/cryptohash-conduit-0.1.1/ghc-7.8.4\",\"-L/usr/lib64/comonad-4.2.7.2/ghc-7.8.4\",\"-L/usr/lib64/distributive-0.4.4/ghc-7.8.4\",\"-L/usr/lib64/contravariant-1.3.1.1/ghc-7.8.4\",\"-L/usr/lib64/clientsession-0.9.1.1/ghc-7.8.4\",\"-L/usr/lib64/skein-1.0.9.3/ghc-7.8.4\",\"-L/usr/lib64/setenv-0.1.1.3/ghc-7.8.4\",\"-L/usr/lib64/crypto-api-0.13.2/ghc-7.8.4\",\"-L/usr/lib64/entropy-0.3.7/ghc-7.8.4\",\"-L/usr/lib64/cprng-aes-0.6.1/ghc-7.8.4\",\"-L/usr/lib64/byteorder-1.0.4/ghc-7.8.4\",\"-L/usr/lib64/bloomfilter-2.0.1.0/ghc-7.8.4\",\"-L/usr/lib64/bifunctors-5/ghc-7.8.4\",\"-L/usr/lib64/base-orphans-0.3.2/ghc-7.8.4\",\"-L/usr/lib64/aws-0.12.1/ghc-7.8.4\",\"-L/usr/lib64/utf8-string-1/ghc-7.8.4\",\"-L/usr/lib64/tagged-0.8.1/ghc-7.8.4\",\"-L/usr/lib64/safe-0.3.9/ghc-7.8.4\",\"-L/usr/lib64/base16-bytestring-0.1.1.6/ghc-7.8.4\",\"-L/usr/lib64/auto-update-0.1.2.2/ghc-7.8.4\",\"-L/usr/lib64/authenticate-1.3.2.11/ghc-7.8.4\",\"-L/usr/lib64/tagstream-conduit-0.5.5.3/ghc-7.8.4\",\"-L/usr/lib64/xml-conduit-1.3.1/ghc-7.8.4\",\"-L/usr/lib64/xml-types-0.3.6/ghc-7.8.4\",\"-L/usr/lib64/blaze-html-0.8.0.2/ghc-7.8.4\",\"-L/usr/lib64/blaze-markup-0.7.0.2/ghc-7.8.4\",\"-L/usr/lib64/data-default-0.5.3/ghc-7.8.4\",\"-L/usr/lib64/data-default-instances-old-locale-0.0.1/ghc-7.8.4\",\"-L/usr/lib64/data-default-instances-dlist-0.0.1/ghc-7.8.4\",\"-L/usr/lib64/data-default-instances-containers-0.0.1/ghc-7.8.4\",\"-L/usr/lib64/data-default-instances-base-0.0.1/ghc-7.8.4\",\"-L/usr/lib64/conduit-extra-1.1.9.1/ghc-7.8.4\",\"-L/usr/lib64/http-conduit-2.1.7.1/ghc-7.8.4\",\"-L/usr/lib64/http-client-tls-0.2.2/ghc-7.8.4\",\"-L/usr/lib64/connection-0.2.4/ghc-7.8.4\",\"-L/usr/lib64/x509-system-1.5.0/ghc-7.8.4\",\"-L/usr/lib64/tls-1.2.18/ghc-7.8.4\",\"-L/usr/lib64/x509-validation-1.5.2/ghc-7.8.4\",\"-L/usr/lib64/x509-store-1.5.0/ghc-7.8.4\",\"-L/usr/lib64/x509-1.5.1/ghc-7.8.4\",\"-L/usr/lib64/pem-0.2.2/ghc-7.8.4\",\"-L/usr/lib64/crypto-pubkey-0.2.8/ghc-7.8.4\",\"-L/usr/lib64/cryptohash-0.11.6/ghc-7.8.4\",\"-L/usr/lib64/crypto-pubkey-types-0.4.3/ghc-7.8.4\",\"-L/usr/lib64/crypto-numbers-0.2.7/ghc-7.8.4\",\"-L/usr/lib64/cipher-rc4-0.1.4/ghc-7.8.4\",\"-L/usr/lib64/cipher-des-0.0.6/ghc-7.8.4\",\"-L/usr/lib64/cipher-aes-0.2.11/ghc-7.8.4\",\"-L/usr/lib64/crypto-cipher-types-0.0.9/ghc-7.8.4\",\"-L/usr/lib64/socks-0.5.4/ghc-7.8.4\",\"-L/usr/lib64/cereal-0.4.1.1/ghc-7.8.4\",\"-L/usr/lib64/crypto-random-0.0.9/ghc-7.8.4\",\"-L/usr/lib64/securemem-0.1.9/ghc-7.8.4\",\"-L/usr/lib64/memory-0.7/ghc-7.8.4\",\"-L/usr/lib64/byteable-0.1.1/ghc-7.8.4\",\"-L/usr/lib64/http-client-0.4.18.1/ghc-7.8.4\",\"-L/usr/lib64/streaming-commons-0.1.12.1/ghc-7.8.4\",\"-L/usr/lib64/zlib-0.5.4.2/ghc-7.8.4\",\"-L/usr/lib64/network-uri-2.6.0.3/ghc-7.8.4\",\"-L/usr/lib64/mime-types-0.1.0.6/ghc-7.8.4\",\"-L/usr/lib64/http-types-0.8.6/ghc-7.8.4\",\"-L/usr/lib64/cookie-0.4.1.6/ghc-7.8.4\",\"-L/usr/lib64/data-default-class-0.0.1/ghc-7.8.4\",\"-L/usr/lib64/base64-bytestring-1.0.0.1/ghc-7.8.4\",\"-L/usr/lib64/conduit-1.2.5/ghc-7.8.4\",\"-L/usr/lib64/void-0.7/ghc-7.8.4\",\"-L/usr/lib64/semigroups-0.16.2.2/ghc-7.8.4\",\"-L/usr/lib64/nats-1/ghc-7.8.4\",\"-L/usr/lib64/resourcet-1.1.5/ghc-7.8.4\",\"-L/usr/lib64/mmorph-1.0.4/ghc-7.8.4\",\"-L/usr/lib64/lifted-base-0.2.3.6/ghc-7.8.4\",\"-L/usr/lib64/monad-control-1.0.0.4/ghc-7.8.4\",\"-L/usr/lib64/transformers-base-0.4.4/ghc-7.8.4\",\"-L/usr/lib64/exceptions-0.8.0.2/ghc-7.8.4\",\"-L/usr/lib64/transformers-compat-0.4.0.4/ghc-7.8.4\",\"-L/usr/lib64/case-insensitive-1.2.0.4/ghc-7.8.4\",\"-L/usr/lib64/blaze-builder-0.4.0.1/ghc-7.8.4\",\"-L/usr/lib64/async-2.0.2/ghc-7.8.4\",\"-L/usr/lib64/asn1-parse-0.9.1/ghc-7.8.4\",\"-L/usr/lib64/asn1-encoding-0.9.0/ghc-7.8.4\",\"-L/usr/lib64/asn1-types-0.3.0/ghc-7.8.4\",\"-L/usr/lib64/hourglass-0.2.9/ghc-7.8.4\",\"-L/usr/lib64/appar-0.1.4/ghc-7.8.4\",\"-L/usr/lib64/ansi-wl-pprint-0.6.7.2/ghc-7.8.4\",\"-L/usr/lib64/ansi-terminal-0.6.2.1/ghc-7.8.4\",\"-L/usr/lib64/aeson-0.9.0.1/ghc-7.8.4\",\"-L/usr/lib64/vector-0.10.12.3/ghc-7.8.4\",\"-L/usr/lib64/unordered-containers-0.2.5.1/ghc-7.8.4\",\"-L/usr/lib64/syb-0.4.4/ghc-7.8.4\",\"-L/usr/lib64/dlist-0.7.1.1/ghc-7.8.4\",\"-L/usr/lib64/attoparsec-0.13.0.1/ghc-7.8.4\",\"-L/usr/lib64/scientific-0.3.3.8/ghc-7.8.4\",\"-L/usr/lib64/hashable-1.2.3.3/ghc-7.8.4\",\"-L/usr/lib64/statevar-1.1.0.0/ghc-7.8.4\",\"-L/usr/lib64/safesemaphore-0.10.1/ghc-7.8.4\",\"-L/usr/lib64/stm-2.4.4/ghc-7.8.4\",\"-L/usr/lib64/quickcheck-2.8.1/ghc-7.8.4\",\"-L/usr/lib64/tf-random-0.5/ghc-7.8.4\",\"-L/usr/lib64/primitive-0.5.4.0/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/template-haskell-2.9.0.0\",\"-L/usr/lib64/ghc-7.8.4/pretty-1.1.1.1\",\"-L/usr/lib64/missingh-1.3.0.1/ghc-7.8.4\",\"-L/usr/lib64/regex-compat-0.95.1/ghc-7.8.4\",\"-L/usr/lib64/regex-posix-0.95.2/ghc-7.8.4\",\"-L/usr/lib64/regex-base-0.93.2/ghc-7.8.4\",\"-L/usr/lib64/random-1.1/ghc-7.8.4\",\"-L/usr/lib64/parsec-3.1.9/ghc-7.8.4\",\"-L/usr/lib64/text-1.2.1.1/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/binary-0.7.4.0\",\"-L/usr/lib64/ghc-7.8.4/old-time-1.1.0.2\",\"-L/usr/lib64/hslogger-1.2.9/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/process-1.2.0.0\",\"-L/usr/lib64/network-2.6.2.1/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/directory-1.2.1.0\",\"-L/usr/lib64/ghc-7.8.4/unix-2.7.0.1\",\"-L/usr/lib64/ghc-7.8.4/bytestring-0.10.4.0\",\"-L/usr/lib64/ghc-7.8.4/time-1.4.2\",\"-L/usr/lib64/ghc-7.8.4/old-locale-1.0.0.6\",\"-L/usr/lib64/ghc-7.8.4/filepath-1.3.0.2\",\"-L/usr/lib64/ghc-7.8.4/containers-0.5.5.1\",\"-L/usr/lib64/ifelse-0.85/ghc-7.8.4\",\"-L/usr/lib64/mtl-2.2.1/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/transformers-0.4.3.0\",\"-L/usr/lib64/hunit-1.2.5.2/ghc-7.8.4\",\"-L/usr/lib64/ghc-7.8.4/deepseq-1.3.0.2\",\"-L/usr/lib64/ghc-7.8.4/array-0.5.0.0\",\"-L/usr/lib64/ghc-7.8.4/base-4.7.0.2\",\"-L/usr/lib64/ghc-7.8.4/integer-gmp-0.5.1.0\",\"-L/usr/lib64/ghc-7.8.4/ghc-prim-0.3.1.0\",\"-L/usr/lib64/ghc-7.8.4/rts-1.0\"]) -runhaskell Setup.hs configure --prefix=/usr --verbose=3 220,76s user 51,62s system 46% cpu 9:44,37 total - -configure needs way over 10GB of RAM so something seems to be broken here. -"""]] diff --git a/doc/bugs/OOM_while_configuring_git-annex/comment_4_66f6cfc973e8d67eb468be1246c82616._comment b/doc/bugs/OOM_while_configuring_git-annex/comment_4_66f6cfc973e8d67eb468be1246c82616._comment deleted file mode 100644 index 030bcef47..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex/comment_4_66f6cfc973e8d67eb468be1246c82616._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-07-30T17:04:06Z" - content=""" -It probably depends on the version of the cabal library you have installed. -Older versions may not print much debugging, and also seem much more likely -to run out of memory while resolving dependencies. - -As I mentioned, using stackage is a good way to present cabal with a canned -solution so it doesn't fry its mind trying to discover one. -"""]] diff --git a/doc/bugs/OOM_while_configuring_git-annex/comment_5_49cfdd1b3a2bf2bc61f1cba7fe7cc11c._comment b/doc/bugs/OOM_while_configuring_git-annex/comment_5_49cfdd1b3a2bf2bc61f1cba7fe7cc11c._comment deleted file mode 100644 index ad63dba60..000000000 --- a/doc/bugs/OOM_while_configuring_git-annex/comment_5_49cfdd1b3a2bf2bc61f1cba7fe7cc11c._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-08-19T16:50:51Z" - content=""" -I notice that you're using Setup configure. It turns out that for some -reason, Setup configure's dependency resolution fails to find available -solutions, where cabal configure will easly succeed without using much -memory. There's a bug filed about this now: -<https://github.com/haskell/cabal/issues/2777> - -So, use cabal configure, or downloading the cabal.config from stackage will -probably prevent this blowup by pinning all the package versions to -particular versions. - -I don't think this can be fixed in git-annex, really. So will close this as -forwarded to the above cabal bug. -"""]] diff --git a/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex.mdwn b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex.mdwn deleted file mode 100644 index 3860456d2..000000000 --- a/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex.mdwn +++ /dev/null @@ -1,54 +0,0 @@ -### Please describe the problem. - -(small) identical files fail to unannex, leaving broken symlinks, except for the first copy. - -### What steps will reproduce the problem? - -* Have multiple identical files. For example, run this, which creates four 6-byte files: - -> echo Hello>file1.txt && cp file1.txt file2.txt && cp file1.txt file3.txt && cp file1.txt file4.txt - -* Run this (git init needs credentials to have been specified though) - -> git init && git-annex init && git-annex add - -Now there are 4 symlinks, pointing to the same object: - -> lrwxrwxrwx 1 186 Aug 16 15:54 file1.txt -> .git/annex/objects/31/XV/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt - -* Optionally run "git commit -a". It doesn't affect the outcome. - -* Run git-annex unannex - -> $ git annex unannex -> unannex file1.txt ok -> (Recording state in git...) -> $ - -Now file1.txt is a normal 6-byte file again, but 2, 3, and 4 are broken symlinks: - - -rw-r----- 1 6 Aug 16 15:54 file1.txt - lrwxrwxrwx 1 186 Aug 16 15:54 file2.txt -> .git/annex/objects/31/XV/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt - lrwxrwxrwx 1 186 Aug 16 15:54 file3.txt -> .git/annex/objects/31/XV/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt - lrwxrwxrwx 1 186 Aug 16 15:54 file4.txt -> .git/annex/objects/31/XV/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt/SHA256E-s6--66a045b452102c59d840ec097d59d9467e13a3f34f6494e539ffd32c1bb35f18.txt - - $ git-annex fsck - fsck file2.txt - ** No known copies exist of file2.txt - failed - fsck file3.txt - ** No known copies exist of file3.txt - failed - fsck file4.txt - ** No known copies exist of file4.txt - failed - git-annex: fsck: 3 failed - - -### What version of git-annex are you using? On what operating system? - -git-annex 4.20130802 package - -on Debian GNU/Linux jessie/sid (testing), amd64. - -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_2_f7149b684a97070cff051b780c73be48._comment b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_2_f7149b684a97070cff051b780c73be48._comment deleted file mode 100644 index ca3ad1229..000000000 --- a/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_2_f7149b684a97070cff051b780c73be48._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://openid.yandex.ru/deletesoftware/" - nickname="deletesoftware" - subject="duplicate" - date="2013-08-16T14:52:23Z" - content=""" -It's the same as these: - -* [Large unannex operations result in stale symlinks and data loss](http://git-annex.branchable.com/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/) -* [unannex removes object even if referred to by others](http://git-annex.branchable.com/bugs/unannex_removes_object_even_if_referred_to_by_others/) -* [annex unannex/uninit should handle copies](http://git-annex.branchable.com/bugs/annex_unannex__47__uninit_should_handle_copies/) - -and (as gernot mentioned) according to those, has a workaround of \"git annex unannex --fast\". Of course, it's not convenient to need to find a workaround, and to notice a potential dataloss issue… - -"""]] diff --git a/doc/bugs/Old_repository_stuck.mdwn b/doc/bugs/Old_repository_stuck.mdwn deleted file mode 100644 index 73903763d..000000000 --- a/doc/bugs/Old_repository_stuck.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -I had created a test repository a time ago with an old version of git-annex. I didn't really used it so I simply deleted the directory by hand. Now I've installed a new version of git-annex and the old repository stills appears on the webapp, but there is no interface to delete it. - -* Old git-annex version: don't remember -* New git-annex version: I downloaded 3.20130107 (twice to be sure), but for some reason 'git-annex version' reports 3.20130102 -* OS: Ubuntu 12.04.1 LTS 3.2.0-35-generic-pae #55-Ubuntu SMP Wed Dec 5 18:04:39 UTC 2012 i686 i686 i386 GNU/Linux - -> This is [[fixed|done]] in git; assuming the repo was showing up -> in the upper-right menu for switching among local repositories. -> --[[Joey]] diff --git a/doc/bugs/On_Windows__44___annex_get_over_HTTP_sends_URLs_with_incorrect_separator.mdwn b/doc/bugs/On_Windows__44___annex_get_over_HTTP_sends_URLs_with_incorrect_separator.mdwn deleted file mode 100644 index 08bc76ed1..000000000 --- a/doc/bugs/On_Windows__44___annex_get_over_HTTP_sends_URLs_with_incorrect_separator.mdwn +++ /dev/null @@ -1,186 +0,0 @@ -### Please describe the problem. -On Windows, attempting to annex get from a remote over HTTP fails. URLs which are nearly correct, but have incorrect slashes, are sent. - -### What steps will reproduce the problem? -1. Create an annex on Linux. -2. Configure repository for HTTP access -3. Clone annex on Windows. -4. "git annex get ." -5. git annex makes requests for urls like the following: http://host/repo/.git/annex/objects\<3-char-hash>\<3-char-hash>\SHA<file hash> - -### What version of git-annex are you using? On what operating system? -Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page) - -Debian Linux: 3.20120629 (from the package manager) - -### Please provide any additional information below. -placing a wrapper script in front of wget which replaces '\' with '/' works around the issue, and allows git annex get to complete. - - -###Full Transcript - -#### 1. setup of linux repo -[[!format sh """ -test-git-annex@linux_host:~/test_annex$ git version -git version 1.7.10.4 -test-git-annex@linux_host:~/test_annex$ git annex version -git-annex version: 3.20120629 -local repository version: 3 -default repository version: 3 -supported repository versions: 3 -upgrade supported from repository versions: 0 1 2 -test-git-annex@linux_host: ~test-git-annex@linux_host:~$ mkdir test_annex -test-git-annex@linux_host: ~test-git-annex@linux_host:~$ cd test_annex/ -test-git-annex@linux_host:~/test_annex$ git init . -Initialized empty Git repository in /home/test-git-annex/test_annex/.git/ -test-git-annex@linux_host:~/test_annex$ annex init laptop -init laptop ok -(Recording state in git...) -~/test_annextest-git-annex@linux_host:~/test_annex$ echo "this is some content" > file1.txt -test-git-annex@linux_host:~/test_annex$ git annex add file1.txt -add file1.txt (checksum...) ok -(Recording state in git...) -test-git-annex@linux_host:~/test_annex$ git commit -a -m "initial commit" -[master (root-commit) 821c6c1] initial commit - 1 file changed, 1 insertion(+) - create mode 120000 file1.txt -test-git-annex@linux_host:~/test_annex$ ls -l -total 4 -lrwxrwxrwx 1 test-git-annex test-git-annex 178 Jul 6 11:33 file1.txt -> .git/annex/objects/J9/m6/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 -test-git-annex@linux_host:~/test_annex$ cat file1.txt -this is some content -"""]] - -#### 2. set up and run http server -[[!format sh """ -test-git-annex@MrLinuxTablet:~/test_annex$ git update-server-info -cd .. -test-git-annex@MrLinuxTablet:~$ python -m SimpleHTTPServer -Serving HTTP on 0.0.0.0 port 8000 ... - -"""]] - -#### 3. Set up Windows, clone repo, init annex - -[[!format sh """ - -#Windows 7 -#download and install git from git-scm.com/download/win -#Git-1.8.3-preview20130601.exe -#on install, selecting "Run Git from the Windows Command Prompt" -#on install, selecting "checkout as-is, commit as-is" -#installs to C:\Program Files (x86)\Git -#download and install git-annex from http://git-annex.branchable.com/install/ -#git-annex-installer.exe -#need to right-click 'run as administrator', per reported bug (link here) -#installs to C:\Program Files (x86)\Git\cmd -#also installs some utilities, including wget.exe - -C:\Users\test-git-annex>git clone http://192.168.0.8:8000/test_annex/.git -Cloning into 'test_annex'... - -C:\Users\test-git-annex>cd test_annex - -C:\Users\test-git-annex\test_annex>dir - Volume in drive C has no label. - - Directory of C:\Users\test-git-annex\test_annex - -<DIR> . -<DIR> .. - 178 file1.txt - 1 File(s) 178 bytes - -C:\Users\test-git-annex\test_annex>type file1.txt -.git/annex/objects/J9/m6/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 - -C:\Users\test-git-annex\test_annex>git annex init windows -init windows - Detected a crippled filesystem. - - Enabling direct mode. - - Detected a filesystem without fifo support. - - Disabling ssh connection caching. -ok -(Recording state in git...) - -"""]] - -####4. annex get - -[[!format sh """ -#create empty file named 'wget' in Git\cmd, and install cygwin, add to path, to provide necessary DLLs -C:\Users\test-git-annex\test_annex> git annex get file.txt - -C:\Users\test-git-annex\test_annex>git annex -vd get file1.txt -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","ls-files","--cached","-z","--","file1.txt"] -get file1.txt [<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","show-ref","git-annex"] -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","show-ref","--hash","refs/heads/git-annex"] -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","refs/heads/git-annex..98d1182bcee688b06307963dfea81aa70a3c8336","--oneline","-n1"] -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","refs/heads/git-annex..304263841906c0b4dda39d0fdbe54e4af4307cb8","--oneline","-n1"] -(merging origin/git-annex into git-annex...) -[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","cat-file","--batch"] -[<datetime>] feed: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-index","-z","--index-info"] -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","304263841906c0b4dda39d0fdbe54e4af4307cb8"] -[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","hash-object","-t","blob","-w","--stdin","--no-filters"] -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","log","304263841906c0b4dda39d0fdbe54e4af4307cb8..refs/heads/git-annex","--oneline","-n1"] -(Recording state in git...) -[<datetime>] read: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","write-tree"] -[<datetime>] chat: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","commit-tree","838284a4dbc1c57bea2595ac7636c32a7a86b745","-p","refs/heads/git-annex","-p","304263841906c0b4dda39d0fdbe54e4af4307cb8"] -[<datetime>] call: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","update-ref","refs/heads/git-annex","c594efcf08bd4de8963cc3fb6890275f623aee12"] -[<datetime>] call: wget ["-q","-c","-O","C:\\Users\\test-git-annex\\AppData\\Local\\Temp\\git-annex4860.tmp","http://192.168.0.8:8000/test_annex/.git/config"] -cygwin warning: - MS-DOS style path detected: C:\Users\test-git-annex\AppData\Local\Temp\git-annex4860.tmp - Preferred POSIX equivalent is: /cygdrive/c/Users/test-git-annex/AppData/Local/Temp/git-annex4860.tmp - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames -[<datetime>] read: git ["config","--null","--list","--file","C:\\Users\\test-git-annex\\AppData\\Local\\Temp\\git-annex4860.tmp"] -[<datetime>] call: git ["--git-dir=C:\\Users\\test-git-annex\\test_annex\\.git","--work-tree=C:\\Users\\test-git-annex\\test_annex","config","remote.origin.annex-uuid","64000156-e66a-11e2-aa76-131bb0a453f3"] -[<datetime>] read: git ["config","--null","--list"] -(from origin...) [<datetime>] call: wget ["-c","-O","C:\\Users\\test-git-annex\\test_annex\\.git\\annex\\tmp\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729","http://192.168.0.8:8000/test_annex/.git/annex\\objects\\c96\\53e\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729"] -cygwin warning: - MS-DOS style path detected: C:\Users\test-git-annex\test_annex\.git\annex\tmp\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 - Preferred POSIX equivalent is: /cygdrive/c/Users/test-git-annex/test_annex/.git/annex/tmp/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames ---<datetime>--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 -Connecting to 192.168.0.8:8000... connected. -HTTP request sent, awaiting response... 404 File not found -<datetime> ERROR 404: File not found. - -[<datetime>] call: wget ["-c","-O","C:\\Users\\test-git-annex\\test_annex\\.git\\annex\\tmp\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729","http://192.168.0.8:8000/test_annex/.git/annex\\objects\\J9\\m6\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729\\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729"] -cygwin warning: - MS-DOS style path detected: C:\Users\test-git-annex\test_annex\.git\annex\tmp\SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 - Preferred POSIX equivalent is: /cygdrive/c/Users/test-git-annex/test_annex/.git/annex/tmp/SHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames ---<datetime>--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 -Connecting to 192.168.0.8:8000... connected. -HTTP request sent, awaiting response... 404 File not found -<datetime> ERROR 404: File not found. - - - Unable to access these remotes: origin - - Try making some of these repositories available: - 64000156-e66a-11e2-aa76-131bb0a453f3 -- origin (laptop) -failed -git-annex: get: 1 failed - -"""]] - -#### http server output from above - -[[!format sh """ -192.168.0.2 - - [<datetime>] code 404, message File not found -192.168.0.2 - - [<datetime>] "GET /test_annex/.git/annex%5Cobjects%5Cc96%5C53e%5CSHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729%5CSHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 HTTP/1.1" 404 - -192.168.0.2 - - [<datetime>] code 404, message File not found -192.168.0.2 - - [<datetime>] "GET /test_annex/.git/annex%5Cobjects%5CJ9%5Cm6%5CSHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729%5CSHA256-s21--6ed275e9e01c84a57fdd99d6af793c5d587d02e699cd2c28b32b7dc90f73e729 HTTP/1.1" 404 - -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/On_Windows_the_Comitted_Symlinks_are_not_Relative.mdwn b/doc/bugs/On_Windows_the_Comitted_Symlinks_are_not_Relative.mdwn deleted file mode 100644 index 3ea44f857..000000000 --- a/doc/bugs/On_Windows_the_Comitted_Symlinks_are_not_Relative.mdwn +++ /dev/null @@ -1,102 +0,0 @@ -### Please describe the problem. -On Windows 7, the committed symlink files are always relative to the repo's .git root; they are not prefixed with the correct number of ../ for the given level of directing nesting. - -Trying to correct this with `git annex fix` returns "You cannot run this command in a direct mode repository." - -I believe that this is also the source of a pathological case I'm seeing on Windows. After adding a lot of content, commands like `git annex sync` and `git annex status` appear to re-checksum the entire annex. After syncing the repo to a Linux machine, fixing the symlinks there, and syncing back, these commands become snappy again. - -### What steps will reproduce the problem? - -[[!format sh """ -git init -git annex init -mkdir -p one/two/three/four/five/six - -# drop files into the dir structure -git annex add . -git annex sync -git log -p -"""]] - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140203-g83e6fb7 - -on Windows 7 Pro - -### Please provide any additional information below. - -The output of `git log -p` for me: - - commit f4d88b6bc99cc94a0b0154da41d06bad3f23cc1e - Author: Justin Geibel <...> - Date: Tue Feb 4 20:56:32 2014 -0500 - - git-annex automatic sync - - diff --git a/git-annex-installer.exe b/git-annex-installer.exe - new file mode 120000 - index 0000000..64f7d83 - --- /dev/null - +++ b/git-annex-installer.exe - @@ -0,0 +1 @@ - +.git/annex/objects/GW/Wk/SHA256E-s14413167--ea3a1e4c09ad12fdb2993a157b77b246a058f7f0ca2cd174d8cc675d1495ec4d.exe/SHA256E-s14413167--ea3a1e4c09ad12fdb2993a157b77b246a058f7f0ca2cd174d8cc675d1495ec4d.exe - \ No newline at end of file - diff --git a/one/git-annex-installer(1).exe b/one/git-annex-installer(1).exe - new file mode 120000 - index 0000000..5b37a29 - --- /dev/null - +++ b/one/git-annex-installer(1).exe - @@ -0,0 +1 @@ - +.git/annex/objects/6k/8K/SHA256E-s19286321--add3e1ac7ceabce7aa1ed1907895ae527fc095610d1e21127e99814728b24f11.exe/SHA256E-s19286321--add3e1ac7ceabce7aa1ed1907895ae527fc095610d1e21127e99814728b24f11.exe - \ No newline at end of file - diff --git a/one/two/git-annex-installer(2).exe b/one/two/git-annex-installer(2).exe - new file mode 120000 - index 0000000..f89508f - --- /dev/null - +++ b/one/two/git-annex-installer(2).exe - @@ -0,0 +1 @@ - +.git/annex/objects/Zm/6K/SHA256E-s19573485--4f2a22c5b96308cf694c85564940d3cba22b5e8b3b714b242116c91369be75ee.exe/SHA256E-s19573485--4f2a22c5b96308cf694c85564940d3cba22b5e8b3b714b242116c91369be75ee.exe - \ No newline at end of file - diff --git a/one/two/three/four/five/git-annex-installer(5).exe b/one/two/three/four/five/git-annex-installer(5).exe - new file mode 120000 - index 0000000..34565f9 - --- /dev/null - +++ b/one/two/three/four/five/git-annex-installer(5).exe - @@ -0,0 +1 @@ - +.git/annex/objects/p3/Xq/SHA256E-s19956630--ec421bfc6cb0b4df2b5195d9229cbcc27a2e5505e0b879bf07e1be38dcc64a42.exe/SHA256E-s19956630--ec421bfc6cb0b4df2b5195d9229cbcc27a2e5505e0b879bf07e1be38dcc64a42.exe - \ No newline at end of file - diff --git a/one/two/three/four/five/six/git-annex-installer(6).exe b/one/two/three/four/five/six/git-annex-installer(6).exe - new file mode 120000 - index 0000000..d6f97d9 - --- /dev/null - +++ b/one/two/three/four/five/six/git-annex-installer(6).exe - @@ -0,0 +1 @@ - +.git/annex/objects/9G/5g/SHA256E-s19967171--c9e33dff779a43e76089ec3bee3411299d5b8abfa67ae1b459cee5a812c5194d.exe/SHA256E-s19967171--c9e33dff779a43e76089ec3bee3411299d5b8abfa67ae1b459cee5a812c5194d.exe - \ No newline at end of file - diff --git a/one/two/three/four/git-annex-installer(4).exe b/one/two/three/four/git-annex-installer(4).exe - new file mode 120000 - index 0000000..a4f791c - --- /dev/null - +++ b/one/two/three/four/git-annex-installer(4).exe - @@ -0,0 +1 @@ - +.git/annex/objects/8J/pM/SHA256E-s19959961--7e4521036f891bba97f4c04527946e26ef43b14576d874c666e73dee405c18cf.exe/SHA256E-s19959961--7e4521036f891bba97f4c04527946e26ef43b14576d874c666e73dee405c18cf.exe - \ No newline at end of file - diff --git a/one/two/three/git-annex-installer(3).exe b/one/two/three/git-annex-installer(3).exe - new file mode 120000 - index 0000000..dda7284 - --- /dev/null - +++ b/one/two/three/git-annex-installer(3).exe - @@ -0,0 +1 @@ - +.git/annex/objects/5X/qQ/SHA256E-s19915186--c6dc288ec8a77404c0ebc22cbe9b4ec911103fd022c3ca74eec582604dff80a7.exe/SHA256E-s19915186--c6dc288ec8a77404c0ebc22cbe9b4ec911103fd022c3ca74eec582604dff80a7.exe - \ No newline at end of file - -> [[fixed|done]] -- I didn't notice this before because it happened to do -> the right thing if you cd'd into the subdir before adding the file there. -> -> WRT the slow down issue, I don't see how it could matter to git-annex on -> Windows whether the symlinks point to the right place. It only looks at -> the basename of the symlink target to get the key. If you have a -> repository that behaves poorly, you can probably use --debug to see if -> git-annex is calling some expensive series of git commands somehow. -> --[[Joey]] diff --git a/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android.mdwn b/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android.mdwn deleted file mode 100644 index 8d1d3e8ec..000000000 --- a/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. -On the first run it seems "Open Webapp" always use the URL used to configure a new repo. - -### What steps will reproduce the problem? -I'm using a /sdcard/DCIM annex. - -1. close the tabs in the git annex terminal to close git annex -2. force close the application in the settings and delete data (not sure if it's needed) -3. delete /sdcard/DCIM/.git/ and /sdcard/git-annex.home/ (I'm not sure I'm deleting everything, maybe I missed some dirs) -4. start git annex - -(WebApp opens and ask to create a repo) see: [http://i.imgur.com/v0EUuir.png](http://i.imgur.com/v0EUuir.png) - -5. Click "Make Camera Repository" - -(WebApp scans and commits the files) see: [http://i.imgur.com/97rYfXa.png](http://i.imgur.com/97rYfXa.png) (note that the port changed) - -6. Return to the terminal. see: [http://i.imgur.com/edL5and.png](http://i.imgur.com/edL5and.png) -7. Open WebApp using the menu - -(Git annex opens the URL to configure a new repo (the webapp is still accessible with the other url). see: [http://i.imgur.com/T8A5NTD.png](http://i.imgur.com/T8A5NTD.png) - -If I close and reopen the terminal, the good url is used when I use "open webapp" - -### What version of git-annex are you using? On what operating system? -4.20130601-g7483ca4 - -### Please provide any additional information below. - -[[!format sh """ -[2013-06-01 17:13:34 EDT] main: starting assistant version 4.20130601-g7483ca4 -(scanning...) [2013-06-01 17:13:34 EDT] Watcher: Performing startup scan -(started...) [2013-06-01 17:13:42 EDT] Committer: Adding 123 files - -add Camera/IMG_20130223_111411.jpg (checksum...) ok -[...] -[2013-06-01 17:14:17 EDT] Committer: Committing changes to git -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android/comment_1_9f10bf273b15e93f1eea029f091f26cb._comment b/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android/comment_1_9f10bf273b15e93f1eea029f091f26cb._comment deleted file mode 100644 index 9ed036f84..000000000 --- a/doc/bugs/Open_webapp_ask_to_create_new_repo___40__on_first_start__41___even_if_repo_exists_on_Android/comment_1_9f10bf273b15e93f1eea029f091f26cb._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-06-01T23:39:39Z" - content=""" -Ah yes, I see what's going on. It's not updating the url in the special file added for Android. - -Should be an easy fix one I return from vacation. - -Workaround: Open a new terminal tab and it will open the web browser viewing the repo you set up. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds.mdwn b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds.mdwn deleted file mode 100644 index c127bac15..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds.mdwn +++ /dev/null @@ -1,84 +0,0 @@ -Before I start on what's gone wrong, many thanks for a great program: finally a way of finding out where I've put all those files, and I enjoyed your talk in Australia. Not quite to New Zealand, but a good start :-) - -To play with git-annex, I decided to convert my ~/Downloads directory to a git-annex repository, as there were a wide variety of files in it, mostly easily replaceable, and also handy to have on multiple machines. In hindsight, probably wasn't a great idea, as I'd regularly forget it was a git-annex repo and move files and directories out manually, which caused all sorts of fun trying to sort out the dead symlinks. Then I after one update, the repository format changed, from WORM to xxx256 format which meant there were now both sorts in the GA object store. - -More recently I'd tried converting the repo to direct mode, you get the idea: lots of playing with git-annex commands, and now that I think about it, possibly some git commands too trying to repair missing files. - -Anyway I've ended up with a 27GB git-annex repo that now manages to kill git-annex whenever I try to check it using "git-annex fsck". - -Not only does the fsck subcommand cause it to die, but also "find", "whereis" and "status". It dies on the same file (for find/whereis/fsck). - -e.g. - - ... lots of stuff deleted ... - whereis 1wolf14.zip (2 copies) - 051f0b00-e265-11e1-894e-3b0b3f3844f2 -- Laptop - 2c4e11e0-a1b4-11e1-9a02-73e17b04c00f -- here (myPC - Downloads) - ok - git-annex: out of memory (requested 2097152 bytes) - -Now "git status" for some repo data: - - myPC:~/Downloads$ git annex status - supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - supported remote types: git S3 bup directory rsync web webdav glacier hook - repository mode: direct - trusted repositories: 0 - semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - 051f0b00-e265-11e1-894e-3b0b3f3844f2 -- Laptop - 2c4e11e0-a1b4-11e1-9a02-73e17b04c00f -- here (myPC - Downloads) - 48fbe52a-a1b3-11e1-bb80-ebc15118871d -- netbk - untrusted repositories: 0 - dead repositories: 0 - transfers in progress: none - available local disk space: 100 gigabytes (+1 megabyte reserved) - local annex keys: 1719 - local annex size: 27 gigabytes - known annex keys: git-annex: out of memory (requested 2097152 bytes) - -It always seems to die at about 3.5GB memory usage. This is running on Ubuntu 12.04, using the latest GA release built using cabal: - - git-annex version: 4.20130227 - local repository version: 3 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - -There are also dead symlinks that point to directories that have meta-data but not the symlink target (manually line-wrapped): - - myPC:~/Downloads$ ls -l precise* - lrwxrwxrwx 1 nino nino 194 Oct 21 12:48 precise-dvd-i386.iso -> - .git/annex/objects/0x/Xz/SHA256-s3590631424-- - b08ecdd4846948ec076b23afae7f87be9cfba5218fb9ba4160f26c0b8d4b5dd0/ - SHA256-s3590631424--b08ecdd4846948ec076b23afae7f87be9cfba5218fb9ba4160f26c0b8d4b5dd0 - -But looking in the symlink destination directory, there's no corresponding object, only metadata: - - myPC:~/Downloads/.git/annex/objects/0x/Xz/SHA256-s3590631424--b08ecdd4846948ec076b23afae7f87be9cfba5218fb9ba4160f26c0b8d4b5dd0$ ls -l - total 8 - -rw-rw-r-- 1 nino nino 30 Jan 8 23:15 SHA256-s3590631424--b08ecdd4846948ec076b23afae7f87be9cfba5218fb9ba4160f26c0b8d4b5dd0.cache - -rw-rw-r-- 1 nino nino 49 Jan 8 23:15 SHA256-s3590631424--b08ecdd4846948ec076b23afae7f87be9cfba5218fb9ba4160f26c0b8d4b5dd0.map - -But there is another version somewhere else. - - -r--r--r-- 1 nino nino 3590631424 Mar 18 2012 ./.git/annex/objects/Kj/wM/WORM-s3590631424-m1331991509 - --precise-dvd-i386.iso/WORM-s3590631424-m1331991509--precise-dvd-i386.iso - -This actual file does exist in the "Used" directory: - - -rw-r--r-- 1 nino nino 3.4G May 27 2012 precise-dvd-i386.iso - -I'm not so worried about the mangled repo - it's quite possibly because of clueless git/git-annex command usage - but the inability to use the fsck command is concerning - -I could just uninit everything, but as it dies prematurely, I'm not certain that all the contents would be restored. -Any thoughts on how I can get git-annex (esp. fsck) to complete would be appreciated. - -Thanks -Giovanni - -> [[fixed|done]]. However, if you saw this behavior, -> you have large files checked directly into git. You may -> want to examine your repository and use git filter-branch to clean -> it up. -> --[[Joey]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_1_3aef6ca929fad198f2dda0868f2d49cb._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_1_3aef6ca929fad198f2dda0868f2d49cb._comment deleted file mode 100644 index d410f960b..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_1_3aef6ca929fad198f2dda0868f2d49cb._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-03-03T18:34:41Z" - content=""" -git-annex is designed to run in constant memory. It should never use a lot of memory. - -What file causes the problem? You show git-annex whereis successfully processing 1wolf14.zip, so that file is apparently not the problem. It's probably the *next* file you told whereis to run on. You can get a file list with `git ls-files` - -Apparently something bad is happening when it tries to calculate the key used by the problem file. - -What does the file look like? You're using direct mode so it may or may not be a symlink. If it's a symlink, show it. If not, show the output of: `echo HEAD:./$filename | git cat-file --batch` - ----- - -The stuff about \"dead symlinks\" etc is all a distraction AFAICS. git-annex allows you to remove content from your repository in multiple ways. That content could be present in another repository (git annex whereis would tell you), or the last copy of it could have been deleted. You can run \"git annex log\" on a file to show where the content was located historically. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment deleted file mode 100644 index 937e9cf8e..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_2_f2c1aa84a0d04e840cb34ae15eb1cb03._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 2" - date="2013-03-18T23:25:24Z" - content=""" -This is an important bug. Could you please get back to me so I can debug it? -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_3_480c39648e3ca6fc58c30377bdb25a8c._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_3_480c39648e3ca6fc58c30377bdb25a8c._comment deleted file mode 100644 index 3e851faa4..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_3_480c39648e3ca6fc58c30377bdb25a8c._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="Xyem" - ip="87.194.19.134" - subject="comment 3" - date="2013-03-22T11:18:53Z" - content=""" -I may have a bug along the same lines of this but I think it is in git, rather than git-annex. - -I've been using git-annex to sort and consolidate ~2TB files that have been spread across several machines. I probably failed to do an important step (such as committing to git, I'm not sure) while moving a lot of these files around which renders me unable to use the repository. - -For example, if I run any command that uses something like 'git status' in the background, it gradually consumes all available memory. I've not had an OOM error yet (8GB RAM, 2GB swap) but it also never seems to complete. - -I just did a quick test on this and running 'git status' in the annex results in, after a few minutes, a growing number of 'git status --porcelain' processes (quickly reaches 70+, currently at 94) and nearly all memory consumed. This would normally be triggered with 'git annex sync' or some other command which uses 'git status' to do some work. - -Hope this information is of some use. If I can help further, please let me know. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment deleted file mode 100644 index 272d2a759..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_4_b31496b37046a9886f632ba4f11c56e3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 4" - date="2013-03-27T16:38:07Z" - content=""" -@Xyem, sounds like an unrelated bug. Also, no git-annex commands run `git status`. You can find other git commands that may be using a lot of memory by passing the --debug flag to git-annex. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment deleted file mode 100644 index 958eb7733..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_5_d25ff424dda1f6021c1ba20f79d71ffc._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="Xyem" - ip="87.194.19.134" - subject="comment 5" - date="2013-03-27T16:50:58Z" - content=""" -@joey: Hm.. I'm sure it was 'git annex sync' that initially consumed all RAM by spawning a lot of 'git status' processes. However, I can't replicate it anymore as I found a way to make the repository useable again. - -I went low into the directory structure and added/committed from there. Now I can 'git annex sync' and 'git status' from the annex root without any problems. - -Sorry for cluttering this bug report up, thought it might be related/of some help. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_6_9e3300b223dd54a3f07c650f5cf70ae0._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_6_9e3300b223dd54a3f07c650f5cf70ae0._comment deleted file mode 100644 index b648eb9a4..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_6_9e3300b223dd54a3f07c650f5cf70ae0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://churchkey.org/author/ian/" - ip="2001:470:8a52:67:a800:4ff:fe00:a04" - subject="Same problem, different user" - date="2013-09-18T22:20:09Z" - content=""" -@joey I appear to have run into this same problem through a similar series of repository operations. I began with the assistant, which caused some trouble while trying to set up on multiple machines, so I started using the git-annex commands directly, switched the client to direct mode, and at some point along the way I started getting the \"git-annex: out of memory (requested 1048576 bytes)\" error on my home client any time I try to run a find, whereis, status, or sync operation. On my work client I instead run into a \"fatal: write error: Invalid argument\" error. Both clients are in direct mode and both stop on the same files. I have tried to drop these files and the ones that follow them sequentially to try and clear out the grit from the machine, but to no avail. I'm available for diagnostics to help resolve this. The files in question are not symlinks and running \"echo HEAD:./$filename | git cat-file --batch\" simply produces binary blobs the same size as the original files. Running \"git ls-tree -r git-annex | wc -l\" gives \"41262\" for the client with the \"Out of memory\" error and \"41260\" for the \"write error\" client. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_7_b91f4a87b6d29ae6b4262922fd65a79d._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_7_b91f4a87b6d29ae6b4262922fd65a79d._comment deleted file mode 100644 index c7832477c..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_7_b91f4a87b6d29ae6b4262922fd65a79d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.153.14.105" - subject="comment 7" - date="2013-09-19T19:07:03Z" - content=""" -[[Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status]] is a duplicate of this bug. -"""]] diff --git a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_8_cf1f9d0be5da4ba874209d981ff8afc6._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_8_cf1f9d0be5da4ba874209d981ff8afc6._comment deleted file mode 100644 index 976664a94..000000000 --- a/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_8_cf1f9d0be5da4ba874209d981ff8afc6._comment +++ /dev/null @@ -1,38 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlVUq_c3-lrQBculOEUu3yjvdavE7JbvEI" - nickname="Stig" - subject="comment 8" - date="2014-07-25T10:02:53Z" - content=""" -\"git annex sync\" or \"git annex fsck\" gives me the same problem. This is an annex which has previously been running with the git annex assistant. - -Output is first: - - $ git annex sync - (merging synced/git-annex into git-annex...) - -…then the workstation starts swapping, and after eating 16 GB RAM, and all of 16 GB swap, OOM killer komes for \"git\". - -The process which eats up all the memory is: - - git --git-dir=/home/ssm/annex/.git --work-tree=/home/ssm/annex \ - -c core.bare=false log \ - 7bed443dc22961214f86e65aedb8861affd215d3..refs/heads/git-annex \ - -n1 --pretty=%H - -I _think_ that since a \"-n1\" argument is given, it will only show the log for the last commit in the range, and one could specify \"refs/heads/git-annex\" instead of the range. With just \"refs/heads/git-annex\" instead of the range, it returns a reference instantly. - -The output of git count-objects is - - $ git count-objects -H -v - count: 334758 - size: 6.27 GiB - in-pack: 16600 - packs: 1 - size-pack: 1.70 MiB - prune-packable: 0 - garbage: 0 - size-garbage: 0 bytes - -…and there is 1043 files in the annex. -"""]] diff --git a/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android.mdwn b/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android.mdwn deleted file mode 100644 index a72b22b63..000000000 --- a/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -### Please describe the problem. - -I have a very simple use case for Git Annex on Android : I want my photos to be transferred to my home server automatically, in a special "incoming photos" folder, where they eventually get classified into other folders or deleted. git-annex in installed on this server. - -However, adding a Remote server (ssh) repository on a Photos repository on Android results in a totally confusing situation where the files on the Android device are removed and transferred to a bare repository on the server. Getting out of this sticky situation requires some commandline-fu. - -### What steps will reproduce the problem? - -1. Install git-annex on Android -2. Open git-annex from the apps menu -3. Accept offer to create a Photos repository -4. Add a "Remote server" server repository -5. Wait a bit. -6. "Uh oh." - -### What version of git-annex are you using? On what operating system? - -Using git-annex Android and Debian. - -### Please provide any additional information below. - -I thought that adding a remote server repository would result in two non-bare repositories, such as what the Local pairing mode achieves. However Local pairing is not available on Android. I assumed the remote server would function in the same manner, except that I entered the SSH connection information manually. - -> [[done]]; not a bug per comment --[[Joey]] diff --git a/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android/comment_1_75b71bf556e54bbf503bb32d54445224._comment b/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android/comment_1_75b71bf556e54bbf503bb32d54445224._comment deleted file mode 100644 index fcd4566de..000000000 --- a/doc/bugs/Photos___34__disappear__34___after_adding_a_remote_server_repository_on_Android/comment_1_75b71bf556e54bbf503bb32d54445224._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-10T17:15:51Z" - content=""" -I don't think this is a bug. By default, git-annex repos on android are -configured to be in the "source" [[group|standard_groups]]. This means -that, as soon as the files have reached some other repository, they're -removed from the Android device. Which saves space. - -If you don't want this behavior, click on Edit for the android repositry -in the webapp, and change to some other group, like "client". -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths.mdwn b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths.mdwn deleted file mode 100644 index 716c76f6c..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -This is a follow-up to [this -qbug](http://git-annex.branchable.com/bugs/WORM_keys_differ_depending_on_working_dir_during_add/). -Thank you for your fix there! However, if I understood correctly, you -indicated in your reply that the current fix completely removes the -relative path component from WORM keys. I gave some thought to this -and believe not having the relative path encoded inside WORM keys -makes key collisions (and accordingly data-loss) a very dire problem, -while they are not of practical concern if the relative path is -encoded. - -When relative paths are encoded within the key, a collision can only -occur when a file in the same directory is annexed twice within the -resolution of the mtime component inside the key (i.e., one second). -As such, unless one adds files automatically with a period of < 1s, -one can very much be certain that no collisions come up. - -Without relative paths, however, one could never be certain that -adding a file will not result in data-loss. - -Instead of just using the basename, WORM keys could be kept stable by -using the relative path and anchoring it to the root of the -repository. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_1_b37615636e685b60fab8ae1c4276d032._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_1_b37615636e685b60fab8ae1c4276d032._comment deleted file mode 100644 index 71164b0bd..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_1_b37615636e685b60fab8ae1c4276d032._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 1" - date="2014-08-15T17:32:15Z" - content=""" -I don't see much difference between (mtime, size, location) and (mtime, size) as far as entropy goes. Consider: A repository with all files in a single directory in the top level is going to have identical probabilities of collision either way. A less special case of a repository that typically has files added to it in a particular directory (\"inbox\", say), is again going to have identical probabilities of collision. - -If you're worried about such collisions, you should not be using WORM. I think that the documentation for it is pretty clear. - -If we really wanted to increase the entropy of worm, we could add a random number to the key, or perhaps the file's (original) inode number. -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment deleted file mode 100644 index 90684d96c..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_2_e8f011263bfa4c3c3d04494ea1c88523._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="78.48.163.229" - subject="comment 2" - date="2014-08-16T11:42:22Z" - content=""" -Hm, I don’t quite follow the remark on having everything in a single -directory. Rather than saying that the relative path adds additional -entropy, what I was aiming at is the file-system cannot have two -alternate versions of one file name at the same path with the same -mtime, and that’s why it occurred to me that encoding both path and -mtime within the key doesn’t just increase the odds, but effectively -_guarantees_ that there won’t be any collisions. Does this seem to -hold up, or am I missing something? (Of course one can fudge the -mtimes, but that’s something under the user’s control.) - -While a large repo with many files very likely has lots of distinct -files with identical basename, mtime (in s.) and size, all these files -with the same mtime must necessarily be located at different paths. - -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment deleted file mode 100644 index 54fe869c5..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="78.48.163.229" - subject="comment 3" - date="2014-08-16T13:58:28Z" - content=""" -One scenario where the above guarantee would be violated is when one -moves a new file of identical size, basename, and mtime, into a path -where a key-colliding file has been kept before. Still, I’d consider -this a scenario one could reasonably control for (especially in the -archive usecase); plus, even without manual control such a -move-induced collision would be much more unlikely than a collision of -basenames only. - -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_4_4241c05a0fa7ce597c75ff5992b71b89._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_4_4241c05a0fa7ce597c75ff5992b71b89._comment deleted file mode 100644 index a02b1deb6..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_4_4241c05a0fa7ce597c75ff5992b71b89._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 4" - date="2014-08-18T18:39:33Z" - content=""" -> Rather than saying that the relative path adds additional entropy, what I was aiming at is the file-system cannot have two alternate versions of one file name at the same path with the same mtime - -True of a single filesystem, but not of a set of connected git repositories. :) - -So there are multiple scenarios when encoding the file path in the key doesn't help. The probabilities of these seem low, but perhaps not as low as the probability that there will be two differing files with the same name+size+mtime in the first place. It's not clear to me that it adds more than a false sense of security to change from basename to git filename. -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_5_8378cd8c03fabdaa300194b66c1ea53c._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_5_8378cd8c03fabdaa300194b66c1ea53c._comment deleted file mode 100644 index 72bc4f8f4..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_5_8378cd8c03fabdaa300194b66c1ea53c._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="78.48.163.229" - subject="comment 5" - date="2014-08-18T20:54:10Z" - content=""" -> True of a single filesystem, but not of a set of connected git repositories. - -That’s a good point. Might depend on the use case, though. - -> The probabilities of these seem low, but perhaps not as low as the probability that there will be two differing files with the same name+size+mtime in the first place. - -This one I’m not completely sure about. E.g., I have an annex with web pages mirrored from the web. Due to the crawler implementation, there are lots of «index.html» or «favicon.ico» with the same mtime (in particular when mtime is read with a 1 sec. precision). Files like favicon are often bitmaps of the same resolution and often have the same size due to this. Because there are file-formats where both size and basename are semantically pre-determined, there is zero entropy from these sources alone (also cf. «readme.txt»). The entropy of mtime alone is not really large, I suppose, and in some use-cases will also approach zero (think «initializing a repo by cp -r on a fast disk without preserving mtime). The relative path could make a huge difference there. I believe this argument is actually what worried me the most. Does it seem valid? - -Apart from entropy, there’s the non-probabilistic advantage we discussed (granted, with some limiting constraints which one has to assure for oneself). Granted, one might argue a hash would be the better way, but this is not always practical in every setup. -"""]] diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_6_d3c9a1bee717b5b99f31be81150a3ec8._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_6_d3c9a1bee717b5b99f31be81150a3ec8._comment deleted file mode 100644 index d22ef3e0a..000000000 --- a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_6_d3c9a1bee717b5b99f31be81150a3ec8._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 6" - date="2014-09-11T18:41:45Z" - content=""" -Ok, those are good examples. I personally think it would be insane to use WORM in a repository in either of those cases, or really in almost any case where you do not have a strong degree of confidence that unique file contents have unique file names. If people are going to abuse WORM like that, it might be best to simply remove it. (Except I have quite a lot of WORMy disks.) - -I suppose I'll add the extra data, although I remain unconvinced that it is going to help anyone who should actually be using WORM. -"""]] diff --git a/doc/bugs/Prevent_accidental_merges.mdwn b/doc/bugs/Prevent_accidental_merges.mdwn deleted file mode 100644 index 9947f7373..000000000 --- a/doc/bugs/Prevent_accidental_merges.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -With the storage layout v3, pulling the git-annex branch into the master branch is... less than ideal. - -The fact that the two branches contain totally different data make an accidental merge worse, arguably. - -Adding a tiny binary file called .gitnomerge to both branches would solve that without any noticeable overhead. - -Yes, there is an argument to be made that this is too much hand-holding, but I still think it's worth it. - --- Richard - -> It should be as easy to undo such an accidential merge -> as it is to undo any other git commit, right? I quite like that git-annex -> no longer adds any clutter to the master branch, and would be reluctant -> to change that. --[[Joey]] - -[[wontfix|done]] --[[Joey]] diff --git a/doc/bugs/Prevent_accidental_merges/comment_1_4c46a193915eab8f308a04175cb2e40a._comment b/doc/bugs/Prevent_accidental_merges/comment_1_4c46a193915eab8f308a04175cb2e40a._comment deleted file mode 100644 index 3e28a28cb..000000000 --- a/doc/bugs/Prevent_accidental_merges/comment_1_4c46a193915eab8f308a04175cb2e40a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 1" - date="2011-10-23T15:00:48Z" - content=""" -Having run into the same issue again, I still think git-annex should ensure no merges take place. The clutter introduced by a .gitnomerge is neglible, imo. -"""]] diff --git a/doc/bugs/Proxy_support.mdwn b/doc/bugs/Proxy_support.mdwn deleted file mode 100644 index 2af63d706..000000000 --- a/doc/bugs/Proxy_support.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -What steps will reproduce the problem? - -Adding a e.g box.com repository from behind a http proxy via webapp. - -What is the expected output? What do you see instead? - -Connection should be made. But there is an error message: - -"Internal Server Error -connect: does not exist (Connection refused): user error" - -What version of git-annex are you using? On what operating system? - -3.20121127 on Archlinux - -Please provide any additional information below. - -I don't use networkmanager if proxy information is obtained from it. There should be a fallback to environment variables. -[[!tag confirmed]] - -> Here's a patch that shows how to enable proxy support for the -> parts of git-annex that use http-client and http-conduit: -> <https://github.com/kiwiroy/git-annex/commit/18a3ceda1beb7c356541270f37ae4c0d56ada726> -> -> Other parts of git-annex use wget/curl and should already support -> the environment variables. - ->> I had a closer look at this, and it turns out that http-client ->> now enables http proxy support by default, when the environment variable ->> is set. Since version 0.4.7. See `defaultProxy`. ->> ->> git-annex uses http-client for all its http access (either directly ->> or through layers like http-conduit and DAV). ->> ->> So I don't need to change ->> git-annex at all; it just needs to be built with a new enough version ->> of http-client. This will happen for the linux autobuilders once the new ->> version reaches Debian. I've updated the OSX autobuilder's http-client ->> so it will already support proxying and anyone can built git-annex ->> using the new http-client and get proxy support. ->> ->> Calling this [[done]] as nothing remains to do in git-annex. --[[Joey]] diff --git a/doc/bugs/Repository_Information_Is_Lost.mdwn b/doc/bugs/Repository_Information_Is_Lost.mdwn deleted file mode 100644 index cbaf866c8..000000000 --- a/doc/bugs/Repository_Information_Is_Lost.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. - -Clone of a repository does not contain the names of other repositories. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - -Mac OS X - -git-annex version: 5.20140308-g06fb279 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Qu -vi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 - SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook extern -al - - -### Please provide any additional information below. - -Clones of my repositories lost all track of other repositories they only seem to know about them selfs attempting to remove other repositories (git annex dead name-of-an-existing-repo) fails, telling me that the repository with the name is not found. - -[[!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. -"""]] - -[[!tag moreinfo]] - -> No followup for over a year, and not enough information in the intial -> report to know if there's a bug at all. It occurs to me that the user -> might have just forgotten to push the git-annex branch to wherever they -> later cloned the repo from. `git annex sync` would fix that mistake up. -> Anyway, [[done]]. --[[Joey]] diff --git a/doc/bugs/Repository_Information_Is_Lost/comment_1_bae0ed4c0a6baf1675f8de1663042f43._comment b/doc/bugs/Repository_Information_Is_Lost/comment_1_bae0ed4c0a6baf1675f8de1663042f43._comment deleted file mode 100644 index 8534442b6..000000000 --- a/doc/bugs/Repository_Information_Is_Lost/comment_1_bae0ed4c0a6baf1675f8de1663042f43._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.244" - subject="comment 1" - date="2014-04-07T19:24:12Z" - content=""" -Have you run `git-annex repair` or used the assistant to repair this repository? This can result in data going missing until the repository is able to pull the data from one of its remotes. -"""]] diff --git a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn deleted file mode 100644 index 3626f2024..000000000 --- a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -### Please describe the problem. - -trying to add a remote host using its avahi local name : nas.local (for example). - -### What steps will reproduce the problem? - -add remote server, use nas.local > cannot resolve nas.local - -### What version of git-annex are you using? On what operating system? - -Version: 5.20140116-g2d9ec29 -Ubuntu - -### Please provide any additional information below. - -> [[closing|done]] --[[Joey]] diff --git a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment deleted file mode 100644 index 17fae5a3b..000000000 --- a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.68" - subject="comment 1" - date="2014-01-19T22:43:10Z" - content=""" -AFAIK, this will work fine if your OS is able to resolve those addresses using its regular resolver. Works fine here. Is `libnss-mdns` installed? -"""]] diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn deleted file mode 100644 index 4a3b1199b..000000000 --- a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -### Please describe the problem. - -Somewhere on the forums you advised that in order to revert to an old -version of a file in a direct-mode annex, one should briefly switch to -indirect mode and check out an earlier revision. - -This won’t work though if the direct-mode repo is on a VFAT -file-system, which does not support indirect mode. - -If I didn’t overlook an alternative way, would it make sense to expose -this functionality in «git annex get $file»? Like «git annex get $file ---from $repo/$revision»? - -Specifying revisions to get from might also be convenient for -alternative use-cases, I suppose. - -Best regards, -T. - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20140421 -Linux 3.14.3 - -> VFAT is a crippled file system. I am not going to reimplenent all of git -> to support it. The suggested method won't work; git-annex would need -> to add a git-annex revert, etc, etc, etc ad infinitum -> -> Instead, see the `git annex proxy` command. [[done]] --[[Joey]] diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment deleted file mode 100644 index 69c33813a..000000000 --- a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_1_7e512732f1d24300dd13bb093f28122d._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 1" - date="2014-05-13T20:43:38Z" - content=""" -Crosslink to related wishlist item. -http://git-annex.branchable.com/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/ -"""]] diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_2_0ede40e0d68bfb9c6dbc1777f944ed06._comment b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_2_0ede40e0d68bfb9c6dbc1777f944ed06._comment deleted file mode 100644 index 066fefa0c..000000000 --- a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_2_0ede40e0d68bfb9c6dbc1777f944ed06._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 2" - date="2014-05-17T14:16:12Z" - content=""" -One follow-up comment, because it occurred to me I might have phrased -the bug inadequately. By «revert» I didn’t mean a revert in the -git-sense, but merely «checking out» a file from a selected commit. - -But I think I can achieve this in direct mode on VFAT by doing «git -show upstream/branch~X:file > file», right? «git annex get file» then -gets the correct content, only that it will not place the content into -the indicated file until I do «git annex fsck». Maybe «git annex get» -could take this into account and have the content immediately stored -there. - -"""]] diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_3_4ce1601f5dbd8fb769d3c5bb429c3bc5._comment b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_3_4ce1601f5dbd8fb769d3c5bb429c3bc5._comment deleted file mode 100644 index 6e5db42d0..000000000 --- a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/comment_3_4ce1601f5dbd8fb769d3c5bb429c3bc5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 3" - date="2014-05-17T14:21:30Z" - content=""" -Plus it seems that the file can’t be dropped normally afterwards. -"""]] diff --git a/doc/bugs/Rsync_remote_created_via_webapp_remains_empty.mdwn b/doc/bugs/Rsync_remote_created_via_webapp_remains_empty.mdwn deleted file mode 100644 index e961bd521..000000000 --- a/doc/bugs/Rsync_remote_created_via_webapp_remains_empty.mdwn +++ /dev/null @@ -1,138 +0,0 @@ -### Please describe the problem. -The remote server, connected with rsync and with encryption enabled doesn't fill with files. - -### What steps will reproduce the problem? -* Add remote server via webapp -* Supply password when asked -* both buttons turn green ('ready to add remote server') -* Select encrypted rsync repository -* When done, files will be queued for transfer, and the queue empties quickly. Afterwards, no files have actually been transferred, but a green message appears and says something like 'synced with xxx'. -* Also, on the remote an empty directory (~/annex) is created. - -### What version of git-annex are you using? On what operating system? -local: kubuntu 12.10, git-annex 4.20130621-g36258de -remote: debian (linux 3.8.0-25), git-annex 4.20130621-g36258de -Both are installed from tarball and PATH is set at the top of .bashrc. - -### Please provide any additional information below. - -[[!format sh """ - -Here is what is put in the logs when the button is toggled from 'syncing disabled' to 'syncing enabled'. -daemon.log: - -[2013-07-03 13:43:07 CEST] call: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","config","remote.mybox.annex-sync","true"] -[2013-07-03 13:43:07 CEST] read: git ["config","--null","--list"] -[2013-07-03 13:43:07 CEST] read: git ["config","--null","--list"] -[2013-07-03 13:43:07 CEST] main: Syncing with mybox -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","symbolic-ref","HEAD"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","show-ref","refs/heads/master"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","show-ref","git-annex"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","log","refs/heads/git-annex..4cc51b410f5257f60e4ea187ab0c29783effcc88","--oneline","-n1"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","log","refs/heads/git-annex..6728d4d49ef97365eea0e2d379951acee9a9ded8","--oneline","-n1"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","symbolic-ref","HEAD"] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","show-ref","refs/heads/master"] -[2013-07-03 13:43:07 CEST] TransferScanner: starting scan of [Remote { name ="mybox" }] -[2013-07-03 13:43:07 CEST] read: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","ls-files","--cached","-z","--"] -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/TSPC_FF_R.png Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/TSPC_FF_R.png Nothing -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/Thumbs.db Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/TSPC_FF_R.png Nothing -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Aanmeldingsformulier Masterexamen.odt Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Intake_form_MSc_Electrical_Engineering_def dec 2011-1.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.doc Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/uren.xls Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/eldo_ur.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/ A 65J-Conversion-Step 0-to-50MS 0-to-0.7mW 9b Charge-Sharing SAR ADC in 90nm Digital CMOS.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/.directory Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/2009SOVC_A_0.92mW_10-bit_50-MSs_SAR_ADC_in_0.13um_CMOS_Process.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/A 8-bit 500-KSs Low Power SAR ADC for Biomedical Applications.pdf Nothing : expensive scan found missing object -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "ea86501fb0db033a103ed2c0806a1bddc145224afc4eb5e17fceb70bf1f674da.png", keyBackendName = "SHA256E", keySize = Just 11004, keyMtime = Nothing}} -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/A 9.2b 47fJ SAR with input range prediction DAC switching.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/Thumbs.db Nothing -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/Thumbs.db Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "23b9a2be728c8af402ededb3eef7e9238b38d54c0ca50a05cbdf4aeea8f03c76.db", keyBackendName = "SHA256E", keySize = Just 12800, keyMtime = Nothing}} -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -: -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/A Low-Power Static Dual Edge-Triggered Flip-Flop.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Aanmeldingsformulier Masterexamen.odt Nothing -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Aanmeldingsformulier Masterexamen.odt Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "f27ac57481c9eb0bf7bf1f6c99666aca5c8282137effa33791241b3d36b12de2.odt", keyBackendName = "SHA256E", keySize = Just 22041, keyMtime = Nothing}} -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/An Energy-Efficient Charge Recycling Approach for a SAR Converter With Capacitive DAC.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Intake_form_MSc_Electrical_Engineering_def dec 2011-1.pdf Nothing -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Intake_form_MSc_Electrical_Engineering_def dec 2011-1.pdf Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "a261cb3835ed869c6ad2347d303ed10e94efa8a50cc9ff053d772c2158097244.pdf", keyBackendName = "SHA256E", keySize = Just 667666, keyMtime = Nothing}} -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:07 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/Calibration Technique for SAR Analog-to-Digital Converters.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:07 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.doc Nothing -[2013-07-03 13:43:07 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.doc Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:08 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "cb69f2f4ae313277acd163b9bba19392ce50d3c5205ba8bbd90bf9c453088176.doc", keyBackendName = "SHA256E", keySize = Just 34304, keyMtime = Nothing}} -[2013-07-03 13:43:08 CEST] call: git ["--git-dir=/home/boris/annex/.git","--work-tree=/home/boris/annex","config","remote.mybox.annex-sync","false"] -[2013-07-03 13:43:08 CEST] read: git ["config","--null","--list"] -[2013-07-03 13:43:08 CEST] read: git ["config","--null","--list"] -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:08 CEST] TransferScanner: queued Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/D15_01.pdf Nothing : expensive scan found missing object -[2013-07-03 13:43:08 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.pdf Nothing -[2013-07-03 13:43:08 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/administratie/Opdrachtomschrijving Master.pdf Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:08 CEST] TransferWatcher: transfer finishing: Transfer {transferDirection = Upload, transferUUID = UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23", transferKey = Key {keyName = "cea054d80cb5ca572b7055c0132ec2d13125534566ed4a79ab2514c9a60d8ee4.pdf", keyBackendName = "SHA256E", keySize = Just 19802, keyMtime = Nothing}} -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-07-03 13:43:08 CEST] Transferrer: Transferring: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/D15_01.pdf Nothing -[2013-07-03 13:43:08 CEST] TransferWatcher: transfer starting: Upload UUID "32841e5f-1e4d-4c72-84c4-bbb54a335a23" afstuderen/literatuur/D15_01.pdf Nothing -fatal: unrecognized command 'rsync --server -vre.iLsf --partial-dir .rsync-partial . annex/' -git-annex-shell: git-shell failed -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] - - - -# End of transcript or log. -"""]] - -> [[fixed|done]], corrected logic error that caused `authorized_keys` -> to incorrectly force the git-annex-shell command for rsync remotes. --[[Joey]] diff --git a/doc/bugs/Rsync_remote_created_via_webapp_remains_empty/comment_1_cccf9d58c0ebb8d31cacdd029ea8e23a._comment b/doc/bugs/Rsync_remote_created_via_webapp_remains_empty/comment_1_cccf9d58c0ebb8d31cacdd029ea8e23a._comment deleted file mode 100644 index 480a16243..000000000 --- a/doc/bugs/Rsync_remote_created_via_webapp_remains_empty/comment_1_cccf9d58c0ebb8d31cacdd029ea8e23a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.153.254.222" - subject="comment 1" - date="2013-07-08T16:55:09Z" - content=""" -Finally got a chance to look into this. - -The ~/.ssh/authorized_keys file on the server has been set up wrong by the webapp. If you look at it, it'll contain a part like: command=\"GIT_ANNEX_SHELL_DIRECTORY=... ~/.ssh/git-annex-shell\" - -That can't be used for rsync. If you delete that command= part, your remote should start working. -"""]] diff --git a/doc/bugs/S3_Access_fails_on_windows.mdwn b/doc/bugs/S3_Access_fails_on_windows.mdwn deleted file mode 100644 index 403d0c0c2..000000000 --- a/doc/bugs/S3_Access_fails_on_windows.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -### Please describe the problem. - -Attempting to do *anything* with an S3 reomote using git-annex on windows fails with error code 10093 (i.e. WSA_NOT_INITIALISED). - -### What steps will reproduce the problem? - -Assuming you have a disabled S3 remote called "the-cloud" (e.g. a fresh clone) -[[!format sh """ -C:\annex> git annex enableremote "the-cloud" -enableremote the-cloud gpg: WARNING: using insecure memory! -gpg: please see http://www.gnupg.org/documentation/faqs.html for more information -(checking bucket...) (creating bucket in ap-southeast-2...) git-annex-old: FailedConnectionException2 "my-bucket-name.s3-ap-southeast-2.amazonaws.com" 80 False getAddrInfo: does not exist (error 10093) -"""]] - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20150113-gcf247cf on windows 8.1 - -### Please provide any additional information below. - -This error is caused by the Winsock library not being initialised before a socket operation is attempted. The patch below fixes the issue, and it should be a no-op on non-Windows platforms. - -[[!format patch """ -diff --git a/git-annex.hs b/git-annex.hs -index cdaa754..0eed9db 100644 ---- a/git-annex.hs -+++ b/git-annex.hs -@@ -21,8 +21,10 @@ import Utility.UserInfo - import Utility.Env - #endif - -+import Network.Socket (withSocketsDo) -+ - main :: IO () --main = do -+main = withSocketsDo $ do - ps <- getArgs - run ps =<< getProgName - where -"""]] - -> Thanks very much for the patch! [[done]] --[[Joey]] diff --git a/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn b/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn deleted file mode 100644 index 9a67db0c6..000000000 --- a/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -### Please describe the problem. - -As described in [[tips/Internet_Archive_via_S3]], there is a problem using S3 with buckets that have capital letters. The bug lies either in the hS3 library or in archive.org itself. - -### What steps will reproduce the problem? - -Try to add an [[special_remotes/S3]] remote with capital letters in the bucket name. - -### What version of git-annex are you using? On what operating system? - -[[!format txt """ -git-annex version: 4.20130921-g434dc22 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi -local repository version: 3 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -"""]] - -### 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 -anarcat@angela:video$ git annex initremote archive-moglenrepublica type=S3 host=s3.us.archive.org bucket=Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia -initremote archive-moglenrepublica (Internet Archive mode) git-annex: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. For more information, see REST Authentication and SOAP Authentication for details. -# End of transcript or log. -"""]] - -Just thought it would be better to have a separate thread for this bug. :) - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/S3_memory_leaks.mdwn b/doc/bugs/S3_memory_leaks.mdwn deleted file mode 100644 index 7dc1e5757..000000000 --- a/doc/bugs/S3_memory_leaks.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -S3 has memory leaks - -Sending a file to S3 causes a slow memory increase toward the file size. - -> This is fixed, now that it uses aws. --[[Joey]] - -Copying the file back from S3 causes a slow memory increase toward the -file size. - -> [[fixed|done]] too! --[[Joey]] - -The author of hS3 is aware of the problem, and working on it. I think I -have identified the root cause of the buffering; it's done by hS3 so it can -resend the data if S3 sends it a 307 redirect. --[[Joey]] - -At least the send leak should be fixed by the patch in the s3-memory-leak -branch in git. That needs a patch to hS3, which I have sent to its author. ---[[Joey]] -[[!tag confirmed]] diff --git a/doc/bugs/S3_memory_leaks/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment b/doc/bugs/S3_memory_leaks/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment deleted file mode 100644 index 0523fd473..000000000 --- a/doc/bugs/S3_memory_leaks/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://schnouki.net/" - nickname="Schnouki" - subject="comment 1" - date="2013-10-18T08:36:45Z" - content=""" -Hi Joey, - -It looks like your patch hasn't been merged yet. And this bug is quite annoying for me (can't backup files bigger than 1.5 GB from my NAS). - -Would it be possible to include this fix in your standalone builds and Debian packages? - -Thanks! -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_2_320a8e3bb7b207d1aff8926b9247f5ba._comment b/doc/bugs/S3_memory_leaks/comment_2_320a8e3bb7b207d1aff8926b9247f5ba._comment deleted file mode 100644 index d4648b9c4..000000000 --- a/doc/bugs/S3_memory_leaks/comment_2_320a8e3bb7b207d1aff8926b9247f5ba._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://schnouki.net/" - nickname="Schnouki" - subject="comment 2" - date="2014-01-29T01:19:27Z" - content=""" -Any news about this? -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment b/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment deleted file mode 100644 index a7bb0265f..000000000 --- a/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.112" - subject="comment 3" - date="2014-08-02T23:08:44Z" - content=""" -hS3's author seems to have abandoned it and it has other problems. I should try to switch to a different S3 library. - -There is now a workaround; S3 special remotes can be configured to use [[chunking]]. A max of one chunk will then be buffered in memory at a time. - -For example, to reconfigure an existing mys3 remote: `enableremote mys3 chunk=1MiB` -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_4_37e41b518813bd7c349017abf4a0ca0f._comment b/doc/bugs/S3_memory_leaks/comment_4_37e41b518813bd7c349017abf4a0ca0f._comment deleted file mode 100644 index 464588a79..000000000 --- a/doc/bugs/S3_memory_leaks/comment_4_37e41b518813bd7c349017abf4a0ca0f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.112" - subject="comment 4" - date="2014-08-03T18:40:26Z" - content=""" -Beginning work on a `s3-aws` branch using the aws library instead of hS3. -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_5_1b6d13852aeb37c5c29baf100bd62789._comment b/doc/bugs/S3_memory_leaks/comment_5_1b6d13852aeb37c5c29baf100bd62789._comment deleted file mode 100644 index ae07de74c..000000000 --- a/doc/bugs/S3_memory_leaks/comment_5_1b6d13852aeb37c5c29baf100bd62789._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 5" - date="2014-11-30T22:18:56Z" - content=""" -This is getting in my way, but I'm concerned about using a mostly-untested branch (and also, compiling for ARM sounds really unpleasant). Can you elaborate on the risks here? Can I perhaps donate developer time to get this merged into mainline? -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_6_71ffb88f548969fd4d45eac4656380c0._comment b/doc/bugs/S3_memory_leaks/comment_6_71ffb88f548969fd4d45eac4656380c0._comment deleted file mode 100644 index fe88d8ef4..000000000 --- a/doc/bugs/S3_memory_leaks/comment_6_71ffb88f548969fd4d45eac4656380c0._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2014-12-02T17:10:42Z" - content=""" -The s3-aws branch is well tested now. - -I am blocked from merging it by some dependency issues, in particular -<http://hackage.haskell.org/package/dbus> needs to have a small dependency -fix. I have emailed its author a second time now to try to get that done. -"""]] diff --git a/doc/bugs/S3_memory_leaks/comment_7_1ac572b79caa23e3f791e4f8461fcddd._comment b/doc/bugs/S3_memory_leaks/comment_7_1ac572b79caa23e3f791e4f8461fcddd._comment deleted file mode 100644 index 5aaab2bdd..000000000 --- a/doc/bugs/S3_memory_leaks/comment_7_1ac572b79caa23e3f791e4f8461fcddd._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 7" - date="2014-12-06T18:15:50Z" - content=""" -The new version works really great for me. I've been copying to S3 over the past few days with no issues on my raspberry pi. - -Thanks a ton for getting this out. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart.mdwn b/doc/bugs/S3_upload_not_using_multipart.mdwn deleted file mode 100644 index ac3817c65..000000000 --- a/doc/bugs/S3_upload_not_using_multipart.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -What steps will reproduce the problem? - -> Try to copy/move a file greater than 5G to S3. - - git annex copy large_file.tgz --to cloud - -What is the expected output? What do you see instead? - -> Looks like git-annex may not be using the Multipart Upload API: http://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html - -> Expected transfer to succeed, instead this error is output: - - copy large-file.tgz (gpg) (checking cloud...) (to cloud...) Reading passphrase from file descriptor 12 - - - Your proposed upload exceeds the maximum allowed size - failed - git-annex: copy: 1 failed - -What version of git-annex are you using? On what operating system? - -> OSX 10.8.2 - -Please provide any additional information below. - - annex [master●] % git annex status - supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - supported remote types: git S3 bup directory rsync web webdav glacier hook - repository mode: indirect - trusted repositories: 0 - semitrusted repositories: 3 - 00000000-0000-0000-0000-000000000001 -- web - BE1D8EC7-C64B-47DE-AD4E-2A50437532B4 -- cloud - E84568BA-6A4B-4AA1-B622-605B9248EDB1 -- here (eric laptop) - untrusted repositories: 0 - dead repositories: 0 - transfers in progress: none - available local disk space: 169 gigabytes (+1 megabyte reserved) - temporary directory size: 218 megabytes (clean up with git-annex unused) - local annex keys: 24 - local annex size: 8 gigabytes - known annex keys: 25 - known annex size: 8 gigabytes - bloom filter size: 16 mebibytes (0% full) - backend usage: - SHA256E: 49 - annex [master●] % git annex version - git-annex version: 3.20130114 - local repository version: 3 - default repository version: 3 - supported repository versions: 3 - upgrade supported from repository versions: 0 1 2 - -[[!tag confirmed]] - -> [[fixed|done]] This is now supported, when git-annex is built with a new -> enough version of the aws library. You need to configure the remote to -> use an appropriate value for multipart, eg: -> -> git annex enableremote cloud partsize=1GiB -> -> --[[Joey]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_11_ba1f866645419476bbedd6b1e4bbd33f._comment b/doc/bugs/S3_upload_not_using_multipart/comment_11_ba1f866645419476bbedd6b1e4bbd33f._comment deleted file mode 100644 index c2fdae5e9..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_11_ba1f866645419476bbedd6b1e4bbd33f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 11""" - date="2014-11-03T21:27:22Z" - content=""" -Now implemented on s3-aws branch. Needs a version of the -haskell aws library that is not quite released yet (but available in git). -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_12_bf98d0c771dfdd15ddafdba2d94d911f._comment b/doc/bugs/S3_upload_not_using_multipart/comment_12_bf98d0c771dfdd15ddafdba2d94d911f._comment deleted file mode 100644 index 2be62f668..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_12_bf98d0c771dfdd15ddafdba2d94d911f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnWvnTWY6LrcPB4BzYEBn5mRTpNhg5EtEg" - nickname="Bence" - subject="comment 12" - date="2014-12-08T17:28:52Z" - content=""" -Linked this bug to [[special remotes/S3|/special_remotes/S3]]. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment b/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment deleted file mode 100644 index 117055e3f..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_1_5bed9faafc43b535f7820749510aaa14._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 1" - date="2014-05-13T15:09:42Z" - content=""" -JFTR, this is impacting DebConf's video storage as well. - -Richard -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_2_d82952cf324e769e45f4d90f200210f4._comment b/doc/bugs/S3_upload_not_using_multipart/comment_2_d82952cf324e769e45f4d90f200210f4._comment deleted file mode 100644 index 7ee3c1167..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_2_d82952cf324e769e45f4d90f200210f4._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="annexuser" - ip="64.71.7.82" - subject="comment 2" - date="2014-07-14T18:21:00Z" - content=""" -I'm having the same problem. Is there a fix for this yet? - - $ git annex version - git-annex version: 5.20140709-gc75193e - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment b/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment deleted file mode 100644 index 46245e657..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_3_d878b87a05f4fcd380e6ff309b615aab._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.112" - subject="comment 3" - date="2014-08-02T23:13:41Z" - content=""" -There is now a workaround; S3 special remotes can be configured to use [[chunking]]. - -For example, to reconfigure an existing mys3 remote: `enableremote mys3 chunk=1MiB` - -I'm leaving this bug open because chunking is not the default (although the assistant does enable it by default), and because this chunking operates at a higher, and less efficient level than S3's own multipart upload API. In particular, AWS will charge a fee for each http request made for a chunk. - -Adding proper multipart support will probably require switching to a different S3 library. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_4_09a3372fd13734cbb05e79d0ba76d052._comment b/doc/bugs/S3_upload_not_using_multipart/comment_4_09a3372fd13734cbb05e79d0ba76d052._comment deleted file mode 100644 index d36628163..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_4_09a3372fd13734cbb05e79d0ba76d052._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.112" - subject="comment 4" - date="2014-08-03T18:22:58Z" - content=""" -The aws library does not support multipart yet either; here's the bug report requesting it: <https://github.com/aristidb/aws/issues/94> -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment b/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment deleted file mode 100644 index 0c7742364..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_5_5add65b5b284f79ec09ee4d0326e7132._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.112" - subject="comment 5" - date="2014-08-03T18:27:32Z" - content=""" -However, I don't think that multipart upload actually allows exceeding the S3 limit of 5 GB per object. Configuring the remote with `chunk=100MiB` *does* allow bypassing whatever S3's maximum object size happens to be. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_6_906abafc53070d8e4f33df486d2241ea._comment b/doc/bugs/S3_upload_not_using_multipart/comment_6_906abafc53070d8e4f33df486d2241ea._comment deleted file mode 100644 index ad9d4b601..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_6_906abafc53070d8e4f33df486d2241ea._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="Multipart S3 support files > 5 GB" - date="2014-08-04T06:00:45Z" - content=""" -The [multipart guide](http://docs.aws.amazon.com/AmazonS3/latest/dev/UploadingObjects.html) says that the limit is 5 TB per file. - -> **Upload objects in parts—Using the Multipart upload API you can upload large objects, up to 5 TB.** - -> The Multipart Upload API is designed to improve the upload experience for larger objects. You can upload objects in parts. These object parts can be uploaded independently, in any order, and in parallel. You can use a Multipart Upload for objects from 5 MB to 5 TB in size. For more information, see Uploading Objects Using Multipart Upload. For more information, see Uploading Objects Using Multipart Upload API. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_7_f620888512cd78628f82ec9e5eed4ad1._comment b/doc/bugs/S3_upload_not_using_multipart/comment_7_f620888512cd78628f82ec9e5eed4ad1._comment deleted file mode 100644 index ec47aa2be..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_7_f620888512cd78628f82ec9e5eed4ad1._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 7" - date="2014-09-29T08:07:55Z" - content=""" -As I found the latest comment confusing, here's the full quote: - - Depending on the size of the data you are uploading, Amazon S3 offers the following options: - - Upload objects in a single operation—With a single PUT operation you can upload objects up to 5 GB in size. - - Upload objects in parts—Using the Multipart upload API you can upload large objects, up to 5 TB. - - The Multipart Upload API is designed to improve the upload experience for larger objects. You can upload objects in parts. - These object parts can be uploaded independently, in any order, and in parallel. - You can use a Multipart Upload for objects from 5 MB to 5 TB in size. - - We encourage Amazon S3 customers to use Multipart Upload for objects greater than 100 MB. - -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_8_4d9242cde0d2348452438659a8aa8d6d._comment b/doc/bugs/S3_upload_not_using_multipart/comment_8_4d9242cde0d2348452438659a8aa8d6d._comment deleted file mode 100644 index a427c504e..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_8_4d9242cde0d2348452438659a8aa8d6d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 8" - date="2014-09-29T08:09:33Z" - content=""" -PS: Chunking spams the S3 remote with individual objects whereas multipart uploads do not. Just something to keep in mind in case you turn on chunking for S3. -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_9_1f5578a9100f0f087a558e5e5968d753._comment b/doc/bugs/S3_upload_not_using_multipart/comment_9_1f5578a9100f0f087a558e5e5968d753._comment deleted file mode 100644 index 10cab3da9..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_9_1f5578a9100f0f087a558e5e5968d753._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 9""" - date="2014-10-28T18:25:04Z" - content=""" -I have a WIP branch `aws-s3-multipart`. I stopped when I got blocked -by a bad API in the aws library: <https://github.com/aristidb/aws/issues/141> -"""]] diff --git a/doc/bugs/S3_upload_not_using_multipart/comment_9_74b2a392a537dde1c28089f1deed940c._comment b/doc/bugs/S3_upload_not_using_multipart/comment_9_74b2a392a537dde1c28089f1deed940c._comment deleted file mode 100644 index b965ff0ab..000000000 --- a/doc/bugs/S3_upload_not_using_multipart/comment_9_74b2a392a537dde1c28089f1deed940c._comment +++ /dev/null @@ -1,31 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 9""" - date="2014-10-28T16:42:21Z" - content=""" -The aws library now supports multipart uploads, using its -S3.Commands.Multipart module. - -I don't think that multipart and chunking fit together: Typically the -chunks are too small to need multipart for individual chunks. And the -chunks shouldn't be combined together into a complete object at the end (at -least not if we care about using chunking to obscure object size). -Individual chunks sizes can vary when encryption is used, so combining them -all into one file wouldn't work. - -Also, multipart uploads require at least 3 http calls, so there's no point -using it for small objects, as it would only add overhead. - -So, multipart uploads should be used when not chunking, when the object to -upload exceeds some size, which should probably defaut to something in the -range of 100 mb to 1 gb. - -It might be possible to support resuming of interrupted multipart uploads. -It seems that git-annex would need to store, locally, the UploadId, -as well as the list of uploaded parts, including the Etag for the upload -(which is needed when completing the multipart upload too). - -Also it should probably set Expires when initiating the multipart upload, -so that incomplete ones get cleaned up after some period of time. -Otherwise, users would probably be billed for them. -"""]] diff --git a/doc/bugs/SanityCheckerStartup_crashed.mdwn b/doc/bugs/SanityCheckerStartup_crashed.mdwn deleted file mode 100644 index 65a9beb65..000000000 --- a/doc/bugs/SanityCheckerStartup_crashed.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. -On startup, the webapp shows the following warning in a box to the upper right of the screen, with an offer to "Restart thread": - - SanityCheckerStartup crashed: /home/anton/Halvhemligt/.git/annex/misctmp/IMG_32978856.JPG: getFileStatus: does not exist (No such file or directory) - -Restarting it causes it to crash again immediately. The log shows the same: - - SanityCheckerStartup crashed: /home/anton/Halvhemligt/.git/annex/misctmp/IMG_32978856.JPG: getFileStatus: does not exist (No such file or directory) - [2014-06-02 23:31:13 CEST] SanityCheckerStartup: warning SanityCheckerStartup crashed: /home/anton/Halvhemligt/.git/annex/misctmp/IMG_32978856.JPG: getFileStatus: does not exist (No such file or directory) - -/home/anton/Halvhemligt/.git/annex/misctmp/ contains the following: - - lrwxrwxrwx 2 anton anton 199 15 maj 21.08 IMG_32978856.JPG -> ../.git/annex/objects/z3/K2/SHA256E-s728022--12de1f194042af3f8c4dbee15c317de0511bbb8b9e8a0463fffb07e7bbc58bb5.JPG/SHA256E-s728022--12de1f194042af3f8c4dbee15c317de0511bbb8b9e8a0463fffb07e7bbc58bb5.JPG - lrwxrwxrwx 2 anton anton 199 15 maj 21.09 IMG_32988856.JPG -> ../.git/annex/objects/vw/30/SHA256E-s688301--8bb6d636163b443705c9a333194116da3937d8272b70613ca6345eaf6bba1255.JPG/SHA256E-s688301--8bb6d636163b443705c9a333194116da3937d8272b70613ca6345eaf6bba1255.JPG - lrwxrwxrwx 2 anton anton 199 15 maj 21.17 IMG_33198856.JPG -> ../.git/annex/objects/p3/WG/SHA256E-s754900--224e6489370527156293912e11390af517ad4ef9374ee22c8324b5af5fac0dd7.JPG/SHA256E-s754900--224e6489370527156293912e11390af517ad4ef9374ee22c8324b5af5fac0dd7.JPG - -The symlinks are all broken. IMG_3297.JPG, IMG_3298.JPG and IMG_3319.JPG exist in the repository, but I do not recognize the appended numbers 8856. git log shows that these three files have not been modified since they were first added. - -### What steps will reproduce the problem? -No idea. I believe this repository was created in the webapp but most of the changes to it has been done in the CLI. - -### What version of git-annex are you using? On what operating system? -Precompiled 5.20140530 on Arch Linux x86_64 (git-annex-bin package from the AUR), but 5.20140518 had the same problem. - -### Please provide any additional information below. -The crash has not caused any real problem for me that I'm aware of. I'm just reporting it because the error message looks a little scary. - -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment b/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment deleted file mode 100644 index 52354d7dc..000000000 --- a/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-04T18:07:11Z" - content=""" -This was already fixed in [[!commit 9c0f3ae7e13cc8ed43ac73fbab565e07c10d2c90]]. -"""]] diff --git a/doc/bugs/SanityCheckerStartup_crashed/comment_2_8b800bf7b54e487e82d0897c87967f22._comment b/doc/bugs/SanityCheckerStartup_crashed/comment_2_8b800bf7b54e487e82d0897c87967f22._comment deleted file mode 100644 index fd08002d2..000000000 --- a/doc/bugs/SanityCheckerStartup_crashed/comment_2_8b800bf7b54e487e82d0897c87967f22._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eliasson" - nickname="eliasson" - subject="comment 2" - date="2014-06-05T17:15:32Z" - content=""" -Great. I will patiently await the next release. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx.mdwn b/doc/bugs/Share_with_friends_crash_in_osx.mdwn deleted file mode 100644 index d7ed801e7..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx.mdwn +++ /dev/null @@ -1,370 +0,0 @@ -### Please describe the problem. -Logging into Jabber (specifically with a google account) crashes on the OSX build of git-annex with a Illegal Instruction 4 error. - -### What steps will reproduce the problem? -The only things I have done to trigger the below crash is start the webapp up, navigate to the jabber login, and login with my gmail account. - -### What version of git-annex are you using? On what operating system? -Version: 5.20140107-g281cde8 OSX - -### Please provide any additional information below. - -There isn't much on the command line to go from: - - Launching web browser on file:///Volumes/Data/Annex/.git/annex/webapp.html - Illegal instruction: 4 - -And the log file isn't any better. - -[[!format sh """ -[2014-01-13 20:40:43 EST] main: starting assistant version 5.20140107-g281cde8 -(scanning...) [2014-01-13 20:40:43 EST] Watcher: Performing startup scan -(started...) -"""]] - -Here is the crash report osx creates -[[!format sh """ - Process: git-annex [11316] - Path: /Applications/git-annex.app/Contents/MacOS/bundle/git-annex - Identifier: git-annex - Version: 0 - Code Type: X86-64 (Native) - Parent Process: bash [10866] - Responsible: Terminal [212] - User ID: 501 - - Date/Time: 2014-01-13 20:12:59.807 -0500 - OS Version: Mac OS X 10.9.1 (13B42) - Report Version: 11 - Anonymous UUID: 43148BA1-3CAA-4C73-2971-CAC673D60B2B - - - Crashed Thread: 5 - - Exception Type: EXC_BAD_INSTRUCTION (SIGILL) - Exception Codes: 0x0000000000000001, 0x0000000000000000 - - Thread 0:: Dispatch queue: com.apple.main-thread - 0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 - 1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 - 2 git-annex 0x0000000103ae2c59 0x100e4f000 + 46742617 - 3 git-annex 0x0000000103abfe7b 0x100e4f000 + 46599803 - 4 git-annex 0x0000000103ace8c2 0x100e4f000 + 46659778 - 5 git-annex 0x0000000103acf334 0x100e4f000 + 46662452 - 6 git-annex 0x0000000103ac9cce 0x100e4f000 + 46640334 - 7 git-annex 0x0000000103ac9dd6 0x100e4f000 + 46640598 - 8 git-annex 0x0000000101701708 0x100e4f000 + 9119496 - 9 libdyld.dylib 0x00007fff9a5695fd start + 1 - - Thread 1: - 0 libsystem_kernel.dylib 0x00007fff9796e662 kevent64 + 10 - 1 git-annex 0x0000000103a6e78a 0x100e4f000 + 46266250 - 2 git-annex 0x0000000103a6e828 0x100e4f000 + 46266408 - - Thread 2: - 0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 - 1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 - 2 git-annex 0x0000000103ae2c59 0x100e4f000 + 46742617 - 3 git-annex 0x0000000103abfe7b 0x100e4f000 + 46599803 - 4 git-annex 0x0000000103ace8c2 0x100e4f000 + 46659778 - 5 git-annex 0x0000000103acf20b 0x100e4f000 + 46662155 - 6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 3: - 0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 - 1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 - 2 git-annex 0x0000000103ae2c59 0x100e4f000 + 46742617 - 3 git-annex 0x0000000103abfe7b 0x100e4f000 + 46599803 - 4 git-annex 0x0000000103ace8c2 0x100e4f000 + 46659778 - 5 git-annex 0x0000000103acf20b 0x100e4f000 + 46662155 - 6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 4: - 0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 - 1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 - 2 git-annex 0x0000000103ae2c59 0x100e4f000 + 46742617 - 3 git-annex 0x0000000103abfe7b 0x100e4f000 + 46599803 - 4 git-annex 0x0000000103ace8c2 0x100e4f000 + 46659778 - 5 git-annex 0x0000000103acf20b 0x100e4f000 + 46662155 - 6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 5 Crashed: - 0 E 0x00000001045b10f3 xmlAllocParserInputBuffer + 32 - 1 E 0x000000010459f451 xmlCreatePushParserCtxt + 65 - 2 git-annex 0x00000001022369ca 0x100e4f000 + 20871626 - 3 git-annex 0x000000010222c9fd 0x100e4f000 + 20830717 - - Thread 6:: Dispatch queue: com.apple.libdispatch-manager - 0 libsystem_kernel.dylib 0x00007fff9796e662 kevent64 + 10 - 1 libdispatch.dylib 0x00007fff92f5243d _dispatch_mgr_invoke + 239 - 2 libdispatch.dylib 0x00007fff92f52152 _dispatch_mgr_thread + 52 - - Thread 7: - 0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 - 1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 - 2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 - 3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 - 4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 - 5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 - 6 git-annex 0x000000010229dbe8 0x100e4f000 + 21294056 - 7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 8: - 0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 - 1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 - 2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 - 3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 - 4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 - 5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 - 6 git-annex 0x000000010229dbe8 0x100e4f000 + 21294056 - 7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 9: - 0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 - 1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 - 2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 - 3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 - 4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 - 5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 - 6 git-annex 0x000000010229dbe8 0x100e4f000 + 21294056 - 7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 10: - 0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 - 1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 - 2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 - 3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 - 4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 - 5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 - 6 git-annex 0x000000010229dbe8 0x100e4f000 + 21294056 - 7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 - 8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 - 9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - - Thread 5 crashed with X86 Thread State (64-bit): - rax: 0x00007fc563c0f6a0 rbx: 0x00007fc563c0f6a0 rcx: 0x0000000000000001 rdx: 0x0000000000000000 - rdi: 0x0000000104a01400 rsi: 0x00000000ffffc7ff rbp: 0x0000000104f7ccb0 rsp: 0x0000000104f7cca0 - r8: 0x0000000000000003 r9: 0x00007fc563c00000 r10: 0x000000010467f9f8 r11: 0x000000010459f410 - r12: 0x0000000104f7cd20 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000104b840c0 - rip: 0x00000001045b10f3 rfl: 0x0000000000010206 cr2: 0x00000001045b10d3 - - Logical CPU: 1 - Error Code: 0x00000000 - Trap Number: 6 - - - Binary Images: - 0x100e4f000 - 0x103c68fef +git-annex (0) <05D25108-337E-3F98-837F-33A4E68BA8A4> /Applications/git-annex.app/Contents/MacOs/bundle/git-annex - 0x104582000 - 0x10466bff7 +E (0) <602E5717-D4D7-314D-A1E9-02AFBFBB7966> /Applications/git-annex.app/Contents/MacOs/bundle/E - 0x10469f000 - 0x1046b3fff +F (0) <FA90B1B1-A866-3A6C-BB97-06955F4C8C0B> /Applications/git-annex.app/Contents/MacOs/bundle/F - 0x1046ba000 - 0x1046e7fff +G (0) <9FFF37C3-8153-345F-9B71-913B95B07511> /Applications/git-annex.app/Contents/MacOs/bundle/G - 0x1046ee000 - 0x1047a7fdf +H (0) <49EC1EB8-F352-303D-8E68-C95171D096CF> /Applications/git-annex.app/Contents/MacOs/bundle/H - 0x1047de000 - 0x1047efff7 +B (53) <42E0C8C6-CA38-3CA4-8619-D24ED5DD492E> /Applications/git-annex.app/Contents/MacOs/bundle/B - 0x1047f6000 - 0x1048e7ff9 +D (41) <BB44B115-AC32-3877-A0ED-AEC6232A4563> /Applications/git-annex.app/Contents/MacOs/bundle/D - 0x1048fe000 - 0x104918ff7 +O (0) <18FCF32F-BAB0-323A-BCAC-D4CE4272B754> /Applications/git-annex.app/Contents/MacOs/bundle/O - 0x10491f000 - 0x104930fff +P (0) <E483648A-97E2-3214-B602-73F6445AAD69> /Applications/git-annex.app/Contents/MacOs/bundle/P - 0x10493f000 - 0x10494cff7 +Q (0) <CFA94087-CD1F-3355-BFC1-2D338F6358C4> /Applications/git-annex.app/Contents/MacOs/bundle/Q - 0x104957000 - 0x104978fff +R (0) <C6EE5DD0-0910-3605-A149-D7F67C2F8C10> /Applications/git-annex.app/Contents/MacOs/bundle/R - 0x104985000 - 0x104991fff +S (0) <9082AF89-3370-3858-B015-CB919CB3EBB0> /Applications/git-annex.app/Contents/MacOs/bundle/S - 0x104998000 - 0x1049f1fcf +T (0) <3AADCBFB-48C4-320D-8CF1-1E8FDAC30276> /Applications/git-annex.app/Contents/MacOs/bundle/T - 0x7fff69dff000 - 0x7fff69e32817 dyld (239.3) <D1DFCF3F-0B0C-332A-BCC0-87A851B570FF> /usr/lib/dyld - 0x7fff8d3b0000 - 0x7fff8d43cff7 com.apple.ink.framework (10.9 - 207) <8A50B893-AD03-3826-8555-A54FEAF08F47> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink - 0x7fff8d44b000 - 0x7fff8d4a3ff7 com.apple.Symbolication (1.4 - 129) <16D42516-7B5E-357C-898A-FAA9EE7642B3> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication - 0x7fff8d515000 - 0x7fff8d516fff libunc.dylib (28) <62682455-1862-36FE-8A04-7A6B91256438> /usr/lib/system/libunc.dylib - 0x7fff8d51c000 - 0x7fff8d522ff7 libsystem_platform.dylib (24.1.4) <331BA4A5-55CE-3B95-99EB-44E0C89D7FB8> /usr/lib/system/libsystem_platform.dylib - 0x7fff8d523000 - 0x7fff8d904ffe libLAPACK.dylib (1094.5) <7E7A9B8D-1638-3914-BAE0-663B69865986> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib - 0x7fff8d952000 - 0x7fff8d959fff com.apple.NetFS (6.0 - 4.0) <8E26C099-CE9D-3819-91A2-64EA929C6137> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS - 0x7fff8d98a000 - 0x7fff8d9c8ff7 libGLImage.dylib (9.0.83) <C08048A7-03CC-3E40-BCDC-7791D87AC8E4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib - 0x7fff8da8d000 - 0x7fff8dd8cfff com.apple.Foundation (6.9 - 1056) <D608EDFD-9634-3573-9B7E-081C7D085F7A> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation - 0x7fff8dfac000 - 0x7fff8dfb0ff7 libheimdal-asn1.dylib (323.12) <063A01C2-E547-39D9-BB42-4CC8E64ADE70> /usr/lib/libheimdal-asn1.dylib - 0x7fff8dfb1000 - 0x7fff8dfb6fff libmacho.dylib (845) <1D2910DF-C036-3A82-A3FD-44FF73B5FF9B> /usr/lib/system/libmacho.dylib - 0x7fff8e022000 - 0x7fff8e024ff3 libsystem_configuration.dylib (596.12) <C4F633D9-94C8-35D9-BB2D-84C5122533C7> /usr/lib/system/libsystem_configuration.dylib - 0x7fff8e35c000 - 0x7fff8e4afff7 com.apple.audio.toolbox.AudioToolbox (1.9 - 1.9) <A0B7B007-9BD8-30E2-B644-47856DA29FEE> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox - 0x7fff8e4ee000 - 0x7fff8f062ff7 com.apple.AppKit (6.9 - 1265) <0E9FC8BF-DA3C-34C5-91CC-12BC922B5F01> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit - 0x7fff8f063000 - 0x7fff8f067ff7 libcache.dylib (62) <BDC1E65B-72A1-3DA3-A57C-B23159CAAD0B> /usr/lib/system/libcache.dylib - 0x7fff8f068000 - 0x7fff8f0a1ff7 com.apple.QD (3.50 - 298) <C1F20764-DEF0-34CF-B3AB-AB5480D64E66> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD - 0x7fff8f0a2000 - 0x7fff8f0adfff libGL.dylib (9.0.83) <984A960A-C159-3AE5-8B40-E2B451F6C712> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib - 0x7fff8f0d7000 - 0x7fff8f0d8ff7 libDiagnosticMessagesClient.dylib (100) <4CDB0F7B-C0AF-3424-BC39-495696F0DB1E> /usr/lib/libDiagnosticMessagesClient.dylib - 0x7fff8f120000 - 0x7fff8f121fff liblangid.dylib (117) <9546E641-F730-3AB0-B3CD-E0E2FDD173D9> /usr/lib/liblangid.dylib - 0x7fff8f122000 - 0x7fff8f169ff7 libcups.2.dylib (372) <348EED62-6C20-35D6-8EFB-E80943965100> /usr/lib/libcups.2.dylib - 0x7fff8f551000 - 0x7fff8f5e0fff com.apple.Metadata (10.7.0 - 800.12.2) <A9F5D471-8732-3F95-A4A2-33864B92A181> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata - 0x7fff8f843000 - 0x7fff8f850ff0 libbz2.1.0.dylib (29) <0B98AC35-B138-349C-8063-2B987A75D24C> /usr/lib/libbz2.1.0.dylib - 0x7fff8fa7e000 - 0x7fff8fa86ffc libGFXShared.dylib (9.0.83) <11A621C3-37A0-39CE-A69B-8739021BD79D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib - 0x7fff8fab1000 - 0x7fff8fc5ef27 libobjc.A.dylib (551.1) <AD7FD984-271E-30F4-A361-6B20319EC73B> /usr/lib/libobjc.A.dylib - 0x7fff8fc5f000 - 0x7fff8fc68fff com.apple.speech.synthesis.framework (4.6.2 - 4.6.2) <0AAE45F0-FC6E-36B6-A6A7-73E6950A74AC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis - 0x7fff90002000 - 0x7fff9000ffff com.apple.Sharing (132.2 - 132.2) <F983394A-226D-3244-B511-FA51FDB6ADDA> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing - 0x7fff90042000 - 0x7fff90071ff5 com.apple.GSS (4.0 - 2.0) <ED98D992-CC14-39F3-9ABC-8D7F986487CC> /System/Library/Frameworks/GSS.framework/Versions/A/GSS - 0x7fff90072000 - 0x7fff90072fff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices - 0x7fff90073000 - 0x7fff900c5fff libc++.1.dylib (120) <4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE> /usr/lib/libc++.1.dylib - 0x7fff90646000 - 0x7fff90646fff com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa - 0x7fff90647000 - 0x7fff90710fff com.apple.LaunchServices (572.23 - 572.23) <8D955BDE-2C4C-3DD4-B4D7-2D916174FE1D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices - 0x7fff90711000 - 0x7fff90762ff3 com.apple.audio.CoreAudio (4.2.0 - 4.2.0) <BF4C2FE3-8BC8-30D1-8347-2A7221268794> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio - 0x7fff90795000 - 0x7fff90858ff7 com.apple.backup.framework (1.5.1 - 1.5.1) <FC4E949B-B41A-3F21-8AF8-AEDB13146FEA> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup - 0x7fff9085f000 - 0x7fff9117b05f com.apple.CoreGraphics (1.600.0 - 599.7) <7D0FD5A7-A061-39BA-8E00-723825D2C4DD> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics - 0x7fff9117c000 - 0x7fff911bbfff libGLU.dylib (9.0.83) <8B457205-513B-3477-AE9C-3AD979D5FE11> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib - 0x7fff91291000 - 0x7fff912acff7 libPng.dylib (1038) <EF781AF8-C2E6-3179-B8A1-A584783070F1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib - 0x7fff912b0000 - 0x7fff912bbff7 com.apple.NetAuth (5.0 - 5.0) <C811E662-9EC3-3B74-808A-A75D624F326B> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth - 0x7fff912bc000 - 0x7fff912e3ff7 libsystem_network.dylib (241.3) <8B1E1F1D-A5CC-3BAE-8B1E-ABC84337A364> /usr/lib/system/libsystem_network.dylib - 0x7fff912e4000 - 0x7fff912e4ffd libOpenScriptingUtil.dylib (157) <19F0E769-0989-3062-9AFB-8976E90E9759> /usr/lib/libOpenScriptingUtil.dylib - 0x7fff91426000 - 0x7fff9144aff7 libJPEG.dylib (1038) <86F349A8-882D-3326-A0B0-63257F68B1A7> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib - 0x7fff916fe000 - 0x7fff91700fff libCVMSPluginSupport.dylib (9.0.83) <E2AED858-6EEB-36C6-8C06-C3CF649A3CD5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib - 0x7fff91701000 - 0x7fff91701fff com.apple.Accelerate.vecLib (3.9 - vecLib 3.9) <F8D0CC77-98AC-3B58-9FE6-0C25421827B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib - 0x7fff9172a000 - 0x7fff9172fff7 libunwind.dylib (35.3) <78DCC358-2FC1-302E-B395-0155B47CB547> /usr/lib/system/libunwind.dylib - 0x7fff91ff7000 - 0x7fff9201effb libsystem_info.dylib (449.1.3) <7D41A156-D285-3849-A2C3-C04ADE797D98> /usr/lib/system/libsystem_info.dylib - 0x7fff920c3000 - 0x7fff92130fff com.apple.SearchKit (1.4.0 - 1.4.0) <B9B8D510-A27E-36B0-93E9-17146D9E9045> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit - 0x7fff92131000 - 0x7fff92389ff1 com.apple.security (7.0 - 55471) <233831C5-C457-3AD5-AFE7-E3E2DE6929C9> /System/Library/Frameworks/Security.framework/Versions/A/Security - 0x7fff92397000 - 0x7fff9266bfc7 com.apple.vImage (7.0 - 7.0) <D241DBFA-AC49-31E2-893D-EAAC31890C90> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage - 0x7fff92f4f000 - 0x7fff92f69fff libdispatch.dylib (339.1.9) <46878A5B-4248-3057-962C-6D4A235EEF31> /usr/lib/system/libdispatch.dylib - 0x7fff92f6a000 - 0x7fff92f92ffb libxslt.1.dylib (13) <C9794936-633C-3F0C-9E71-30190B9B41C1> /usr/lib/libxslt.1.dylib - 0x7fff93591000 - 0x7fff935d3ff7 libauto.dylib (185.5) <F45C36E8-B606-3886-B5B1-B6745E757CA8> /usr/lib/libauto.dylib - 0x7fff935d4000 - 0x7fff93604fff com.apple.IconServices (25 - 25.17) <4751127E-FBD5-3ED5-8510-08D4E4166EFE> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices - 0x7fff937e6000 - 0x7fff93820ff3 com.apple.bom (12.0 - 192) <989690DB-B9CC-3DB5-89AE-B5D33EDC474E> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom - 0x7fff9397e000 - 0x7fff93aecff7 libBLAS.dylib (1094.5) <DE93A590-5FA5-32A2-A16C-5D7D7361769F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib - 0x7fff93b18000 - 0x7fff93b1bfff com.apple.TCC (1.0 - 1) <32A075D9-47FD-3E71-95BC-BFB0D583F41C> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC - 0x7fff93b1c000 - 0x7fff93b20fff libpam.2.dylib (20) <B93CE8F5-DAA8-30A1-B1F6-F890509513CB> /usr/lib/libpam.2.dylib - 0x7fff93c44000 - 0x7fff94077ffb com.apple.vision.FaceCore (3.0.0 - 3.0.0) <F42BFC9C-0B16-35EF-9A07-91B7FDAB7FC5> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore - 0x7fff94101000 - 0x7fff94174ffb com.apple.securityfoundation (6.0 - 55122) <119D1C53-B292-3378-AEE1-A3B1FB02F43F> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation - 0x7fff94180000 - 0x7fff9418dff7 libxar.1.dylib (202) <5572AA71-E98D-3FE1-9402-BB4A84E0E71E> /usr/lib/libxar.1.dylib - 0x7fff941a2000 - 0x7fff941a4fff libRadiance.dylib (1038) <55F99274-5074-3C73-BAC5-AF234E71CF38> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib - 0x7fff9420c000 - 0x7fff94259ff2 com.apple.print.framework.PrintCore (9.0 - 428) <8D8253E3-302F-3DB2-9C5C-572CB974E8B3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore - 0x7fff9425a000 - 0x7fff9425ffff com.apple.DiskArbitration (2.6 - 2.6) <F8A47F61-83D1-3F92-B7A8-A169E0D187C0> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration - 0x7fff94260000 - 0x7fff94270fff libbsm.0.dylib (33) <2CAC00A2-1352-302A-88FA-C567D4D69179> /usr/lib/libbsm.0.dylib - 0x7fff942c5000 - 0x7fff942cfff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <2D27B498-BB9C-3D88-B05A-76908A8A26F3> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement - 0x7fff942d0000 - 0x7fff942f5ff7 com.apple.CoreVideo (1.8 - 117.2) <4674339E-26D0-35FA-9958-422832B39B12> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo - 0x7fff942f8000 - 0x7fff94346fff libcorecrypto.dylib (161.1) <F3973C28-14B6-3006-BB2B-00DD7F09ABC7> /usr/lib/system/libcorecrypto.dylib - 0x7fff94347000 - 0x7fff9434affc com.apple.IOSurface (91 - 91) <07CA8A59-1E32-3FB6-B506-18DAF58A8CE0> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface - 0x7fff9434b000 - 0x7fff94354ff3 libsystem_notify.dylib (121) <52571EC3-6894-37E4-946E-064B021ED44E> /usr/lib/system/libsystem_notify.dylib - 0x7fff943ae000 - 0x7fff943c0ff7 com.apple.MultitouchSupport.framework (245.13 - 245.13) <D5E7416D-45AB-3690-86C6-CC4B5FCEA2D2> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport - 0x7fff943c1000 - 0x7fff9455dff7 com.apple.QuartzCore (1.8 - 332.0) <994D1E0A-64B6-398C-B9A2-C362F02DE943> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore - 0x7fff94953000 - 0x7fff94a42fff libFontParser.dylib (111.1) <835A8253-6AB9-3AAB-9CBF-171440DEC486> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib - 0x7fff94a44000 - 0x7fff94a68fff libxpc.dylib (300.1.17) <4554927A-9467-365C-91F1-5A116989DD7F> /usr/lib/system/libxpc.dylib - 0x7fff94a69000 - 0x7fff94ab0fff libFontRegistry.dylib (127) <A77A0480-AA5D-3CC8-8B68-69985CD546DC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib - 0x7fff94b00000 - 0x7fff94b53fff com.apple.ScalableUserInterface (1.0 - 1) <CF745298-7373-38D2-B3B1-727D5A569E48> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface - 0x7fff94b5e000 - 0x7fff94b6cfff com.apple.opengl (9.0.83 - 9.0.83) <AF467644-7B1D-327A-AC47-CECFCAF61990> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL - 0x7fff94b8a000 - 0x7fff94b91ff7 liblaunch.dylib (842.1.4) <FCBF0A02-0B06-3F97-9248-5062A9DEB32C> /usr/lib/system/liblaunch.dylib - 0x7fff94b92000 - 0x7fff94b9dfff libkxld.dylib (2422.1.72) <C88EF3E6-B31F-3E12-BE9B-562D912BA733> /usr/lib/system/libkxld.dylib - 0x7fff94ec9000 - 0x7fff94ec9ff7 libkeymgr.dylib (28) <3AA8D85D-CF00-3BD3-A5A0-E28E1A32A6D8> /usr/lib/system/libkeymgr.dylib - 0x7fff94eca000 - 0x7fff94f23fff libTIFF.dylib (1038) <5CBFE0C2-9DD8-340B-BA63-A94CE2E476F2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib - 0x7fff94f24000 - 0x7fff94f3fff7 libsystem_malloc.dylib (23.1.10) <FFE5C472-B23A-318A-85BF-77CDE61900D1> /usr/lib/system/libsystem_malloc.dylib - 0x7fff950ab000 - 0x7fff950dafd2 libsystem_m.dylib (3047.16) <B7F0E2E4-2777-33FC-A787-D6430B630D54> /usr/lib/system/libsystem_m.dylib - 0x7fff950db000 - 0x7fff950e3ff7 com.apple.speech.recognition.framework (4.2.4 - 4.2.4) <98BBB3E4-6239-3EF1-90B2-84EA0D3B8D61> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition - 0x7fff950e6000 - 0x7fff950e7ff7 libsystem_blocks.dylib (63) <FB856CD1-2AEA-3907-8E9B-1E54B6827F82> /usr/lib/system/libsystem_blocks.dylib - 0x7fff950ef000 - 0x7fff952d4ff7 com.apple.CoreFoundation (6.9 - 855.11) <E22C6A1F-8996-349C-905E-96C3BBE07C2F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - 0x7fff952d5000 - 0x7fff952ecfff com.apple.CFOpenDirectory (10.9 - 173.1.1) <3FB4D5FE-860B-3BDE-BAE2-3531D919EF10> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory - 0x7fff953a1000 - 0x7fff953a5ff7 libGIF.dylib (1038) <C29B4323-1B9E-36B9-96C2-7CEDBAA124F0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib - 0x7fff958d8000 - 0x7fff958e2ff7 com.apple.CrashReporterSupport (10.9 - 538) <B487466B-3AA1-3854-A808-A61F049FA794> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport - 0x7fff958e3000 - 0x7fff95bb1ff4 com.apple.CoreImage (9.0.54) <74BB8685-69A9-3A45-8DED-EA26BD39D710> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage - 0x7fff95e9a000 - 0x7fff95e9bfff com.apple.TrustEvaluationAgent (2.0 - 25) <334A82F4-4AE4-3719-A511-86D0B0723E2B> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent - 0x7fff95e9c000 - 0x7fff95f4cff7 libvMisc.dylib (423.32) <049C0735-1808-39B9-943F-76CB8021744F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib - 0x7fff95fa5000 - 0x7fff95faefff com.apple.CommonAuth (4.0 - 2.0) <1D263127-5F27-3128-996D-7397660D0C6E> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth - 0x7fff95fd9000 - 0x7fff96283ffd com.apple.HIToolbox (2.1 - 696) <1CFFF37B-C392-3088-B0A4-C08C55B2AF8F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox - 0x7fff962bc000 - 0x7fff962fdfff com.apple.PerformanceAnalysis (1.47 - 47) <784ED7B8-FAE4-36CE-8C76-B7D300316C9F> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis - 0x7fff96478000 - 0x7fff96482fff libcommonCrypto.dylib (60049) <8C4F0CA0-389C-3EDC-B155-E62DD2187E1D> /usr/lib/system/libcommonCrypto.dylib - 0x7fff96483000 - 0x7fff9648afff libcompiler_rt.dylib (35) <4CD916B2-1B17-362A-B403-EF24A1DAC141> /usr/lib/system/libcompiler_rt.dylib - 0x7fff965c3000 - 0x7fff965c4ff7 libsystem_sandbox.dylib (278.10) <A47E7E11-3C76-318E-B67D-98972B86F094> /usr/lib/system/libsystem_sandbox.dylib - 0x7fff9752f000 - 0x7fff97777fff com.apple.CoreData (107 - 481) <E5AFBA07-F73E-3B3F-9099-F51224EE8EAD> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData - 0x7fff97849000 - 0x7fff97930ff7 libxml2.2.dylib (26) <A1DADD11-89E5-3DE4-8802-07186225967F> /usr/lib/libxml2.2.dylib - 0x7fff97958000 - 0x7fff97974ff7 libsystem_kernel.dylib (2422.1.72) <D14913DB-47F1-3591-8DAF-D4B4EF5F8818> /usr/lib/system/libsystem_kernel.dylib - 0x7fff97a67000 - 0x7fff97ae7fff com.apple.CoreSymbolication (3.0 - 141) <B018335C-698B-3F87-AF1C-6115C4FA8954> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication - 0x7fff97ae8000 - 0x7fff97bedfff com.apple.ImageIO.framework (3.3.0 - 1038) <2C058216-C6D8-3380-A7EA-92A3F04520C1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO - 0x7fff97ca5000 - 0x7fff97d2eff7 libsystem_c.dylib (997.1.1) <61833FAA-7281-3FF9-937F-686B6F20427C> /usr/lib/system/libsystem_c.dylib - 0x7fff97d45000 - 0x7fff97d5eff7 com.apple.Ubiquity (1.3 - 289) <C7F1B734-CE81-334D-BE41-8B20D95A1F9B> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity - 0x7fff97d64000 - 0x7fff97e94ff7 com.apple.desktopservices (1.8 - 1.8) <09DC9BB8-432F-3C7A-BB08-956A2DDFC2DE> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv - 0x7fff97f05000 - 0x7fff98075ff6 com.apple.CFNetwork (673.0.3 - 673.0.3) <42CFC3DB-35C8-3652-AF37-4BCC73D8BDEF> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork - 0x7fff98076000 - 0x7fff980e0ff7 com.apple.framework.IOKit (2.0.1 - 907.1.13) <C1E95F5C-B79B-31BE-9F2A-1B25163C1F16> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit - 0x7fff9877f000 - 0x7fff987e2ff7 com.apple.SystemConfiguration (1.13 - 1.13) <F05F4149-981B-380B-8F50-51CE804BBB89> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration - 0x7fff988e8000 - 0x7fff9894cff9 com.apple.Heimdal (4.0 - 2.0) <E7D20A4D-4674-37E1-A949-635FFF7C439A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal - 0x7fff9894d000 - 0x7fff98a18fff libvDSP.dylib (423.32) <3BF732BE-DDE0-38EB-8C54-E4E3C64F77A7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib - 0x7fff98ba3000 - 0x7fff98babfff libsystem_dnssd.dylib (522.1.11) <270DCF6C-502D-389A-AA9F-DE4624A36FF7> /usr/lib/system/libsystem_dnssd.dylib - 0x7fff98bac000 - 0x7fff98baffff libCoreVMClient.dylib (58.1) <EBC36C69-C896-3C3D-8589-3E9023E7E56F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib - 0x7fff98bb0000 - 0x7fff98c72ff1 com.apple.CoreText (352.0 - 367.15) <E5C70FC8-C861-39B8-A491-595E5B55CFC8> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText - 0x7fff98c73000 - 0x7fff98c7fff7 com.apple.OpenDirectory (10.9 - 173.1.1) <6B78BD7B-5622-38E6-8FC6-86A117E3ACCA> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory - 0x7fff98c80000 - 0x7fff98caffff com.apple.DebugSymbols (106 - 106) <E1BDED08-523A-36F4-B2DA-9D5C712F0AC7> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols - 0x7fff98cb0000 - 0x7fff98d9efff libJP2.dylib (1038) <6C8179F5-8063-3ED6-A7C2-D5603DECDF28> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib - 0x7fff98e1f000 - 0x7fff98f03fff com.apple.coreui (2.1 - 231) <432DB40C-6B7E-39C8-9FB5-B95917930056> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI - 0x7fff98f6f000 - 0x7fff98f73fff libsystem_stats.dylib (93.1.26) <B9E26A9E-FBBC-3938-B8B7-6CF7CA8C99AD> /usr/lib/system/libsystem_stats.dylib - 0x7fff98f74000 - 0x7fff98ffdfff com.apple.ColorSync (4.9.0 - 4.9.0) <B756B908-9AD1-3F5D-83F9-7A0B068387D2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync - 0x7fff99029000 - 0x7fff9908dff3 com.apple.datadetectorscore (5.0 - 354.0) <9ACF24B8-3268-3134-A5BC-D72C9371A195> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore - 0x7fff993e4000 - 0x7fff993ebff3 libcopyfile.dylib (103) <5A881779-D0D6-3029-B371-E3021C2DDA5E> /usr/lib/system/libcopyfile.dylib - 0x7fff994a3000 - 0x7fff99512ff1 com.apple.ApplicationServices.ATS (360 - 363.1) <88976B22-A9B8-3E7B-9AE6-0B8E09A968FC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS - 0x7fff99513000 - 0x7fff9952ffff libresolv.9.dylib (54) <11C2C826-F1C6-39C6-B4E8-6E0C41D4FA95> /usr/lib/libresolv.9.dylib - 0x7fff99530000 - 0x7fff9953fff8 com.apple.LangAnalysis (1.7.0 - 1.7.0) <8FE131B6-1180-3892-98F5-C9C9B79072D4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis - 0x7fff99656000 - 0x7fff9966fff7 com.apple.Kerberos (3.0 - 1) <F108AFEB-198A-3BAF-BCA5-9DFCE55EFF92> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos - 0x7fff99673000 - 0x7fff99674ffb libremovefile.dylib (33) <3543F917-928E-3DB2-A2F4-7AB73B4970EF> /usr/lib/system/libremovefile.dylib - 0x7fff99675000 - 0x7fff99676ff7 libSystem.B.dylib (1197.1.1) <BFC0DC97-46C6-3BE0-9983-54A98734897A> /usr/lib/libSystem.B.dylib - 0x7fff99c76000 - 0x7fff99c87ff7 libsystem_asl.dylib (217.1.4) <655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib - 0x7fff99c88000 - 0x7fff99f72fff com.apple.CoreServices.CarbonCore (1077.14 - 1077.14) <B00BEB34-A9F5-381F-99FD-11E405768A9A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore - 0x7fff99f73000 - 0x7fff99feafff com.apple.CoreServices.OSServices (600.4 - 600.4) <36B2B009-C35E-3F21-824E-E0D00E7808C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices - 0x7fff99feb000 - 0x7fff9a014ff7 libc++abi.dylib (48) <8C16158F-CBF8-3BD7-BEF4-022704B2A326> /usr/lib/libc++abi.dylib - 0x7fff9a076000 - 0x7fff9a0aeff7 com.apple.RemoteViewServices (2.0 - 94) <3F34D630-3DDB-3411-BC28-A56A9B55EBDA> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices - 0x7fff9a0ca000 - 0x7fff9a0d1ff7 libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib - 0x7fff9a0d2000 - 0x7fff9a0d2fff com.apple.Accelerate (1.9 - Accelerate 1.9) <509BB27A-AE62-366D-86D8-0B06D217CF56> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate - 0x7fff9a0d3000 - 0x7fff9a1bdfff libsqlite3.dylib (158) <00269BF9-43BE-39E0-9C85-24585B9923C8> /usr/lib/libsqlite3.dylib - 0x7fff9a248000 - 0x7fff9a2a3ffb com.apple.AE (665.5 - 665.5) <BBA230F9-144C-3CAB-A77A-0621719244CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE - 0x7fff9a517000 - 0x7fff9a565fff com.apple.opencl (2.3.57 - 2.3.57) <FC03A80D-543A-3448-83FF-D399C3A240D9> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL - 0x7fff9a566000 - 0x7fff9a569ff7 libdyld.dylib (239.3) <62F4D752-4089-31A8-8B73-B95A68893B3C> /usr/lib/system/libdyld.dylib - 0x7fff9a571000 - 0x7fff9a729ff3 libicucore.A.dylib (511.27) <003B6C21-CBD1-3486-9A1D-030ADF5FA061> /usr/lib/libicucore.A.dylib - 0x7fff9a72a000 - 0x7fff9a753fff com.apple.DictionaryServices (1.2 - 208) <A539A058-BA57-35EE-AA08-D0B0E835127D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices - 0x7fff9a75a000 - 0x7fff9a766ff3 com.apple.AppleFSCompression (56 - 1.0) <5652B0D0-EB08-381F-B23A-6DCF96991FB5> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression - 0x7fff9a8f5000 - 0x7fff9a90dff7 com.apple.GenerationalStorage (2.0 - 160.2) <79629AC7-896F-3302-8AC1-4939020F08C3> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage - 0x7fff9a939000 - 0x7fff9a954ff7 libCRFSuite.dylib (34) <FFAE75FA-C54E-398B-AA97-18164CD9789D> /usr/lib/libCRFSuite.dylib - 0x7fff9ab57000 - 0x7fff9ab59ff7 libquarantine.dylib (71) <7A1A2BCB-C03D-3A25-BFA4-3E569B2D2C38> /usr/lib/system/libquarantine.dylib - 0x7fff9ab5a000 - 0x7fff9ab5affd com.apple.audio.units.AudioUnit (1.9 - 1.9) <6E89F3CB-CC41-3728-9F9A-FDFC151E8261> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit - 0x7fff9ac14000 - 0x7fff9ac59ff6 com.apple.HIServices (1.22 - 466) <21807AF8-3BC7-32BB-AB96-7C35CB59D7F6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices - 0x7fff9ac5a000 - 0x7fff9ac5afff com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices - 0x7fff9adc0000 - 0x7fff9ade5ff7 com.apple.ChunkingLibrary (2.0 - 155.1) <B845DC7A-D1EA-31E2-967C-D1FE0C628036> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary - - External Modification Summary: - Calls made by other processes targeting this process: - task_for_pid: 1 - thread_create: 0 - thread_set_state: 0 - Calls made by this process: - task_for_pid: 0 - thread_create: 0 - thread_set_state: 0 - Calls made by all processes on this machine: - task_for_pid: 210855 - thread_create: 1 - thread_set_state: 0 - - VM Region Summary: - ReadOnly portion of Libraries: Total=206.9M resident=76.3M(37%) swapped_out_or_unallocated=130.6M(63%) - Writable regions: Total=51.2M written=15.3M(30%) resident=16.2M(32%) swapped_out=0K(0%) unallocated=35.0M(68%) - - REGION TYPE VIRTUAL - =========== ======= - Dispatch continuations 4096K - Kernel Alloc Once 4K - MALLOC 18.3M - MALLOC (admin) 32K - STACK GUARD 56.0M - Stack 12.6M - VM_ALLOCATE 12.3M - VM_ALLOCATE (reserved) 12K reserved VM address space (unallocated) - __DATA 22.9M - __IMAGE 528K - __LINKEDIT 71.2M - __TEXT 135.6M - __UNICODE 544K - shared memory 4K - =========== ======= - TOTAL 334.2M - TOTAL, minus reserved VM space 334.2M - -# End of transcript or log. -"""]] - -> Apparently this is [[fixed|done]] in the latest release. --[[Joey]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_10_8d90e23514d9f14283857c57017a5fcf._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_10_8d90e23514d9f14283857c57017a5fcf._comment deleted file mode 100644 index ef7579c46..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_10_8d90e23514d9f14283857c57017a5fcf._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.68" - subject="comment 10" - date="2014-01-20T16:28:43Z" - content=""" -I have updated the autobuild again, now nettle is built with more optimisations disabled. I hope this fixes it because I'm running out of things to try. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_11_1a0e174969e99e7b562854d2c3b3e606._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_11_1a0e174969e99e7b562854d2c3b3e606._comment deleted file mode 100644 index 5b5b94a40..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_11_1a0e174969e99e7b562854d2c3b3e606._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="Past the SHA issues" - date="2014-01-20T23:14:53Z" - content=""" -Now we still have an issue with nettle, but now it's part of urandom. I'm not sure what to suggest... - -[[!format sh \"\"\" -Thread 1 Crashed: -0 H 0x00000001075d9756 do_device_source_urandom + 108 -1 H 0x00000001075d9686 do_device_source + 46 -2 H 0x00000001075d92b9 wrap_nettle_rnd_init + 74 -3 H 0x000000010755d585 _gnutls_rnd_init + 32 -4 H 0x0000000107551dae gnutls_global_init + 262 -5 git-annex 0x00000001054a28c3 0x103c83000 + 25295043 -6 git-annex 0x000000010692ab28 0x103c83000 + 46824232 -\"\"\"]] -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_12_dfde39222a91923c570e5405d9e527f4._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_12_dfde39222a91923c570e5405d9e527f4._comment deleted file mode 100644 index cd2047a93..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_12_dfde39222a91923c570e5405d9e527f4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="Seems to be working now" - date="2014-03-12T02:36:59Z" - content=""" -Just tried again off of the most recent osx release build and it appears to be working without crashing. Not sure what else you did but thanks! -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_13_65de2b5dd3af89c2f0f6508ffddda3b5._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_13_65de2b5dd3af89c2f0f6508ffddda3b5._comment deleted file mode 100644 index 3a02f2f8c..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_13_65de2b5dd3af89c2f0f6508ffddda3b5._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 13" - date="2014-03-12T17:01:12Z" - content=""" -Well that's good and unexpected news! - -I did make some changes on the OSX autobuilder recently. For one thing, I updated and rebuilt all the homebrew stuff, and remembered to pass --build-bottle when doing so. Which I think I had always done before.. Homebrew also removed some dependencies on gnutls in wget, and perhaps they also made other changes -- I'd not be surprised if a change to homebrew made --build-bottle start disabling some optimisations. - -In any case, I suppose I can close this bug now.. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_1_804c394e97223b1f9cc9f1f3adaa2e74._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_1_804c394e97223b1f9cc9f1f3adaa2e74._comment deleted file mode 100644 index f8c36c1fd..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_1_804c394e97223b1f9cc9f1f3adaa2e74._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 1" - date="2014-01-14T20:54:52Z" - content=""" -This must be more stuff on the OSX build machine that is using processor-specific optimisations. Similar to previously fixed problems with wget etc being built with those optimisations. - -This time, it must be one of the several libraries git-annex links with, and only one that is used when using XMPP. So, one of libxml2, libidn, libgsasl, libgnutls. - -I have replaced all of those libraries with unoptimised ones built with `brew install --build-bottle`. This is available in the daily built app now. Since I cannot test it myself, please download that <https://downloads.kitenet.net/git-annex/autobuild/x86_64-apple-mavericks/git-annex.dmg> and let me know how it goes. - - -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_2_f1fe0c05724236988e77f4b7f393e7d5._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_2_f1fe0c05724236988e77f4b7f393e7d5._comment deleted file mode 100644 index 1131f74a1..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_2_f1fe0c05724236988e77f4b7f393e7d5._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="Different Crash on startup" - date="2014-01-14T22:40:26Z" - content=""" -dyld: Library not loaded: /usr/local/opt/libxml2/lib/libxml2.2.dylib - Referenced from: /Applications/git-annex.app/Contents/MacOs/bundle/git-annex - Reason: Incompatible library version: git-annex requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 - -I think the problem at this point is I don't have brew installed though. I'll try to do that later tonight. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_3_3d9ec79231e1b340b5e8b7b63a902546._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_3_3d9ec79231e1b340b5e8b7b63a902546._comment deleted file mode 100644 index d11cf6b77..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_3_3d9ec79231e1b340b5e8b7b63a902546._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawn_3tllXjSmtgm__aGr9Z4gVNFgJgGyJ30" - nickname="David Alan" - subject="Partly fixed?" - date="2014-01-15T01:35:19Z" - content=""" -The new build fixed it for me on Mac OS 10.8.5 but not on 10.9.1 -Using the app, it won't start anything on 10.9.1 now. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_4_f63bb1d29fc7130bfa0c15feeba4e5fd._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_4_f63bb1d29fc7130bfa0c15feeba4e5fd._comment deleted file mode 100644 index e76fecc3c..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_4_f63bb1d29fc7130bfa0c15feeba4e5fd._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="comment 4" - date="2014-01-15T02:21:38Z" - content=""" -The problem on 10.9.1 appears to be related to the version of libxml2 thats being used. There is a console message on startup that shows this: - - dyld: Library not loaded: /usr/local/opt/libxml2/lib/libxml2.2.dylib - Referenced from: /Applications/git-annex.app/Contents/MacOs/bundle/git-annex - Reason: Incompatible library version: git-annex requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 - - I have actually been unable to build the newest version of libxml2 which I guess will have a library version 12 on mavericks so far tonight via Brew. I keep getting errors like: - - /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/sys/_types.h:132:9: error: unknown type name '__int32_t' - typedef __int32_t __darwin_suseconds_t; /* [???] microseconds */ - -So far the interwebs are failing me and I don't have a solution. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_5_a024902e300cf50e8f6a63c7feef63a1._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_5_a024902e300cf50e8f6a63c7feef63a1._comment deleted file mode 100644 index f8cb706e5..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_5_a024902e300cf50e8f6a63c7feef63a1._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 5" - date="2014-01-15T17:28:56Z" - content=""" -It's not supposed to use the system version of libxml2 etc. I have updated the build with the problem that was causing it to do so fixed, please re-test. - -BTW, I am surprised that you report the Mavericks build works on 10.8.5 -- isn't that snow leopard? -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_6_baf0333f307dff0f79cd7c73b4c56c18._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_6_baf0333f307dff0f79cd7c73b4c56c18._comment deleted file mode 100644 index f8d04af92..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_6_baf0333f307dff0f79cd7c73b4c56c18._comment +++ /dev/null @@ -1,356 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="Still crashing " - date="2014-01-15T22:36:15Z" - content=""" -But it's a different crash now. Previously the thread that crashed was doing xml related things. Now the crash is doing what looks like hash related things. - -[[!format sh \"\"\" - -Process: git-annex [27419] -Path: /Applications/git-annex.app/Contents/MacOS/bundle/git-annex -Identifier: git-annex -Version: 0 -Code Type: X86-64 (Native) -Parent Process: ??? [1] -Responsible: git-annex [27419] -User ID: 501 - -Date/Time: 2014-01-15 17:31:49.406 -0500 -OS Version: Mac OS X 10.9.1 (13B42) -Report Version: 11 -Anonymous UUID: 43148BA1-3CAA-4C73-2971-CAC673D60B2B - - -Crashed Thread: 1 - -Exception Type: EXC_BAD_INSTRUCTION (SIGILL) -Exception Codes: 0x0000000000000001, 0x0000000000000000 - -Thread 0:: Dispatch queue: com.apple.main-thread -0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 -1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 -2 git-annex 0x000000010a0026f9 0x107364000 + 46786297 -3 git-annex 0x0000000109fdf91b 0x107364000 + 46643483 -4 git-annex 0x0000000109fee362 0x107364000 + 46703458 -5 git-annex 0x0000000109feedd4 0x107364000 + 46706132 -6 git-annex 0x0000000109fe976e 0x107364000 + 46684014 -7 git-annex 0x0000000109fe9876 0x107364000 + 46684278 -8 git-annex 0x0000000107c211e8 0x107364000 + 9163240 -9 libdyld.dylib 0x00007fff9a5695fd start + 1 - -Thread 1 Crashed: -0 V 0x000000010aeb2b9d nettle_sha256_init + 4 -1 V 0x000000010aeb9e60 nettle_yarrow256_init + 24 -2 H 0x000000010acb3293 wrap_nettle_rnd_init + 52 -3 H 0x000000010ac378cf _gnutls_rnd_init + 32 -4 H 0x000000010ac2bfba gnutls_global_init + 262 -5 git-annex 0x0000000108b80873 0x107364000 + 25282675 -6 git-annex 0x000000010a008c08 0x107364000 + 46812168 - -Thread 2: -0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 -1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 -2 git-annex 0x000000010a0026f9 0x107364000 + 46786297 -3 git-annex 0x0000000109fdf91b 0x107364000 + 46643483 -4 git-annex 0x0000000109fee362 0x107364000 + 46703458 -5 git-annex 0x0000000109feecab 0x107364000 + 46705835 -6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 3: -0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 -1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 -2 git-annex 0x000000010a0026f9 0x107364000 + 46786297 -3 git-annex 0x0000000109fdf91b 0x107364000 + 46643483 -4 git-annex 0x0000000109fee362 0x107364000 + 46703458 -5 git-annex 0x0000000109feecab 0x107364000 + 46705835 -6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 4: -0 libsystem_kernel.dylib 0x00007fff9796e662 kevent64 + 10 -1 git-annex 0x0000000109f8e23a 0x107364000 + 46309946 - -Thread 5: -0 libsystem_kernel.dylib 0x00007fff9796d716 __psynch_cvwait + 10 -1 libsystem_pthread.dylib 0x00007fff9a0cdc3b _pthread_cond_wait + 727 -2 git-annex 0x000000010a0026f9 0x107364000 + 46786297 -3 git-annex 0x0000000109fdf91b 0x107364000 + 46643483 -4 git-annex 0x0000000109fee362 0x107364000 + 46703458 -5 git-annex 0x0000000109feecab 0x107364000 + 46705835 -6 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -7 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -8 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 6:: Dispatch queue: com.apple.libdispatch-manager -0 libsystem_kernel.dylib 0x00007fff9796e662 kevent64 + 10 -1 libdispatch.dylib 0x00007fff92f5243d _dispatch_mgr_invoke + 239 -2 libdispatch.dylib 0x00007fff92f52152 _dispatch_mgr_thread + 52 - -Thread 7: -0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 -1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 -2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 -3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 -4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 -5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 -6 git-annex 0x00000001087bd6c8 0x107364000 + 21337800 -7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 8: -0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 -1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 -2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 -3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 -4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 -5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 -6 git-annex 0x00000001087bd6c8 0x107364000 + 21337800 -7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 9: -0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 -1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 -2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 -3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 -4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 -5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 -6 git-annex 0x00000001087bd6c8 0x107364000 + 21337800 -7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 10: -0 libsystem_kernel.dylib 0x00007fff97969a1a mach_msg_trap + 10 -1 libsystem_kernel.dylib 0x00007fff97968d18 mach_msg + 64 -2 com.apple.CoreFoundation 0x00007fff95160315 __CFRunLoopServiceMachPort + 181 -3 com.apple.CoreFoundation 0x00007fff9515f939 __CFRunLoopRun + 1161 -4 com.apple.CoreFoundation 0x00007fff9515f275 CFRunLoopRunSpecific + 309 -5 com.apple.CoreFoundation 0x00007fff952149d1 CFRunLoopRun + 97 -6 git-annex 0x00000001087bd6c8 0x107364000 + 21337800 -7 libsystem_pthread.dylib 0x00007fff9a0cb899 _pthread_body + 138 -8 libsystem_pthread.dylib 0x00007fff9a0cb72a _pthread_start + 137 -9 libsystem_pthread.dylib 0x00007fff9a0cffc9 thread_start + 13 - -Thread 1 crashed with X86 Thread State (64-bit): - rax: 0x0000000000000000 rbx: 0x000000010acd31d0 rcx: 0x0000000000000000 rdx: 0x000000010acd31d0 - rdi: 0x000000010acd2f20 rsi: 0x0000000000000002 rbp: 0x000000010b17cda0 rsp: 0x000000010b17cda0 - r8: 0x0000000000000003 r9: 0x00007fcdbbc00000 r10: 0x000000010aec7208 r11: 0x000000010aeb9e48 - r12: 0x000000010b073d50 r13: 0x000000010a554598 r14: 0x0000000000000002 r15: 0x000000010acd2f20 - rip: 0x000000010aeb2b9d rfl: 0x0000000000010206 cr2: 0x000000010aeb2b99 - -Logical CPU: 1 -Error Code: 0x00000000 -Trap Number: 6 - - -Binary Images: - 0x107364000 - 0x10a188fef +git-annex (0) <81FF250D-D672-3822-B1EB-7AE0378499F6> /Applications/git-annex.app/Contents/MacOS/bundle/git-annex - 0x10aaa5000 - 0x10ab8fff7 +E (0) <6ABB8037-E5D8-31BE-AC66-66C1F9ACB39E> /Applications/git-annex.app/Contents/MacOS/bundle/E - 0x10abc1000 - 0x10abd5fff +F (0) <69078CE7-B622-3D03-A100-6438C3D523F9> /Applications/git-annex.app/Contents/MacOS/bundle/F - 0x10abdc000 - 0x10ac09fff +G (0) <4DF43DFC-832F-3C44-A990-BD3328CE6E2B> /Applications/git-annex.app/Contents/MacOS/bundle/G - 0x10ac10000 - 0x10acc9fe7 +H (0) <70CFD2E5-AE2E-3CA8-A398-B90FBBA66F02> /Applications/git-annex.app/Contents/MacOS/bundle/H - 0x10acf9000 - 0x10ad0aff7 +B (53) <42E0C8C6-CA38-3CA4-8619-D24ED5DD492E> /Applications/git-annex.app/Contents/MacOS/bundle/B - 0x10ad16000 - 0x10ae07ff9 +D (41) <BB44B115-AC32-3877-A0ED-AEC6232A4563> /Applications/git-annex.app/Contents/MacOS/bundle/D - 0x10ae18000 - 0x10ae32ff7 +P (0) <18FCF32F-BAB0-323A-BCAC-D4CE4272B754> /Applications/git-annex.app/Contents/MacOS/bundle/P - 0x10ae71000 - 0x10ae82fff +T (0) <DE89C58A-64F4-3C78-B6AC-A0D0A485B75F> /Applications/git-annex.app/Contents/MacOS/bundle/T - 0x10ae8f000 - 0x10ae9cfff +U (0) <22B05EAF-3BFB-3CC8-AE46-35F548CD7194> /Applications/git-annex.app/Contents/MacOS/bundle/U - 0x10aea3000 - 0x10aec4fff +V (0) <D81BE70A-76E4-32B0-8066-E63D4E0EED16> /Applications/git-annex.app/Contents/MacOS/bundle/V - 0x10aece000 - 0x10aedafff +W (0) <AF6A36A9-D689-3044-8545-656B6B04A9BA> /Applications/git-annex.app/Contents/MacOS/bundle/W - 0x10aee3000 - 0x10af44fff +X (0) <AB4ED07E-0B12-36E9-B513-7F402AE3CCB5> /Applications/git-annex.app/Contents/MacOS/bundle/X - 0x7fff69636000 - 0x7fff69669817 dyld (239.3) <D1DFCF3F-0B0C-332A-BCC0-87A851B570FF> /usr/lib/dyld - 0x7fff8d3b0000 - 0x7fff8d43cff7 com.apple.ink.framework (10.9 - 207) <8A50B893-AD03-3826-8555-A54FEAF08F47> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink - 0x7fff8d44b000 - 0x7fff8d4a3ff7 com.apple.Symbolication (1.4 - 129) <16D42516-7B5E-357C-898A-FAA9EE7642B3> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication - 0x7fff8d515000 - 0x7fff8d516fff libunc.dylib (28) <62682455-1862-36FE-8A04-7A6B91256438> /usr/lib/system/libunc.dylib - 0x7fff8d51c000 - 0x7fff8d522ff7 libsystem_platform.dylib (24.1.4) <331BA4A5-55CE-3B95-99EB-44E0C89D7FB8> /usr/lib/system/libsystem_platform.dylib - 0x7fff8d523000 - 0x7fff8d904ffe libLAPACK.dylib (1094.5) <7E7A9B8D-1638-3914-BAE0-663B69865986> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib - 0x7fff8d952000 - 0x7fff8d959fff com.apple.NetFS (6.0 - 4.0) <8E26C099-CE9D-3819-91A2-64EA929C6137> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS - 0x7fff8d98a000 - 0x7fff8d9c8ff7 libGLImage.dylib (9.0.83) <C08048A7-03CC-3E40-BCDC-7791D87AC8E4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib - 0x7fff8da8d000 - 0x7fff8dd8cfff com.apple.Foundation (6.9 - 1056) <D608EDFD-9634-3573-9B7E-081C7D085F7A> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation - 0x7fff8dfac000 - 0x7fff8dfb0ff7 libheimdal-asn1.dylib (323.12) <063A01C2-E547-39D9-BB42-4CC8E64ADE70> /usr/lib/libheimdal-asn1.dylib - 0x7fff8dfb1000 - 0x7fff8dfb6fff libmacho.dylib (845) <1D2910DF-C036-3A82-A3FD-44FF73B5FF9B> /usr/lib/system/libmacho.dylib - 0x7fff8e022000 - 0x7fff8e024ff3 libsystem_configuration.dylib (596.12) <C4F633D9-94C8-35D9-BB2D-84C5122533C7> /usr/lib/system/libsystem_configuration.dylib - 0x7fff8e35c000 - 0x7fff8e4afff7 com.apple.audio.toolbox.AudioToolbox (1.9 - 1.9) <A0B7B007-9BD8-30E2-B644-47856DA29FEE> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox - 0x7fff8e4ee000 - 0x7fff8f062ff7 com.apple.AppKit (6.9 - 1265) <0E9FC8BF-DA3C-34C5-91CC-12BC922B5F01> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit - 0x7fff8f063000 - 0x7fff8f067ff7 libcache.dylib (62) <BDC1E65B-72A1-3DA3-A57C-B23159CAAD0B> /usr/lib/system/libcache.dylib - 0x7fff8f068000 - 0x7fff8f0a1ff7 com.apple.QD (3.50 - 298) <C1F20764-DEF0-34CF-B3AB-AB5480D64E66> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD - 0x7fff8f0a2000 - 0x7fff8f0adfff libGL.dylib (9.0.83) <984A960A-C159-3AE5-8B40-E2B451F6C712> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib - 0x7fff8f0d7000 - 0x7fff8f0d8ff7 libDiagnosticMessagesClient.dylib (100) <4CDB0F7B-C0AF-3424-BC39-495696F0DB1E> /usr/lib/libDiagnosticMessagesClient.dylib - 0x7fff8f120000 - 0x7fff8f121fff liblangid.dylib (117) <9546E641-F730-3AB0-B3CD-E0E2FDD173D9> /usr/lib/liblangid.dylib - 0x7fff8f122000 - 0x7fff8f169ff7 libcups.2.dylib (372) <348EED62-6C20-35D6-8EFB-E80943965100> /usr/lib/libcups.2.dylib - 0x7fff8f551000 - 0x7fff8f5e0fff com.apple.Metadata (10.7.0 - 800.12.2) <A9F5D471-8732-3F95-A4A2-33864B92A181> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata - 0x7fff8f843000 - 0x7fff8f850ff0 libbz2.1.0.dylib (29) <0B98AC35-B138-349C-8063-2B987A75D24C> /usr/lib/libbz2.1.0.dylib - 0x7fff8fa7e000 - 0x7fff8fa86ffc libGFXShared.dylib (9.0.83) <11A621C3-37A0-39CE-A69B-8739021BD79D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib - 0x7fff8fab1000 - 0x7fff8fc5ef27 libobjc.A.dylib (551.1) <AD7FD984-271E-30F4-A361-6B20319EC73B> /usr/lib/libobjc.A.dylib - 0x7fff8fc5f000 - 0x7fff8fc68fff com.apple.speech.synthesis.framework (4.6.2 - 4.6.2) <0AAE45F0-FC6E-36B6-A6A7-73E6950A74AC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis - 0x7fff90002000 - 0x7fff9000ffff com.apple.Sharing (132.2 - 132.2) <F983394A-226D-3244-B511-FA51FDB6ADDA> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing - 0x7fff90042000 - 0x7fff90071ff5 com.apple.GSS (4.0 - 2.0) <ED98D992-CC14-39F3-9ABC-8D7F986487CC> /System/Library/Frameworks/GSS.framework/Versions/A/GSS - 0x7fff90072000 - 0x7fff90072fff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices - 0x7fff90073000 - 0x7fff900c5fff libc++.1.dylib (120) <4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE> /usr/lib/libc++.1.dylib - 0x7fff90646000 - 0x7fff90646fff com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa - 0x7fff90647000 - 0x7fff90710fff com.apple.LaunchServices (572.23 - 572.23) <8D955BDE-2C4C-3DD4-B4D7-2D916174FE1D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices - 0x7fff90711000 - 0x7fff90762ff3 com.apple.audio.CoreAudio (4.2.0 - 4.2.0) <BF4C2FE3-8BC8-30D1-8347-2A7221268794> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio - 0x7fff90795000 - 0x7fff90858ff7 com.apple.backup.framework (1.5.1 - 1.5.1) <FC4E949B-B41A-3F21-8AF8-AEDB13146FEA> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup - 0x7fff9085f000 - 0x7fff9117b05f com.apple.CoreGraphics (1.600.0 - 599.7) <7D0FD5A7-A061-39BA-8E00-723825D2C4DD> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics - 0x7fff9117c000 - 0x7fff911bbfff libGLU.dylib (9.0.83) <8B457205-513B-3477-AE9C-3AD979D5FE11> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib - 0x7fff91291000 - 0x7fff912acff7 libPng.dylib (1038) <EF781AF8-C2E6-3179-B8A1-A584783070F1> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib - 0x7fff912b0000 - 0x7fff912bbff7 com.apple.NetAuth (5.0 - 5.0) <C811E662-9EC3-3B74-808A-A75D624F326B> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth - 0x7fff912bc000 - 0x7fff912e3ff7 libsystem_network.dylib (241.3) <8B1E1F1D-A5CC-3BAE-8B1E-ABC84337A364> /usr/lib/system/libsystem_network.dylib - 0x7fff912e4000 - 0x7fff912e4ffd libOpenScriptingUtil.dylib (157) <19F0E769-0989-3062-9AFB-8976E90E9759> /usr/lib/libOpenScriptingUtil.dylib - 0x7fff91426000 - 0x7fff9144aff7 libJPEG.dylib (1038) <86F349A8-882D-3326-A0B0-63257F68B1A7> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib - 0x7fff916fe000 - 0x7fff91700fff libCVMSPluginSupport.dylib (9.0.83) <E2AED858-6EEB-36C6-8C06-C3CF649A3CD5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib - 0x7fff91701000 - 0x7fff91701fff com.apple.Accelerate.vecLib (3.9 - vecLib 3.9) <F8D0CC77-98AC-3B58-9FE6-0C25421827B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib - 0x7fff9172a000 - 0x7fff9172fff7 libunwind.dylib (35.3) <78DCC358-2FC1-302E-B395-0155B47CB547> /usr/lib/system/libunwind.dylib - 0x7fff91ff7000 - 0x7fff9201effb libsystem_info.dylib (449.1.3) <7D41A156-D285-3849-A2C3-C04ADE797D98> /usr/lib/system/libsystem_info.dylib - 0x7fff920c3000 - 0x7fff92130fff com.apple.SearchKit (1.4.0 - 1.4.0) <B9B8D510-A27E-36B0-93E9-17146D9E9045> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit - 0x7fff92131000 - 0x7fff92389ff1 com.apple.security (7.0 - 55471) <233831C5-C457-3AD5-AFE7-E3E2DE6929C9> /System/Library/Frameworks/Security.framework/Versions/A/Security - 0x7fff92397000 - 0x7fff9266bfc7 com.apple.vImage (7.0 - 7.0) <D241DBFA-AC49-31E2-893D-EAAC31890C90> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage - 0x7fff92f4f000 - 0x7fff92f69fff libdispatch.dylib (339.1.9) <46878A5B-4248-3057-962C-6D4A235EEF31> /usr/lib/system/libdispatch.dylib - 0x7fff92f6a000 - 0x7fff92f92ffb libxslt.1.dylib (13) <C9794936-633C-3F0C-9E71-30190B9B41C1> /usr/lib/libxslt.1.dylib - 0x7fff93591000 - 0x7fff935d3ff7 libauto.dylib (185.5) <F45C36E8-B606-3886-B5B1-B6745E757CA8> /usr/lib/libauto.dylib - 0x7fff935d4000 - 0x7fff93604fff com.apple.IconServices (25 - 25.17) <4751127E-FBD5-3ED5-8510-08D4E4166EFE> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices - 0x7fff937e6000 - 0x7fff93820ff3 com.apple.bom (12.0 - 192) <989690DB-B9CC-3DB5-89AE-B5D33EDC474E> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom - 0x7fff9397e000 - 0x7fff93aecff7 libBLAS.dylib (1094.5) <DE93A590-5FA5-32A2-A16C-5D7D7361769F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib - 0x7fff93b18000 - 0x7fff93b1bfff com.apple.TCC (1.0 - 1) <32A075D9-47FD-3E71-95BC-BFB0D583F41C> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC - 0x7fff93b1c000 - 0x7fff93b20fff libpam.2.dylib (20) <B93CE8F5-DAA8-30A1-B1F6-F890509513CB> /usr/lib/libpam.2.dylib - 0x7fff93c44000 - 0x7fff94077ffb com.apple.vision.FaceCore (3.0.0 - 3.0.0) <F42BFC9C-0B16-35EF-9A07-91B7FDAB7FC5> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore - 0x7fff94101000 - 0x7fff94174ffb com.apple.securityfoundation (6.0 - 55122) <119D1C53-B292-3378-AEE1-A3B1FB02F43F> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation - 0x7fff94180000 - 0x7fff9418dff7 libxar.1.dylib (202) <5572AA71-E98D-3FE1-9402-BB4A84E0E71E> /usr/lib/libxar.1.dylib - 0x7fff941a2000 - 0x7fff941a4fff libRadiance.dylib (1038) <55F99274-5074-3C73-BAC5-AF234E71CF38> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib - 0x7fff9420c000 - 0x7fff94259ff2 com.apple.print.framework.PrintCore (9.0 - 428) <8D8253E3-302F-3DB2-9C5C-572CB974E8B3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore - 0x7fff9425a000 - 0x7fff9425ffff com.apple.DiskArbitration (2.6 - 2.6) <F8A47F61-83D1-3F92-B7A8-A169E0D187C0> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration - 0x7fff94260000 - 0x7fff94270fff libbsm.0.dylib (33) <2CAC00A2-1352-302A-88FA-C567D4D69179> /usr/lib/libbsm.0.dylib - 0x7fff942c5000 - 0x7fff942cfff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <2D27B498-BB9C-3D88-B05A-76908A8A26F3> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement - 0x7fff942d0000 - 0x7fff942f5ff7 com.apple.CoreVideo (1.8 - 117.2) <4674339E-26D0-35FA-9958-422832B39B12> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo - 0x7fff942f8000 - 0x7fff94346fff libcorecrypto.dylib (161.1) <F3973C28-14B6-3006-BB2B-00DD7F09ABC7> /usr/lib/system/libcorecrypto.dylib - 0x7fff94347000 - 0x7fff9434affc com.apple.IOSurface (91 - 91) <07CA8A59-1E32-3FB6-B506-18DAF58A8CE0> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface - 0x7fff9434b000 - 0x7fff94354ff3 libsystem_notify.dylib (121) <52571EC3-6894-37E4-946E-064B021ED44E> /usr/lib/system/libsystem_notify.dylib - 0x7fff943ae000 - 0x7fff943c0ff7 com.apple.MultitouchSupport.framework (245.13 - 245.13) <D5E7416D-45AB-3690-86C6-CC4B5FCEA2D2> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport - 0x7fff943c1000 - 0x7fff9455dff7 com.apple.QuartzCore (1.8 - 332.0) <994D1E0A-64B6-398C-B9A2-C362F02DE943> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore - 0x7fff94953000 - 0x7fff94a42fff libFontParser.dylib (111.1) <835A8253-6AB9-3AAB-9CBF-171440DEC486> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib - 0x7fff94a44000 - 0x7fff94a68fff libxpc.dylib (300.1.17) <4554927A-9467-365C-91F1-5A116989DD7F> /usr/lib/system/libxpc.dylib - 0x7fff94a69000 - 0x7fff94ab0fff libFontRegistry.dylib (127) <A77A0480-AA5D-3CC8-8B68-69985CD546DC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib - 0x7fff94b00000 - 0x7fff94b53fff com.apple.ScalableUserInterface (1.0 - 1) <CF745298-7373-38D2-B3B1-727D5A569E48> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface - 0x7fff94b5e000 - 0x7fff94b6cfff com.apple.opengl (9.0.83 - 9.0.83) <AF467644-7B1D-327A-AC47-CECFCAF61990> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL - 0x7fff94b8a000 - 0x7fff94b91ff7 liblaunch.dylib (842.1.4) <FCBF0A02-0B06-3F97-9248-5062A9DEB32C> /usr/lib/system/liblaunch.dylib - 0x7fff94b92000 - 0x7fff94b9dfff libkxld.dylib (2422.1.72) <C88EF3E6-B31F-3E12-BE9B-562D912BA733> /usr/lib/system/libkxld.dylib - 0x7fff94ec9000 - 0x7fff94ec9ff7 libkeymgr.dylib (28) <3AA8D85D-CF00-3BD3-A5A0-E28E1A32A6D8> /usr/lib/system/libkeymgr.dylib - 0x7fff94eca000 - 0x7fff94f23fff libTIFF.dylib (1038) <5CBFE0C2-9DD8-340B-BA63-A94CE2E476F2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib - 0x7fff94f24000 - 0x7fff94f3fff7 libsystem_malloc.dylib (23.1.10) <FFE5C472-B23A-318A-85BF-77CDE61900D1> /usr/lib/system/libsystem_malloc.dylib - 0x7fff950ab000 - 0x7fff950dafd2 libsystem_m.dylib (3047.16) <B7F0E2E4-2777-33FC-A787-D6430B630D54> /usr/lib/system/libsystem_m.dylib - 0x7fff950db000 - 0x7fff950e3ff7 com.apple.speech.recognition.framework (4.2.4 - 4.2.4) <98BBB3E4-6239-3EF1-90B2-84EA0D3B8D61> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition - 0x7fff950e6000 - 0x7fff950e7ff7 libsystem_blocks.dylib (63) <FB856CD1-2AEA-3907-8E9B-1E54B6827F82> /usr/lib/system/libsystem_blocks.dylib - 0x7fff950ef000 - 0x7fff952d4ff7 com.apple.CoreFoundation (6.9 - 855.11) <E22C6A1F-8996-349C-905E-96C3BBE07C2F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - 0x7fff952d5000 - 0x7fff952ecfff com.apple.CFOpenDirectory (10.9 - 173.1.1) <3FB4D5FE-860B-3BDE-BAE2-3531D919EF10> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory - 0x7fff953a1000 - 0x7fff953a5ff7 libGIF.dylib (1038) <C29B4323-1B9E-36B9-96C2-7CEDBAA124F0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib - 0x7fff958d8000 - 0x7fff958e2ff7 com.apple.CrashReporterSupport (10.9 - 538) <B487466B-3AA1-3854-A808-A61F049FA794> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport - 0x7fff958e3000 - 0x7fff95bb1ff4 com.apple.CoreImage (9.0.54) <74BB8685-69A9-3A45-8DED-EA26BD39D710> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage - 0x7fff95e9a000 - 0x7fff95e9bfff com.apple.TrustEvaluationAgent (2.0 - 25) <334A82F4-4AE4-3719-A511-86D0B0723E2B> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent - 0x7fff95e9c000 - 0x7fff95f4cff7 libvMisc.dylib (423.32) <049C0735-1808-39B9-943F-76CB8021744F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib - 0x7fff95fa5000 - 0x7fff95faefff com.apple.CommonAuth (4.0 - 2.0) <1D263127-5F27-3128-996D-7397660D0C6E> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth - 0x7fff95fd9000 - 0x7fff96283ffd com.apple.HIToolbox (2.1 - 696) <1CFFF37B-C392-3088-B0A4-C08C55B2AF8F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox - 0x7fff962bc000 - 0x7fff962fdfff com.apple.PerformanceAnalysis (1.47 - 47) <784ED7B8-FAE4-36CE-8C76-B7D300316C9F> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis - 0x7fff96478000 - 0x7fff96482fff libcommonCrypto.dylib (60049) <8C4F0CA0-389C-3EDC-B155-E62DD2187E1D> /usr/lib/system/libcommonCrypto.dylib - 0x7fff96483000 - 0x7fff9648afff libcompiler_rt.dylib (35) <4CD916B2-1B17-362A-B403-EF24A1DAC141> /usr/lib/system/libcompiler_rt.dylib - 0x7fff965c3000 - 0x7fff965c4ff7 libsystem_sandbox.dylib (278.10) <A47E7E11-3C76-318E-B67D-98972B86F094> /usr/lib/system/libsystem_sandbox.dylib - 0x7fff9752f000 - 0x7fff97777fff com.apple.CoreData (107 - 481) <E5AFBA07-F73E-3B3F-9099-F51224EE8EAD> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData - 0x7fff97849000 - 0x7fff97930ff7 libxml2.2.dylib (26) <A1DADD11-89E5-3DE4-8802-07186225967F> /usr/lib/libxml2.2.dylib - 0x7fff97958000 - 0x7fff97974ff7 libsystem_kernel.dylib (2422.1.72) <D14913DB-47F1-3591-8DAF-D4B4EF5F8818> /usr/lib/system/libsystem_kernel.dylib - 0x7fff97a67000 - 0x7fff97ae7fff com.apple.CoreSymbolication (3.0 - 141) <B018335C-698B-3F87-AF1C-6115C4FA8954> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication - 0x7fff97ae8000 - 0x7fff97bedfff com.apple.ImageIO.framework (3.3.0 - 1038) <2C058216-C6D8-3380-A7EA-92A3F04520C1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO - 0x7fff97ca5000 - 0x7fff97d2eff7 libsystem_c.dylib (997.1.1) <61833FAA-7281-3FF9-937F-686B6F20427C> /usr/lib/system/libsystem_c.dylib - 0x7fff97d45000 - 0x7fff97d5eff7 com.apple.Ubiquity (1.3 - 289) <C7F1B734-CE81-334D-BE41-8B20D95A1F9B> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity - 0x7fff97d64000 - 0x7fff97e94ff7 com.apple.desktopservices (1.8 - 1.8) <09DC9BB8-432F-3C7A-BB08-956A2DDFC2DE> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv - 0x7fff97f05000 - 0x7fff98075ff6 com.apple.CFNetwork (673.0.3 - 673.0.3) <42CFC3DB-35C8-3652-AF37-4BCC73D8BDEF> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork - 0x7fff98076000 - 0x7fff980e0ff7 com.apple.framework.IOKit (2.0.1 - 907.1.13) <C1E95F5C-B79B-31BE-9F2A-1B25163C1F16> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit - 0x7fff9877f000 - 0x7fff987e2ff7 com.apple.SystemConfiguration (1.13 - 1.13) <F05F4149-981B-380B-8F50-51CE804BBB89> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration - 0x7fff988e8000 - 0x7fff9894cff9 com.apple.Heimdal (4.0 - 2.0) <E7D20A4D-4674-37E1-A949-635FFF7C439A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal - 0x7fff9894d000 - 0x7fff98a18fff libvDSP.dylib (423.32) <3BF732BE-DDE0-38EB-8C54-E4E3C64F77A7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib - 0x7fff98ba3000 - 0x7fff98babfff libsystem_dnssd.dylib (522.1.11) <270DCF6C-502D-389A-AA9F-DE4624A36FF7> /usr/lib/system/libsystem_dnssd.dylib - 0x7fff98bac000 - 0x7fff98baffff libCoreVMClient.dylib (58.1) <EBC36C69-C896-3C3D-8589-3E9023E7E56F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib - 0x7fff98bb0000 - 0x7fff98c72ff1 com.apple.CoreText (352.0 - 367.15) <E5C70FC8-C861-39B8-A491-595E5B55CFC8> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText - 0x7fff98c73000 - 0x7fff98c7fff7 com.apple.OpenDirectory (10.9 - 173.1.1) <6B78BD7B-5622-38E6-8FC6-86A117E3ACCA> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory - 0x7fff98c80000 - 0x7fff98caffff com.apple.DebugSymbols (106 - 106) <E1BDED08-523A-36F4-B2DA-9D5C712F0AC7> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols - 0x7fff98cb0000 - 0x7fff98d9efff libJP2.dylib (1038) <6C8179F5-8063-3ED6-A7C2-D5603DECDF28> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib - 0x7fff98e1f000 - 0x7fff98f03fff com.apple.coreui (2.1 - 231) <432DB40C-6B7E-39C8-9FB5-B95917930056> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI - 0x7fff98f6f000 - 0x7fff98f73fff libsystem_stats.dylib (93.1.26) <B9E26A9E-FBBC-3938-B8B7-6CF7CA8C99AD> /usr/lib/system/libsystem_stats.dylib - 0x7fff98f74000 - 0x7fff98ffdfff com.apple.ColorSync (4.9.0 - 4.9.0) <B756B908-9AD1-3F5D-83F9-7A0B068387D2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync - 0x7fff99029000 - 0x7fff9908dff3 com.apple.datadetectorscore (5.0 - 354.0) <9ACF24B8-3268-3134-A5BC-D72C9371A195> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore - 0x7fff993e4000 - 0x7fff993ebff3 libcopyfile.dylib (103) <5A881779-D0D6-3029-B371-E3021C2DDA5E> /usr/lib/system/libcopyfile.dylib - 0x7fff994a3000 - 0x7fff99512ff1 com.apple.ApplicationServices.ATS (360 - 363.1) <88976B22-A9B8-3E7B-9AE6-0B8E09A968FC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS - 0x7fff99513000 - 0x7fff9952ffff libresolv.9.dylib (54) <11C2C826-F1C6-39C6-B4E8-6E0C41D4FA95> /usr/lib/libresolv.9.dylib - 0x7fff99530000 - 0x7fff9953fff8 com.apple.LangAnalysis (1.7.0 - 1.7.0) <8FE131B6-1180-3892-98F5-C9C9B79072D4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis - 0x7fff99656000 - 0x7fff9966fff7 com.apple.Kerberos (3.0 - 1) <F108AFEB-198A-3BAF-BCA5-9DFCE55EFF92> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos - 0x7fff99673000 - 0x7fff99674ffb libremovefile.dylib (33) <3543F917-928E-3DB2-A2F4-7AB73B4970EF> /usr/lib/system/libremovefile.dylib - 0x7fff99675000 - 0x7fff99676ff7 libSystem.B.dylib (1197.1.1) <BFC0DC97-46C6-3BE0-9983-54A98734897A> /usr/lib/libSystem.B.dylib - 0x7fff99c76000 - 0x7fff99c87ff7 libsystem_asl.dylib (217.1.4) <655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib - 0x7fff99c88000 - 0x7fff99f72fff com.apple.CoreServices.CarbonCore (1077.14 - 1077.14) <B00BEB34-A9F5-381F-99FD-11E405768A9A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore - 0x7fff99f73000 - 0x7fff99feafff com.apple.CoreServices.OSServices (600.4 - 600.4) <36B2B009-C35E-3F21-824E-E0D00E7808C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices - 0x7fff99feb000 - 0x7fff9a014ff7 libc++abi.dylib (48) <8C16158F-CBF8-3BD7-BEF4-022704B2A326> /usr/lib/libc++abi.dylib - 0x7fff9a076000 - 0x7fff9a0aeff7 com.apple.RemoteViewServices (2.0 - 94) <3F34D630-3DDB-3411-BC28-A56A9B55EBDA> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices - 0x7fff9a0ca000 - 0x7fff9a0d1ff7 libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib - 0x7fff9a0d2000 - 0x7fff9a0d2fff com.apple.Accelerate (1.9 - Accelerate 1.9) <509BB27A-AE62-366D-86D8-0B06D217CF56> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate - 0x7fff9a0d3000 - 0x7fff9a1bdfff libsqlite3.dylib (158) <00269BF9-43BE-39E0-9C85-24585B9923C8> /usr/lib/libsqlite3.dylib - 0x7fff9a248000 - 0x7fff9a2a3ffb com.apple.AE (665.5 - 665.5) <BBA230F9-144C-3CAB-A77A-0621719244CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE - 0x7fff9a517000 - 0x7fff9a565fff com.apple.opencl (2.3.57 - 2.3.57) <FC03A80D-543A-3448-83FF-D399C3A240D9> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL - 0x7fff9a566000 - 0x7fff9a569ff7 libdyld.dylib (239.3) <62F4D752-4089-31A8-8B73-B95A68893B3C> /usr/lib/system/libdyld.dylib - 0x7fff9a571000 - 0x7fff9a729ff3 libicucore.A.dylib (511.27) <003B6C21-CBD1-3486-9A1D-030ADF5FA061> /usr/lib/libicucore.A.dylib - 0x7fff9a72a000 - 0x7fff9a753fff com.apple.DictionaryServices (1.2 - 208) <A539A058-BA57-35EE-AA08-D0B0E835127D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices - 0x7fff9a75a000 - 0x7fff9a766ff3 com.apple.AppleFSCompression (56 - 1.0) <5652B0D0-EB08-381F-B23A-6DCF96991FB5> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression - 0x7fff9a8f5000 - 0x7fff9a90dff7 com.apple.GenerationalStorage (2.0 - 160.2) <79629AC7-896F-3302-8AC1-4939020F08C3> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage - 0x7fff9a939000 - 0x7fff9a954ff7 libCRFSuite.dylib (34) <FFAE75FA-C54E-398B-AA97-18164CD9789D> /usr/lib/libCRFSuite.dylib - 0x7fff9ab57000 - 0x7fff9ab59ff7 libquarantine.dylib (71) <7A1A2BCB-C03D-3A25-BFA4-3E569B2D2C38> /usr/lib/system/libquarantine.dylib - 0x7fff9ab5a000 - 0x7fff9ab5affd com.apple.audio.units.AudioUnit (1.9 - 1.9) <6E89F3CB-CC41-3728-9F9A-FDFC151E8261> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit - 0x7fff9ac14000 - 0x7fff9ac59ff6 com.apple.HIServices (1.22 - 466) <21807AF8-3BC7-32BB-AB96-7C35CB59D7F6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices - 0x7fff9ac5a000 - 0x7fff9ac5afff com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices - 0x7fff9adc0000 - 0x7fff9ade5ff7 com.apple.ChunkingLibrary (2.0 - 155.1) <B845DC7A-D1EA-31E2-967C-D1FE0C628036> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary - -External Modification Summary: - Calls made by other processes targeting this process: - task_for_pid: 19 - thread_create: 0 - thread_set_state: 0 - Calls made by this process: - task_for_pid: 0 - thread_create: 0 - thread_set_state: 0 - Calls made by all processes on this machine: - task_for_pid: 3885694 - thread_create: 1 - thread_set_state: 0 - -VM Region Summary: -ReadOnly portion of Libraries: Total=206.9M resident=102.5M(50%) swapped_out_or_unallocated=104.5M(50%) -Writable regions: Total=51.2M written=13.9M(27%) resident=16.1M(31%) swapped_out=0K(0%) unallocated=35.1M(69%) - -REGION TYPE VIRTUAL -=========== ======= -Dispatch continuations 4096K -Kernel Alloc Once 4K -MALLOC 18.3M -MALLOC (admin) 32K -STACK GUARD 56.0M -Stack 12.6M -VM_ALLOCATE 12.3M -VM_ALLOCATE (reserved) 12K reserved VM address space (unallocated) -__DATA 23.0M -__IMAGE 528K -__LINKEDIT 71.2M -__TEXT 135.7M -__UNICODE 544K -shared memory 4K -=========== ======= -TOTAL 334.3M -TOTAL, minus reserved VM space 334.3M - - - -\"\"\"]] -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_7_849759a5c92de57733b14adce2f49c14._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_7_849759a5c92de57733b14adce2f49c14._comment deleted file mode 100644 index ff4e1947c..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_7_849759a5c92de57733b14adce2f49c14._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 7" - date="2014-01-16T03:32:08Z" - content=""" -The new crash is in gnutls. - -I have removed the gnutls stuff that I asked homebrew to build a portable version of, since it seemed to fail to do so. Perhaps this will get us there. Autobuild is updated. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_8_01530dd4ddbf620435a4d8f1edeaee8e._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_8_01530dd4ddbf620435a4d8f1edeaee8e._comment deleted file mode 100644 index 0ea4b4953..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_8_01530dd4ddbf620435a4d8f1edeaee8e._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawn_3tllXjSmtgm__aGr9Z4gVNFgJgGyJ30" - nickname="David Alan" - subject="Same" - date="2014-01-16T05:45:34Z" - content=""" -Same problem for me here, although I would not know how to make a nice log like David does. - -versioning of osx is like this: - -10.6 -> Snow Leopard -10.7 -> Lion -10.8 -> Mountain Lion -10.9 -> Mavericks - -Thanks for the efforts. -"""]] diff --git a/doc/bugs/Share_with_friends_crash_in_osx/comment_9_6ef922e1ebb72db8ebbff4a76017e535._comment b/doc/bugs/Share_with_friends_crash_in_osx/comment_9_6ef922e1ebb72db8ebbff4a76017e535._comment deleted file mode 100644 index edc8f2af2..000000000 --- a/doc/bugs/Share_with_friends_crash_in_osx/comment_9_6ef922e1ebb72db8ebbff4a76017e535._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkLdR1fuu5aEz3s9VKTBKVMize_SmeNRJM" - nickname="David" - subject="Still crashing (again)" - date="2014-01-16T23:33:15Z" - content=""" -Here is the relevant section of the new crash. Looks like the same crash as yesterdays to me. - -[[!format sh \"\"\" -Thread 4 Crashed: -0 S 0x000000010cea0b9d nettle_sha256_init + 4 -1 S 0x000000010cea7e60 nettle_yarrow256_init + 24 -2 H 0x000000010cccf2a3 wrap_nettle_rnd_init + 52 -3 H 0x000000010cc53585 _gnutls_rnd_init + 32 -4 H 0x000000010cc47dae gnutls_global_init + 262 -5 git-annex 0x000000010ab95873 0x10937a000 + 25278579 -6 git-annex 0x000000010c01dc08 0x10937a000 + 46808072 -\"\"\"]] -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials.mdwn b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials.mdwn deleted file mode 100644 index 125a3f626..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -I have an existing Git annex repository with an Amazon S3 remote. I don't have the original credentials for this S3 account any more, but I would like to enable this remote in a fresh clone. When using the new IAM credentials, I get a SignatureDoesNotMatch error. - -### What steps will reproduce the problem? - - [ollie@nixos:/media/music]$ export AWS_ACCESS_KEY_ID="redacted" - - [ollie@nixos:/media/music]$ export AWS_SECRET_ACCESS_KEY="redacted" - - [ollie@nixos:/media/music]$ git annex enableremote S3musicencrypted - enableremote S3musicencrypted (checking bucket...) (creating bucket in EU...) git-annex: S3Error {s3StatusCode = Status {statusCode = 403, statusMessage = "Forbidden"}, s3ErrorCode = "SignatureDoesNotMatch", s3ErrorMessage = "The request signature we calculated does not match the signature you provided. Check your key and signing method.", s3ErrorResource = Nothing, s3ErrorHostId = Just "jjTIOt9HhXtYTYTHQB7a7CryvCVwZI2nW2EoR/GcF5QxlNf//qDd5ySLnlBiU3BDN4KzZuI2U8w=", s3ErrorAccessKeyId = Just "redacted", s3ErrorStringToSign = Just "PUT\n\n\nTue, 3 Feb 2015 19:36:58 GMT\n/s3musicencrypted-a7e22956-5ce2-11e2-97a5-6f33220ffbf3/"} - - -### What version of git-annex are you using? On what operating system? - - [ollie@nixos:/media/music]$ git annex version - git-annex version: 5.20150113 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash TorrentParser - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - - [ollie@nixos:/media/music]$ uname -a - Linux nixos 3.18.3 #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x86_64 GNU/Linux - - [ollie@nixos:/media/music]$ cat /run/current-system/nixos-version - 15.05pre-70b398d - -> Apparently something changed in a newer verison of git-annex that fixed -> this. Since I can't think of what the change could be, my guess is the -> newer git-annex was built against a newer version of the aws library, and -> that the fix was in the aws library. In any case, apparently this bug is -> [[done]] --[[Joey]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_1_804a51b57ac9261a95b268d122eb7cae._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_1_804a51b57ac9261a95b268d122eb7cae._comment deleted file mode 100644 index ada6829eb..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_1_804a51b57ac9261a95b268d122eb7cae._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-04T19:03:35Z" - content=""" -Does the S3musicencrypted special remote have embedcreds=yes set -in its configuration? You could look at `git show git-annex:remote.log` -to check. (Don't paste it here, may contain access keys.) - -Does `.git/annex/creds/a7e22956-5ce2-11e2-97a5-6f33220ffbf3` exist? - -Based on looking at the code, I'd expect environment variables to override -both of those, so I wonder if perhaps the creds you passed in the -environment are just wrong. -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_2_ed27571352892fb5229b4daa50934308._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_2_ed27571352892fb5229b4daa50934308._comment deleted file mode 100644 index 64d6a148c..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_2_ed27571352892fb5229b4daa50934308._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmg0NqVniTETKYIWr6eyYRJnakNg0A6tRc" - nickname="Oliver" - subject="comment 2" - date="2015-02-04T21:42:22Z" - content=""" -Hi joey, - -It doesn't seem like embedcreds is set - `git show git-annex:remote.log | grep embed` doesn't yield anything. - -The file you asked me to check does exist, and whenever I run `git annex enableremote` it gets updated with the contents of my environment variables. - -I'm pretty certain the contents of these variables is correct - I'm using AWS' \"IAM\" options to allocate new access keys to my git-annex user, and would expect a different error if things were wrong there. I'll continue to double check my account settings. -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment deleted file mode 100644 index a53456b8d..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_3_8d4217b54a37eabfd12016c04c7e55b1._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-02-09T18:30:46Z" - content=""" -Well, looks like git-annex is using the IAM credentials you're providing. - -You could try to use a different S3 client on -the same bucket to check if the credentials are good. - -This may be a problem with the credentials not allowing some actions, -like creating a bucket. Which is the action git-annex is failing at. - -The bucket does already exist, right? Does it contain an "annex-uuid" -file? Does that file contain "a7e22956-5ce2-11e2-97a5-6f33220ffbf3"? -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_4_17391f47897f166b763e8f3e33426fcf._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_4_17391f47897f166b763e8f3e33426fcf._comment deleted file mode 100644 index 1d221cb3a..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_4_17391f47897f166b763e8f3e33426fcf._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmg0NqVniTETKYIWr6eyYRJnakNg0A6tRc" - nickname="Oliver" - subject="comment 4" - date="2015-02-19T11:54:14Z" - content=""" -I used `s3cmd` with the same credentials and I'm able to list the bucket contents. That file does exist, and it does contain the line expected. If I try and make the bucket: - -s3cmd mb s3://s3musicencrypted-a7e22956-5ce2-11e2-97a5-6f33220ffbf3 -ERROR: S3 error: 409 (BucketAlreadyOwnedByYou): Your previous request to create the named bucket succeeded and you already own it. - -So I should be able to create buckets, but of course creating a bucket that already exists doesn't really do anything. - -Taking exactly the same credentials as my .s3cfg and using them with git annex continues to fail with signature errors. -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_5_e720d301c2bc17483b0e50dde3ccb23c._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_5_e720d301c2bc17483b0e50dde3ccb23c._comment deleted file mode 100644 index 5a0b3000b..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_5_e720d301c2bc17483b0e50dde3ccb23c._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-07-07T17:58:03Z" - content=""" -Seems we're ruled out nearly anything except for a bug in the aws library -that git-annex uses. - -So, I think we need to file a bug on that library. It would be very helpful -to include the library's debugging output with such a bug report. You can -get it by upgrading to git-annex version 5.20150420 or newer, and passing ---debug to git-annex. Should result in some debug logs for aws. - -Also, if possible make sure git-annex is built with the newest version of -the aws library. I assume this is easy, since you're using Nix. ;) - -(If you're comfortable building haskell programs, it would also be great to -test with Examples/GetObject.hs from the aws package's source, which -has to be modified to use your bucket, and to get the annex-uuid file from -it. If we can get git-annex entirely out of the loop, we can be sure the -bug is in the aws library..) -"""]] diff --git a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_6_5e3bd68936199a29bf38fee43f1030b8._comment b/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_6_5e3bd68936199a29bf38fee43f1030b8._comment deleted file mode 100644 index fc2a41fa1..000000000 --- a/doc/bugs/SignatureDoesNotMatch_error_when_trying_to_enable_S3_remote_with_IAM_credentials/comment_6_5e3bd68936199a29bf38fee43f1030b8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="ollie@6d66b5a4b0992998efe3e4c244a66708bf5d96f3" - nickname="ollie" - subject="comment 6" - date="2015-07-17T10:42:05Z" - content=""" -I've just updated to a much newer git-annex, and everything seems to be working again now. Hurrah! -"""]] diff --git a/doc/bugs/Small_archive_behaving_like_archive.mdwn b/doc/bugs/Small_archive_behaving_like_archive.mdwn deleted file mode 100644 index 947777279..000000000 --- a/doc/bugs/Small_archive_behaving_like_archive.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -repos of group smallarchive have started trying to accumulate all files. - -I have an archive repo (rsync) and a smallarchive repo (glacier). The assistant is now trying to transfer everything up to glacier. This is new behavior as of this version of annex. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - -Mac OSX 10.8.3 (Build 12D78) - - git-annex version: 4.20130501-ged2fc6f - - local repository version: 4 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS - - -### 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/debug.log - - -# End of transcript or log. -"""]] - -[[!tag moreinfo]] - -> Since there's a plausible explanation in my comment and no followup, -> [[done]] --[[Joey]] diff --git a/doc/bugs/Small_archive_behaving_like_archive/comment_1_718dc246cbbbeae04436fa033011ab12._comment b/doc/bugs/Small_archive_behaving_like_archive/comment_1_718dc246cbbbeae04436fa033011ab12._comment deleted file mode 100644 index dd509cdde..000000000 --- a/doc/bugs/Small_archive_behaving_like_archive/comment_1_718dc246cbbbeae04436fa033011ab12._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-05-06T21:09:00Z" - content=""" -I have tested smallarchive and do not see any bug with its operation. Files not in an `archive` directory are not sent to the smallarchive repository. Files in `archive` directories are, unless they have already been sent to some other archive repository. - -There has, however, been a recent change that could have led you to see a change in behavior, though not one that is really a bug: -Now smallarchive repositories will accept any content if it's only located on repositories that are untrusted or dead. So for example if your main client repo is for some reason marked as untrusted, the glacier repo would assume it's going away, and accept content from it. - -If that's not the explanation, you will need to provide more details.. -"""]] diff --git a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn deleted file mode 100644 index 738534358..000000000 --- a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. -At some point, I migrated all my WORM-backed objects to SHA1E. I then squashed my master branch to get rid of any WORM references and dropped unused objects. Recently, I noticed that the git-annex branch still has all tracking information on the old WORM keys. I tried running git-annex forget, but the old keys are not purged, even though no (local or remote) branch refers to them and no git-annex repository has the data for these keys anymore. Should such keys be purged by git-annex forget, too? - -### What steps will reproduce the problem? - -[[!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 -git init /tmp/repo -cd /tmp/repo -git annex init -echo hi > file -git annex add --backend=WORM file -git commit -m init -git annex migrate -git commit -m migrated -git checkout --orphan tmp -git commit -m squashed -git branch -m master -f -git annex unused -git annex dropunused 1 --force -git annex forget --drop-dead --force -git ls-tree -r git-annex | grep WORM - -# End of transcript or log. -"""]] - -### What version of git-annex are you using? On what operating system? -git-annex 5.20150508 -Linux 4.0.4 - -> This can now be dealt with by providing the key to `git annex dead -> --key` [[done]] --[[Joey]] diff --git a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment deleted file mode 100644 index e5f50c84a..000000000 --- a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_1_2b34b39ef76f205187b1d44fbbccd7f6._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-05-22T17:16:28Z" - content=""" -`git annex forget` removes historcal data about where files were located in -the past, but it does not affect the current logs about the current -location (or lack of location) of files. - -It would be possible to extend `git annex forget` to do that, which is one -approach to possibly solving [[fsck_reports_unsolvable_problem]]. -"""]] diff --git a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_2_ce97390480a04918cf20c12944ee65ef._comment b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_2_ce97390480a04918cf20c12944ee65ef._comment deleted file mode 100644 index d757eefa9..000000000 --- a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget/comment_2_ce97390480a04918cf20c12944ee65ef._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 2" - date="2015-05-24T14:58:30Z" - content=""" -Thanks! This would be useful. While it probably takes up only little disk space, the noise it creates during fsck would make it harder to discern which data has been unintentionally lost, as opposed to migrated to another back-end. -"""]] diff --git a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported.mdwn b/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported.mdwn deleted file mode 100644 index 82141ce68..000000000 --- a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. -Symlinks get dereferenced. - -### What steps will reproduce the problem? -Include a symlink in the repo. Wait until another client syncs the repo. - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20131117-gbd514dc - -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - -local repository version: unknown - -default repository version: 3 - -supported repository versions: 3 5 - -upgrade supported from repository versions: 0 1 2 4 - -### Please provide any additional information below. -I have a file `/Users/lhunath/annex/Library/Application Support/CrossOver/Bottles/Fallout 3/drive_c/users/crossover/My Documents` which is a symlink to `~/Documents` on the originating client. On the destination client, This turns into a directory, causing the whole content of `~/Documents` to get included in each bottle, which includes a bunch of VM images etc..... - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_1_06ac38f32039ad43b0c2623c8fdb1df6._comment b/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_1_06ac38f32039ad43b0c2623c8fdb1df6._comment deleted file mode 100644 index 01685d804..000000000 --- a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_1_06ac38f32039ad43b0c2623c8fdb1df6._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8" - nickname="Maarten" - subject="workaround?" - date="2013-12-05T14:17:57Z" - content=""" -Until this is fixed, how can I manually remove a file from git annex syncing? -"""]] diff --git a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_2_91a8daa3d49799d0784c9fe3ee10558a._comment b/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_2_91a8daa3d49799d0784c9fe3ee10558a._comment deleted file mode 100644 index 40140c852..000000000 --- a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_2_91a8daa3d49799d0784c9fe3ee10558a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 2" - date="2013-12-18T18:27:04Z" - content=""" -I don't quite understand how to reproduce this bug, and have tried a few things with symlinks and multiple syncing repositories without apparent difficulty. - -Can you pleaseexplain in more detail how I could reproduce the problem? -"""]] diff --git a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_3_166ae413b7c41f00f13292855ac66974._comment b/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_3_166ae413b7c41f00f13292855ac66974._comment deleted file mode 100644 index d01f64d27..000000000 --- a/doc/bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported/comment_3_166ae413b7c41f00f13292855ac66974._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 3" - date="2013-12-18T19:31:04Z" - content=""" -I see that you're using OSX. I have replicated the bug there, and fixed it. (I think.) -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__.mdwn b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__.mdwn deleted file mode 100644 index 8dd74acc3..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__.mdwn +++ /dev/null @@ -1,1175 +0,0 @@ -### Please describe the problem. - -On test fails when running "git annex test" on Windows. - -### What steps will reproduce the problem? - -Install Git-1.8.5.2-preview20131230 -Install git-annex-5.20131222 -Run "git annex test" in cmd - -### What version of git-annex are you using? On what operating system? - -git-annex-5.20131222 on Windows 7 Professional - -### Please provide any additional information below. - -The failed test is "test_mixed_conflict_resolution" with "conflictor directory missing". The problem can also be reproduced with the attached batch script. -(EDIT: I couldn't attach a file, so I pasted its contents below the log.) - -You can find the complete output of "git annex test" below. - -[[!format text """ -Tests - QuickCheck - prop_idempotent_deencode_git: OK - +++ OK, passed 100 tests. - prop_idempotent_deencode: OK - +++ OK, passed 100 tests. - prop_idempotent_fileKey: OK - +++ OK, passed 100 tests. - prop_idempotent_key_encode: OK - +++ OK, passed 100 tests. - prop_idempotent_key_decode: OK - +++ OK, passed 100 tests. - prop_idempotent_shellEscape: OK - +++ OK, passed 100 tests. - prop_idempotent_shellEscape_multiword: OK - +++ OK, passed 100 tests. - prop_logs_sane: OK - +++ OK, passed 100 tests. - prop_idempotent_configEscape: OK - +++ OK, passed 100 tests. - prop_parse_show_Config: OK - +++ OK, passed 100 tests. - prop_parentDir_basics: OK - +++ OK, passed 100 tests. - prop_relPathDirToFile_basics: OK - +++ OK, passed 100 tests. - prop_relPathDirToFile_regressionTest: OK - +++ OK, passed 100 tests. - prop_cost_sane: OK - +++ OK, passed 100 tests. - prop_matcher_sane: OK - +++ OK, passed 100 tests. - prop_HmacSha1WithCipher_sane: OK - +++ OK, passed 100 tests. - prop_TimeStamp_sane: OK - +++ OK, passed 100 tests. - prop_addLog_sane: OK - +++ OK, passed 100 tests. - prop_verifiable_sane: OK - +++ OK, passed 100 tests. - prop_segment_regressionTest: OK - +++ OK, passed 100 tests. - prop_read_write_transferinfo: OK - +++ OK, passed 100 tests. - prop_read_show_inodecache: OK - +++ OK, passed 100 tests. - prop_parse_show_log: OK - +++ OK, passed 100 tests. - prop_read_show_TrustLevel: OK - +++ OK, passed 100 tests. - prop_parse_show_TrustLog: OK - +++ OK, passed 100 tests. - prop_hashes_stable: OK - +++ OK, passed 100 tests. - prop_schedule_roundtrips: OK - +++ OK, passed 100 tests. - prop_duration_roundtrips: OK - +++ OK, passed 100 tests. - Unit Tests - init: init test repo - Detected a filesystem without fifo support. - - Disabling ssh connection caching. - - Detected a crippled filesystem. - - Enabling direct mode. -ok -(Recording state in git...) -OK - add: add foo ok -(Recording state in git...) -add sha1foo ok -(Recording state in git...) -add apple ok -(Recording state in git...) -fatal: This operation must be run in a work tree -commit (Recording state in git...) -ok -(Recording state in git...) -OK - add sha1dup: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -add sha1foodup cygwin warning: - MS-DOS style path detected: C:\Users\Tobias\testdir\t2\.t\tmprepo0\.git\annex\tmp\tmp5876 - Preferred POSIX equivalent is: /cygdrive/c/Users/Tobias/testdir/t2/.t/tmprepo0/.git/annex/tmp/tmp5876 - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames -ok -(Recording state in git...) -OK - add subdirs: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -add dir/foo cygwin warning: - MS-DOS style path detected: C:\Users\Tobias\testdir\t2\.t\tmprepo1\.git\annex\tmp\tmp3396 - Preferred POSIX equivalent is: /cygdrive/c/Users/Tobias/testdir/t2/.t/tmprepo1/.git/annex/tmp/tmp3396 - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames -ok -(Recording state in git...) -OK - reinject: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - unannex (no copy): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -OK - unannex (with copy): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -unannex foo ok -(Recording state in git...) -OK - drop (no remote): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -drop foo (unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Try making some of these repositories available: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- test repo - - (Use --force to override this check, or adjust annex.numcopies.) -failed -git-annex: drop: 1 failed -drop foo ok -(Recording state in git...) -OK - drop (with remote): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 78.67 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -drop foo ok -(Recording state in git...) -OK - drop (untrusted remote): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -untrust origin (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -(Recording state in git...) -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 78.67 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -drop foo (unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Also these untrusted repositories may contain the file: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) - - (Use --force to override this check, or adjust annex.numcopies.) -failed -git-annex: drop: 1 failed -OK - get: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -OK - move: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -move foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -move foo (to origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -OK - copy: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -copy foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -copy foo ok -move foo ok -(Recording state in git...) -OK - lock: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - edit (no pre-commit): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - edit (pre-commit): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - fix: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - trust: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -trust origin (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -(Recording state in git...) -trust origin ok -(Recording state in git...) -untrust origin ok -(Recording state in git...) -untrust origin ok -(Recording state in git...) -dead origin ok -(Recording state in git...) -dead origin ok -(Recording state in git...) -semitrust origin ok -(Recording state in git...) -semitrust origin ok -(Recording state in git...) -OK - fsck (basics): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -fsck foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -fsck sha1foo ok -fsck foo - Only 1 of 2 trustworthy copies exist of foo - Back it up with git-annex copy. -failed -fsck sha1foo - Only 1 of 2 trustworthy copies exist of sha1foo - Back it up with git-annex copy. -failed -git-annex: fsck: 2 failed -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -fsck foo ok -fsck sha1foo ok -fsck foo ok -fsck sha1foo ok -get sha1foo (from origin...) -sha1foo - 25 100% 0.00kB/s 0:00:00 - 25 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 96 bytes received 31 bytes 254.00 bytes/sec -total size is 25 speedup is 0.20 -ok -(Recording state in git...) -fsck foo ok -fsck sha1foo ok -fsck foo ok -fsck sha1foo ok -OK - fsck (bare): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -fsck SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77 ok -fsck WORM-s25-m1388499859--apple ok -fsck SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa ok -OK - fsck (local untrusted): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 78.67 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -untrust origin ok -(Recording state in git...) -untrust . ok -(Recording state in git...) -fsck foo - Only these untrusted locations may have copies of foo - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) - 68deb80b-3a46-42f9-bb58-0f3b5a689d28 -- here (.t\tmprepo18) - Back it up to trusted locations with git-annex copy. -failed -fsck sha1foo - Only these untrusted locations may have copies of sha1foo - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) - Back it up to trusted locations with git-annex copy. -failed -git-annex: fsck: 2 failed -trust . ok -(Recording state in git...) -fsck foo ok -OK - fsck (remote untrusted): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -get sha1foo (from origin...) -sha1foo - 25 100% 0.00kB/s 0:00:00 - 25 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 96 bytes received 31 bytes 254.00 bytes/sec -total size is 25 speedup is 0.20 -ok -(Recording state in git...) -fsck foo ok -fsck sha1foo ok -untrust origin ok -(Recording state in git...) -fsck foo - Only 1 of 2 trustworthy copies exist of foo - Back it up with git-annex copy. - The following untrusted locations may also have copies: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) -failed -fsck sha1foo - Only 1 of 2 trustworthy copies exist of sha1foo - Back it up with git-annex copy. - The following untrusted locations may also have copies: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) -failed -git-annex: fsck: 2 failed -OK - migrate: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - migrate (via gitattributes): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - unused: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - describe: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -describe . ok -(Recording state in git...) -describe origin (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -(Recording state in git...) -OK - find: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -foo -foo -sha1foo -sha1foo -add dir/subfile ok -(Recording state in git...) -dir/subfile -OK - merge: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -merge git-annex (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -OK - info: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -{"command":"info","repository mode":"direct","trusted repositories":[],"semitrusted repositories":[{"uuid":"00000000-0000-0000-0000-000000000001","description":"web","here":false},{"uuid":"3bbb68d2-9ef1-4126-bee5-f60569f8ad82","description":"origin (test repo)","here":false},{"uuid":"fe838913-724e-4fb1-a47f-4b3815b1aab5","description":".t\\tmprepo26","here":true}],"untrusted repositories":[],"available local disk space":"7.78 gigabytes (+1 megabyte reserved)","local annex keys":0,"local annex size":"0 bytes","annexed files in working tree":2,"size of annexed files in working tree":"45 bytes","bloom filter size":"16 mebibytes (0% full)","success":true} -OK - version: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -git-annex version: 5.20131230-g192d991 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 2 3 4 -OK - sync: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -(merging origin/git-annex into git-annex...) -(Recording state in git...) -commit ok -pull origin bash.exe: warning: could not find /tmp, please create! - -ok -push origin bash.exe: warning: could not find /tmp, please create! -To C:/Users/Tobias/testdir/t2/.t\repo - * [new branch] git-annex -> synced/git-annex - -ok -OK - union merge regression: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 78.67 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -commit ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo30 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - -ok -pull r1 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo29 - * [new branch] annex/direct/master -> r1/annex/direct/master - * [new branch] git-annex -> r1/git-annex - -ok -(merging r1/git-annex r2/git-annex into git-annex...) -(Recording state in git...) -push r2 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo30 - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master - -ok -push r1 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo29 - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master - -ok -(merging synced/git-annex into git-annex...) -commit ok -pull r3 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo31 - * [new branch] annex/direct/master -> r3/annex/direct/master - * [new branch] git-annex -> r3/git-annex - * [new branch] master -> r3/master - * [new branch] synced/master -> r3/synced/master - -ok -pull r1 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo29 - * [new branch] annex/direct/master -> r1/annex/direct/master - * [new branch] git-annex -> r1/git-annex - * [new branch] master -> r1/master - * [new branch] synced/git-annex -> r1/synced/git-annex - * [new branch] synced/master -> r1/synced/master - -ok -push r1 bash.exe: warning: could not find /tmp, please create! -Everything up-to-date - -ok -(merging synced/git-annex into git-annex...) -commit ok -pull r3 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo31 - * [new branch] annex/direct/master -> r3/annex/direct/master - * [new branch] git-annex -> r3/git-annex - * [new branch] master -> r3/master - * [new branch] synced/master -> r3/synced/master - -ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo30 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/git-annex -> r2/synced/git-annex - * [new branch] synced/master -> r2/synced/master - -ok -drop foo ok -(Recording state in git...) -drop foo ok -(Recording state in git...) -commit ok -pull r3 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo31 - 55d5b14..3b6c15d git-annex -> r3/git-annex - -ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo30 - 55d5b14..a4599c9 git-annex -> r2/git-annex - -ok -(merging r2/git-annex r3/git-annex into git-annex...) -(Recording state in git...) -push r3 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo31 - * [new branch] git-annex -> synced/git-annex - -ok -push r2 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo30 - 55d5b14..4ff2e44 git-annex -> synced/git-annex - -ok -OK - conflict resolution: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -get sha1foo (from origin...) -sha1foo - 25 100% 0.00kB/s 0:00:00 - 25 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 96 bytes received 31 bytes 254.00 bytes/sec -total size is 25 speedup is 0.20 -ok -(Recording state in git...) -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -get sha1foo (from origin...) -sha1foo - 25 100% 0.00kB/s 0:00:00 - 25 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 96 bytes received 31 bytes 254.00 bytes/sec -total size is 25 speedup is 0.20 -ok -(Recording state in git...) -commit add foo ok -(Recording state in git...) -ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo33 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - -ok -(merging r2/git-annex into git-annex...) -(Recording state in git...) -push r2 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo33 - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master - -ok -(merging synced/git-annex into git-annex...) -commit add foo ok -(Recording state in git...) -ok -merge synced/master Auto-merging foo -CONFLICT (content): Merge conflict in foo -Automatic merge failed; fix conflicts and then commit the result. -foo: needs merge -[annex/direct/master ab51abe] git-annex automatic merge conflict fix - -(Recording state in git...) - - Merge conflict was automatically resolved; you may want to examine the result. -ok -pull r1 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo32 - * [new branch] annex/direct/master -> r1/annex/direct/master - * [new branch] git-annex -> r1/git-annex - * [new branch] master -> r1/master - * [new branch] synced/master -> r1/synced/master - -ok -(Recording state in git...) -push r1 bash.exe: warning: could not find /tmp, please create! -To ../../.t\tmprepo32 - 0c0b4c1..ab51abe annex/direct/master -> synced/master - * [new branch] git-annex -> synced/git-annex - -ok -(merging synced/git-annex into git-annex...) -commit ok -merge synced/master Updating 0c0b4c1..ab51abe -Fast-forward - foo | 1 - - foo.variant-0b0e | 1 + - foo.variant-bc25 | 1 + - 3 files changed, 2 insertions(+), 1 deletion(-) - delete mode 120000 foo - create mode 120000 foo.variant-0b0e - create mode 120000 foo.variant-bc25 - -ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo33 - 09047a9..ab51abe annex/direct/master -> r2/annex/direct/master - 6208675..2aef6c1 git-annex -> r2/git-annex - 0c0b4c1..ab51abe master -> r2/master - 0c0b4c1..ab51abe synced/master -> r2/synced/master - -ok -get foo.variant-bc25 (from r2...) -foo.variant-bc25 - 22 100% 0.00kB/s 0:00:00 - 22 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 102 bytes received 31 bytes 266.00 bytes/sec -total size is 22 speedup is 0.17 -ok -(Recording state in git...) -get foo.variant-0b0e (from r1...) -foo.variant-0b0e - 22 100% 0.00kB/s 0:00:00 - 22 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 102 bytes received 31 bytes 266.00 bytes/sec -total size is 22 speedup is 0.17 -ok -(Recording state in git...) -OK - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -add conflictor ok -(Recording state in git...) -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -commit ok -pull origin bash.exe: warning: could not find /tmp, please create! - -ok -push origin bash.exe: warning: could not find /tmp, please create! -To C:/Users/Tobias/testdir/t2/.t\repo - 488868c..2ab23aa git-annex -> synced/git-annex - 09047a9..fdc68bf annex/direct/master -> synced/master - -ok -add conflictor/subfile ok -(Recording state in git...) -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -commit ok -pull origin bash.exe: warning: could not find /tmp, please create! -From C:/Users/Tobias/testdir/t2/.t\repo - 09047a9..fdc68bf master -> origin/master - 488868c..2ab23aa synced/git-annex -> origin/synced/git-annex - 09047a9..fdc68bf synced/master -> origin/synced/master -Adding conflictor/subfile -CONFLICT (directory/file): There is a directory with name conflictor in HEAD. Adding conflictor as conflictor~refs_remotes_origin_synced_master -Automatic merge failed; fix conflicts and then commit the result. -conflictor: needs merge -[annex/direct/master 77177a0] git-annex automatic merge conflict fix - - -(Recording state in git...) - - Merge conflict was automatically resolved; you may want to examine the result. -ok -(merging origin/synced/git-annex into git-annex...) -(Recording state in git...) -push origin bash.exe: warning: could not find /tmp, please create! -To C:/Users/Tobias/testdir/t2/.t\repo - 2ab23aa..0ba8d35 git-annex -> synced/git-annex - fdc68bf..77177a0 annex/direct/master -> synced/master - -ok -commit ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo35 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/master -> r2/synced/master -Updating fdc68bf..77177a0 -Fast-forward - conflictor | 1 - - conflictor.variant-cc12 | 1 + - conflictor/subfile | 1 + - 3 files changed, 2 insertions(+), 1 deletion(-) - delete mode 120000 conflictor - create mode 120000 conflictor.variant-cc12 - create mode 120000 conflictor/subfile -Already up-to-date. - - - -ok -(merging r2/git-annex into git-annex...) -FAIL - .t\tmprepo34 conflictor directory missing - map: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -describe . ok -(Recording state in git...) -describe origin (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -ok -(Recording state in git...) -map C:\Users\Tobias\testdir\t2\.t\tmprepo36 ok -map C:\Users\Tobias\testdir\t2\.t\repo ok -ok -OK - uninit: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -get sha1foo (from origin...) -sha1foo - 25 100% 0.00kB/s 0:00:00 - 25 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 96 bytes received 31 bytes 254.00 bytes/sec -total size is 25 speedup is 0.20 -ok -(Recording state in git...) -unannex foo ok -unannex sha1foo -git-annex: C:\Users\Tobias\testdir\t2\.t\tmprepo37\.git\annex\objects\ecb\0b5\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa.map4964.tmp: MoveFileEx "C:\\Users\\Tobias\\testdir\\t2\\.t\\tmprepo37\\.git\\annex\\objects\\ecb\\0b5\\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa\\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa.map4964.tmp" "C:\\Users\\Tobias\\testdir\\t2\\.t\\tmprepo37\\.git\\annex\\objects\\ecb\\0b5\\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa\\SHA1-s25--ee80d2cec57a3810db83b80e1b320df3a3721ffa.map": permission denied (Access is denied.) -failed -git-annex: Not fully uninitialized -Some annexed data is still left in C:\Users\Tobias\testdir\t2\.t\tmprepo37\.git\annex\objects\ -This may include deleted files, or old versions of modified files. - -If you don't care about preserving the data, just delete the -directory. - -Or, you can move it to another location, in case it turns out -something in there is important. - -Or, you can run `git annex unused` followed by `git annex dropunused` -to remove data that is not used by any tag or branch, which might -take care of all the data. - -Then run `git annex uninit` again to finish. - -OK - uninit (in git-annex branch): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. -not supported in direct mode; skipping -OK - upgrade: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -upgrade . ok -OK - whereis: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -whereis foo (1 copy) - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) -ok -untrust origin ok -(Recording state in git...) -whereis foo (0 copies) - The following untrusted locations may also have copies: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) -failed -git-annex: whereis: 1 failed -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -whereis foo (1 copy) - 28bccded-ea59-4d64-bf20-d58540e72892 -- here (.t\tmprepo40) - - The following untrusted locations may also have copies: - 3bbb68d2-9ef1-4126-bee5-f60569f8ad82 -- origin (test repo) -ok -OK - hook remote: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -OK - directory remote: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -initremote foo ok -(Recording state in git...) -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -copy foo (to foo...) - -100% 0.0 B/s 0s - -ok -(Recording state in git...) -drop foo ok -(Recording state in git...) -move foo (from foo...) - -100% 0.0 B/s 0s - -ok -(Recording state in git...) -drop foo (unsafe) - Could only verify the existence of 1 out of 2 necessary copies - - Rather than dropping this file, try using: git annex move - - (Use --force to override this check, or adjust annex.numcopies.) -failed -git-annex: drop: 1 failed -OK - rsync remote: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -OK - bup remote: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -OKg -pg t e sctriynpgt on:o t i m p l e m e n t e d o n W i n d o w s - OK - preferred content: Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -wanted . ok -(Recording state in git...) -group . ok -(Recording state in git...) -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -ungroup . ok -(Recording state in git...) -wanted . ok -(Recording state in git...) -group . ok -(Recording state in git...) -drop foo ok -(Recording state in git...) -ungroup . ok -(Recording state in git...) -wanted . ok -(Recording state in git...) -get foo (from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -drop foo ok -(Recording state in git...) -OK - global cleanup: OK - -1 out of 74 tests failed - (This could be due to a bug in git-annex, or an incompatability - with utilities, such as git, installed on this system.) -"""]] - -batch script to reproduce the problem in the cmd shell: -[[!format bat """ -mkdir repo -cd repo -git init -git annex init "main repo" -echo x > f1 -git annex add f1 -git annex sync -cd .. -git clone repo r1 -git clone repo r2 -cd r1 -echo xyz > conflictor -git annex add conflictor -git annex sync -cd ..\r2 -mkdir conflictor -echo abc > conflictor\subfile -git annex add conflictor\subfile -git annex sync -cd ..\r1 -git remote add r2 ..\r2 -git remote remove origin -cd ..\r2 -git remote add r1 ..\r1 -git remote remove origin -cd ..\r1 -git annex sync -cd ..\r2 -git annex sync -cd .. -dir repo r1 r2 -"""]] - -> Yet another wonderful case of \\ vs / confusion. [[fixed|done]]. -> -> That sucked, but I am rather stunned that the rest of the test -> suite passes for you. That's a lot better that it's ever done on windows -> before. Sadly I don't have as much luck on XP, still 9 failing tests -> there. -> -> --[[Joey]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_1_dfb520258fdd633285b44cb16fd35612._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_1_dfb520258fdd633285b44cb16fd35612._comment deleted file mode 100644 index 7ece79f42..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_1_dfb520258fdd633285b44cb16fd35612._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawltxdgYMUK4CMJh3jC8AlegwyoiHA9Ka7o" - nickname="Justin" - subject="This test is still failing on Windows" - date="2014-01-29T14:37:33Z" - content=""" -This 1 test is still failing for me on Windows 7 Pro with the latest release (git-annex version: 5.20140128-gddb2083). - -I also followed the manual steps provided in the initial bug report. This resulted in two cloned repos which appeared to have resolved the conflict differently. Upon further investigation, I see that the conflict was in fact resolved consistently, just that the file sizes in the working directories are different because the file contents has not been synced (so some files contain the \"symlink\" path rather than the actual contents). - -After running a sync in both repositories with the new --contents option, the two working directories appear to be resolved consistently. -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_2_7908bf367652d2485ec703ae8958891b._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_2_7908bf367652d2485ec703ae8958891b._comment deleted file mode 100644 index 0a9e852f2..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_2_7908bf367652d2485ec703ae8958891b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.199" - subject="comment 2" - date="2014-01-29T17:52:27Z" - content=""" -AFAICS, the test suite does not look at the contents of the files when testing this. Anyway, you said a lot about how it works when you try to reproduce the bug manually, but you didn't actually show how the test suite is failing. -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_3_30684a993b667b2594890f734638e91b._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_3_30684a993b667b2594890f734638e91b._comment deleted file mode 100644 index 83c033aed..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_3_30684a993b667b2594890f734638e91b._comment +++ /dev/null @@ -1,142 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawltxdgYMUK4CMJh3jC8AlegwyoiHA9Ka7o" - nickname="Justin" - subject="comment 3" - date="2014-01-29T18:43:07Z" - content=""" -Here is the relevant portion of the test output. Sorry for getting caught up in my manual troubleshooting and not providing this info earlier. - - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - ok - push origin - Counting objects: 21, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (13/13), done. - Writing objects: 100% (16/16), 1.62 KiB | 0 bytes/s, done. - Total 16 (delta 2), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - 5a1abd2..b0de6d7 git-annex -> synced/git-annex - 4539cc8..af0b4de annex/direct/master -> synced/master - ok - add conflictor/subfile ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - remote: Counting objects: 21, done. - remote: Compressing objects: 100% (13/13), done. - remote: Total 16 (delta 2), reused 0 (delta 0) - Unpacking objects: 100% (16/16), done. - From c:/Users/geibeljt/annex/.t\repo - 4539cc8..af0b4de master -> origin/master - 5a1abd2..b0de6d7 synced/git-annex -> origin/synced/git-annex - 4539cc8..af0b4de synced/master -> origin/synced/master - - Adding conflictor/subfile - CONFLICT (directory/file): There is a directory with name conflictor in HEAD. Adding conflictor as conflictor~ - refs_remotes_origin_synced_master - Automatic merge failed; fix conflicts and then commit the result. - (Recording state in git...) - conflictor: needs merge - [annex/direct/master 7b21326] git-annex automatic merge conflict fix - - Merge conflict was automatically resolved; you may want to examine the result. - ok - (merging origin/synced/git-annex into git-annex...) - (Recording state in git...) - push origin - Counting objects: 32, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (19/19), done. - Writing objects: 100% (23/23), 2.18 KiB | 0 bytes/s, done. - Total 23 (delta 7), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - b0de6d7..b64838f git-annex -> synced/git-annex - af0b4de..7b21326 annex/direct/master -> synced/master - ok - commit ok - pull r2 - remote: Counting objects: 32, done. - remote: Compressing objects: 100% (19/19), done. - remote: Total 23 (delta 7), reused 0 (delta 0) - Unpacking objects: 100% (23/23), done. - From ../../.t\tmprepo36 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/master -> r2/synced/master - - Updating af0b4de..7b21326 - Fast-forward - conflictor | 1 - - conflictor.variant-cc12 | 1 + - conflictor/subfile | 1 + - 3 files changed, 2 insertions(+), 1 deletion(-) - delete mode 120000 conflictor - create mode 120000 conflictor.variant-cc12 - create mode 120000 conflictor/subfile - - Already up-to-date. - ok - (merging r2/git-annex into git-annex...) - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - - Adding conflictor/subfile - CONFLICT (file/directory): There is a directory with name conflictor in refs/remotes/origin/synced/master. Add - ing conflictor as conflictor~HEAD - Automatic merge failed; fix conflicts and then commit the result. - conflictor: needs merge - - git-annex: c:\Users\geibeljt\annex\.t\tmprepo37\.git\annex\merge\conflictor: renameFile: inappropriate type (i - s a directory) - failed - push origin - Counting objects: 29, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (15/15), done. - Writing objects: 100% (19/19), 1.71 KiB | 0 bytes/s, done. - Total 19 (delta 5), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - b64838f..0c094c8 git-annex -> synced/git-annex - ! [rejected] annex/direct/master -> synced/master (non-fast-forward) - error: failed to push some refs to 'c:/Users/geibeljt/annex/.t\repo' - hint: Updates were rejected because a pushed branch tip is behind its remote - hint: counterpart. Check out this branch and integrate the remote changes - hint: (e.g. 'git pull ...') before pushing again. - hint: See the 'Note about fast-forwards' in 'git push --help' for details. - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git - config) - failed - git-annex: sync: 2 failed - FAIL -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_4_30e847ff438eda036c57cc740b638d8a._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_4_30e847ff438eda036c57cc740b638d8a._comment deleted file mode 100644 index 9a33c64cc..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_4_30e847ff438eda036c57cc740b638d8a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.199" - subject="comment 4" - date="2014-01-29T19:48:51Z" - content=""" -Ok, what's happening is that code path calls System.PosixCompat.Files.rename, and on unix that maps to regular rename() which can rename files or directories, but on windows, it's a compatability stub that calls haskell's renameFile, which oddly refuses to rename directories. - -I remember testing my fix to the parent bug originally, but I don't know how. Possibly I changed something afterwards that exposed this new problem. - -Need to use System.Win32.File.moveFile, which actually can move directories too. Made this change in git, and you can download an windows autobuild of it already if you'd like. -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_5_04232cf2097676057cddf841ad47f44c._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_5_04232cf2097676057cddf841ad47f44c._comment deleted file mode 100644 index b6d338318..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_5_04232cf2097676057cddf841ad47f44c._comment +++ /dev/null @@ -1,86 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawltxdgYMUK4CMJh3jC8AlegwyoiHA9Ka7o" - nickname="Justin" - subject="comment 5" - date="2014-01-29T20:26:15Z" - content=""" -This seems to have affected a lot of tests, I'm now getting \"20 out of 72 tests failed\". In particular, error messages similar to the following show up now in many tests (with different paths for each test). - - git-annex: MoveFile \"c:\\Users\\geibeljt\\annex\\.t\\tmprepo36\\.git\\annex\\objects\\574\\4ca\\SHA256E-s7--6f - e7bd6dcd1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7\\SHA256E-s7--6fe7bd6dcd1d46cfa98027c64f1e51d596 - 64989c3b1e80a980bac1cb352a2ba7.map25112.tmp\" \"c:\\Users\\geibeljt\\annex\\.t\\tmprepo36\\.git\\annex\\objects\ - \574\\4ca\\SHA256E-s7--6fe7bd6dcd1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7\\SHA256E-s7--6fe7bd6dc - d1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7.map\": already exists (Cannot create a file when that f - ile already exists.) - - ---- -And here is the full output for the test that was originally failing. It now appears to fail much earlier than before. - - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - ok - push origin - Counting objects: 21, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (13/13), done. - Writing objects: 100% (16/16), 1.57 KiB | 0 bytes/s, done. - Total 16 (delta 3), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - a462941..43dcc49 git-annex -> synced/git-annex - 8268d47..3012c35 annex/direct/master -> synced/master - ok - add conflictor/subfile ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit - git-annex: MoveFile \"c:\\Users\\geibeljt\\annex\\.t\\tmprepo36\\.git\\annex\\objects\\574\\4ca\\SHA256E-s7--6f - e7bd6dcd1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7\\SHA256E-s7--6fe7bd6dcd1d46cfa98027c64f1e51d596 - 64989c3b1e80a980bac1cb352a2ba7.map25112.tmp\" \"c:\\Users\\geibeljt\\annex\\.t\\tmprepo36\\.git\\annex\\objects\ - \574\\4ca\\SHA256E-s7--6fe7bd6dcd1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7\\SHA256E-s7--6fe7bd6dc - d1d46cfa98027c64f1e51d59664989c3b1e80a980bac1cb352a2ba7.map\": already exists (Cannot create a file when that f - ile already exists.) - failed - pull origin - remote: Counting objects: 21, done. - remote: Compressing objects: 100% (13/13), done. - remote: Total 16 (delta 3), reused 0 (delta 0) - Unpacking objects: 100% (16/16), done. - From c:/Users/geibeljt/annex/.t\repo - 8268d47..3012c35 master -> origin/master - a462941..43dcc49 synced/git-annex -> origin/synced/git-annex - 8268d47..3012c35 synced/master -> origin/synced/master - - Updating 8268d47..3012c35 - Fast-forward - conflictor | 1 + - 1 file changed, 1 insertion(+) - create mode 120000 conflictor - ok - (merging origin/synced/git-annex into git-annex...) - (Recording state in git...) - push origin - Counting objects: 24, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (13/13), done. - Writing objects: 100% (16/16), 1.42 KiB | 0 bytes/s, done. - Total 16 (delta 6), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - 43dcc49..c040cd6 git-annex -> synced/git-annex - ok - git-annex: sync: 1 failed - FAIL -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_6_9cb32f198eee25b7175cc9ad1795acb3._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_6_9cb32f198eee25b7175cc9ad1795acb3._comment deleted file mode 100644 index 3ba917fcb..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_6_9cb32f198eee25b7175cc9ad1795acb3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.199" - subject="comment 6" - date="2014-01-29T21:24:34Z" - content=""" -I missed that moveFile refuses to overwrite existing files. This is fixed in git, and the autobuild is updating. -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_7_f8a70156d56c4be6cfbadb50e8a08285._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_7_f8a70156d56c4be6cfbadb50e8a08285._comment deleted file mode 100644 index a41cf40af..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_7_f8a70156d56c4be6cfbadb50e8a08285._comment +++ /dev/null @@ -1,174 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawltxdgYMUK4CMJh3jC8AlegwyoiHA9Ka7o" - nickname="Justin" - subject="comment 7" - date="2014-01-30T16:02:08Z" - content=""" -Alright, I've grabbed the latest autobuild and have tested again with 5.20140130-gcb99900. Back to failing just this one test case. Compared to my last two comments, the test appears to be getting further along before failing. - - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - ok - push origin - Counting objects: 21, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (13/13), done. - Writing objects: 100% (16/16), 1.66 KiB | 0 bytes/s, done. - Total 16 (delta 1), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - dafdb0b..2d106aa git-annex -> synced/git-annex - 688224a..18c2edb annex/direct/master -> synced/master - ok - add conflictor/subfile ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - remote: Counting objects: 21, done. - remote: Compressing objects: 100% (13/13), done. - remote: Total 16 (delta 1), reused 0 (delta 0) - Unpacking objects: 100% (16/16), done. - From c:/Users/geibeljt/annex/.t\repo - 688224a..18c2edb master -> origin/master - dafdb0b..2d106aa synced/git-annex -> origin/synced/git-annex - 688224a..18c2edb synced/master -> origin/synced/master - - Adding conflictor/subfile - CONFLICT (directory/file): There is a directory with name conflictor in HEAD. Adding conflictor as conflictor~ - refs_remotes_origin_synced_master - Automatic merge failed; fix conflicts and then commit the result. - (Recording state in git...) - conflictor: needs merge - [annex/direct/master 5026450] git-annex automatic merge conflict fix - - Merge conflict was automatically resolved; you may want to examine the result. - ok - (merging origin/synced/git-annex into git-annex...) - (Recording state in git...) - push origin - Counting objects: 32, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (19/19), done. - Writing objects: 100% (23/23), 2.18 KiB | 0 bytes/s, done. - Total 23 (delta 7), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - 2d106aa..aca0d04 git-annex -> synced/git-annex - 18c2edb..5026450 annex/direct/master -> synced/master - ok - commit ok - pull r2 - remote: Counting objects: 32, done. - remote: Compressing objects: 100% (19/19), done. - remote: Total 23 (delta 7), reused 0 (delta 0) - Unpacking objects: 100% (23/23), done. - From ../../.t\tmprepo36 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/master -> r2/synced/master - - Updating 18c2edb..5026450 - Fast-forward - conflictor | 1 - - conflictor.variant-cc12 | 1 + - conflictor/subfile | 1 + - 3 files changed, 2 insertions(+), 1 deletion(-) - delete mode 120000 conflictor - create mode 120000 conflictor.variant-cc12 - create mode 120000 conflictor/subfile - - Already up-to-date. - ok - (merging r2/git-annex into git-annex...) - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - - Adding conflictor/subfile - CONFLICT (file/directory): There is a directory with name conflictor in refs/remotes/origin/synced/master. Add - ing conflictor as conflictor~HEAD - Automatic merge failed; fix conflicts and then commit the result. - conflictor: needs merge - (Recording state in git...) - [annex/direct/master 82abd2f] git-annex automatic merge conflict fix - - Merge conflict was automatically resolved; you may want to examine the result. - ok - push origin - Counting objects: 32, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (17/17), done. - Writing objects: 100% (22/22), 1.95 KiB | 0 bytes/s, done. - Total 22 (delta 7), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - aca0d04..9d475c9 git-annex -> synced/git-annex - 5026450..82abd2f annex/direct/master -> synced/master - ok - add conflictor/subfile ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit ok - pull origin - remote: Counting objects: 32, done. - remote: Compressing objects: 100% (17/17), done. - remote: Total 22 (delta 7), reused 0 (delta 0) - Unpacking objects: 100% (22/22), done. - From c:/Users/geibeljt/annex/.t\repo - 5026450..82abd2f master -> origin/master - aca0d04..9d475c9 synced/git-annex -> origin/synced/git-annex - 5026450..82abd2f synced/master -> origin/synced/master - - Auto-merging conflictor/subfile - CONFLICT (add/add): Merge conflict in conflictor/subfile - Automatic merge failed; fix conflicts and then commit the result. - failed - (merging origin/synced/git-annex into git-annex...) - (Recording state in git...) - push origin - Counting objects: 34, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (17/17), done. - Writing objects: 100% (22/22), 2.05 KiB | 0 bytes/s, done. - Total 22 (delta 5), reused 0 (delta 0) - To c:/Users/geibeljt/annex/.t\repo - 9d475c9..13a0faa git-annex -> synced/git-annex - ! [rejected] annex/direct/master -> synced/master (non-fast-forward) - error: failed to push some refs to 'c:/Users/geibeljt/annex/.t\repo' - hint: Updates were rejected because a pushed branch tip is behind its remote - hint: counterpart. Check out this branch and integrate the remote changes - hint: (e.g. 'git pull ...') before pushing again. - hint: See the 'Note about fast-forwards' in 'git push --help' for details. - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git - config) - failed - git-annex: sync: 2 failed - FAIL -"""]] diff --git a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_8_02699dbf30270db090b00192850831db._comment b/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_8_02699dbf30270db090b00192850831db._comment deleted file mode 100644 index 4db1b7786..000000000 --- a/doc/bugs/Test_test__95__mixed__95__conflict__95__resolution_fails_on_Windows_with___34__conflictor_directory_missing__34__/comment_8_02699dbf30270db090b00192850831db._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawltxdgYMUK4CMJh3jC8AlegwyoiHA9Ka7o" - nickname="Justin" - subject="comment 8" - date="2014-02-04T02:05:36Z" - content=""" -With the changes pushed today, I confirm I also have all 72 tests passing on Windows 7 with 5.20140203-g83e6fb7. - -Thanks! -"""]] diff --git a/doc/bugs/The_tests_are_failing_to_build_now_on_commit_e0fdfb2e706da2cb1451193c658dc676b0530968.mdwn b/doc/bugs/The_tests_are_failing_to_build_now_on_commit_e0fdfb2e706da2cb1451193c658dc676b0530968.mdwn deleted file mode 100644 index be6db378c..000000000 --- a/doc/bugs/The_tests_are_failing_to_build_now_on_commit_e0fdfb2e706da2cb1451193c658dc676b0530968.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -I only saw this just now, but the tests fail to link/build on OSX - -<pre> -[181 of 181] Compiling Main ( git-annex.hs, tmp/Main.o ) -Linking git-annex ... -+ make -q test -+ '[' 1 = 1 ']' -+ ../maxtime 1800 make test -[175 of 175] Compiling Main ( test.hs, tmp/Main.o ) -test.hs:175:17: -Not in scope: data constructor `Types.Backend.KeySource' -test.hs:175:43: -`Types.Backend.keyFilename' is not a (visible) constructor field name -test.hs:175:76: -`Types.Backend.contentLocation' is not a (visible) constructor field name -** failed to build the test suite -make: *** [test] Error 1 -+ exit 4 -</pre> - -this issue seems to got introduced at commit e0fdfb2e706da2cb1451193c658dc676b0530968 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3.mdwn b/doc/bugs/Truncated_file_transferred_via_S3.mdwn deleted file mode 100644 index b489f60d9..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3.mdwn +++ /dev/null @@ -1,617 +0,0 @@ -### Please describe the problem. - -I have two machines connected with annex assistant via XMPP and S3. I placed a file into the annex directory on one computer, and it fairly immediately transferred to the other, as expected. However the resulting file appears to be truncated. - -### What steps will reproduce the problem? - -Unknown, I haven't noticed this happen before. - -### What version of git-annex are you using? On what operating system? - -The sending end was from commit ef1fd09c5c1c3950727f0760df36075e45192b33 (Tue Jul 2 16:52:43 2013 +0000), the receiving end was at 1c16de8ebcef6c1920a8437af380f8aea5a2c535 (Wed Jun 12 20:31:43 2013 +0000). Both on Ubuntu 13.04. - -### Please provide any additional information below. - -Details of the file at the sending end: - -[[!format text """ -$ stat git-annex_4.20130627_amd64.deb - Bestand: ‘git-annex_4.20130627_amd64.deb’ - Grootte: 10140744 Blokken: 19808 IO-blok: 4096 normaal bestand -Apparaat: 801h/2049d Inode: 27394054 Koppelingen: 1 -Toegang: (0644/-rw-r--r--) UID: ( 1000/ robin) GID: ( 1000/ robin) -Toegang: 2013-07-03 21:57:26.774297184 +1200 -Gewijzigd: 2013-07-03 21:57:25.526306867 +1200 -Veranderd: 2013-07-03 21:57:26.770297214 +1200 -"""]] - -and at the receiving end: - -[[!format text """ - Bestand: ‘git-annex_4.20130627_amd64.deb’ - Grootte: 10105870 Blokken: 19760 IO-blok: 4096 normaal bestand -Apparaat: 16h/22d Inode: 6167474 Koppelingen: 1 -Toegang: (0664/-rw-rw-r--) UID: ( 1000/ robin) GID: ( 1000/ robin) -Toegang: 2013-07-03 10:58:02.653724449 +0100 -Gewijzigd: 2013-07-03 10:58:02.365724461 +0100 -Veranderd: 2013-07-03 10:58:02.369724461 +0100 -"""]] - -(it was coincidence I expect that it was a deb of git-annex I'd just made :) - -Some more poking indicates that it's not strictly a truncation, not too far into the file, the content changes: - -Sent: - -[[!format text """ -00002a0 4ea6 bb1e 4c18 d54e b836 b19a d9a2 6314 -00002b0 4a0d 2954 d6aa fb42 2699 7437 df7f 6a6d -00002c0 7f7f 4f1c bce5 5e0f 5cc3 d5b1 e896 2829 -00002d0 4ed2 8426 9496 a669 3dd1 d6ed 26dd 3b1d -00002e0 4c2a 4ef2 e29b 778c 4818 0e49 990e 314c -"""]] - -Received: - -[[!format text """ -00002a0 4ea6 bb1e 4c18 d54e b836 b19a d9a2 6314 -00002b0 544a aa29 42d6 99fb 3726 7f74 6ddf 7f6a -00002c0 1c7f e54f 0fbc c35e b15c 96d5 29e8 d228 -00002d0 264e 9684 6994 d1a6 ed3d ddd6 1d26 2a3b -00002e0 f24c 9b4e 8ce2 1877 4948 0e0e 4c99 1931 -"""]] - -Oddly, there seems to be a pattern in the difference of the first incorrect row, it looks like kind of like strange endian weirdness rearranging things. - -aabb ccdd eeff gghh - -becomes: - -bbdd ffcc hhee ..gg - -where the .. comes from further along the pattern. - -Deleting and re-adding the file doesn't cause the new version to appear, but that's presumably because it's addressing by SHA, so it doesn't see that as a change. - -[[!format text """ -# 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 - -Sending machine: - -(started...) [2013-07-03 21:57:17 NZST] XMPPSendPack: Syncing with eythian -[2013-07-03 21:57:17 NZST] XMPPReceivePack: Syncing with eythian -Everything up-to-date -[2013-07-03 21:57:25 NZST] Committer: Adding git-annex..amd64.deb - -add git-annex_4.20130627_amd64.deb (checksum...) [2013-07-03 21:57:25 NZST] Committer: Committing changes to git -[2013-07-03 21:57:25 NZST] Pusher: Syncing with backups -To /mnt/backups/annex - 2783051..69b3503 git-annex -> synced/git-annex - 0b10576..e1b6f29 master -> synced/master -(gpg) Already up-to-date. -Already up-to-date. -[2013-07-03 21:57:26 NZST] XMPPSendPack: Syncing with eythian -[2013-07-03 21:57:26 NZST] Committer: Adding git-annex..amd64.deb -ok -(Recording state in git...) -(Recording state in git...) - - -add git-annex_4.20130627_amd64.deb (checksum...) [2013-07-03 21:57:26 NZST] Committer: Committing changes to git - -0% 96.0KB/s 1m42s[2013-07-03 21:57:27 NZST] Pusher: Syncing with backups -To /mnt/backups/annex - 69b3503..026ba8e git-annex -> synced/git-annex -To xmpp::eythian@jabber.kallisti.net.nz - 2783051..69b3503 git-annex -> refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex - 0b10576..e1b6f29 master -> refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master -1% 127.9KB/s 1m16s[2013-07-03 21:57:27 NZST] XMPPSendPack: Syncing with eythian -25% 631.7KB/s 12sTo xmpp::eythian@jabber.kallisti.net.nz - 69b3503..35b3fd8 git-annex -> refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex -[2013-07-03 21:57:30 NZST] XMPPSendPack: Syncing with eythian -51% 1.2MB/s 4sEverything up-to-date -[2013-07-03 21:57:34 NZST] Transferrer: Uploaded git-annex..amd64.deb -[2013-07-03 21:57:34 NZST] Pusher: Syncing with backups -To /mnt/backups/annex - 026ba8e..1eb67d8 git-annex -> synced/git-annex -[2013-07-03 21:57:35 NZST] XMPPSendPack: Syncing with eythian -To xmpp::eythian@jabber.kallisti.net.nz - 35b3fd8..1eb67d8 git-annex -> refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex -[2013-07-03 21:57:36 NZST] XMPPSendPack: Syncing with eythian -Everything up-to-date -[2013-07-03 21:58:03 NZST] XMPPReceivePack: Syncing with eythian -Already up-to-date. -[2013-07-03 21:58:04 NZST] XMPPReceivePack: Syncing with eythian -[2013-07-03 22:09:44 NZST] XMPPSendPack: Syncing with eythian -To xmpp::eythian@jabber.kallisti.net.nz - 1eb67d8..822dbb1 git-annex -> refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex -[2013-07-03 22:09:45 NZST] XMPPSendPack: Syncing with eythian -Everything up-to-date - -Receiving machine: - -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from a18/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from a22/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from a20/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from b24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from c27/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from c25/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from c16/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from c22/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from c21/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d23/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d15/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d27/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d15/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d21/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from d24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from f21/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from h24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from h24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from h26/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from j22/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from j20/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from j23/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from k22/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from k26/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from k26/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from k22/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from l26/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from l17/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from m32/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from m23/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from m18/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from m21/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from o20/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s24/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s19/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s21/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s25/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s19/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s20/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s25/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s16/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from s26/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from w23/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from w20/msn Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: sending to new client: e7/27209141331372845435882587 "Pushing \"e57\" (CanPush (UUID \"2c0b788e-7b2d-474b-8963-d889b9556229\") [0b10576100879220b2f50bf53f552befe2fda8de,27830516f221de09f7906954ba0bcc6b3dd31680])" -[2013-07-03 10:57:16 BST] XMPPClient: sending to new client: e7/27209141331372845435882587 "Pushing \"e57\" (PushRequest (UUID \"2c0b788e-7b2d-474b-8963-d889b9556229\"))" -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from m9/Adium Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from p6/NEW_HOTNESS Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"query\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"\"])], elementNodes = []})","QueryPresence"] -[2013-07-03 10:57:16 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"push\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"])], elementNodes = []})","NotifyPush [UUID \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"]"] -[2013-07-03 10:57:17 BST] XMPPClient: push notification for -[2013-07-03 10:57:17 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:17 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"query\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"\"])], elementNodes = []})","QueryPresence"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [0b10576100879220b2f50bf53f552befe2fda8de,27830516f221de09f7906954ba0bcc6b3dd31680])"] -[2013-07-03 10:57:17 BST] XMPPClient: ignoring CanPush with known shas -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (PushRequest (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:17 BST] XMPPSendPack: started running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:17 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:17 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:17 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","branch","-f","synced/master"] -[2013-07-03 10:57:17 BST] XMPPSendPack: Syncing with eythian -[2013-07-03 10:57:17 BST] XMPPClient: sending: Pushing "e57" (StartingPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:17 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","push","eythian","git-annex:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex","refs/heads/master:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master"] -[2013-07-03 10:57:17 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:17 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:17 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:17 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 1 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:57:17 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 2 \"<elided>\")"] -[2013-07-03 10:57:17 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:17 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 2 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:57:17 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:17 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 2 "<elided>") -[2013-07-03 10:57:17 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:17 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 3 "<elided>") -[2013-07-03 10:57:17 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 3 \"<elided>\")"] -[2013-07-03 10:57:17 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 3 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 4 \"<elided>\")"] -[2013-07-03 10:57:17 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 4 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:57:17 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 5 \"<elided>\")"] -[2013-07-03 10:57:17 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 5 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:57:17 BST] XMPPClient: sending: Pushing "e57" (SendPackOutput 1 "<elided>") -[2013-07-03 10:57:17 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:18 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:18 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:18 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:18 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:18 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:18 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackDone ExitSuccess)"] -[2013-07-03 10:57Everything up-to-date -:18 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackDone ExitSuccess) in SendPack inbox "e57" -[2013-07-03 10:57:18 BST] XMPPSendPack: finished running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:21 BST] XMPPClient: received: ["Presence from a15/android_talk53f054b9e972 Nothing"] -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"push\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"])], elementNodes = []})","NotifyPush [UUID \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"]"] -[2013-07-03 10:57:26 BST] XMPPClient: push notification for -[2013-07-03 10:57:26 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:26 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"query\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"\"])], elementNodes = []})","QueryPresence"] -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,69b3503287d87c26989a755d0cc660c3c68f2c80])"] -[2013-07-03 10:57:26 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:26 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,69b3503287d87c26989a755d0cc660c3c68f2c80])"] -[2013-07-03 10:57:26 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:26 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:26 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:26 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:26 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:26 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:26 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:26 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:26 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 2 "<elided>") -[2013-07-03 10:57:26 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:27 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:27 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:27 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 2 \"<elided>\")"] -[2013-07-03 10:57:27 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 2 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:27 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 3 "<elided>") -[2013-07-03 10:57:27 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:27 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..27830516f221de09f7906954ba0bcc6b3dd31680","--oneline","-n1"] -[2013-07-03 10:57:27 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 4 "<elided>") -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..69b3503287d87c26989a755d0cc660c3c68f2c80","--oneline","-n1"] -[2013-07-03 10:57:27 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:27 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:27 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","69b3503287d87c26989a755d0cc660c3c68f2c80"] -[2013-07-03 10:57:27 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","69b3503287d87c26989a755d0cc660c3c68f2c80..refs/heads/git-annex","--oneline","-n1"] -[2013-07-03 10:57:27 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-ref","refs/heads/git-annex","69b3503287d87c26989a755d0cc660c3c68f2c80"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:27 BST] TransferScanner: starting scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:27 BST] Merger: merging refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master into refs/heads/master -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","ls-files","--cached","-z","--"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/master"] -[2013-07-03 10:57:27 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex/.git/annex/merge/","merge","--no-edit","refs/synced/9e67bebc-655c-47da-97a0-2bb02bbbc580/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master"] -Updating 0b10576..e1b6f29 -Fast-forward - git-annex_4.20130627_amd64.deb | 1 + - 1 file changed, 1 insertion(+) - create mode 120000 git-annex_4.20130627_amd64.deb -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/master"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-tree","-z","--raw","--no-renames","-l0","-r","0b10576100879220b2f50bf53f552befe2fda8de","e1b6f2944e7d082299cb1696c55d9064a11c4577"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..69b3503287d87c26989a755d0cc660c3c68f2c80","--oneline","-n1"] -[2013-07-03 10:57:27 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","refs/heads/git-annex"] -[2013-07-03 10:57:28 BST] Watcher: add symlink git-annex_4.20130627_amd64.deb -[2013-07-03 10:57:28 BST] chat: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","hash-object","-t","blob","-w","--stdin"] -[2013-07-03 10:57:28 BST] Committer: committing 1 changes -[2013-07-03 10:57:28 BST] Committer: Committing changes to git -[2013-07-03 10:57:28 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"push\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"])], elementNodes = []})","NotifyPush [UUID \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"]"] -[2013-07-03 10:57:28 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:28 BST] XMPPClient: push notification for -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"] -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:28 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--head","refs/heads/git-annex","HEAD"] -[2013-07-03 10:57:28 BST] XMPPClient: sending: Pushing "e30" (CanPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229") [e1b6f2944e7d082299cb1696c55d9064a11c4577,69b3503287d87c26989a755d0cc660c3c68f2c80]) -[2013-07-03 10:57:28 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"query\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"\"])], elementNodes = []})","QueryPresence"] -[2013-07-03 10:57:28 BST] XMPPClient: exploded undirected message to clients e7/27209141331372845435882587 -[2013-07-03 10:57:28 BST] XMPPClient: sending to new client: e7/27209141331372845435882587 "Pushing \"e57\" (CanPush (UUID \"2c0b788e-7b2d-474b-8963-d889b9556229\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,69b3503287d87c26989a755d0cc660c3c68f2c80])" -[2013-07-03 10:57:28 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,026ba8e7ba89bccd22f5ff31a26c82ee75641b55])"] -[2013-07-03 10:57:28 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:28 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:28 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:28 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:29 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,026ba8e7ba89bccd22f5ff31a26c82ee75641b55])"] -[2013-07-03 10:57:29 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:29 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:29 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:29 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})"] -[2013-07-03 10:57:29 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:29 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:29 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:29 BST] TransferScanner: finished scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:29 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:29 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:30 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 2 \"<elided>\")"] -[2013-07-03 10:57:30 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 2 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 2 "<elided>") -[2013-07-03 10:57:30 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..69b3503287d87c26989a755d0cc660c3c68f2c80","--oneline","-n1"] -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 3 "<elided>") -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..35b3fd81218834a29b9f516b64b4671c0b0902d3","--oneline","-n1"] -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:30 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","35b3fd81218834a29b9f516b64b4671c0b0902d3"] -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","35b3fd81218834a29b9f516b64b4671c0b0902d3..refs/heads/git-annex","--oneline","-n1"] -[2013-07-03 10:57:30 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-ref","refs/heads/git-annex","35b3fd81218834a29b9f516b64b4671c0b0902d3"] -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..35b3fd81218834a29b9f516b64b4671c0b0902d3","--oneline","-n1"] -[2013-07-03 10:57:30 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:30 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","refs/heads/git-annex"] -[2013-07-03 10:57:30 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:30 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:30 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:30 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 2 "<elided>") -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:30 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 3 "<elided>") -[2013-07-03 10:57:30 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:31 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:31 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:31 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:31 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:31 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:31 BST] TransferScanner: starting scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:31 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","ls-files","--cached","-z","--"] -[2013-07-03 10:57:32 BST] TransferScanner: finished scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:34 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"push\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"])], elementNodes = []})","NotifyPush [UUID \"a23dd126-7bb7-42ce-b15a-b01990df5f2a\"]"] -[2013-07-03 10:57:34 BST] XMPPClient: push notification for -[2013-07-03 10:57:34 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:57:34 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:57:35 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \"query\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \"\"])], elementNodes = []})","QueryPresence"] -[2013-07-03 10:57:35 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,1eb67d85f89c92345757805d83939d75e8ce54a0])"] -[2013-07-03 10:57:35 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:35 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:35 BST] XMPPClient: received: ["Pushing \"e57\" (CanPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,1eb67d85f89c92345757805d83939d75e8ce54a0])"] -[2013-07-03 10:57:35 BST] XMPPClient: sending: Pushing "e57" (PushRequest (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:57:35 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:35 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:35 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:35 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:35 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:35 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:35 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:35 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 2 "<elided>") -[2013-07-03 10:57:35 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:36 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:36 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:36 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 2 \"<elided>\")"] -[2013-07-03 10:57:36 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 2 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:36 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 3 "<elided>") -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:36 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:36 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:36 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 4 "<elided>") -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..35b3fd81218834a29b9f516b64b4671c0b0902d3","--oneline","-n1"] -[2013-07-03 10:57:36 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..1eb67d85f89c92345757805d83939d75e8ce54a0","--oneline","-n1"] -[2013-07-03 10:57:36 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:36 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:36 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","1eb67d85f89c92345757805d83939d75e8ce54a0"] -[2013-07-03 10:57:36 BST] chat: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","hash-object","-t","blob","-w","--stdin"] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","1eb67d85f89c92345757805d83939d75e8ce54a0..refs/heads/git-annex","--oneline","-n1"] -[2013-07-03 10:57:36 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-ref","refs/heads/git-annex","1eb67d85f89c92345757805d83939d75e8ce54a0"] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:57:36 BST] TransferScanner: starting scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..1eb67d85f89c92345757805d83939d75e8ce54a0","--oneline","-n1"] -[2013-07-03 10:57:36 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-index","--raw","-z","-r","--no-renames","-l0","--cached","refs/heads/git-annex"] -[2013-07-03 10:57:36 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","ls-files","--cached","-z","--"] -[2013-07-03 10:57:37 BST] XMPPClient: received: ["Pushing \"e57\" (StartingPush (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:57:37 BST] XMPPReceivePack: started running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:57:37 BST] XMPPReceivePack: Syncing with eythian -[2013-07-03 10:57:37 BST] chat: git ["receive-pack","/home/robin/Bureaublad/annex"] -[2013-07-03 10:57:37 BST] XMPPClient: sending: Pushing "e57" (ReceivePackOutput 1 "<elided>") -[2013-07-03 10:57:37 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:37 BST] XMPPClient: received: ["Pushing \"e57\" (SendPackOutput 1 \"<elided>\")"] -[2013-07-03 10:57:37 BST] XMPPClient: NetMessager stored Pushing "e57" (SendPackOutput 1 "<elided>") in ReceivePack inbox "e57" -[2013-07-03 10:57:37 BST] XMPPReceivePack: finished running push Pushing "e57" (StartingPush (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:57:37 BST] XMPPClient: sending: Pushing "e57" (ReceivePackDone ExitSuccess) -[2013-07-03 10:57:37 BST] TransferScanner: queued Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Nothing : expensive scan found missing object -[2013-07-03 10:57:37 BST] Transferrer: Transferring: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Nothing -[2013-07-03 10:57:38 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:57:38 BST] TransferScanner: finished scan of [Remote { name ="eythian" }] -[2013-07-03 10:57:38 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Nothing -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 131008 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 262016 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 393024 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 524032 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 655040 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 786048 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 917056 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1048064 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1179072 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1310080 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1441088 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1572096 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1703104 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1834112 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 1965120 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2096128 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2227136 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2358144 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2489152 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2620160 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2751168 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 2882176 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3013184 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3144192 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3275200 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3406208 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3537216 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3668224 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3799232 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 3930240 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4192256 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4323264 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4454272 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4585280 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4716288 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 4847296 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5109312 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5240320 -[2013-07-03 10:58:01 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5371328 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5502336 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5633344 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5764352 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 5895360 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6157376 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6288384 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6419392 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6550400 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6681408 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 6943424 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7074432 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7205440 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7336448 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7598464 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7729472 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7860480 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 7991488 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8122496 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8253504 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8384512 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8515520 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8646528 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8646528 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8777536 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 8908544 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9039552 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9170560 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9301568 -[2013-07-03 10:58:02 BST] XMPPClient: received: ["Unknown message"] -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9432576 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9563584 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9694592 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9694592 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9825600 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 9956608 -[2013-07-03 10:58:02 BST] TransferWatcher: transfer starting: Download UUID "971c808b-ce67-4edb-b317-21c0da6b5462" git-annex_4.20130627_amd64.deb Just 10087616 -[2013-07-03 10:58:02 BST] Watcher: add symlink git-annex_4.20130627_amd64.deb -[2013-07-03 10:58:02 BST] Transferrer: Downloaded git-annex..amd64.deb -[2013-07-03 10:58:02 BST] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "971c808b-ce67-4edb-b317-21c0da6b5462", transferKey = Key {keyName = "8514472fd7c4ea28b385b0335db408ee28f58911b5ad0ba9d2e2cbfd1b99c86d.deb", keyBackendName = "SHA256E", keySize = Just 10140744, keyMtime = Nothing}} -[2013-07-03 10:58:02 BST] chat: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","hash-object","-t","blob","-w","--stdin"] -[2013-07-03 10:58:02 BST] chat: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","hash-object","-w","--stdin-paths"] -[2013-07-03 10:58:02 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","write-tree"] -[2013-07-03 10:58:02 BST] chat: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","commit-tree","9b6f9b59c19650e25f11e2d50acb3bf25b631150","-p","refs/heads/git-annex"] -[2013-07-03 10:58:02 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-ref","refs/heads/git-annex","822dbb101976fed8b775d04bba6da876c591a9f0"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","git-annex"] -[2013-07-03 10:58:02 BST] Committer: committing 1 changes -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/git-annex"] -[2013-07-03 10:58:02 BST] Committer: Committing changes to git -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..822dbb101976fed8b775d04bba6da876c591a9f0","--oneline","-n1"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","log","refs/heads/git-annex..1eb67d85f89c92345757805d83939d75e8ce54a0","--oneline","-n1"] -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--head","refs/heads/git-annex","HEAD"] -[2013-07-03 10:58:02 BST] feed: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","update-index","-z","--index-info"] -[2013-07-03 10:58:02 BST] XMPPClient: sending: Pushing "e30" (CanPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229") [e1b6f2944e7d082299cb1696c55d9064a11c4577,822dbb101976fed8b775d04bba6da876c591a9f0]) -[2013-07-03 10:58:02 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"] -[2013-07-03 10:58:02 BST] XMPPClient: exploded undirected message to clients e7/27209141331372845435882587 -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})"] -[2013-07-03 10:58:03 BST] XMPPClient: sending to new client: e7/27209141331372845435882587 "Pushing \"e57\" (CanPush (UUID \"2c0b788e-7b2d-474b-8963-d889b9556229\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,822dbb101976fed8b775d04bba6da876c591a9f0])" -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (PushRequest (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:58:03 BST] XMPPSendPack: started running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:03 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","branch","-f","synced/master"] -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:03 BST] XMPPSendPack: Syncing with eythian -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:03 BST] Merger: merging refs/heads/synced/master into refs/heads/master -[2013-07-03 10:58:03 BST] XMPPClient: sending: Pushing "e57" (StartingPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:58:03 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","push","eythian","git-annex:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex","refs/heads/master:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master"] -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:03 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/master"] -[2013-07-03 10:58:03 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex/.git/annex/merge/","merge","--no-edit","refs/heads/synced/master"] -Already up-to-date. -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--hash","refs/heads/master"] -[2013-07-03 10:58:03 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","diff-tree","-z","--raw","--no-renames","-l0","-r","e1b6f2944e7d082299cb1696c55d9064a11c4577","e1b6f2944e7d082299cb1696c55d9064a11c4577"] -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (PushRequest (UUID \"9e67bebc-655c-47da-97a0-2bb02bbbc580\"))"] -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 1 \"<elided>\")"] -[2013-07-03 10:58:03 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 1 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 2 \"<elided>\")"] -[2013-07-03 10:58:03 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 2 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 3 \"<elided>\")"] -[2013-07-03 10:58:03 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 3 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 4 \"<elided>\")"] -[2013-07-03 10:58:03 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 4 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:03 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 5 \"<elided>\")"] -[2013-07-03 10:58:03 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 5 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:03 BST] XMPPClient: sending: Pushing "e57" (SendPackOutput 1 "<elided>") -[2013-07-03 10:58:03 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:58:03 BST] XMPPClient: sending: Pushing "e57" (SendPackOutput 2 "<elided>") -[2013-07-03 10:58:03 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:58:04 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 6 \"<elided>\")"] -[2013-07-03 10:58:04 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 6 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:04 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 7 \"<elided>\")"] -[2013-07-03 10:58:04 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 7 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:04 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackDone ExitSuccess)"] -[2013-07-03 10:58To xmpp::eythian@jabber.kallisti.net.nz -:0 2783051..822dbb1 4git-annex -> refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex -BS 0b10576..e1b6f29 Tmaster -> refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master] - XMPPClient: NetMessager stored Pushing "e57" (ReceivePackDone ExitSuccess) in SendPack inbox "e57" -[2013-07-03 10:58:04 BST] XMPPSendPack: finished running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:58:04 BST] XMPPSendPack: started running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) -[2013-07-03 10:58:04 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:04 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:04 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","symbolic-ref","HEAD"] -[2013-07-03 10:58:04 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","refs/heads/master"] -[2013-07-03 10:58:04 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","show-ref","--head","refs/heads/git-annex","HEAD"] -[2013-07-03 10:58:04 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","branch","-f","synced/master"] -[2013-07-03 10:58:04 BST] XMPPClient: sending: Pushing "e30" (CanPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229") [e1b6f2944e7d082299cb1696c55d9064a11c4577,822dbb101976fed8b775d04bba6da876c591a9f0]) -[2013-07-03 10:58:04 BST] XMPPSendPack: Syncing with eythian -[2013-07-03 10:58:04 BST] XMPPClient: exploded undirected message to clients e7/27209141331372845435882587 -[2013-07-03 10:58:04 BST] call: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","push","eythian","git-annex:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/git-annex","refs/heads/master:refs/synced/2c0b788e-7b2d-474b-8963-d889b9556229/ZXl0aGlhbkBqYWJiZXIua2FsbGlzdGkubmV0Lm56/master"] -[2013-07-03 10:58:04 BST] XMPPClient: sending: Pushing "e57" (StartingPush (UUID "2c0b788e-7b2d-474b-8963-d889b9556229")) -[2013-07-03 10:58:04 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:58:04 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:58:05 BST] XMPPClient: received: ["Presence from e7/27209141331372845435882587 Just (Element {elementName = Name {nameLocalName = \"git-annex\", nameNamespace = Just \"git-annex\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})"] -[2013-07-03 10:58:05 BST] XMPPClient: sending to new client: e7/27209141331372845435882587 "Pushing \"e57\" (CanPush (UUID \"2c0b788e-7b2d-474b-8963-d889b9556229\") [e1b6f2944e7d082299cb1696c55d9064a11c4577,822dbb101976fed8b775d04bba6da876c591a9f0])" -[2013-07-03 10:58:05 BST] XMPPClient: received: ["Presence from 0/ Nothing"] -[2013-07-03 10:58:05 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackOutput 1 \"<elided>\")"] -[2013-07-03 10:58:05 BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackOutput 1 "<elided>") in SendPack inbox "e57" -[2013-07-03 10:58:05 BST] XMPPClient: sending: Pushing "e57" (SendPackOutput 1 "<elided>") -[2013-07-03 10:58:05 BST] XMPPClient: to client: e7/27209141331372845435882587 -[2013-07-03 10:58:05 BST] XMPPClient: received: ["Pushing \"e57\" (ReceivePackDone ExitSuccess)"] -[2013-07-03 10:58:05 Everything up-to-date -BST] XMPPClient: NetMessager stored Pushing "e57" (ReceivePackDone ExitSuccess) in SendPack inbox "e57" -[2013-07-03 10:58:05 BST] XMPPSendPack: finished running push Pushing "e57" (PushRequest (UUID "9e67bebc-655c-47da-97a0-2bb02bbbc580")) True -[2013-07-03 10:58:27 BST] read: git ["--git-dir=/home/robin/Bureaublad/annex/.git","--work-tree=/home/robin/Bureaublad/annex","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"] - - -# End of transcript or log. -"""]] - -> Pretty sure this must have been due to Char8 truncation. So, -> [[fixed|done]]. diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment deleted file mode 100644 index f3583d31b..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.4.193" - subject="comment 1" - date="2013-07-05T16:49:33Z" - content=""" -Did you get a chance to run `git annex fsck` on the file? I'd hope it would detect this problem. - -It's certainly possible for data to get corrupted somehow in transit. git-annex does not check that it got the expected contents until a fsck happens. -"""]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_2_75a2c272c36fc4fe8f9a79a3fd3ac4e5._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_2_75a2c272c36fc4fe8f9a79a3fd3ac4e5._comment deleted file mode 100644 index 7eeb7ccaf..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_2_75a2c272c36fc4fe8f9a79a3fd3ac4e5._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eythian" - nickname="eythian" - subject="comment 2" - date="2013-07-11T12:44:24Z" - content=""" -I did it just then: - - fsck git-annex_4.20130627_amd64.deb (checksum...) [2013-07-11 13:38:46 BST] read: sha256sum [\"git-annex_4.20130627_amd64.deb\"] - - Bad file content; left in place for you to examine - failed - -however, more concerningly, this happened to almost all the files in the repo: - - git-annex: fsck: 79 failed - -and they do seem to be a different size between the two computers. -"""]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_3_3dae1914c8c90fdad0c21e1fc795f2ca._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_3_3dae1914c8c90fdad0c21e1fc795f2ca._comment deleted file mode 100644 index ecf3c4a1a..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_3_3dae1914c8c90fdad0c21e1fc795f2ca._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.7.235" - subject="comment 3" - date="2013-07-11T16:16:03Z" - content=""" -Would all these files that wrong size have been transferred to this computer via S3 too? And can you spot the same weird endinaness problem in them too? Are the files only getting corrupted on one computer, or on both? -"""]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_4_3c5fe109f2196cfc196c30da3b62bafd._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_4_3c5fe109f2196cfc196c30da3b62bafd._comment deleted file mode 100644 index b22380dc0..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_4_3c5fe109f2196cfc196c30da3b62bafd._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eythian" - nickname="eythian" - subject="comment 4" - date="2013-07-12T10:14:16Z" - content=""" -Yes, they would have gone via S3 too. - -However, it seems that running git annex fsck assumed the files on disk were correct, and they got resynched. So now both the computers have the incorrect version. I'll have a go pulling them out of backups and take a look. -"""]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment deleted file mode 100644 index 742d22e2d..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eythian" - nickname="eythian" - subject="comment 5" - date="2013-07-12T10:43:23Z" - content=""" -Good thing I set up obnam a while ago :) - -Anyway, yes, a very similar pattern of corruption can be seen here. It might be worth nothing that it starts in a different place in the file. The one I'm looking at now begins at byte 0x1C, whereas it was a little bit further into the file previously. - -I created a large file that'd make the issue really clear and synced it over, and of course, everything worked perfectly. - -Here is a pair of small files that shows the problem, from around the 0x4BC mark. - -<http://www.kallisti.net.nz/~robin/good-bad-annex-files.tar.gz> -"""]] diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment deleted file mode 100644 index b5c27c5fd..000000000 --- a/doc/bugs/Truncated_file_transferred_via_S3/comment_6_6aa9261c0cdb02c6dd66d25f5c71f622._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 6" - date="2014-05-28T00:33:48Z" - content=""" -I've just noticed the the S3 backend used Char8 for reading/writing encrypted files. I don't know that this could result in this problem, but it at least seems possible. If you can still reproduce the bug, try getting the next daily build and see if perhaps it fixed it. -"""]] diff --git a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error.mdwn b/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error.mdwn deleted file mode 100644 index 560597632..000000000 --- a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -I am receiving a weird error when trying to add a file into a git annex repo on Android. I can't explain how it got into this state, and I can't figure out how to fix it. - -### What steps will reproduce the problem? - -See the output below - I'm happy to run any debugging commands that are required. - -### What version of git-annex are you using? On what operating system? - -ASUS Transformer Infinity Android Tablet, Android 4.2.1. - -[[!format sh """ -git-annex version: 4.20130601-g7483ca4 -build flags: Assistant Webapp Testsuite S3 WebDAV Inotify XMPP DNS -local repository version: 3 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -"""]] - - -### Please provide any additional information below. - -[[!format sh """ -u0_a141@android:/sdcard/git-annex.home/Documents $ git annex add Music/MobileSheets/The\ New\ Real\ Book\ 1/New\ Real\ Book\ 1\ Eb_19.pdf -add Music/MobileSheets/The New Real Book 1/New Real Book 1 Eb_19.pdf (checksum...) unknown option -- reflink=auto -git-annex: /storage/emulated/legacy/git-annex.home/Documents/.git/annex/tmp/New Real Book 1 Eb15137.pdf: rename: does not exist (No such file or directory) -failed -git-annex: add: 1 failed -1|u0_a141@android:/sdcard/git-annex.home/Documents $ ls -la .git/annex/tmp/ -drwxrwxr-x 2 root sdcard_r 4096 Jun 14 13:42 . -drwxrwxr-x 6 root sdcard_r 4096 Jun 14 13:35 .. -u0_a141@android:/sdcard/git-annex.home/Documents $ -"""]] - -> Should be [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_1_928289956111d1b22f9d55f15b54f72f._comment b/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_1_928289956111d1b22f9d55f15b54f72f._comment deleted file mode 100644 index 84a7498c4..000000000 --- a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_1_928289956111d1b22f9d55f15b54f72f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-06-14T16:20:57Z" - content=""" -I suspect you probably have another file already in the repository with the same content as the file you're trying to add. That, or something like it is why you're the lucky one who got to discover this bug in the build of the Android app! ;) The exact reason doesn't matter much -- It seems that it's trying to run `cp --reflink=auto`, which works on the build system, but not using the minimal busybox cp shipped with the Android app. - -I have put out a fix, and the Android daily build has been updated, so you can upgrade to that. -"""]] diff --git a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_2_6a0cb836b93ba4cb1e07b11d5d2a7094._comment b/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_2_6a0cb836b93ba4cb1e07b11d5d2a7094._comment deleted file mode 100644 index 52441b074..000000000 --- a/doc/bugs/Unable_to_add_files_on_Android_due_to_weird_rename_error/comment_2_6a0cb836b93ba4cb1e07b11d5d2a7094._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawknOATcOkmzX4jKuET5Z2RsaFUNnLKnQsU" - nickname="Stephen" - subject="comment 2" - date="2013-06-14T23:01:35Z" - content=""" -Yep, it's fixed in the latest. Thanks! -"""]] diff --git a/doc/bugs/Unclear_output_during_git-annex_copy.mdwn b/doc/bugs/Unclear_output_during_git-annex_copy.mdwn deleted file mode 100644 index 12ae9a745..000000000 --- a/doc/bugs/Unclear_output_during_git-annex_copy.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -I noticed the following output during a `git-annex sync --content` run -which I found a little disconcerting: - - copy file.idx copy file.idx (gpg) (checking s3...) (to s3...) - ok - copy file.pack copy file.pack (checking s3...) (to s3...) - ok - (Recording state in git...) - -It's confusing that seemingly only the first file got encrypted (gpg). - -Fortunately, it appears that actually all files were encrypted (only GPGHMAC file names in remote location), -so this is hopefully just a cosmetic issue. - -git-annex version: 5.20141024-g613f396 - -> removed confusing output, [[done]] --[[Joey]] diff --git a/doc/bugs/Unicode_characters_lost__47__converted_in_metadata.mdwn b/doc/bugs/Unicode_characters_lost__47__converted_in_metadata.mdwn deleted file mode 100644 index ebfef3b77..000000000 --- a/doc/bugs/Unicode_characters_lost__47__converted_in_metadata.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -### Please describe the problem. - -Unicode characters in metadata are pruned/converted/lost: - - % git annex metadata -s caption='Unicode → … characters' test.W1z7M7.txt - metadata test.W1z7M7.txt - caption=Unicode & characters - caption-lastchanged=2015-03-04@08-55-26 - lastchanged=2015-03-04@08-55-26 - ok - (Recording state in git...) - -### What version of git-annex are you using? On what operating system? - -5.20141125 Debian - -> [[fixed|done]]; test pass. --[[Joey]] diff --git a/doc/bugs/Unicode_characters_lost__47__converted_in_metadata/comment_1_799fd2dc62dc51a6a8fa8a6d15d7a1f9._comment b/doc/bugs/Unicode_characters_lost__47__converted_in_metadata/comment_1_799fd2dc62dc51a6a8fa8a6d15d7a1f9._comment deleted file mode 100644 index 1ae278289..000000000 --- a/doc/bugs/Unicode_characters_lost__47__converted_in_metadata/comment_1_799fd2dc62dc51a6a8fa8a6d15d7a1f9._comment +++ /dev/null @@ -1,32 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-04T14:31:21Z" - content=""" -What I'm seeing is the unicode arrow is replaced with 0092 and the elipsis -with &. It's losing the other byte. - -The problem seems to be in the base64 encoding that's done, when the metadata -value contains spaces or a few other problem characters. These same -unicode characters roundtrip through without a problem when not embedded -in a string with spaces. - -<pre> -*Utility.Base64> let s = "…" -*Utility.Base64> (s, fromB64 $ toB64 s) -("\8230","&") -</pre> - -git-annex also uses base64 for encoding some creds -(and for tagged pushes over XMPP, but only the JID is encoded). - -The real culprit is the use of `w82s`, which doesn't handle multi-byte -characters. I can easily fix this by using `encodeW8` instead. -Audited git-annex for other problem w82s uses and don't see any, so will -only need to fix this once. - -Added a quickcheck test for fromB64 . toB64 roundtripping. - -Unfortunately, the entered unicode characters didn't get saved right, -so git-annex can do nothing to fix data that was already entered. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows.mdwn b/doc/bugs/Unicode_file_names_ignored_on_Windows.mdwn deleted file mode 100644 index 5d0b73b17..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. - -The "add" command silently ignores all files and directories with non-ascii characters. - -### What steps will reproduce the problem? - -I created empty repository (git init, git annex init). I created some files with ascii and nonascii file names (hacky.txt, háčky.txt). - -git annex add . correctly adds only hacky.txt. - -git annex add "háčky.txt" does nothing. - -### What version of git-annex are you using? On what operating system? - -git 1.9.0, -git-annex installer from 2014-03-06 - -Windows XP and 7 with czech localization. CP1250 is used for czech characters on windows. - -### Please provide any additional information below. - - $ ls - hacky.txt h????ky.txt - $ git annex add . - add hacky.txt ok - (Recording state in git...) - $ git annex status - D h├í─Źky.txt - -According to https://github.com/msysgit/msysgit/wiki/Git-for-Windows-Unicode-Support ls prints junk, but only to console. - - D:\anntest>git annex add "háčky.txt" --debug - [2014-03-18 14:28:03 Central Europe Standard Time] read: git ["--git-dir=D:\\anntest\\.git","--work-tree=D:\\anntest","-c","core.bare=false","ls-files","--others","--exclude-standard","-z","--","h\225\269ky.txt"] - [2014-03-18 14:28:03 Central Europe Standard Time] chat: git ["--git-dir=D:\\anntest\\.git","--work-tree=D:\\anntest","-c","core.bare=false","cat-file","--batch"] - [2014-03-18 14:28:03 Central Europe Standard Time] read: git ["--git-dir=D:\\anntest\\.git","--work-tree=D:\\anntest","-c","core.bare=false","ls-files","--modified","-z","--","h\225\269ky.txt"] - -I can provide additional information, just tell me what you need. - -> [[fixed|done]], although this is not the end of encoding issues -> on Windows. Updating [[todo/windows_support]] to discuss some other ones. -> --[[Joey]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_1_3dfa4559dceec50c08ba180f41b4c220._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_1_3dfa4559dceec50c08ba180f41b4c220._comment deleted file mode 100644 index c1778db78..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_1_3dfa4559dceec50c08ba180f41b4c220._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="analysis" - date="2014-03-18T17:54:09Z" - content=""" -The `git ls-files --others -z output` is fine; the mojibake seems to occur in git-annex's reading of that output, which uses GHC's filesystem encoding. On Linux it reads \"h\225\269ky.txt\" but on Windows, \"h\195\161\196\56461ky.txt\". - -So, it's failing to compose the multibyte characters, and it seems to have escaped the last byte (which should be \"\141\" based on the other 3) out into the high code plane used for undecodable bytes. - -Note that on Linux with LANG=C, the add works, and it sees \"h\56515\56481\56516\56461ky.txt\" -- in this case, all 4 bytes are represented in the high code plane, and so round-trip through ok despite the locale not supporting the utf8 encoding. - -Interestingly, while both `[readFile \"h\225\269ky.txt\", readFile \"h\56515\56481\56516\56461ky.txt\"]` work on Linux, only the former does on Windows. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_2_4dafea4367d455c2e63b0f7b1cc39559._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_2_4dafea4367d455c2e63b0f7b1cc39559._comment deleted file mode 100644 index 97d7012a1..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_2_4dafea4367d455c2e63b0f7b1cc39559._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 2" - date="2014-03-18T18:09:08Z" - content=""" -One approach might be to not use the GHC FileSystemEncoding on Windows, and assume that Windows filenames are always in a unicode encoding. After all, the FileSystemEncoding is only used by git-annex on Unix because Unix has no canonical encoding that will work for all filenames. - -Hmm, nope, I tried this and it just causes an \"invalid byte sequence\" crash when reading from git-ls-files. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_3_bdde68a990a330ee0cf626be44b1c132._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_3_bdde68a990a330ee0cf626be44b1c132._comment deleted file mode 100644 index 1f35dc9dd..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_3_bdde68a990a330ee0cf626be44b1c132._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 3" - date="2014-03-18T18:14:57Z" - content=""" -ghc docs on FileSystemEncoding: \"On Windows, this encoding *should not* be used if possible because the use of code pages is deprecated: Strings should be retrieved via the wide W-family of UTF-16 APIs instead\" -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_4_9140fb8034b1449ee2f4762093bc1f89._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_4_9140fb8034b1449ee2f4762093bc1f89._comment deleted file mode 100644 index e40a6ab33..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_4_9140fb8034b1449ee2f4762093bc1f89._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 4" - date="2014-03-18T18:42:57Z" - content=""" -As well as the default encoding, I've tried `utf8`, `utf16`, `utf16le`, and `utf16be` encodings, and none of them is able to successfully read the git ls-files output, all fail with encoding error. (I also tried `mkUTF16 RoundtripFailure` but it completely broke git-annex.) - -Unsure where to go from here.. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_5_661ca15b68bc0e3fbe85f11400570446._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_5_661ca15b68bc0e3fbe85f11400570446._comment deleted file mode 100644 index ccafb635e..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_5_661ca15b68bc0e3fbe85f11400570446._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk5aY0oBmuQtnoTNtji-dPgDw9p7J24YeY" - nickname="Jiří" - subject="further info" - date="2014-03-18T23:46:08Z" - content=""" -On my windows 7 machine, ls-files does return something better - - c:\JSH\antest>git --work-tree=c:\JSH\antest ls-files --others - \"h\303\241\304\215ky.txt\" - -If I am correct, it is unicode 225 269, but as octal utf-8. ls-files -z return correct utf-8 (68 C3 A1 C4 8D 6B ...) - -I will test that tomorrow also on windows xp on my work pc. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_6_0e8820169c0300d296c697154fd05dc4._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_6_0e8820169c0300d296c697154fd05dc4._comment deleted file mode 100644 index 4f7ec51fa..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_6_0e8820169c0300d296c697154fd05dc4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk5aY0oBmuQtnoTNtji-dPgDw9p7J24YeY" - nickname="Jiří" - subject="further info 2" - date="2014-03-19T11:53:17Z" - content=""" -And on my windows xp computer, git ls-files returns valid utf-8 too. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_7_b23a2bf106053f105798b270536057e5._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_7_b23a2bf106053f105798b270536057e5._comment deleted file mode 100644 index b5cf90ef0..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_7_b23a2bf106053f105798b270536057e5._comment +++ /dev/null @@ -1,38 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk5aY0oBmuQtnoTNtji-dPgDw9p7J24YeY" - nickname="Jiří" - subject="further info 3" - date="2014-03-19T16:23:58Z" - content=""" -Also ghc doesn't seem to do any weird transformations with that string - - import System.Process - import qualified Data.ByteString as S - import qualified Data.ByteString.UTF8 as U - import GHC.IO.Handle - - files :: S.ByteString -> [S.ByteString] - files ps - | S.null ps = [] - | otherwise = case search ps of - Nothing -> [ps] - Just n -> S.take n ps : files (S.drop (n+1) ps) - where search = S.elemIndex 0 - - main = do - let prc = CreateProcess { - cmdspec = RawCommand \"git\" [\"--work-tree=D:\\antest\",\"ls-files\",\"--others\",\"-z\",\"--\",\"h\225\269ky.txt\"], - cwd = Nothing, - env = Nothing, - std_in = Inherit, - std_out = CreatePipe, - std_err = Inherit, - close_fds = False, - create_group = False } - (_,Just out,_,_) <- createProcess prc - hSetBinaryMode out True - str <- S.hGetContents out - print $ map U.toString $ files str - -prints correctly [\"h\225\269ky.txt\"] I don't think that FilesystemEncoding will do any good on windows, since git seems to use utf-8 instead of normal windows console encoding. -"""]] diff --git a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_8_7f23911705eaa58a9230f19ab890e87f._comment b/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_8_7f23911705eaa58a9230f19ab890e87f._comment deleted file mode 100644 index 2cd4b346e..000000000 --- a/doc/bugs/Unicode_file_names_ignored_on_Windows/comment_8_7f23911705eaa58a9230f19ab890e87f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.102" - subject="comment 8" - date="2014-03-19T19:57:00Z" - content=""" -Windows & haskell? I'd only be more surprised if spj wandered in here. ;) - -So, that works because you're using ByteStrings. But git-annex mostly does not use ByteStrings, and it would be a lot of work to switch to them everywhere it reads FilePaths from git. - -But it seems my test yesterday using `hSetEncoding h Encoding.utf8` went wrong somehow. That does work. git-annex can operate on the file with that change. -"""]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll.mdwn b/doc/bugs/Uninstalling_removes_libcrypto.dll.mdwn deleted file mode 100644 index 642bcef8b..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. -Just feedback to you: -After I uninstalled git-annex (Windows), traditional git was not able to push changes to an origin server via ssh. -Instead I got an error "libcrypto.dll is missing". -Installing git once again after uninstalling git-annex solved the problem. - -### What steps will reproduce the problem? -Installing and uninstalling git-annex. - -### What version of git-annex are you using? On what operating system? -File "git-annex-installer.exe" downloaded 2014-11-09. -Windows 8. - -### 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. -"""]] - -> [[fixed|done]]; git-annex no longer includes its own ssh, and uses the -> one from msysgit. --[[Joey]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_1_0a0c8c62ca4d314f14d50306546c33c2._comment b/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_1_0a0c8c62ca4d314f14d50306546c33c2._comment deleted file mode 100644 index 941f41361..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_1_0a0c8c62ca4d314f14d50306546c33c2._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-12-01T23:15:42Z" - content=""" -Hmm, git-annex bundles a libcrypto.dll, and so the uninstallation -process should remove that. - -I suspect what's going on is that the uninstaller is accidentially -being told the full path to the library, as it was on the build system. - -Hmm, doesn't seem so, relevant code is: - - removefilesFrom d = mapM_ (\f -> delete [RebootOK] $ fromString $ d ++ "/" ++ takeFileName f) - -Note `takeFileName`.. - -Alternate theory: Maybe if git-annex is installed before git, it -installs libcrypto.dll. Then maybe git's installer sees that is installed -and doesn't install its own copy. -"""]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_2_68f84ce2eb95567012ed4ff20524c166._comment b/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_2_68f84ce2eb95567012ed4ff20524c166._comment deleted file mode 100644 index 80d9a36c9..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_2_68f84ce2eb95567012ed4ff20524c166._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2014-12-02T17:02:05Z" - content=""" -Tried uninistalling git-annex on my windows test box, and there was -no ssh command for git to use. git-annex provides a ssh, does msysgit -also provide one now? Lacking bandwidth to check. -"""]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_3_fad04c6f0c4d46b648d6cabfb59d92cf._comment b/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_3_fad04c6f0c4d46b648d6cabfb59d92cf._comment deleted file mode 100644 index 96851c557..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_3_fad04c6f0c4d46b648d6cabfb59d92cf._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 3" - date="2014-12-03T17:26:08Z" - content=""" -msysgit does ship a ssh, in Git/bin/ - -So, when git-annex is installed on top of git, it installs its own ssh there, overwriting git's. Removing git-annex will then remove the ssh, and leave git w/o a ssh. -So, that's clearly wrong, although I was not able to reproduce git-annex's ssh being left behind. That must be what happened though, since git's ssh is not linked with libcrypto.dll. - -In any case, there's no reason for git-annex to ship a ssh, since msysgit already does. So I will fix the bug that way. -"""]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_4_8d36cf821c62207df0a3b1fda5758fae._comment b/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_4_8d36cf821c62207df0a3b1fda5758fae._comment deleted file mode 100644 index c048d7e54..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_4_8d36cf821c62207df0a3b1fda5758fae._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 4" - date="2014-12-03T17:36:58Z" - content=""" -Except it turns out that Git/bin is not in PATH by default. - -So, instead, git-annex will bundle ssh, but install it to Git/cmd, which is in PATH. This avoids the conflict and fixed [[bugs/Internal_server_error_while_adding_remote_server_on_Windows]] -"""]] diff --git a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_5_4741efcc77b1bf1125ef230a0278ca51._comment b/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_5_4741efcc77b1bf1125ef230a0278ca51._comment deleted file mode 100644 index 06b160ac9..000000000 --- a/doc/bugs/Uninstalling_removes_libcrypto.dll/comment_5_4741efcc77b1bf1125ef230a0278ca51._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawktFJRkdqZvsZB59DrY-N1988HkjSIIZ5w" - nickname="Michał" - subject="More details." - date="2014-12-03T21:56:35Z" - content=""" -Just to put more info: Yes, I installed git-annex when git been already installed. -"""]] diff --git a/doc/bugs/Update_freebsd_install_instructions.mdwn b/doc/bugs/Update_freebsd_install_instructions.mdwn deleted file mode 100644 index d7698d45c..000000000 --- a/doc/bugs/Update_freebsd_install_instructions.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -### Please describe the problem. - -The install documentation is out of date at least for the FreeBSD example. - -### Please provide any additional information below. - -Latest FreeBSD 10.x uses pkgng instead of pkg_add and the correct command is now 'pkg install hs-git-annex'. - -If you find the time please update it at https://git-annex.branchable.com/install/ . - -[[done]] diff --git a/doc/bugs/Update_freebsd_install_instructions/comment_1_002b3701e5dbb8bc77d09a822568f3dc._comment b/doc/bugs/Update_freebsd_install_instructions/comment_1_002b3701e5dbb8bc77d09a822568f3dc._comment deleted file mode 100644 index 18c464196..000000000 --- a/doc/bugs/Update_freebsd_install_instructions/comment_1_002b3701e5dbb8bc77d09a822568f3dc._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlRZkzmh7d76UJwDPbUj7Ml_TyC9grHbXw" - nickname="Hilbert" - subject="It's done" - date="2015-02-23T22:32:16Z" - content=""" -I really feel stupid now for not understanding that I can correct it myself. - -Done -"""]] diff --git a/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn b/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn deleted file mode 100644 index 1fcaf80a9..000000000 --- a/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -### Please describe the problem. - -Every time git-annex launches (after a reboot). It prompts me to finish upgrade, even though the binary is not updated. (All my repos are set to not auto update and this happens on all my repos). - - -### What steps will reproduce the problem? - -Relaunching git-annex. - - -### What version of git-annex are you using? On what operating system? - -OS X 10.9 - -git-annex version: 5.20140419-g477c0c0 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - - -### 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. -"""]] - -> This seems to be a duplicate of this bug: [[Upgrade_impossible_om_Mac_OSX]]. Please follow up there with any details you can provide. --[[Joey]] -> [[dup|done]] diff --git a/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_.mdwn b/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_.mdwn deleted file mode 100644 index 3a3a0b3cd..000000000 --- a/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - - -### What steps will reproduce the problem? - -Run with a custom external remote which provides CHECKURL-CONTENTS response with filename, and then run -annex addurl --file=existing_file URL expecting to get that URL assigned to existing_file - -Alternatively, there is a small test repo -<http://www.onerussian.com/tmp/tmpSqa8CH.tgz> -with .git/bin/git-annex-remote-dl+archive under /tmp/tmpSqa8CH having what was supposed to be a replayable protocol (if you do - - cd /tmp/tmplVoa6C; PATH=/tmp/tmplVoa6C/.git/bin:$PATH git annex --debug addurl --file test2.dat --relaxed dl+archive:SHA256E-s163--e424b6fef10c18b9aaa5bc773ef62a2632eaf1448ff3372d43557be4adca6419.tar.gz/a/d/test.dat - -But for this one, I guess since addurl command actually succeeds, it is no longer replayable (protocol of interactions diverges) but you will see all the interactions between my remote and annex in that file recorded for you. And you will see the test.dat uncommitted and with somewhat obscured URL-based key, although originally the call was - - git annex --debug addurl --file test2.dat --relaxed dl+archive:SHA256E-s163--1f86ca26e1ca3cad3e8c8f1684d558b5e5f48d5928e0db45ab2e7d3be3d35307.tar.gz/a/d/test.dat - -from which I expected test2.dat get a new URL and that Filename remote spit out being ignored - -### What version of git-annex are you using? On what operating system? - -5.20150327+git27-g6af24b6-1 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_/comment_1_73721f7709b1d8ca90522b2147428c6d._comment b/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_/comment_1_73721f7709b1d8ca90522b2147428c6d._comment deleted file mode 100644 index 76bd70453..000000000 --- a/doc/bugs/Uses_suggested_by_CHECKURL-CONTENTS_filename_instead_of_explicitly_specified_one_in_addurl_--file_/comment_1_73721f7709b1d8ca90522b2147428c6d._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-31T18:48:12Z" - content=""" -I think I didn't fully consider the `addurl --file` behavior when adding this -feature. - -It seems to make sense for CLAIMURL to be used, since a special remote may -claim the url. It seems to make sense for CHECKURL to then be called (if -not --relaxed) to check that the url's content is present before adding it. - -If CHECKURL-CONTENTS returns a file, it makes sense to check the file -size, but not use the suggested filename. - -If CHECKURL-MULTI returns multiple files, I think it makes sense to give up -with an error. -"""]] diff --git a/doc/bugs/Using_date_matching_options_gives_scary_error_messaes_on_empty_reflog.mdwn b/doc/bugs/Using_date_matching_options_gives_scary_error_messaes_on_empty_reflog.mdwn deleted file mode 100644 index 006de8300..000000000 --- a/doc/bugs/Using_date_matching_options_gives_scary_error_messaes_on_empty_reflog.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. - -When the reflog is empty, time-based `--in` expressions give scary messages that makes it look like something is really broken. - -Instead of `Fatal: Log blabla is empty` and `Broken pipe` a reasonable message would be e.g. `warning: Log for 'refs/heads/git-annex' is empty.` - -### What steps will reproduce the problem? - -Emptying reflog for `refs/heads/git-annex`, then using an `--in=here{date}` option to e.g. `git annex fsck`. - -### What version of git-annex are you using? On what operating system? - -`git-annex version: 5.20140412ubuntu1` on Ubuntu Trusty. - -### 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 - -$ git reflog expire --expire=all refs/heads/git-annex -$ git annex find --not --in here@{yesterday} -fatal: Log /home/clacke/pics/.git/logs/refs/heads/git-annex is empty. -fatal: Log /home/clacke/pics/.git/logs/refs/heads/git-annex is empty. -[ . . . ] -^C -git-annex: fd:10: hGetLine: end of file -git-annex: fd:9: hFlush: resource vanished (Broken pipe) -git-annex: fd:9: hFlush: resource vanished (Broken pipe) -[ . . . ] - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Visual_glitch_while_xmpp_pairing.mdwn b/doc/bugs/Visual_glitch_while_xmpp_pairing.mdwn deleted file mode 100644 index 03b0a5350..000000000 --- a/doc/bugs/Visual_glitch_while_xmpp_pairing.mdwn +++ /dev/null @@ -1,14 +0,0 @@ -### Please describe the problem. -When pairing with xmpp buddies, the well does not expand to fit the whole buddy list - -### What steps will reproduce the problem? -Go to the pairing menu - -### What version of git-annex are you using? On what operating system? - 5.20140717 from the homebrew bottle - -### Please provide any additional information below. - - - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/WORM_keys_differ_depending_on_working_dir_during_add.mdwn b/doc/bugs/WORM_keys_differ_depending_on_working_dir_during_add.mdwn deleted file mode 100644 index 9787ad5cc..000000000 --- a/doc/bugs/WORM_keys_differ_depending_on_working_dir_during_add.mdwn +++ /dev/null @@ -1,68 +0,0 @@ -### Please describe the problem. - -While the docs say that WORM keys are a function of a files basename, -when doing «git annex add .», the generated keys will actually contain -the relative path (with slashes escaped). Not sure whether this is by -design or a bug in its own right. I suppose that to minimize the chance -of collisions on WORM, having the path within the key is preferable. - -A problem about this, however, is that the path in the key is not -stable, but varies with the working dir when doing the «git annex -add». So, when a file is added from one working dir (say, the repo -base), later unlocked, and readded from another working dir (say, -somewhere below the repo base), this will generate a different key -even when the file has not been touched. - -Is there a rationale for this variability, or should «add» canonicalize -the encoded paths to the repo root? - - -### What steps will reproduce the problem? - - -[[!format sh """ - -# Init -$ git init /tmp/foo -$ cd /tmp/foo && git annex init - -$ mkdir baz -$ touch baz/quux - -# Add file with working dir at repo root. -$ git annex add --backend=WORM baz -$ git commit -m "first" - -# Key includes relative path. -$ readlink baz/quux -../.git/annex/objects/8x/8V/WORM-s0-m1406981486--baz%quux/WORM-s0-m1406981486--baz%quux - -# Unlock and readd with working dir at path below repo root. -$ cd baz -$ git annex unlock quux - -$ git annex add quux -$ git com -m "second" - -# Relative path is anchored to working dir instead of repo root. -$ readlink quux -../.git/annex/objects/9G/72/WORM-s0-m1406981486--quux/WORM-s0-m1406981486--quux - -# End of transcript or log. -"""]] - -### What version of git-annex are you using? On what operating system? -Linux 3.15.8 - -git-annex 5.20140716 - -> This was a bug. I suspect it got broken a while ago and I didn't noticed -> since I rarely use WORM and when I do it's almost always adding files -> in the current directory. [[fixed|done]] to take the filename only. -> -> I don't think it's a problem to have the subdirectory path in the -> existing WORM keys, other than the problems you note with this meaning -> a later add of the same file will generate a different key. So I have not -> done anything to try to fix up existing keys. (If this became a problem, -> I could add upgrade code to the WORM backend.) -> --[[Joey]] diff --git a/doc/bugs/Webapp_fails_to_resolve_ipv6_hostname.mdwn b/doc/bugs/Webapp_fails_to_resolve_ipv6_hostname.mdwn deleted file mode 100644 index da9bb4627..000000000 --- a/doc/bugs/Webapp_fails_to_resolve_ipv6_hostname.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -What steps will reproduce the problem? - -From the webapp, go to Configuration > Manage repositories > Remote server. Enter a hostname that only has an IPv6 hostname (e.g. ipv6.google.com). Click Check this server. - -What is the expected output? What do you see instead? - -Expect the application to attempt to check the server via SSH. Instead, it results in error "cannot resolve host name". - -What version of git-annex are you using? On what operating system? - -git-annex 3.20120924 on Debian testing (amd64). - -Please provide any additional information below. - -> Thanks, [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Weird_directories_appearing.mdwn b/doc/bugs/Weird_directories_appearing.mdwn deleted file mode 100644 index ea85cead6..000000000 --- a/doc/bugs/Weird_directories_appearing.mdwn +++ /dev/null @@ -1,82 +0,0 @@ -Hello! - -Can someone explain this behavior to me? System is ArchLinux with the newest prebuilt tarballs as of Jan 12th. - - ~ % mkdir GA1 - ~ % cd GA1 - ~/GA1 % git init - Initialized empty Git repository in /home/florian/GA1/.git/ - ~/GA1 (git)-[master] % git annex init - init ok - (Recording state in git...) - ~/GA1 (git)-[master] % echo "GA1" > testfile - ~/GA1 (git)-[master] % git annex add . - add testfile ok - (Recording state in git...) - ~/GA1 (git)-[master] % git annex sync - commit ok - ~/GA1 (git)-[master] % cd .. - - ~ % git clone GA1 GA2 - Cloning into 'GA2'... - done. - ~ % cd GA2 - ~/GA2 (git)-[master] % git annex init - init ok - (Recording state in git...) - ~/GA2 (git)-[master] % git annex get . - get testfile (merging origin/git-annex into git-annex...) - (Recording state in git...) - (from origin...) ok - (Recording state in git...) - ~/GA2 (git)-[master] % git annex unlock testfile - unlock testfile (copying...) ok - ~/GA2 (git)-[master] % echo "GA2" > testfile - commit ok - pull origin - ok - push origin - Counting objects: 27, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (16/16), done. - Writing objects: 100% (20/20), 1.88 KiB | 0 bytes/s, done. - Total 20 (delta 2), reused 0 (delta 0) - To /home/florian/GA1 - f0654aa..8d0bdf9 master -> synced/master - * [new branch] git-annex -> synced/git-annex - ok - ~/GA2 (git)-[master] % cd ../GA1 - - ~/GA1 (git)-[master] % git annex sync - (merging synced/git-annex into git-annex...) - commit ok - merge synced/master - Updating f0654aa..8d0bdf9 - Fast-forward - e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log | 1 + - testfile | 2 +- - 2 files changed, 2 insertions(+), 1 deletion(-) - create mode 100644 e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log - ok - - ~/GA1 (git)-[master] % ll - total 4 - drwxr-x--- 1 florian florian 6 Jan 12 13:59 e6a/ - lrwxrwxrwx 1 florian florian 178 Jan 12 13:59 testfile -> .git/annex/objects/V6/ZM/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c - - ~/GA1 (git)-[master] % cat e6a/e57/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c.log - 1389531554.951523s 1 dedf9799-0131-4773-8939-8f76294fa8e9 - -Where does the e6a directory comes from? I don't suspect a bug there, but in my conception of git-annex. - -Thanks! -Florian - -> [[fixed|done]] -> -> I know someone reported this a looong time ago (years), and I cannot find -> that bug report. Probably I closed it because I was unable to find a way -> to reproduce it. -> -> The spurious log files can be safely removed from your working tree. -> --[[Joey]] diff --git a/doc/bugs/Weird_directories_appearing/comment_1_989541faf18e476c06e3be94c979e588._comment b/doc/bugs/Weird_directories_appearing/comment_1_989541faf18e476c06e3be94c979e588._comment deleted file mode 100644 index d578c46ef..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_1_989541faf18e476c06e3be94c979e588._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 1" - date="2014-01-13T18:57:48Z" - content=""" -The log file is supposed to be stored by git-annex in the git-annex branch of the git repository. I don't know how it could end up being committed to the master branch instead. - -Can you run these same commands again and reproduce the problem? -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_2_7aedaa3286a827303d90bd660429f0e7._comment b/doc/bugs/Weird_directories_appearing/comment_2_7aedaa3286a827303d90bd660429f0e7._comment deleted file mode 100644 index adeb97d7b..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_2_7aedaa3286a827303d90bd660429f0e7._comment +++ /dev/null @@ -1,43 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" - nickname="Florian" - subject="comment 2" - date="2014-01-14T12:12:52Z" - content=""" -Yes, I can always reproduce it with running \"sh test_ga.sh\" with test_ga.sh being: - - set -x - - mkdir GA1 - cd GA1 - git init - git annex init \"GA1\" - echo \"GA1\" > testfile - git annex add . - git annex sync - cd .. - - git clone GA1 GA2 - cd GA2 - git annex init \"GA2\" - git annex get . - cat testfile - git annex unlock testfile - echo \"GA2\" > testfile - git annex sync - cd ../GA1 - - git annex sync - cd .. - -which gives: - - florian@horus ~/test % ll GA1 - insgesamt 4 - drwxr-x--- 1 florian florian 6 14. Jan 13:07 e6a/ - lrwxrwxrwx 1 florian florian 178 14. Jan 13:07 testfile -> .git/annex/objects/V6/ZM/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c/SHA256E-s4--241dca52164d30bee7a0be8c097f02e382acff765a9d4136718a37abd437a57c - -with testfile being a dead link. Complete output of the script is at http://pastebin.com/VktWAp2V - -I would be glad to help furthermore. -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_3_5d3afa17d1e038c66a2cb6400b74aa41._comment b/doc/bugs/Weird_directories_appearing/comment_3_5d3afa17d1e038c66a2cb6400b74aa41._comment deleted file mode 100644 index fcc9a4ab1..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_3_5d3afa17d1e038c66a2cb6400b74aa41._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 3" - date="2014-01-14T18:55:11Z" - content=""" -This script does not produce the problem for me. How did you install git-annex from the tarball? -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_4_8db476bc89d3b9b1fdd82624829b4975._comment b/doc/bugs/Weird_directories_appearing/comment_4_8db476bc89d3b9b1fdd82624829b4975._comment deleted file mode 100644 index 9d99f91f5..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_4_8db476bc89d3b9b1fdd82624829b4975._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 4" - date="2014-01-14T19:00:33Z" - content=""" -Actually, I was able to reproduce this using the standalone tarball and runshell. -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_5_4f3a8e3b0201829059c6e7e0cff0ff75._comment b/doc/bugs/Weird_directories_appearing/comment_5_4f3a8e3b0201829059c6e7e0cff0ff75._comment deleted file mode 100644 index f61b61155..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_5_4f3a8e3b0201829059c6e7e0cff0ff75._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 5" - date="2014-01-14T19:14:35Z" - content=""" -Analysis: pre-commit hook is run with `GIT_INDEX_FILE=.git/index.lock`; this seems to be causing git-annex branch commits to land in that index file instead of where they are supposed to go. Also, commits of the files in the work tree also end up adding the symlinks to the git-annex branch when this happens. Apparantly because again it's using the wrong index file when committing to the git-annex branch. - -So, an easy workaround (disable pre-commit hook or make it `unset GIT_INDEX_FILE`, but I need to dig into why this env var is messing with git-annex like this.. I thought git-annex set the env var itself! -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_6_1c3218c8858397acc0e9fd718d7fd973._comment b/doc/bugs/Weird_directories_appearing/comment_6_1c3218c8858397acc0e9fd718d7fd973._comment deleted file mode 100644 index c7dc6c274..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_6_1c3218c8858397acc0e9fd718d7fd973._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 6" - date="2014-01-14T19:16:15Z" - content=""" -Problem is that git-annex prepends `GIT_INDEX_FILE` to the environment; it does not overwrite it. So environment ends up with 2 copies of the var, and which will be used is undefined. -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_7_9d055063f58042ff048c5b71e9e67f6e._comment b/doc/bugs/Weird_directories_appearing/comment_7_9d055063f58042ff048c5b71e9e67f6e._comment deleted file mode 100644 index 3ca131f5d..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_7_9d055063f58042ff048c5b71e9e67f6e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 7" - date="2014-01-14T19:33:28Z" - content=""" -I have fixed this in git. I will be moving this thread from the forum to the bug report tracker. -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_8_b39be0251e96099142b659f3c8340293._comment b/doc/bugs/Weird_directories_appearing/comment_8_b39be0251e96099142b659f3c8340293._comment deleted file mode 100644 index 69a78cfca..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_8_b39be0251e96099142b659f3c8340293._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" - nickname="Florian" - subject="comment 8" - date="2014-01-14T21:15:51Z" - content=""" -Wow, thanks a lot! The fix will be included in the next release of the tarballs? -"""]] diff --git a/doc/bugs/Weird_directories_appearing/comment_9_431c62c81573468ccf99eeed6ecc2bfd._comment b/doc/bugs/Weird_directories_appearing/comment_9_431c62c81573468ccf99eeed6ecc2bfd._comment deleted file mode 100644 index a6aaf9517..000000000 --- a/doc/bugs/Weird_directories_appearing/comment_9_431c62c81573468ccf99eeed6ecc2bfd._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 9" - date="2014-01-14T21:17:16Z" - content=""" -It will be included in the next build of the daily built tarballs. Within an hour of now. -"""]] diff --git a/doc/bugs/When_adding_a_box.com_repo_with_the_webapp_the_old-style_chunking_is_used.mdwn b/doc/bugs/When_adding_a_box.com_repo_with_the_webapp_the_old-style_chunking_is_used.mdwn deleted file mode 100644 index 7f00a2e51..000000000 --- a/doc/bugs/When_adding_a_box.com_repo_with_the_webapp_the_old-style_chunking_is_used.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -Last week I added a new Box.com repository through the webapp with the latest git-annex version, and I've noticed that the remote uses the old chunksize param. - -Is this correct? AFAIK it should use the chunk param: http://git-annex.branchable.com/chunking/ - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths.mdwn b/doc/bugs/Windows_build_has_hardcoded_paths.mdwn deleted file mode 100644 index 199d00b03..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. - -The windows build seems to be hardcoded to finding git at c:\program files\Git\ -I have git in another directory. Git-annex does not find it. - -### What steps will reproduce the problem? - -Install git-annex. Run the webapp. -Get error "Internal Server Error -You need to install git in order to use git-annex!" - -### What version of git-annex are you using? On what operating system? - -5.20140817-g71c2250. -Windows XP. - -### 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. -"""]] - -[[!meta title="git-annex on windows does not find msgit if user does not let msysgit add itsselt to PATH"]] - -> I don't think it's any better for git-annex's installer to prompt for the -> path to git, than it is for msysgit's installer to prompt for adding it -> to the system path. -> -> The best fix would be to bundle msysgit into the git-annex installer -> along with all the other stuff. But, that adds build-time complications -> I would rather avoid. -> -> For now, I am going to treat this as a documentation problem; -> I've updated the install page to be clear that msysgit needs to be -> installed into PATH. [[done]] --[[Joey]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_1_03518523a823a89fbb97b6a57d650e2b._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_1_03518523a823a89fbb97b6a57d650e2b._comment deleted file mode 100644 index f1a170e21..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_1_03518523a823a89fbb97b6a57d650e2b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="24.159.78.125" - subject="comment 1" - date="2014-08-20T14:37:30Z" - content=""" -git-annex does not hardcode any paths, and certianly not the path to git. Your system probably does not have the location you installed git added to the PATH. In that case, git-annex may do what windows programs do and look for git.exe in the same directory it was installed into. -"""]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_2_58b856e19c8d5e59164b42399ba6b1fd._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_2_58b856e19c8d5e59164b42399ba6b1fd._comment deleted file mode 100644 index a4784c634..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_2_58b856e19c8d5e59164b42399ba6b1fd._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="Hans_Ryding" - ip="81.229.194.7" - subject="Quite right" - date="2014-08-21T08:54:50Z" - content=""" -Incorrect assumption from my part. -I reinstalled git into the expected path (C:\program files\Git) -and the problem is still there. - -Running git-annex from command-line works. -(I tried running git-annex test. It had 23 failed tests, -most of them because of inability to access the remote: origin. -But it ran just fine.) -Running the web-app gives the error listed above. -"""]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_3_f9543c0ca1ff81c4d495a01c77429ea8._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_3_f9543c0ca1ff81c4d495a01c77429ea8._comment deleted file mode 100644 index ba06cd435..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_3_f9543c0ca1ff81c4d495a01c77429ea8._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="Hans_Ryding" - ip="81.229.194.7" - subject="Change the name of the bug" - date="2014-08-21T09:14:16Z" - content=""" -I can't seem to change the name of the bug to something more appropriate. -Maybe you can? -"""]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_4_01096994c19b7d0df1cc6866d4f22e21._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_4_01096994c19b7d0df1cc6866d4f22e21._comment deleted file mode 100644 index 5daa87d5e..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_4_01096994c19b7d0df1cc6866d4f22e21._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmBmv0HhwTFxkpxlf8ifTlMOHnIwHCHTYs" - nickname="y" - subject="path on windows" - date="2014-08-23T22:02:07Z" - content=""" -I think I have a related problem on win7 sp1. - -When first installing msys git, there's a screen asking for how to set the PATH variable. I chose the option not to update the windows PATH variable, which is the default. Then I installed git annex. Then launching the git-annex-autostart.vbs as well as the webapp one gets an object not found error (on line 2). launching git-annex from git bash with full path yielded an error about not finding git. - -Then I proceeded and reinstalled git on top of itself and picked the option to only add git and bash to windows path and it worked. -"""]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_5_0d7a4f740180dff7c0853062e4913804._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_5_0d7a4f740180dff7c0853062e4913804._comment deleted file mode 100644 index 42537f9f4..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_5_0d7a4f740180dff7c0853062e4913804._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="Hans_Ryding" - ip="81.229.194.7" - subject="Relying on path is not best practice in a Windows environment" - date="2014-08-25T16:16:33Z" - content=""" -Unlike under POSIX environments -generally applications under windows don't add themselves to path, -or to a directory already in path. - -Generally applications announce their location using the registry. -Under either HKEY_LOCAL_MACHINE\SOFTWARE, -or in case of software installed for one particular user only -under HKEY_CURRENT_USER\SOFTWARE. - -Git however AFAIK does not. -Most likely the best thing to do is to prompt the user when installing git-annex -where git is, and store this variable. - -Note that in both my installs I installed git-annex into the git directory, -and the git-annex webapp still couldn't find it. -"""]] diff --git a/doc/bugs/Windows_build_has_hardcoded_paths/comment_6_748aa921afee3d7e4667dee50e70a558._comment b/doc/bugs/Windows_build_has_hardcoded_paths/comment_6_748aa921afee3d7e4667dee50e70a558._comment deleted file mode 100644 index 4cbf0ea58..000000000 --- a/doc/bugs/Windows_build_has_hardcoded_paths/comment_6_748aa921afee3d7e4667dee50e70a558._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmBmv0HhwTFxkpxlf8ifTlMOHnIwHCHTYs" - nickname="y" - subject="path on windows" - date="2014-08-26T12:18:39Z" - content=""" -To add to my comment I also installed git-annex in the same directory as the msys git distrib in both cases. -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies.mdwn b/doc/bugs/Windows_daemon_silently_dies.mdwn deleted file mode 100644 index cbffc0083..000000000 --- a/doc/bugs/Windows_daemon_silently_dies.mdwn +++ /dev/null @@ -1,132 +0,0 @@ -### Please describe the problem. - -Using the latest build, when the agent is started, it works ... and works ... and works ... until it silently dies at some point. - -### What steps will reproduce the problem? - -I hope this will reproduce: - -* Create a remote with an invalid host which is not reachable -* Start git-annex-autostart.vbs -* Wait 5-30 minutes until no git.exe/git-annex.exe are visible any more in task manager (for my current test it took 10 minutes) -* Inspect the logs - -### What version of git-annex are you using? On what operating system? - - $ git annex version - git-annex version: 5.20140715-g622a376 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 2 3 4 - -### Please provide any additional information below. - -I hope/think that this is also related to what I wrote in: -https://git-annex.branchable.com/forum/Restricting_SSH_+_supply_key - -Here the assistant apparently takes the wrong ssh.exe (from bin/ instead than cmd/ directory). This results in the fact that for some reason .ssh/config is not used. -In any case, the host alias can not be resolved. -At some point git annex assistant seems to die because of that, but I am not sure. -In any case, a non-reachable server should not be the cause that the assistant dies. -The last entries of daemon.log are always: - - git-annex: <stdin>: hGetLine: invalid argument (Bad file descriptor) - failed - git-annex: assistant: 1 failed - -So I think this is the cause. - -[[!format sh """ -[2014-07-14 21:21:19 Pacific Daylight Time] main: starting assistant version 5.20140715-g622a376 -[2014-07-14 21:21:19 Pacific Daylight Time] Cronner: You should enable consistency checking to protect your data. -[2014-07-14 21:21:24 Pacific Daylight Time] TransferScanner: Syncing with 192.168.200.121 -(scanning...) [2014-07-14 21:21:25 Pacific Daylight Time] Watcher: Performing startup scan -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -sssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -sssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -(started...) [2014-07-14 21:21:43 Pacific Daylight Time] Committer: Committing changes to git -[2014-07-14 21:21:43 Pacific Daylight Time] Pusher: Syncing with 192.168.200.121 -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -ssh: Could notssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-07-14 21:22:03 Pacific Daylight Time] Committer: Committing changes to git -fatal: Unable to create 'c:\data\annex\.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: Unable to create 'c:\data\annex\.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -Committer crashed: failed to read sha from git write-tree -[2014-07-14 21:22:03 Pacific Daylight Time] Committer: warning Committer crashed: failed to read sha from git write-tree -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -Network.Socket.ByteString.send: does not exist (No such file or directory) -Network.Socket.ByteString.send: does not exist (No such file or directory) - -(Recording state in git...) -(Recording state in git...) - -git-annex: <stdin>: hGetLine: invalid argument (Bad file descriptor) -failed -git-annex: assistant: 1 failed -"""]] - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_1_b590aaeedec78c8540d549a8c773881e._comment b/doc/bugs/Windows_daemon_silently_dies/comment_1_b590aaeedec78c8540d549a8c773881e._comment deleted file mode 100644 index e2c6cdecf..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_1_b590aaeedec78c8540d549a8c773881e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-15T17:36:22Z" - content=""" -I doubt that it has anything to do with a ssh remote. - -Please enable debug logging and see if you can get a more detailed log around when it dies. -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_2_472975d2bd9784ae40b35f11fc561231._comment b/doc/bugs/Windows_daemon_silently_dies/comment_2_472975d2bd9784ae40b35f11fc561231._comment deleted file mode 100644 index dae862205..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_2_472975d2bd9784ae40b35f11fc561231._comment +++ /dev/null @@ -1,72 +0,0 @@ -[[!comment format=mdwn - username="divB" - ip="128.12.90.218" - subject="comment 2" - date="2014-07-15T20:51:07Z" - content=""" -Unfortunately not. I did that already. At least in my opinion nothing special. - -These are the latest lines: - -[[!format sh \"\"\" -Please make sure you have the correct access rights -and the repository exists. -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"show-ref\",\"git-annex\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..8ea0bbec209e1ec1240aa94ba2d6975023d83ac5\",\"-n1\",\"--pretty=%H\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..528b6b61318d138db5df2262ee501d6895b859d0\",\"-n1\",\"--pretty=%H\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..45aff729d5c9e60d925fad4c7fd75497ff5301fa\",\"-n1\",\"--pretty=%H\"] -[2014-07-15 13:34:32 Pacific Daylight Time] call: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/server/annex/direct/master\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/annex/direct/master..refs/remotes/server/annex/direct/master\",\"-n1\",\"--pretty=%H\"] -[2014-07-15 13:34:32 Pacific Daylight Time] call: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/server/synced/master\"] -[2014-07-15 13:34:32 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/synced/master..refs/remotes/server/synced/master\",\"-n1\",\"--pretty=%H\"] -[2014-07-15 13:34:32 Pacific Daylight Time] Pusher: pushing to [Remote { name =\"server\" }] -[2014-07-15 13:34:32 Pacific Daylight Time] call: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"push\",\"server\",\"+git-annex:synced/git-annex\",\"annex/direct/master:synced/master\"] -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-07-15 13:34:34 Pacific Daylight Time] read: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"push\",\"server\",\"master\"] -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -[2014-07-15 13:34:35 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:34:35 Pacific Daylight Time] RemoteControl: fromList [] -[2014-07-15 13:34:36 Pacific Daylight Time] Pusher: fallback pushing to [Remote { name =\"server\" }] -[2014-07-15 13:34:36 Pacific Daylight Time] call: git [\"--git-dir=c:\\data\\annex\\.git\",\"--work-tree=c:\\data\\annex\",\"-c\",\"core.bare=false\",\"push\",\"server\",\"+git-annex:refs/synced/91347741-60cd-4bca-a64a-90adee8d1910/git-annex\",\"refs/heads/annex/direct/master:refs/synced/91347741-60cd-4bca-a64a-90adee8d1910/annex/direct/master\"] -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-07-15 13:34:51 Pacific Daylight Time] chat: ssh [\"-T\",\"test@annex\",\"git-annex-shell 'notifychanges' '/srv/data/Shared' --uuid df1c0b77-f9b6-4ed7-96f3-3e7f010c4fb6\"] -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -[2014-07-15 13:35:03 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:35:03 Pacific Daylight Time] RemoteControl: fromList [] -[2014-07-15 13:35:35 Pacific Daylight Time] chat: ssh [\"-T\",\"test@annex\",\"git-annex-shell 'notifychanges' '/srv/data/Shared' --uuid df1c0b77-f9b6-4ed7-96f3-3e7f010c4fb6\"] -ss[2014-07-15 13:35:47 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:35:47 Pacific Daylight Time] RemoteControl: fromList [] -[2014-07-15 13:36:51 Pacific Daylight Time] chat: ssh [\"-T\",\"test@annex\",\"git-annex-shell 'notifychanges' '/srv/data/Shared' --uuid df1c0b77-f9b6-4ed7-96f3-3e7f010c4fb6\"] -ssh: Could not resolve hostname annex: hostname nor servname provided, or not known - -[2014-07-15 13:37:02 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:37:02 Pacific Daylight Time] RemoteControl: fromList [] -[2014-07-15 13:39:10 Pacific Daylight Time] chat: ssh [\"-T\",\"test@annex\",\"git-annex-shell 'notifychanges' '/srv/data/Shared' --uuid df1c0b77-f9b6-4ed7-96f3-3e7f010c4fb6\"] -ssh: Co[2014-07-15 13:39:21 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:39:21 Pacific Daylight Time] RemoteControl: fromList [] -[2014-07-15 13:43:37 Pacific Daylight Time] chat: ssh [\"-T\",\"test@annex\",\"git-annex-shell 'notifychanges' '/srv/data/Shared' --uuid df1c0b77-f9b6-4ed7-96f3-3e7f010c4fb6\"] -ssh: Could not resolve hostname an[2014-07-15 13:43:49 Pacific Daylight Time] RemoteControl: DISCONNECTED ssh://test@annex/srv/data/Shared -[2014-07-15 13:43:49 Pacific Daylight Time] RemoteControl: fromList [] - -(Recording state in git...) - -git-annex: <stdin>: hGetLine: invalid argument (Bad file descriptor) -failed -git-annex: assistant: 1 failed -\"\"\"]] - -Maybe it's something different but what could it be? - - -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_3_48415a7251abffca998b8dccc5e0ba80._comment b/doc/bugs/Windows_daemon_silently_dies/comment_3_48415a7251abffca998b8dccc5e0ba80._comment deleted file mode 100644 index 3498cc88e..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_3_48415a7251abffca998b8dccc5e0ba80._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="divB" - ip="128.12.90.218" - subject="comment 3" - date="2014-07-15T22:02:41Z" - content=""" -Update: You are right. It has nothing to do with the connections. I created a new repository without any sync. Same here: - - [2014-07-15 13:53:33 Pacific Daylight Time] main: starting assistant version 5.20140715-g622a376 - [2014-07-15 13:53:33 Pacific Daylight Time] Cronner: You should enable consistency checking to protect your data. - (scanning...) [2014-07-15 13:53:38 Pacific Daylight Time] Watcher: Performing startup scan - (started...) - - git-annex: <stdin>: hGetLine: invalid argument (Bad file descriptor) - failed - git-annex: assistant: 1 failed - -It always takes exactly 10 minutes until it dies (you see is started 13:53:33 and it died at 14:03:33 (=modification of daemon.log). -So this is reproduceable ... - - -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_4_1c0b0b2e7180425ff2d5e5316a138f7d._comment b/doc/bugs/Windows_daemon_silently_dies/comment_4_1c0b0b2e7180425ff2d5e5316a138f7d._comment deleted file mode 100644 index 63b37a7e1..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_4_1c0b0b2e7180425ff2d5e5316a138f7d._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 4" - date="2014-07-16T18:18:11Z" - content=""" -Hmm, there are two places where the assistant happens to hard code a 10 minute time period. But one is 10 minutes from starting to configure a ssh remote in the webapp, not from start. And the other is the watcher's afterLastDaemonRun check, which only happens when a symlink appears in the repository (which shouldn't happen on windows and wouldn't necessarily happen 10 minutes after start). - -Fabulous .. I just reproduced the crash! -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_5_0d14dd2c8d94a81ffd5aae07e927344f._comment b/doc/bugs/Windows_daemon_silently_dies/comment_5_0d14dd2c8d94a81ffd5aae07e927344f._comment deleted file mode 100644 index 2b2e81946..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_5_0d14dd2c8d94a81ffd5aae07e927344f._comment +++ /dev/null @@ -1,40 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 5" - date="2014-07-16T18:21:24Z" - content=""" -A full log in an empty repo of the crash: - -<pre> -[2014-07-16 14:00:53 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"show-ref\",\"git-annex\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..9c07d1385e80dbc6044814357e9097fd231b8c99\",\"-n1\",\"--pretty=%H\"] -[2014-07-16 14:00:54 Atlantic Standard Time] chat: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"cat-file\",\"--batch\"] -[2014-07-16 14:00:54 Atlantic Standard Time] logging to C:\WINDOWS\TT\.git\annex\daemon.log -[2014-07-16 14:00:54 Atlantic Standard Time] main: starting assistant version 5.20140714-gf892329 -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"show-ref\",\"git-annex\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..9c07d1385e80dbc6044814357e9097fd231b8c99\",\"-n1\",\"--pretty=%H\"] -[2014-07-16 14:00:54 Atlantic Standard Time] chat: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"cat-file\",\"--batch\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"ls-files\",\"--stage\",\"-z\",\"--\",\"C:\\WINDOWS\\TT\"] -[2014-07-16 14:00:54 Atlantic Standard Time] Cronner: You should enable consistency checking to protect your data. -[2014-07-16 14:00:54 Atlantic Standard Time] SanityCheckerStartup: no index file; restaging -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"ls-files\",\"--stage\",\"-z\",\"--\",\"C:\\WINDOWS\\TT\"] -[2014-07-16 14:00:54 Atlantic Standard Time] chat: git-annex [\"remotedaemon\"] -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"ls-tree\",\"--full-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"numcopies.log\",\"schedule.log\",\"preferred-content.log\",\"required-content.log\",\"group-preferred-content.log\"] -[2014-07-16 14:00:54 Atlantic Standard Time] Merger: watching C:\WINDOWS\TT\.git\refs -[2014-07-16 14:00:54 Atlantic Standard Time] TransferWatcher: watching for transfers -(scanning...) [2014-07-16 14:00:54 Atlantic Standard Time] Watcher: Performing startup scan -[2014-07-16 14:00:54 Atlantic Standard Time] read: git [\"--git-dir=C:\\WINDOWS\\TT\\.git\",\"--work-tree=C:\\WINDOWS\\TT\",\"-c\",\"core.bare=false\",\"ls-files\",\"--deleted\",\"-z\",\"--\",\"C:\\WINDOWS\\TT\"] -(started...) [2014-07-16 14:00:54 Atlantic Standard Time] Watcher: watching . - - -git-annex: <stdin>: hGetLine: invalid argument (Bad file descriptor) -failed -git-annex: assistant: 1 failed -</pre> - -The two blank lines just before the crash seem to be significant somehow; they are not output at the beginning, so must occur just before it crashes. - -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_6_20a420680058f84a8cbd43682957fe7b._comment b/doc/bugs/Windows_daemon_silently_dies/comment_6_20a420680058f84a8cbd43682957fe7b._comment deleted file mode 100644 index 4b596c762..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_6_20a420680058f84a8cbd43682957fe7b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 6" - date="2014-07-16T18:38:51Z" - content=""" -It appears to be the remoteResponderThread crashing (based on adding debugging around all hGetLine call sites). -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_7_1514739ba9885917d03597dcc6aa7bec._comment b/doc/bugs/Windows_daemon_silently_dies/comment_7_1514739ba9885917d03597dcc6aa7bec._comment deleted file mode 100644 index 3ce65580a..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_7_1514739ba9885917d03597dcc6aa7bec._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 7" - date="2014-07-16T20:18:50Z" - content=""" -Well, it seems not to be the RemoteControl thread after all. I made that thread start the remotedaemon and then not read from it at all, and the crash still happens. Also, the remotedaemon itself seems to run forever ok. - -(This is sort of a relief, because it should not be possible for a crash of a named thread like RemoteControl to take down the whole assistant!) - -The hGetLine must be being called by some other library function. - -Hmm... Could it perhaps be waitForTermination? On windows that ends up calling getLine in a loop. A 600 second loop! - -Update: Seems so. With a 60 second loop, it crashes after 60 seconds. With the 2 newlines happening just before. - -Also, it makes sense now why this is a new crash. Before the assistant ran with stdio connected to the terminal, but recently on windows it got hooked up to the debug log, and stdin is closed now. - -I still don't understand where the 2 newlines come from (possibly output by something while git-annex is crashing?).. But have confirmed I've fixed the problem now. -"""]] diff --git a/doc/bugs/Windows_daemon_silently_dies/comment_8_0210436870e6622a83c9b4788e31eef4._comment b/doc/bugs/Windows_daemon_silently_dies/comment_8_0210436870e6622a83c9b4788e31eef4._comment deleted file mode 100644 index 09e7eb867..000000000 --- a/doc/bugs/Windows_daemon_silently_dies/comment_8_0210436870e6622a83c9b4788e31eef4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="divB" - ip="204.17.143.10" - subject="comment 8" - date="2014-07-16T23:53:39Z" - content=""" -Really great, seems to be fixed in the current version (at least it's running for 1h now). Thank you!! -"""]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn b/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn deleted file mode 100644 index 69e9838f2..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -Windows has an unfortunate handling of time zones, which means that when -the time zone is changed (or DST changes), the timestamps of files also -appear to change. - -This means that after such a change, git-annex will see new mtimes, and -want to re-checksum every file in the repo. - -[[!tag confirmed]] - -> Update: Actually, I seem to have been getting confused by behavior of -> cygwin terminal setting TZ. That indeed led to timestamp changes when the -> time zone changed. I have made git-annex unset TZ to avoid this. -> -> Without TZ set, time stamps are actually stable across time zone changes. -> Ie, a simple program to read the time stamp of a file and print it -> always shows the same thing, before and after a timezone change. -> -> However, and here's where it gets truely ghastly: A program that stats a -> file in a loop will see its timestamp change when the timezone changes. -> I suspect this might be a bug in the Haskell RTS caching something it -> should not. Stopping and re-running the program gets back to the -> original timestamp. -> -> I have not tested DST changes, but it's hard to imagine it being any -> worse than the above behavior. -> -> So, that's insane then. We can't trust timestamps to be stable on windows -> when git-annex is running for a long period of time. --[[Joey]] -> -> > [[fixed|done]], using the inode sentinal file to detect when windows -> > has lost its mind, and calculating its delta from insanity. --[[Joey]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_1_9db59ab2242186a23a47337a1597f4e2._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_1_9db59ab2242186a23a47337a1597f4e2._comment deleted file mode 100644 index fbda5c285..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_1_9db59ab2242186a23a47337a1597f4e2._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-11T19:09:17Z" - content=""" -Rather than getting the timezone, another approach might be to look at the inode sentinal file. Its timestamp will also appear to have changed. If the delta is exactly some number of hours, and the inode sential's other data is unchanged, a Windows-specific hack could apply that same delta to all inode cache timestamps. - -Except, time zones are not all actually on hour boundaries. Some are half hours, some may be 15 minutes, and next week some crazy country might legislate a 3 minute delta for all I know. - -Well, could just say if the inode sentinal's mtime has changed at all (delta < 3600 seconds), and it's otherwise unchanged, and we're on windows, assume this is a time zone change. When would that fail? Only if the repository is copied to someplace, and the mtime is not preserved. -"""]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_2_a6a3871747306913b69abcd73d13305e._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_2_a6a3871747306913b69abcd73d13305e._comment deleted file mode 100644 index c213aa0a9..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_2_a6a3871747306913b69abcd73d13305e._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 2" - date="2014-06-11T19:51:15Z" - content=""" -Note that multiple time zone changes complicate this. I think that means that the delta can't be simply applied when comparing inode caches. Instead, probably it needs to be applied when generating inode caches. - -A scenario: - -1. Time zone is at +1h when the inode sential is written. -2. Time zone changes to +2h -3. File F is added (with a current timestamp of T) -4. Time zone changes to +5h - -I am a little confused by which way windows moves the timestamps when the time zone changes. Let's assume I might get the sign wrong. - -Let F's timestamp after step 4, F4 = T+-3h. - -Let the delta after step 4, D4 = +-4h -And, let the delta after step 2, D2 = +-1h - -If step 3 writes the current timestamp to the inode cache, then the cache still has T in it after step 4. F4+D4 /= T (T +-3h +-4h /= T). So comparison doesn't work. - -If instead the current delta is applied when generating inode caches (both for storing on disk, and for immediate comparison), then the inode cache will have T+D2 in it. Then after step 4, generating a new inode cache for F will yield F4+D4. So, does F4+D4 == T+D2? T +-3h +-4h == T +-1h YES! -"""]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment deleted file mode 100644 index 1a25d3c82..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_3_7fe149bedb8ceab75953996ac8e20f0f._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 3" - date="2014-06-11T22:11:38Z" - content=""" -I have implemented this on the loststamp git branch. It seems to work! - -However, it has a big problem: - - If the timezone changes while the assistant (or a long-running command) - runs, it won't notice, since it only checks the inode cache once, and - so will use the old delta for all new inode caches it generates for new - files it's added. Which will result in them seeming changed the next time - it runs. - -So, it would be really nice to be able to check the actual timezone instead. -But I suppose I can make the assistant poll the inode cache file, or check -it when adding a new file, or something like that. Bleagh. -"""]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_4_c9e8c9997b7c3a82c14fc34af319382d._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_4_c9e8c9997b7c3a82c14fc34af319382d._comment deleted file mode 100644 index d06df7b77..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_4_c9e8c9997b7c3a82c14fc34af319382d._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 4" - date="2014-06-11T22:54:48Z" - content=""" -Getting the actual time zone on windows works better if you unset TZ first. - -But, a haskell program that polls the time zone fails to notice when it's changed. It only notices after being restarted. I have contacted the time library maintainer about this. -"""]] diff --git a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_5_0739426403f5bf9954acbc86ca0d11ea._comment b/doc/bugs/Windows_file_timestamp_timezone_madness/comment_5_0739426403f5bf9954acbc86ca0d11ea._comment deleted file mode 100644 index ac1f090f5..000000000 --- a/doc/bugs/Windows_file_timestamp_timezone_madness/comment_5_0739426403f5bf9954acbc86ca0d11ea._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 5" - date="2014-06-11T23:02:28Z" - content=""" -I've developed a fix for the time library. This patch has been sent to the author, hopefully it will get applied and then I can use getCurrentTImeZone. Note that git-annex would need to unset TZ first, which might be hard on windows. - -<pre> -diff --git a/cbits/HsTime.c b/cbits/HsTime.c -index cfafb27..86ca92a 100644 ---- a/cbits/HsTime.c -+++ b/cbits/HsTime.c -@@ -8,6 +8,7 @@ long int get_current_timezone_seconds (time_t t,int* pdst,char const* * pname) - tzset(); - struct tm* ptm = localtime_r(&t,&tmd); - #else -+ tzset(); - struct tm* ptm = localtime(&t); - #endif - if (ptm) -</pre> -"""]] diff --git a/doc/bugs/Won__39__t_drop_files__44___even_though_remote_annexes_have_at_least_numcopies.mdwn b/doc/bugs/Won__39__t_drop_files__44___even_though_remote_annexes_have_at_least_numcopies.mdwn deleted file mode 100644 index ec87cefbe..000000000 --- a/doc/bugs/Won__39__t_drop_files__44___even_though_remote_annexes_have_at_least_numcopies.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. -On a Windows machine, I try to drop some files from an annex. These files exist in the origin annex. However, the drop fails, claiming it can't verify the existence of the remote copies. - -### What steps will reproduce the problem? -1. Create annex, serve git repo over HTTP. -2. clone repo. "git annex get ." -3. "git annex drop <file>". This will fail. - - -### What version of git-annex are you using? On what operating system? -Windows: 4.20130709-gea6fdc7 -Debian: 3.20120629 - -### Please provide any additional information below. - -[[!format sh """ -git annex -vd drop file2.txt -[<datetime>] read: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","ls-files","--cached","-z","--","file2.txt"] -[<datetime>] chat: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"] -drop file2.txt [<datetime>] read: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","show-ref","git-annex"] -[<datetime>] read: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","show-ref","--hash","refs/heads/git-annex"] -[<datetime>] read: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","log","refs/heads/git-annex..37bdd895d74131fddbdb8d2e6ae707ee2097598e","--oneline","-n1"] -[<datetime>] read: git ["--git-dir=C:\\Users\\<<user>>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","log","refs/heads/git-annex..f0ba6f30c63a9d586642d828c37613894191931e","--oneline","-n1"] -[<datetime>] chat: git ["--git-dir=C:\\Users\\<user>\\test_annex_2\\.git","--work-tree=C:\\Users\\<user>\\test_annex_2","cat-file","--batch"] -[<datetime>] read: curl ["-s","--head","-L","http://192.168.0.8:8000/test_annex_2/.git/annex/objects/738/e2a/SHA256-s27--4fc887746d7ea6c9574f6735bd3dfd9b0485b30acaaf0727658cd1796991dd2d/SHA256-s27--4fc887746d7ea6c9574f6735bd3dfd9b0485b30acaaf0727658cd1796991dd2d","-w","%{http_code}"] -(unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Rather than dropping this file, try using: git annex move - - (Use --force to override this check, or adjust annex.numcopies.) -failed -git-annex: drop: 1 failed -"""]] - -the given curl command fails with a 404, because the remote annex isn't using the 3-character hash directory scheme, but the 2-character one, and it seems that 'annex drop' doesn't check both schemes (unlike annex get). - -> Ah, the http remote is a non-bare repository, that's why. -> Ok, [[fixed|done]]! --[[Joey]] diff --git a/doc/bugs/Wrong_port_while_configuring_ssh_remote.mdwn b/doc/bugs/Wrong_port_while_configuring_ssh_remote.mdwn deleted file mode 100644 index 561cad199..000000000 --- a/doc/bugs/Wrong_port_while_configuring_ssh_remote.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. - -When the assistant connects the second time during adding a ssh remote, it assumes port 22 when different port is given. - -### What steps will reproduce the problem? - -Adding a ssh git remote with non-standard port. - -### What version of git-annex are you using? On what operating system? - -GNU/Linux, Ubuntu 12.10, amd64, git-annex 4.20130627-g728b27a - -Happens on android as well. - -### 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 - -Error message (nothing related in daemon.log): - -Failed to make repository - -Something went wrong setting up the repository on the remote server. - -Transcript: - -ssh: connect to host xxxxx port 22: Connection refused - -# End of transcript or log. -"""]] - -> [[Fixed|done]]; this bug was introcuded in version -> 4.20130627 while making some other ssh fixes. --[[Joey]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes.mdwn b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes.mdwn deleted file mode 100644 index e7ff53723..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. -git-annex assistant is currently running. Here is the output of **ps -A u | grep -i git**: - -[[!format sh """ -5457 pts/2 Z+ 0:00 [git-annex] <defunct> -5510 ? Sl 0:05 git-annex assistant -5522 ? S 0:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -5573 ? S 0:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -5679 ? SN 0:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex check-attr -z --stdin annex.backend annex.numcopies -- -5680 ? Z 0:03 [git-annex] <defunct> -5710 ? Z 0:00 [git-annex] <defunct> -5732 pts/2 Z+ 0:00 [git-annex] <defunct> -5752 pts/2 Z+ 0:00 [git-annex] <defunct> -5785 ? Ss 0:00 ssh: .git/annex/ssh/example.net [mux] -5905 ? Z 0:00 [git-annex] <defunct> -5923 ? Z 0:00 [git-annex] <defunct> -6513 pts/2 Z+ 0:00 [git-annex] <defunct> -6552 ? Z 0:00 [git-annex] <defunct> -7797 ? Z 0:00 [git-annex] <defunct> -7873 pts/2 Z 0:00 [git-annex] <defunct> -8708 pts/2 Z+ 0:00 [git-annex] <defunct> -9821 ? Z 0:00 [git-annex] <defunct> -9841 pts/2 Z+ 0:00 [git-annex] <defunct> -10462 ? Z 0:00 [git-annex] <defunct> -10522 pts/2 Z 0:00 [git-annex] <defunct> -12777 pts/2 Z+ 0:00 [git-annex] <defunct> -13878 pts/2 Z+ 0:00 [git-annex] <defunct> -14254 ? Z 0:00 [git-annex] <defunct> -14276 pts/2 Z+ 0:00 [git-annex] <defunct> -15932 ? Sl 0:00 git-annex transferkeys --readfd 37 --writefd 20 -16022 pts/2 Sl 0:00 git-annex transferkeys --readfd 28 --writefd 22 -16079 pts/2 S 0:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -16081 ? S 0:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -31565 pts/2 Sl+ 0:20 git-annex webapp -31580 pts/2 S+ 0:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31590 pts/2 S+ 0:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31618 pts/2 S+ 0:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31635 ? Sl 9:26 /usr/lib/firefox/firefox /mnt/debian/home/me/annex-backup/.git/annex/webapp.html -31689 pts/2 SN+ 0:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup check-attr -z --stdin annex.backend annex.numcopies -- -31812 pts/2 Z 0:00 [git-annex] <defunct> -31835 ? Ss 0:02 ssh: .git/annex/ssh/example.net [mux] -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_1_0f8b248025722309e9577d7dad74b76b._comment b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_1_0f8b248025722309e9577d7dad74b76b._comment deleted file mode 100644 index 578fecb58..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_1_0f8b248025722309e9577d7dad74b76b._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 1" - date="2013-11-03T01:12:25Z" - content=""" -This is apparently the same repository where [[all_this_went_on|bugs/Unnecessary_remote_transfers]]. - -I don't know if this is indicative of a problem. I see more zombies than I would normally expect, but I don't know if the number is growing, or shrinking, or staying the same. You should at least look at ps -f to see which of the multiple git-annex assistant daemons you have configured to run on this machine (not a usual configuration) is the parent of the zombies. -"""]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_2_f5f7db688a2a93ee7453674fb742043b._comment b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_2_f5f7db688a2a93ee7453674fb742043b._comment deleted file mode 100644 index ceb05ea0c..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_2_f5f7db688a2a93ee7453674fb742043b._comment +++ /dev/null @@ -1,52 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" - nickname="Adam" - subject="comment 2" - date="2013-11-03T01:19:42Z" - content=""" -Indeed. I've been looking forward to setting up git-annex assistant for a long time, waiting until I had more free time, and was finally pushed to do it when I had a weird problem with Dropbox. I'm not sure what I did wrong to make such a mess, haha. - -I see \"5510 git-annex assistant\" and \"31565 git-annex webapp\"--does the \"webapp\" one count as an assistant process too? -[[!format sh \"\"\"$ ps -ef | gi git -UID PID PPID C STIME TTY TIME CMD -me 3404 31565 0 17:44 pts/2 00:00:04 [git-annex] <defunct> -me 5457 31565 0 17:59 pts/2 00:00:00 [git-annex] <defunct> -me 5510 1 0 17:59 ? 00:00:06 git-annex assistant -me 5522 5510 0 17:59 ? 00:00:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -me 5573 5510 0 17:59 ? 00:00:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -me 5679 5510 0 17:59 ? 00:00:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex check-attr -z --stdin annex.backend annex.numcopies -- -me 5680 5510 0 17:59 ? 00:00:03 [git-annex] <defunct> -me 5710 5510 0 18:00 ? 00:00:00 [git-annex] <defunct> -me 5732 31565 0 18:00 pts/2 00:00:00 [git-annex] <defunct> -me 5752 31565 0 18:00 pts/2 00:00:00 [git-annex] <defunct> -me 5785 1 0 18:01 ? 00:00:00 ssh: .git/annex/ssh/example.net [mux] -me 5905 5510 0 18:02 ? 00:00:00 [git-annex] <defunct> -me 5923 5510 0 18:02 ? 00:00:00 [git-annex] <defunct> -me 6513 31565 0 18:05 pts/2 00:00:00 [git-annex] <defunct> -me 6552 5510 0 18:06 ? 00:00:00 [git-annex] <defunct> -me 7797 5510 0 18:09 ? 00:00:00 [git-annex] <defunct> -me 7873 31565 0 18:09 pts/2 00:00:00 [git-annex] <defunct> -me 8708 31565 0 18:10 pts/2 00:00:00 [git-annex] <defunct> -me 9821 5510 0 18:12 ? 00:00:00 [git-annex] <defunct> -me 9841 31565 0 18:14 pts/2 00:00:00 [git-annex] <defunct> -me 10462 5510 0 18:23 ? 00:00:00 [git-annex] <defunct> -me 10522 31565 0 18:24 pts/2 00:00:00 [git-annex] <defunct> -me 12777 31565 0 18:34 pts/2 00:00:00 [git-annex] <defunct> -me 13878 31565 0 18:35 pts/2 00:00:00 [git-annex] <defunct> -me 14254 5510 0 18:36 ? 00:00:00 [git-annex] <defunct> -me 14276 31565 0 18:36 pts/2 00:00:00 [git-annex] <defunct> -me 15932 5510 0 18:55 ? 00:00:00 git-annex transferkeys --readfd 37 --writefd 20 -me 16022 31565 0 18:55 pts/2 00:00:00 git-annex transferkeys --readfd 28 --writefd 22 -me 16079 16022 0 18:55 pts/2 00:00:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -me 16081 15932 0 18:55 ? 00:00:00 git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch -me 25136 25135 0 20:15 pts/6 00:00:00 grep -i git -me 31565 31478 0 17:42 pts/2 00:00:21 git-annex webapp -me 31580 31565 0 17:42 pts/2 00:00:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -me 31590 31565 0 17:42 pts/2 00:00:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -me 31618 31565 0 17:42 pts/2 00:00:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -me 31635 27578 8 17:42 ? 00:13:42 /usr/lib/firefox/firefox /mnt/debian/home/me/annex-backup/.git/annex/webapp.html -me 31689 31565 0 17:42 pts/2 00:00:00 git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup check-attr -z --stdin annex.backend annex.numcopies -- -me 31812 31565 0 17:42 pts/2 00:00:00 [git-annex] <defunct> -me 31835 1 0 17:42 ? 00:00:02 ssh: .git/annex/ssh/example.net [mux]\"\"\"]] - -"""]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_3_ffcae976aa3dc2426188797c1aaffb82._comment b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_3_ffcae976aa3dc2426188797c1aaffb82._comment deleted file mode 100644 index 78e816f06..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_3_ffcae976aa3dc2426188797c1aaffb82._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 3" - date="2013-11-03T01:31:26Z" - content=""" -`ps fax` is much easier to read - -Yes, the assistant can be started by either `git annex assistant` or, if it's not already running, `git annex webapp` -"""]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_4_8a7ff6841ad7c27ead06bf12f46b20a0._comment b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_4_8a7ff6841ad7c27ead06bf12f46b20a0._comment deleted file mode 100644 index 2bf32bd37..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_4_8a7ff6841ad7c27ead06bf12f46b20a0._comment +++ /dev/null @@ -1,49 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" - nickname="Adam" - subject="comment 4" - date="2013-11-03T01:35:32Z" - content=""" -Ah, thank you. I get lost in ps's man page. :) - -[[!format sh \"\"\" -31635 ? Rl 16:16 \_ /usr/lib/firefox/firefox /mnt/debian/home/me/annex-backup/.git/annex/webapp.html -31565 pts/2 Sl+ 0:21 | \_ git-annex webapp -31580 pts/2 S+ 0:00 | \_ git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31590 pts/2 S+ 0:00 | \_ git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31618 pts/2 S+ 0:00 | \_ git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -31689 pts/2 SN+ 0:00 | \_ git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup check-attr -z --stdin annex.backend annex.numcopies -- -31812 pts/2 Z 0:00 | \_ [git-annex] <defunct> - 3404 pts/2 Z 0:04 | \_ [git-annex] <defunct> - 5457 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> - 5732 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> - 5752 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> - 6513 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> - 7873 pts/2 Z 0:00 | \_ [git-annex] <defunct> - 8708 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> - 9841 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> -10522 pts/2 Z 0:00 | \_ [git-annex] <defunct> -12777 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> -13878 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> -14276 pts/2 Z+ 0:00 | \_ [git-annex] <defunct> -16022 pts/2 Sl 0:00 | \_ git-annex transferkeys --readfd 28 --writefd 22 -16079 pts/2 S 0:00 | \_ git --git-dir=/mnt/debian/home/me/annex-backup/.git --work-tree=/mnt/debian/home/me/annex-backup cat-file --batch -26828 pts/6 S+ 0:00 | \_ grep -i git -31835 ? Ss 0:02 ssh: .git/annex/ssh/example.net [mux] - 5510 ? Sl 0:06 git-annex assistant - 5522 ? S 0:00 \_ git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch - 5573 ? S 0:00 \_ git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch - 5679 ? SN 0:00 \_ git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex check-attr -z --stdin annex.backend annex.numcopies -- - 5680 ? Z 0:03 \_ [git-annex] <defunct> - 5710 ? Z 0:00 \_ [git-annex] <defunct> - 5905 ? Z 0:00 \_ [git-annex] <defunct> - 5923 ? Z 0:00 \_ [git-annex] <defunct> - 6552 ? Z 0:00 \_ [git-annex] <defunct> - 7797 ? Z 0:00 \_ [git-annex] <defunct> - 9821 ? Z 0:00 \_ [git-annex] <defunct> -10462 ? Z 0:00 \_ [git-annex] <defunct> -14254 ? Z 0:00 \_ [git-annex] <defunct> -15932 ? Sl 0:00 \_ git-annex transferkeys --readfd 37 --writefd 20 -16081 ? S 0:00 \_ git --git-dir=/home/me/annex/.git --work-tree=/home/me/annex cat-file --batch - 5785 ? Ss 0:00 ssh: .git/annex/ssh/example.net [mux] \"\"\"]] -"""]] diff --git a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_5_406fdee0728680774a69d28446163f10._comment b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_5_406fdee0728680774a69d28446163f10._comment deleted file mode 100644 index f8f223524..000000000 --- a/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_5_406fdee0728680774a69d28446163f10._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 5" - date="2013-11-03T02:33:14Z" - content=""" -I believe that these zombies were all caused by switching between repository views in the webapp. I was able to reproduce 1 zombie per switch between repos. - -There are a few other places where git-annex execs itself, but not many, and most of them are often used and it would be noticed if they were crypts from which pour forth the living dead. (Oddly the TV show I was thinking about watching this evening.) - -<pre> -joey@darkstar:~/src/git-annex>git grep readProgramFile -Assistant/Repair.hs: program <- readProgramFile -Assistant/Threads/Cronner.hs: program <- liftIO $ readProgramFile -Assistant/Threads/Cronner.hs: program <- readProgramFile -Assistant/Threads/Transferrer.hs: program <- liftIO readProgramFile -Assistant/TransferSlots.hs: program <- liftIO readProgramFile -Assistant/WebApp/Control.hs: program <- readProgramFile -Assistant/WebApp/OtherRepos.hs: program <- readProgramFile -Assistant/XMPP/Git.hs: program <- readProgramFile -Command/Assistant.hs: program <- readProgramFile -Config/Files.hs:readProgramFile :: IO FilePath -Config/Files.hs:readProgramFile = do -Remote/Git.hs: program <- readProgramFile -</pre> -"""]] diff --git a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes.mdwn b/doc/bugs/__171__transferkey__187___fails_for_bare_remotes.mdwn deleted file mode 100644 index b8c583618..000000000 --- a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -### Please describe the problem. - -I wanted to inspect the state of an object present in a bare remote -without touching the working copy. So I issued «transferkey $KEY --from -bare-remote»; however, even for keys that are definitely present on -the remote, this would fail with «requested key is not present». - -The same method, when using a non-bare repo in «--from», would succeed -under otherwise identical conditions. - -### What steps will reproduce the problem? - -Cf. above. - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20140708 - -Linux 3.15.4 - -> [[done]] not a bug per comment. diff --git a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_1_dd4538ab19a7f8e0f49aa0156aeaae43._comment b/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_1_dd4538ab19a7f8e0f49aa0156aeaae43._comment deleted file mode 100644 index c7760dc05..000000000 --- a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_1_dd4538ab19a7f8e0f49aa0156aeaae43._comment +++ /dev/null @@ -1,32 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="134.147.14.84" - subject="comment 1" - date="2014-07-09T08:51:22Z" - content=""" -[[!format sh \"\"\" - -# Key present on remote. -seb@vserver [ /srv/git/seb/ebooks.git ]$ ls -l annex/objects/f15/e83/WORM-s55921664-m1404679753--calibre%metadata.db/WORM-s55921664-m1404679753--calibre%metadata.db --r--r--r-- 1 seb users 54M 6. Jul 22:49 annex/objects/f15/e83/WORM-s55921664-m1404679753--calibre%metadata.db/WORM-s55921664-m1404679753--calibre%metadata.db - -# Trying to transfer key from remote. -seb [ ~/Ebooks ]$ git annex transferkey WORM-s55921664-m1404679753--calibre%metadata.db --from vserver -d -[2014-07-09 10:49:37 CEST] read: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"show-ref\",\"git-annex\"] -[2014-07-09 10:49:37 CEST] read: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-07-09 10:49:37 CEST] read: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..d2ae02b03f8b87c3465c82f96a924ac7b913fed7\",\"-n1\",\"--pretty=%H\"] -[2014-07-09 10:49:37 CEST] read: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..fc2251ff897bdbc3152c98c4142dcdf77328404b\",\"-n1\",\"--pretty=%H\"] -[2014-07-09 10:49:37 CEST] read: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"log\",\"refs/heads/git-annex..717b07d139b3375cab8c0d54c5dc6379a6c5cb89\",\"-n1\",\"--pretty=%H\"] -[2014-07-09 10:49:37 CEST] chat: git [\"--git-dir=/home/seb/Ebooks/.git\",\"--work-tree=/home/seb/Ebooks\",\"-c\",\"core.bare=false\",\"cat-file\",\"--batch\"] -[2014-07-09 10:49:37 CEST] read: ssh [\"-O\",\"stop\",\"-S\",\"wirrsal.net\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"localhost\"] - -[2014-07-09 10:49:37 CEST] read: rsync [\"--progress\",\"--inplace\",\"--perms\",\"-e\",\"'ssh' '-S' '.git/annex/ssh/wirrsal.net' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-T' 'wirrsal.net' 'git-annex-shell ''sendkey'' ''/srv/git/seb/ebooks.git'' ''WORM-s55921664-m1404679753--calibre%metadata.db'' --uuid 4316c3dc-5b6d-46eb-b780-948c717b7be5 ''--'' ''remoteuuid=a97ab0e5-320e-488b-b9e8-b9da57785b81'' ''direct=1'' ''--'''\",\"--\",\"dummy:\",\"/home/seb/Ebooks/.git/annex/tmp/WORM-s55921664-m1404679753--calibre&smetadata.db\"] - requested key is not present -rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] -rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.1] - - rsync failed -- run git annex again to resume file transfer - - -\"\"\"]] -"""]] diff --git a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_2_4276ff682d10c1d4be9728f9b649ebae._comment b/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_2_4276ff682d10c1d4be9728f9b649ebae._comment deleted file mode 100644 index ef593e5c1..000000000 --- a/doc/bugs/__171__transferkey__187___fails_for_bare_remotes/comment_2_4276ff682d10c1d4be9728f9b649ebae._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="134.147.14.84" - subject="comment 2" - date="2014-07-09T09:02:59Z" - content=""" -Ah, sorry. I see. So, the «%» have to be unescaped into slashes, of course. My bad. - -[[!tag done]] -"""]] diff --git a/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn b/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn deleted file mode 100644 index 44644c890..000000000 --- a/doc/bugs/__34__git_annex_metadata__34___without_a_file_name_is_hazardous.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -### Please describe the problem. - -Accidentally leaving of the file name when invoking git annex metadata means that -the changes are applied to all files. This is almost never what I want, and generally leads to either manual work or trying to undo the commit on the git-annex branch. - -### What steps will reproduce the problem? - -% git annex metadata -s field=value - -congrats, your old values of field are (kinda) gone. - -### What version of git-annex are you using? On what operating system? - -5.20141125, debian - -### 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. -"""]] - -> agreed; [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up.mdwn b/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up.mdwn deleted file mode 100644 index e11d79867..000000000 --- a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -~~~~ -$ git annex version -git-annex version: 5.20140818-g10bf03a -~~~~ - -When repository was initially created, it used "old" hashing from http://git-annex.branchable.com/internals/hashing/ . After some operations, annex was upgraded to "new" format. However, symlinks are still in "old" format and dangling. "git annex fsck", "git annex repair", "git annex pre-commit" - none helps. - -~~~~ -$ ls -l pics -lrwxrwxrwx 1 pfalcon pfalcon 199 Jan 22 2012 IMG_3776.JPG -> ../.git/annex/objects/KM/j6/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG -lrwxrwxrwx 1 pfalcon pfalcon 199 Jan 22 2012 renamed2.jpg -> ../.git/annex/objects/7F/z3/SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG/SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG -lrwxrwxrwx 1 pfalcon pfalcon 199 Jan 22 2012 renamed.jpg -> ../.git/annex/objects/W1/vK/SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG/SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG - -$ find .git/annex/objects/ -.git/annex/objects/ -.git/annex/objects/219 -.git/annex/objects/219/741 -.git/annex/objects/219/741/SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG -.git/annex/objects/219/741/SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG/SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG -.git/annex/objects/7a6 -.git/annex/objects/7a6/632 -.git/annex/objects/7a6/632/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG -.git/annex/objects/7a6/632/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG -.git/annex/objects/df3 -.git/annex/objects/df3/9a8 -.git/annex/objects/df3/9a8/SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG -.git/annex/objects/df3/9a8/SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG/SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG -~~~~ - -> Unforunately, I cannot see through the attitude problem to a clear bug -> report. Lacking time/energy to try to coax one out. [[done]] --[[Joey]] diff --git a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_1_5ed3f7b21b007e269f5846cb2d805493._comment b/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_1_5ed3f7b21b007e269f5846cb2d805493._comment deleted file mode 100644 index 8ca81d325..000000000 --- a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_1_5ed3f7b21b007e269f5846cb2d805493._comment +++ /dev/null @@ -1,35 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawld54zdyk6b0W4jXnssSO_j2Nn3W1uVsUE" - nickname="Paul" - subject="comment 1" - date="2014-08-24T20:27:08Z" - content=""" -Aha, so local repo is created with old hash format. But when you add remote (special rsync remote in my case), and copy --to it, it uses new hashes: - -~~~~ -copy 20120122 Routing doorbell/IMG_3776.JPG (checking nas-rsync...) (to nas-rsync...) -sending incremental file list -7a6/ -7a6/632/ -7a6/632/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG/ -7a6/632/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG/SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG -~~~~ - -This explains this nonsense: - -~~~~ -$ git annex unused --from=nas-rsync -unused nas-rsync (checking for unused data...) (checking master...) - Some annexed data on nas-rsync is not used by any files: - NUMBER KEY - 1 SHA256E-s585398--005fe0534d6cc17a3536c1817b091d00249834c338f289ec6569e9f262889251.JPG - 2 SHA256E-s688630--5bc2e8beb7a57f6fbcd7d9321cd5283f04448ea475099dac07ae38f002208040.JPG - 3 SHA256E-s676047--3cd28892ee54aba13e074f230709b2c3b87915ff36efd9be3ddfc603e92ecdda.JPG - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused --from nas-rsync NUMBER - -ok -~~~~ - -"""]] diff --git a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_2_436d8994457517e4c6f68f572b83decc._comment b/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_2_436d8994457517e4c6f68f572b83decc._comment deleted file mode 100644 index 192d48fc7..000000000 --- a/doc/bugs/__34__old__34___and___34__new__34___hash_formats_are_mixed_up/comment_2_436d8994457517e4c6f68f572b83decc._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawld54zdyk6b0W4jXnssSO_j2Nn3W1uVsUE" - nickname="Paul" - subject="comment 2" - date="2014-08-24T22:26:47Z" - content=""" -Ok, I see, http://git-annex.branchable.com/internals/hashing/ says that old vs new hash mess is deliberate, to make user experience better. (One might ask why one hash was replaced with another equivalent, but nobody would. Oh wait, it's a filesystem case sensitivity issue of course. But it's too secret to be mentioned on \"hashing\" page.) - -\"unused --from=\" issue comes and goes, don't see it now. That initial issue of completely broken symlinks happened after running testremote, then breaking it (because it should say it takes hour(s) to complete). So, many users probably won't be affected (nevermind that those who will, will essentially have data loss). - -Last issue I faced that somehow my local working copy gets \"bare = true\" each time I sync against remote SSH repo (which is bare of course, as remote repo should be). - -"""]] diff --git a/doc/bugs/__34__transfers_in_progress__34___gets_the_direction_wrong.mdwn b/doc/bugs/__34__transfers_in_progress__34___gets_the_direction_wrong.mdwn deleted file mode 100644 index e0b02a704..000000000 --- a/doc/bugs/__34__transfers_in_progress__34___gets_the_direction_wrong.mdwn +++ /dev/null @@ -1,55 +0,0 @@ -### Please describe the problem. - - 07:32 warp@18-volt:/mnt/zooyork/annex/somerepo (master)$ git annex info --fast - repository mode: indirect - trusted repositories: 0 - semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - 3dca408f-ccfd-48df-a8a0-b7d517a482ef -- zooyork [here] - 9fbb4e2c-4ed9-47b4-877c-74d2eeea6296 -- [kirby] - d1b57403-2bc2-41d8-9a8e-eec0d3f31e67 -- [pucca] - untrusted repositories: 0 - transfers in progress: - downloading folder/some-large-file.mp4 from pucca - available local disk space: 232.2 gigabytes (+1 megabyte reserved) - -The "transfers in progress" section of the above "git annex info" output describes a file being downloaded from pucca, presumably to [here], which is zooyork. This does not describe the transfer correctly, when I ran the "git annex info --fast" command another git annex process was downloading folder/some-large-file.mp4 from zooyork to pucca (so, in the other direction than git annex info described). - -### What steps will reproduce the problem? - -1. Make two regular git annex repositories, add some big files so a transfer takes long enough that you can run some git annex commands while the transfer is ongoing -2. cd /repo/a ; git annex get a-big-file.mp4 --from=b -3. (in a different window), cd /repo/b ; git annex info --fast - -### What version of git-annex are you using? On what operating system? - - 07:37 warp@18-volt:/mnt/zooyork/annex$ git annex version - git-annex version: 5.20141105-g8b19598 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - - 07:37 warp@18-volt:/mnt/zooyork/annex$ lsb_release -a - No LSB modules are available. - Distributor ID: Ubuntu - Description: Ubuntu 14.04 LTS - Release: 14.04 - Codename: trusty - - -### Please provide any additional information below. - -If you need more info, I'm "kuno" in the #git-annex IRC channel. - -[[!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. -"""]] - -> When I follow those steps, I see "uploading bigfile" in repo B, -> which is indeed the case since repo A is downloading that file from B. -> -> I suspect you're the one who got confused. [[done]] --[[Joey]] diff --git a/doc/bugs/__39__annex_add__39___fails_to___39__git_add__39___for_parent_relative_path.mdwn b/doc/bugs/__39__annex_add__39___fails_to___39__git_add__39___for_parent_relative_path.mdwn deleted file mode 100644 index f129abf62..000000000 --- a/doc/bugs/__39__annex_add__39___fails_to___39__git_add__39___for_parent_relative_path.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -The following commands show the failure: - -$ mkdir d && touch d/f - -$ mkdir g && cd g && git annex add ../d/f - -add ... ok - -error: Invalid path '.git/annex/objects/Jx/... - -... - -Then it seems it is enough to 'git add ../d/f' to complete the operation. - -> Thanks for reporting, [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__39__copy_destdir__61____60__path__62____39___fails.mdwn b/doc/bugs/__39__copy_destdir__61____60__path__62____39___fails.mdwn deleted file mode 100644 index 93f101772..000000000 --- a/doc/bugs/__39__copy_destdir__61____60__path__62____39___fails.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -### Please describe the problem. - -Using `copy --destdir=<path>` fails. - -### What steps will reproduce the problem? - -~~~ -% ./Setup.hs configure --prefix=/usr -% ./Setup.hs build -% ./Setup.hs copy --destdir=my/pkg/dir -~~~ - -### What version of git-annex are you using? On what operating system? - -5.20150731 on Linux (Arch Linux) - -### Please provide any additional information below. - -The steps in `myPostCopy` doesn't consider the destination directory, the following change is enough for my uses: - -~~~ -Index: habs/git-annex/src/git-annex-5.20150731/Setup.hs -=================================================================== ---- habs.orig/git-annex/src/git-annex-5.20150731/Setup.hs -+++ habs/git-annex/src/git-annex-5.20150731/Setup.hs -@@ -27,13 +27,13 @@ main = defaultMainWithHooks simpleUserHo - } - - myPostCopy :: Args -> CopyFlags -> PackageDescription -> LocalBuildInfo -> IO () --myPostCopy _ (CopyFlags { copyVerbosity }) pkg lbi = do -+myPostCopy _ flags pkg lbi = do - installGitAnnexShell dest verbosity pkg lbi - installManpages dest verbosity pkg lbi -- installDesktopFile dest verbosity pkg lbi -+ -- installDesktopFile dest verbosity pkg lbi - where -- dest = NoCopyDest -- verbosity = fromFlag copyVerbosity -+ dest = fromFlag $ copyDest flags -+ verbosity = fromFlag $ copyVerbosity flags - - installGitAnnexShell :: CopyDest -> Verbosity -> PackageDescription -> LocalBuildInfo -> IO () - installGitAnnexShell copyDest verbosity pkg lbi = -~~~ - -As you see I commented out installation of desktop files completely for the moment. I don't really need them, and they require larger changes to be correct. - -> So, by "fails", you mean it installs to ~/.cabal instead of the speficied -> location. -> -> And, the issue with the desktop file installation is that it's not inside -> ~/.cabal at all. -> -> I've applied your patch, thanks. And dealt with the desktop file by -> making it not install it anywhere, unless it's installing to the regular -> ~/.cabal location. [[done]] --[[Joey]] diff --git a/doc/bugs/__39__git_annex_get__39___returns_success_when_file_not_found.mdwn b/doc/bugs/__39__git_annex_get__39___returns_success_when_file_not_found.mdwn deleted file mode 100644 index 93f2a8fd9..000000000 --- a/doc/bugs/__39__git_annex_get__39___returns_success_when_file_not_found.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -### Please describe the problem. -When attempting to 'git annex get' a file that does not exist in the git repository, git-annex correctly reports "not found". But it still returns exit code 0, incorrectly indicating success. This is problematic for scripting. - -### What steps will reproduce the problem? -See transcript - -### What version of git-annex are you using? On what operating system? -git-annex 5.20140517.4 as supplied by 'git-annex' aptitude package on Ubuntu 12.04.4 LTS (32-bit) - -### Please provide any additional information below. - -[[!format sh """ - -henry@commsbox:~/work/tmp$ git init test -Initialized empty Git repository in /home/henry/work/tmp/test/.git/ -henry@commsbox:~/work/tmp$ cd test -henry@commsbox:~/work/tmp/test$ git annex init -init ok -(Recording state in git...) -henry@commsbox:~/work/tmp/test$ git annex get nonexistent.file -git-annex: nonexistent.file not found -henry@commsbox:~/work/tmp/test$ echo $? -0 - - -"""]] - -> Ok, I can find no reason why it was implemented as a warning in -> 5f3661238de9f31e6fed0be74fca9d5f1659278c in the bug report associated -> with that commit. So, promoted to error. [[done]] --[[Joey]] diff --git a/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu.mdwn b/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu.mdwn deleted file mode 100644 index 68ad05809..000000000 --- a/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -### Please describe the problem. -Using assistant via xfce's "Internet -> Git annex" menu item, trying to connect to an ssh server fails - -### What steps will reproduce the problem? -Use xubuntu 13.04 and git-annex - -### What version of git-annex are you using? On what operating system? -git-annex version: 3.20121112ubuntu2 - -xubuntu 13.04 - -### Please provide any additional information below. -if I "sudo apt-get install ssh-askpass", this gets resolved. I think this should be fixed in the ubuntu repository's program dependencies. - -Also if I run "git-annex webapp" from the terminal, this doesn't happen because it will ask me for the password in the terminal. -[[!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 - Failed to ssh to the server. Transcript: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory Permission denied, please try again. ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory Received disconnect from xxx.xxx.xxx.xxx: 2: Too many authentication failures for <user> - -# End of transcript or log. -"""]] - -> [[fixed|done]]; the assistant no longer recommends ssh-askpass, it does -> its own ssh password prompting and is its own ssh password agent. -> --[[Joey]] diff --git a/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu/comment_1_f4656f8a0f36535def0772db06098c5f._comment b/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu/comment_1_f4656f8a0f36535def0772db06098c5f._comment deleted file mode 100644 index 34a2ed325..000000000 --- a/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu/comment_1_f4656f8a0f36535def0772db06098c5f._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.153.255.110" - subject="comment 1" - date="2013-09-09T20:08:57Z" - content=""" -It's not a dependency. It's a recommends. - -apt does not install new recommends that get added to a package. Adding that recommends only causes it to be installed by default when new users install the package - -This seems to be the best I can do, short of adding a separate git-annex-assistant package, which could depend on ssh-askpass. -Might not be a bad idea.. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__.mdwn b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__.mdwn deleted file mode 100644 index 57a8b9756..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -### Please describe the problem. -Android 5.0 (apparently) requires PIE executables. [You get "error: only position independent executables (PIE) are supported.") - -### What steps will reproduce the problem? -Trying to start git annex (or the webapp) on android 5.0 - -### What version of git-annex are you using? On what operating system? -Currently nightly on Android 5.0 (Nexus 5) - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_10_2e434e142a0d8b7ad27c00836043e261._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_10_2e434e142a0d8b7ad27c00836043e261._comment deleted file mode 100644 index 01fdc9b4a..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_10_2e434e142a0d8b7ad27c00836043e261._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 10" - date="2015-01-07T02:41:21Z" - content=""" -I really want to know if I managed to get git-annex linked PIE before proceeding with furher yak shaving on getting busybox, etc built PIE. - -If you can use adb or another terminal, see if you can run /data/data/ga.androidterm/lib/lib.git-annex.so and if it prints git-annex's usage message. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_11_d8d5a0c61320b583dc1c42e875173bc3._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_11_d8d5a0c61320b583dc1c42e875173bc3._comment deleted file mode 100644 index a76fd7869..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_11_d8d5a0c61320b583dc1c42e875173bc3._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="etset" - subject="git-annex is correctly linked" - date="2015-01-07T14:30:38Z" - content=""" -I tested the executable you mention, and indeed, the git-annex help/list of commands appears. I also tested every other executable in the folder, and most of them display the PIE error message. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_12_feeb65a0cb3273b605061ae3d3b8ff92._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_12_feeb65a0cb3273b605061ae3d3b8ff92._comment deleted file mode 100644 index 6bf56ddea..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_12_feeb65a0cb3273b605061ae3d3b8ff92._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 12" - date="2015-01-07T20:39:27Z" - content=""" -After some work, all binaries are now built PIE. Further testing appreciated. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_13_bec0fb96b4b26382c20511a3c9ed537c._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_13_bec0fb96b4b26382c20511a3c9ed537c._comment deleted file mode 100644 index 878a6b376..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_13_bec0fb96b4b26382c20511a3c9ed537c._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="etset" - subject="Seems to be fixed" - date="2015-01-07T22:14:57Z" - content=""" -I didn't have an opportunity to do a sync with it yet, but the main problem seems to be gone with this last build: it now successfully opens and shows the assistant web interface. Thanks a lot! :D -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_14_fd30c9f9c3713728fb910b310397ba32._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_14_fd30c9f9c3713728fb910b310397ba32._comment deleted file mode 100644 index de92a09ee..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_14_fd30c9f9c3713728fb910b310397ba32._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="ztzg" - subject="Build 5.20150107-g0e8cf92 seems to work" - date="2015-01-12T17:53:07Z" - content=""" -Hi Joey, everybody, - -I was successful in syncing a repository (twice, and including contents) using version 5.20150107-g0e8cf92. -The environment is: Nexus 7 (2013), Android 5.0.1, not rooted. - -Note, however, that this version spews a lot of bionic warnings (I'm using -git-annex from the terminal): - - - -Probably hamless, but I thought I'd mention them. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_15_82446751b835e95832d4aefd7805cd1f._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_15_82446751b835e95832d4aefd7805cd1f._comment deleted file mode 100644 index c86607ef8..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_15_82446751b835e95832d4aefd7805cd1f._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="ztzg" - subject="comment 15" - date="2015-01-12T17:56:20Z" - content=""" -Oh, and many thanks! -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_1_526c86345ab82e4344c6b50bc00f2437._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_1_526c86345ab82e4344c6b50bc00f2437._comment deleted file mode 100644 index a98dd2266..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_1_526c86345ab82e4344c6b50bc00f2437._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="etset" - subject="comment 1" - date="2014-12-03T09:42:01Z" - content=""" -git-annex also stopped working for me after upgrading to Android 5 in my Nexus 7 (2012). Opening it shows the above error (\"error: only position independent executables (PIE) are supported.\") in the terminal, and that's it. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_2_43bb5bb481f54764d355dfac536daba6._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_2_43bb5bb481f54764d355dfac536daba6._comment deleted file mode 100644 index cb171e604..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_2_43bb5bb481f54764d355dfac536daba6._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="ztzg" - subject="+1" - date="2014-12-19T07:39:20Z" - content=""" -Same here. Nexus 7 (2013), Android 5.0.1. It looks like non-PIE executables are not coming back. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_3_3c37c32fe851f2a8cd854ccdd64b4453._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_3_3c37c32fe851f2a8cd854ccdd64b4453._comment deleted file mode 100644 index 5509e8668..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_3_3c37c32fe851f2a8cd854ccdd64b4453._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkev8_Er652-NMvfEpn3r5VwulP5phjNuI" - nickname="jerome" - subject="it need to be built with -fPIE -pie." - date="2014-12-30T10:40:11Z" - content=""" -https://code.google.com/p/android-developer-preview/issues/detail?id=888 -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_4_35a4da019f17c7979f220aba04b6b80a._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_4_35a4da019f17c7979f220aba04b6b80a._comment deleted file mode 100644 index 23cde1d17..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_4_35a4da019f17c7979f220aba04b6b80a._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-01-05T16:27:20Z" - content=""" -I have added a 5.0 build that is built with -fPIE -pie. I have not tested -this build yet so look forward to your feedback. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_5_6b7da5bd28e8f9463b141ffdf2b60011._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_5_6b7da5bd28e8f9463b141ffdf2b60011._comment deleted file mode 100644 index ebfab6f18..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_5_6b7da5bd28e8f9463b141ffdf2b60011._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="gio" - subject="comment 5" - date="2015-01-06T10:07:50Z" - content=""" -With the new build, it still complains about the executable not being PIE. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_6_105c4a78e10fd74f2775ec01be6a3324._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_6_105c4a78e10fd74f2775ec01be6a3324._comment deleted file mode 100644 index 45fe8a4ea..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_6_105c4a78e10fd74f2775ec01be6a3324._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="etset" - subject="Same for me" - date="2015-01-06T12:45:25Z" - content=""" -I confirm that the new build still doesn't work, unfortunately. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_7_c9104ad6d9cfec93f561b9cd514b6f48._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_7_c9104ad6d9cfec93f561b9cd514b6f48._comment deleted file mode 100644 index 3d4f7e230..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_7_c9104ad6d9cfec93f561b9cd514b6f48._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 7" - date="2015-01-06T17:43:45Z" - content=""" -I verified with `eu-readelf --file-header` that the git-annex binary is DYN; ie linked PIE. - -It might be that I also need to tell the C compiler to build it with PIE options. I have now updated the build to include that. Please test the new build. - -It occurs to me that the problem might be not git-annex, but one of the other binaries, like busybox. Does the android app install to the point that there is a working terminal app with a shell? - -It also seems possible that the entire haskell library stack might need to be built with PIE options. If so, that will be a massive pain; I'd need an entire separate autobuilder instance. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_8_e628cc5365b1268450f0245b362266cc._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_8_e628cc5365b1268450f0245b362266cc._comment deleted file mode 100644 index ad25a2694..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_8_e628cc5365b1268450f0245b362266cc._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="etset" - subject="Still not working" - date="2015-01-06T22:48:18Z" - content=""" -The terminal opens, showing the error message at start and at every new opened tab, without a working shell ever appearing. -"""]] diff --git a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_9_0c8b65e117ffb3f00c57c4a420313c05._comment b/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_9_0c8b65e117ffb3f00c57c4a420313c05._comment deleted file mode 100644 index 7b14e7328..000000000 --- a/doc/bugs/__91__Android__93___5.0_needs_PIE_executables___40__git_annex_does_not_work_on_android_5.0__41__/comment_9_0c8b65e117ffb3f00c57c4a420313c05._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 9" - date="2015-01-07T02:37:25Z" - content=""" -Then it's busybox (and git, and...) that's the problem. -"""]] diff --git a/doc/bugs/__92____92___instead_of___47___on_rsync_special_remote_on_linux_accessed_from_a_windows_git-annex.mdwn b/doc/bugs/__92____92___instead_of___47___on_rsync_special_remote_on_linux_accessed_from_a_windows_git-annex.mdwn deleted file mode 100644 index 5f6d35fad..000000000 --- a/doc/bugs/__92____92___instead_of___47___on_rsync_special_remote_on_linux_accessed_from_a_windows_git-annex.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -Getting file from a linux rsync special remote from a windows machine is impossible. - -### What steps will reproduce the problem? -git annex get . - -### What version of git-annex are you using? On what operating system? -5.20140316-gbe47273 on windows 8. - -### Please provide any additional information below. - -Launching in debug mode, we see the wrong \\ used instead of / used. Syntax that rsync doesn't understand on a linux box. -[[!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 -read: rsync ["-e","'ssh' '-l' 'git' '-T' -","--progress","--inplace","git@strasser-family.ch:~/files/G5\\jj\\'SHA256E-s675 ---1112f74fc9ebea01460efe26e447171a1aacf8e551f06f62ef6fe683df02e03c.mat\\SHA256E- -s675--1112f74fc9ebea01460efe26e447171a1aacf8e551f06f62ef6fe683df02e03c.mat'","/c -ygdrive/c/Users/pablo/Desktop/Nouveau dossier/InnerResult/.git/annex/tmp/SHA256E --s675--1112f74fc9ebea01460efe26e447171a1aacf8e551f06f62ef6fe683df02e03c.mat"] - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails.mdwn b/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails.mdwn deleted file mode 100644 index d580d39ef..000000000 --- a/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. - -I do `git annex add .` to add all new files. However I'm busy copying a big file. This file fails with "... changed while it was being added". -When the `add` ends, none of the files have been added. - -I would expect all the files except the one that was changing to be added. - -### What steps will reproduce the problem? - -Add files while changing one. - -### What version of git-annex are you using? On what operating system? - -5.20140412ubuntu1 - -### 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. -"""]] - -> I don't know if I would call this a bug, since you can just re-run the -> command to pick up where it left off. -> -> However, `git annex add` was actually changed in -> [[!commit efb37e7c789921f3f8705d8a5d42d41d9343a00d]] to not -> stop when it fails to add one file, and continue adding the rest. -> So, this is already [[done]]. You just need to get a -> version of git-annex from this April, rather than April 2014.. -> --[[Joey]] diff --git a/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails/comment_1_bddb8b5bf46335788fb9134c74262945._comment b/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails/comment_1_bddb8b5bf46335788fb9134c74262945._comment deleted file mode 100644 index b45c74077..000000000 --- a/doc/bugs/__96__git_annex_add_.__96___fails_for_all_files_if_one_fails/comment_1_bddb8b5bf46335788fb9134c74262945._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="jean.jordaan@4bb3bd508a9eb0a4bab5d1b587dadd2b6c4a7edc" - nickname="jean.jordaan" - subject="Sorry for the noise, thanks for the tool :-)" - date="2015-06-10T05:31:40Z" - content=""" -Looks like I need to get back to a build-from-source distro! -"""]] diff --git a/doc/bugs/__96__git_annex_add__96___changes_mtime_if_symlinks_are_fixed_in_the_background.mdwn b/doc/bugs/__96__git_annex_add__96___changes_mtime_if_symlinks_are_fixed_in_the_background.mdwn deleted file mode 100644 index eba11aa2d..000000000 --- a/doc/bugs/__96__git_annex_add__96___changes_mtime_if_symlinks_are_fixed_in_the_background.mdwn +++ /dev/null @@ -1,51 +0,0 @@ -### Please describe the problem. - -When `git annex add` is run on dangling symlinks which point to the annex, the pre-commit hook `git annex pre-commit .` is run which, in turn, runs `git annex fix`. - -During this fix, the mtime of the symlink changes. I assume the symlink is actually deleted and re-created in the background which would explain this behavior. - -### What steps will reproduce the problem? - -[[!format sh """ -# manual import of annexed data into new annex -% mkdir repo1.annex -% cd !$ -% git init; git annex init -% echo hi > foo -% git annex add foo; git commit -m bar -% mkdir ../repo2 -% cd !$ -% git init; git annex init -% mkdir .git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/ -% cp -ax ../repo1/.git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4 .git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4 -% mkdir subdirectory -% cd !$ -% cp -ax ../../repo1.annex/foo . -% ls -l foo -total 4 -lrwxrwxrwx 1 richih richih 194 Jul 11 12:20 foo -> .git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4 -% git annex fix # this does nothing -% ls -l foo -total 4 -lrwxrwxrwx 1 richih richih 194 Jul 11 12:20 foo -> ..git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4 -% git annex add foo -add foo ok -(Recording state in git...) -% ls -l foo -total 4 -lrwxrwxrwx 1 richih richih 197 Jul 11 12:23 foo -> ../.git/annex/objects/zQ/MQ/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4/SHA256E-s3--98ea6e4f216f2fb4b69fff9b3a44842c38686ca685f3f55dc48c5d3fb1107be4 -% - -"""]] - - -### What version of git-annex are you using? On what operating system? - -git-annex 4.20130709 on Debian unstable i386 and x64. - -### Please provide any additional information below. - -As noted in [[todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex/#comment-e0ea68b5f84cf4130001ad34e9f3b2ff]], `git annex import` does not seem to work on other repos which is why I tried to build this by hand. This works fine and retains mtime as long as I don't need to change the relative depth the symlinks. -I think that the issue above should be fixed in and as of itself, though. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories.mdwn b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories.mdwn deleted file mode 100644 index ef0f85662..000000000 --- a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories.mdwn +++ /dev/null @@ -1,88 +0,0 @@ -As per topic, `git annex forget --drop-dead --force` does not behave as expected. Instead of getting rid of dead repositories, it actually revives them. - -I messed up the initial setup of the S3 special remote and instead of risking manual intervention, I figured it would be cleanest to nuke the old special remotes, using a new one instead. -And yes, I should have used a test repo :( - -As this is apu.debconf.org, you could get access to the repo if that helps. - - -[[!format sh """ -richih@apu (git)-[master] /srv/video/video.debian.net % git annex info -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - 070cff8a-6302-4aa7-a63c-3fdd34e598a2 -- amazon_s3_us_east--SHA512E - 0bae683f-bede-43dd-a815-c4f8fb6db32d -- aws_s3_us_east--SHA512E - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: 4392 -local annex size: 884.64 gigabytes -annexed files in working tree: 4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu (git)-[master] /srv/video/video.debian.net % git annex dead 070cff8a-6302-4aa7-a63c-3fdd34e598a2 -dead 070cff8a-6302-4aa7-a63c-3fdd34e598a2 ok -(Recording state in git...) -richih@apu (git)-[master] /srv/video/video.debian.net % git annex dead 0bae683f-bede-43dd-a815-c4f8fb6db32d -dead 0bae683f-bede-43dd-a815-c4f8fb6db32d ok -(Recording state in git...) -richih@apu (git)-[master] /srv/video/video.debian.net % git annex initremote amazon_aws_s3-us_east_1--SHA512E type=S3 encryption='none' embedcreds='no' fileprefix='SHA512E/' bucket='debian-video' -initremote amazon_aws_s3-us_east_1--SHA512E (checking bucket...) git-annex: This bucket is already in use by a different S3 special remote, with UUID: 0bae683f-bede-43dd-a815-c4f8fb6db32d -richih@apu (git)-[master] /srv/video/video.debian.net % git annex info -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: 4392 -local annex size: 884.64 gigabytes -annexed files in working tree: 4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu (git)-[master] /srv/video/video.debian.net % git annex forget --drop-dead --force -forget git-annex (Recording state in git...) -ok -(Recording state in git...) -richih@apu (git)-[master] /srv/video/video.debian.net % git annex info -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - 070cff8a-6302-4aa7-a63c-3fdd34e598a2 -- amazon_s3_us_east--SHA512E - 0bae683f-bede-43dd-a815-c4f8fb6db32d -- aws_s3_us_east--SHA512E - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: 4392 -local annex size: 884.64 gigabytes -annexed files in working tree: 4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu (git)-[master] /srv/video/video.debian.net % git annex version -git-annex version: 5.20140117~bpo70+2 -build flags: Assistant Webapp Pairing S3 Inotify DBus XMPP Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL -remote types: git gcrypt S3 bup directory rsync web tahoe glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -richih@apu (git)-[master] /srv/video/video.debian.net % cat /etc/issue -Debian GNU/Linux 7 \n \l - -richih@apu (git)-[master] /srv/video/video.debian.net % -"""]] - -> [[fixed|done]] via not removing from trust.log --[[Joey]] diff --git a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment deleted file mode 100644 index 05aa545ef..000000000 --- a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.41" - subject="comment 1" - date="2014-03-26T17:19:58Z" - content=""" -You still have git remotes configured with the uuid of the remote, so `git annex info` pulls that data in. Since --drop-dead removes all mention of the remote from the git-annex branch, including that its trust level is dead, the remaining info from the .git/config takes effect. - ---drop-dead could `git remote rm` but that won't help other clones of the repo that also have the dead remote. Instead, I think it may make sense for --drop-dead to avoid removing the uuid from trust.log, so it will still know this remote is dead. - -(Of course, you can easily deal with this locally by `git remote rm` yourself.) -"""]] diff --git a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_2_5397d488bc337cb3d7cb46ed774d0437._comment b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_2_5397d488bc337cb3d7cb46ed774d0437._comment deleted file mode 100644 index 8bdde8972..000000000 --- a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_2_5397d488bc337cb3d7cb46ed774d0437._comment +++ /dev/null @@ -1,90 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 2" - date="2014-03-26T22:39:34Z" - content=""" -Sorry, I had to remove the fixed tag. - - -The bug makes sense, as does your fix. I didn't even consider that this may be the cause. Still, `git remote rm` and `git annex forget --drop-dead --force` does not seem to be enough to truly get rid of the repo (and its UUID & state): - -[[!format sh \"\"\" -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex info -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 4 - 00000000-0000-0000-0000-000000000001 -- web - 070cff8a-6302-4aa7-a63c-3fdd34e598a2 -- amazon_s3_us_east--SHA512E - 0bae683f-bede-43dd-a815-c4f8fb6db32d -- aws_s3_us_east--SHA512E - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: git4392 -local annex size: 884.64 gigabytes -annexed files in working tree: am4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex dead amazon_s3_us_east--SHA512E -dead amazon_s3_us_east--SHA512E ok -(Recording state in git...) -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex dead aws_s3_us_east--SHA512E -dead aws_s3_us_east--SHA512E ok -(Recording state in git...) -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git remote rm amazon_s3_us_east--SHA512E -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git remote rm aws_s3_us_east--SHA512E -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex forget --drop-dead --force -forget git-annex (Recording state in git...) -ok -(Recording state in git...) -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex info -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: 4392 -local annex size: 884.64 gigabytes -annexed files in working tree: 4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex initremote amazon_aws_s3-us_east_1--SHA512E type=S3 encryption='none' embedcreds='no' fileprefix='SHA512E/' bucket='debian-video' -initremote amazon_aws_s3-us_east_1--SHA512E (checking bucket...) git-annex: This bucket is already in use by a different S3 special remote, with UUID: 0bae683f-bede-43dd-a815-c4f8fb6db32d -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % cat .git/annex -cat: .git/annex: Ist ein Verzeichnis -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % cat .git/config -[core] - repositoryformatversion = 0 - filemode = true - bare = false - logallrefupdates = true -[annex] - uuid = 92e9fac9-97ec-401f-a421-33f6b4f43e47 - version = 5 -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % git annex info 537 23:33:37 Mi 26.03.2014 -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - 92e9fac9-97ec-401f-a421-33f6b4f43e47 -- here (apu.debconf.org/srv/video/conference_videos.annex) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 136.3 gigabytes (+1 megabyte reserved) -local annex keys: 4392 -local annex size: 884.64 gigabytes -annexed files in working tree: 4628 -size of annexed files in working tree: 885.68 gigabytes -bloom filter size: 16 mebibytes (0.9% full) -backend usage: - SHA512E: 9020 -richih@apu [2] [0] (git)-[master] /srv/video/video.debian.net % -\"\"\"]] -"""]] diff --git a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_3_1b30e7611ec824dc6e79ef35e43ac740._comment b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_3_1b30e7611ec824dc6e79ef35e43ac740._comment deleted file mode 100644 index 5b5784012..000000000 --- a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_3_1b30e7611ec824dc6e79ef35e43ac740._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.41" - subject="comment 3" - date="2014-03-27T17:40:51Z" - content=""" -git-annex stores the uuid of a S3 remote inside the bucket for various reasons. Now that you have removed all knowledge of the remote from the repository, when you attempt to reuse the same bucket for some reason, git-annex has no way to know that this is a remote it used to use with that bucket. - -I think this behavior is entirely reasonable. Also, it's not what you filed the original bug report about; I fixed that bug. I'm going to re-close this. -"""]] diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn b/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn deleted file mode 100644 index 7edebe584..000000000 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -### Please describe the problem. - -mtimes are clobbered with what I think is the time of the first time `git annex` saw a file in that directory on all files which are `git annex import`ed. - - -### What steps will reproduce the problem? - - richih@eudyptes (git)-[master] ~/killme/target % date; stat ../source/*; date; git annex import ../source/*; date; stat *; date - Tue Jul 30 01:41:43 CEST 2013 - File: ‘../source/foo’ - Size: 0 Blocks: 0 IO Block: 4096 regular empty file - Device: 804h/2052d Inode: 110095 Links: 1 - Access: (0644/-rw-r--r--) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-07-30 01:41:03.860703428 +0200 - Modify: 2013-07-30 01:41:03.860703428 +0200 - Change: 2013-07-30 01:41:03.860703428 +0200 - Birth: - - File: ‘../source/foobar’ - Size: 0 Blocks: 0 IO Block: 4096 regular empty file - Device: 804h/2052d Inode: 110104 Links: 1 - Access: (0644/-rw-r--r--) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-07-30 01:41:05.512703349 +0200 - Modify: 2013-07-30 01:41:05.512703349 +0200 - Change: 2013-07-30 01:41:05.512703349 +0200 - Birth: - - Tue Jul 30 01:41:43 CEST 2013 - import foo (checksum...) ok - import foobar (checksum...) ok - (Recording state in git...) - Tue Jul 30 01:41:43 CEST 2013 - File: ‘foo’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268638577 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-07-30 01:41:43.704701516 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘foobar’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268774374 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-07-30 01:41:43.704701516 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - Tue Jul 30 01:41:43 CEST 2013 - richih@eudyptes (git)-[master] ~/killme/target % - - -### What version of git-annex are you using? On what operating system? - - git-annex version: 4.20130709 - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP - local repository version: 3 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - -Debian unstable amd64 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_1_d173f2903faf4bff115a0be02c146ce9._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_1_d173f2903faf4bff115a0be02c146ce9._comment deleted file mode 100644 index acb266abe..000000000 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_1_d173f2903faf4bff115a0be02c146ce9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 1" - date="2013-07-29T23:49:12Z" - content=""" -PS: Maybe adding tests that _all_ commands leave mtime in place would be an option? As it is, I keep (for some value of) finding places where mtimes are clobbered. -"""]] diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment deleted file mode 100644 index 842c713df..000000000 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_2_3563d9eeb9806f8ca1b9b340925837f5._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.21" - subject="comment 2" - date="2013-07-30T17:40:04Z" - content=""" -git-annex makes only a best-effort attempt to preserve mtime. There are multiple cases where it cannot: - -* filesystems that do not support changing the mtime of a symlink -* special remotes -* when 2 files with the same content get stored in the annex, the mtime of one must win over the other since we only have 1 inode - -This last seems to be what has happened in the example you show. Both `foo` and `foobar` are empty. I'm not sure where the 01:19:41 time came from -- perhaps you had a third empty file that was not shown? - -I've tested `git annex import` and it preserves mtimes otherwise. - - -"""]] diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_3_d5c7488db16b71c4f337662c897278ca._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_3_d5c7488db16b71c4f337662c897278ca._comment deleted file mode 100644 index f3cfcfd2d..000000000 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_3_d5c7488db16b71c4f337662c897278ca._comment +++ /dev/null @@ -1,95 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 3" - date="2013-08-02T06:57:12Z" - content=""" -In this particular case - -* It's XFS -* It's a normal repo -* That the inode can have only one shared mtime is obvious, but the symlinks could have their own: - -Random line to make MarkDown happy - - richih@eudyptes (git)-[master] ~/killme/target % stat * .git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - File: ‘foo’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268638577 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:51:35.976674954 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘foobar’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268774374 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:51:35.976674954 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 0 Blocks: 0 IO Block: 4096 regular empty file - Device: 804h/2052d Inode: 73750 Links: 1 - Access: (0444/-r--r--r--) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-07-30 01:20:11.915507749 +0200 - Modify: 2013-07-30 01:19:41.131509226 +0200 - Change: 2013-07-30 01:20:11.915507749 +0200 - Birth: - - richih@eudyptes (git)-[master] ~/killme/target % touch foo - richih@eudyptes (git)-[master] ~/killme/target % stat * .git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - File: ‘foo’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268638577 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:51:35.976674954 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘foobar’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268774374 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:51:35.976674954 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 0 Blocks: 0 IO Block: 4096 regular empty file - Device: 804h/2052d Inode: 73750 Links: 1 - Access: (0444/-r--r--r--) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:54:34.464668766 +0200 - Modify: 2013-08-02 08:54:34.464668766 +0200 - Change: 2013-08-02 08:54:34.464668766 +0200 - Birth: - - richih@eudyptes (git)-[master] ~/killme/target % touch --no-dereference foo - richih@eudyptes (git)-[master] ~/killme/target % stat * .git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - File: ‘foo’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268638577 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:55:07.796667610 +0200 - Modify: 2013-08-02 08:55:07.796667610 +0200 - Change: 2013-08-02 08:55:07.796667610 +0200 - Birth: - - File: ‘foobar’ -> ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 178 Blocks: 8 IO Block: 4096 symbolic link - Device: 804h/2052d Inode: 268774374 Links: 1 - Access: (0777/lrwxrwxrwx) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:51:35.976674954 +0200 - Modify: 2013-07-30 01:19:41.000000000 +0200 - Change: 2013-07-30 01:41:43.700701516 +0200 - Birth: - - File: ‘.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855’ - Size: 0 Blocks: 0 IO Block: 4096 regular empty file - Device: 804h/2052d Inode: 73750 Links: 1 - Access: (0444/-r--r--r--) Uid: ( 1000/ richih) Gid: ( 1000/ richih) - Access: 2013-08-02 08:54:34.464668766 +0200 - Modify: 2013-08-02 08:54:34.464668766 +0200 - Change: 2013-08-02 08:54:34.464668766 +0200 - Birth: - - richih@eudyptes (git)-[master] ~/killme/target % - -As to where the initial time of 01:19:41 came from: Yes, those were earlier tests with other imports of empty files. -"""]] diff --git a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_4_7235130786e764ec3ad5facfecde62da._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_4_7235130786e764ec3ad5facfecde62da._comment deleted file mode 100644 index 8bc6274f9..000000000 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_4_7235130786e764ec3ad5facfecde62da._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 4" - date="2013-09-26T09:08:11Z" - content=""" -Fixed in http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=98fc7e8 -"""]] diff --git a/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency.mdwn b/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency.mdwn deleted file mode 100644 index 12a5e0c14..000000000 --- a/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency.mdwn +++ /dev/null @@ -1,95 +0,0 @@ -### Please describe the problem. - -Building a recent git-annex with cabal with the `minimal build' -options given in the installation instructions fails. It is probably -just a matter of fixing the dependencies in the cabal file. - -### What steps will reproduce the problem? -Compile with: - -cabal install git-annex-5.20140108 --bindir=$HOME/bin -f"-assistant -webapp -webdav -pairing -xmpp -dns" - -### What version of git-annex are you using? On what operating system? -Linux 2.6.32-5-686 i686 GNU/Linux - - -### 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 -Resolving dependencies... -[ 1 of 27] Compiling Utility.PartialPrelude ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/PartialPrelude.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/PartialPrelude.o ) -[ 2 of 27] Compiling Utility.FileSystemEncoding ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/FileSystemEncoding.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/FileSystemEncoding.o ) -[ 3 of 27] Compiling Utility.Applicative ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Applicative.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Applicative.o ) -[ 4 of 27] Compiling Utility.Data ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Data.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Data.o ) -[ 5 of 27] Compiling Utility.Exception ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Exception.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Exception.o ) -[ 6 of 27] Compiling Utility.Tmp ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Tmp.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Tmp.o ) -[ 7 of 27] Compiling Utility.Env ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Env.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Env.o ) -[ 8 of 27] Compiling Utility.UserInfo ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/UserInfo.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/UserInfo.o ) -[ 9 of 27] Compiling Utility.OSX ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/OSX.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/OSX.o ) -[10 of 27] Compiling Utility.Monad ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Monad.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Monad.o ) -[11 of 27] Compiling Utility.Misc ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Misc.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Misc.o ) -[12 of 27] Compiling Utility.Process ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Process.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Process.o ) -[13 of 27] Compiling Utility.Path ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Path.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Path.o ) -[14 of 27] Compiling Utility.FreeDesktop ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/FreeDesktop.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/FreeDesktop.o ) -[15 of 27] Compiling Assistant.Install.AutoStart ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Assistant/Install/AutoStart.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Assistant/Install/AutoStart.o ) -[16 of 27] Compiling Utility.SafeCommand ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/SafeCommand.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/SafeCommand.o ) -[17 of 27] Compiling Utility.ExternalSHA ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/ExternalSHA.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/ExternalSHA.o ) -[18 of 27] Compiling Utility.Directory ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Utility/Directory.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Utility/Directory.o ) -[19 of 27] Compiling Common ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Common.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Common.o ) -[20 of 27] Compiling Git.Version ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Git/Version.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Git/Version.o ) -[21 of 27] Compiling Config.Files ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Config/Files.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Config/Files.o ) -[22 of 27] Compiling Assistant.Install.Menu ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Assistant/Install/Menu.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Assistant/Install/Menu.o ) -[23 of 27] Compiling Build.TestConfig ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Build/TestConfig.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Build/TestConfig.o ) -[24 of 27] Compiling Build.Version ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Build/Version.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Build/Version.o ) -[25 of 27] Compiling Build.Configure ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Build/Configure.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Build/Configure.o ) -[26 of 27] Compiling Build.DesktopFile ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Build/DesktopFile.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Build/DesktopFile.o ) -[27 of 27] Compiling Main ( /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/Setup.hs, /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/Main.o ) -Linking /tmp/git-annex-5.20140108-30015/git-annex-5.20140108/dist/setup/setup ... - checking version...fatal: Not a git repository (or any of the parent directories): .git - 5.20140107 - checking UPGRADE_LOCATION... not available - checking git... yes - checking git version... 1.7.2.5 - checking cp -a... yes - checking cp -p... yes - checking cp --reflink=auto... yes - checking xargs -0... yes - checking rsync... yes - checking curl... no - checking wget... yes - checking bup... no - checking quvi... no - checking newquvi... no - checking nice... yes - checking ionice... yes - checking nocache... no - checking gpg... gpg - checking lsof... lsof - checking git-remote-gcrypt... not available - checking ssh connection caching... no - checking sha1... sha1sum - checking sha256... sha256sum - checking sha512... sha512sum - checking sha224... sha224sum - checking sha384... sha384sum -Configuring git-annex-5.20140108... -Building git-annex-5.20140108... -Preprocessing executable 'git-annex' for git-annex-5.20140108... - -Remote/External.hs:29:8: - Could not find module `Control.Concurrent.STM' - It is a member of the hidden package `stm-2.4.2'. - Perhaps you need to add `stm' to the build-depends in your .cabal file. - Use -v to see a list of the files searched for. -Failed to install git-annex-5.20140108 -cabal: Error: some packages failed to install: -git-annex-5.20140108 failed during the building phase. The exception was: -ExitFailure 1 - - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency/comment_1_86e26ee9ec90aa00f25392052737f0f0._comment b/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency/comment_1_86e26ee9ec90aa00f25392052737f0f0._comment deleted file mode 100644 index a1f52dc5e..000000000 --- a/doc/bugs/__96__minimal_build__39____fails_due_to_missing_stm_dependency/comment_1_86e26ee9ec90aa00f25392052737f0f0._comment +++ /dev/null @@ -1,36 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnlotDRSLW2JVXY3SLSwhrcHteqUHhTtoY" - nickname="Péter" - subject="Not fixed." - date="2014-01-27T00:43:45Z" - content=""" -It's still failing for me, on both i386 and amd64. - -Where exactly is it fixed? - -How is it possible to install git-annex using Cabal? - -http://stackoverflow.com/questions/21371272/cabal-missing-dependency-error - -$ cabal install git-annex --force-reinstalls --bindir=$HOME/bin.local -f\"-assistant -webapp -webdav -pairing -xmpp -dns\" -... -Configuring git-annex-5.20140116... -Building git-annex-5.20140116... -Preprocessing executable 'git-annex' for git-annex-5.20140116... - -Remote/External.hs:29:8: - Could not find module `Control.Concurrent.STM' - It is a member of the hidden package `stm-2.4.2'. - Perhaps you need to add `stm' to the build-depends in your .cabal file. - It is a member of the hidden package `stm-2.2.0.1'. - Perhaps you need to add `stm' to the build-depends in your .cabal file. - Use -v to see a list of the files searched for. -cabal: Error: some packages failed to install: -git-annex-5.20140116 failed during the building phase. The exception was: ExitFailure 1 -$ cabal install stm --force-reinstalls --bindir=$HOME/bin.local -Resolving dependencies... -All the requested packages are already installed: -stm-2.4.2 -Use --reinstall if you want to reinstall anyway. - -"""]] diff --git a/doc/bugs/adding_existing_repo_as_remote_in_webapp_may_reset_its_group.mdwn b/doc/bugs/adding_existing_repo_as_remote_in_webapp_may_reset_its_group.mdwn deleted file mode 100644 index 37a9c2a2e..000000000 --- a/doc/bugs/adding_existing_repo_as_remote_in_webapp_may_reset_its_group.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -Adding eg a ssh remote when the remote repo already exists, in the webapp, -resets its group to transfer. It also clears any preferred content -settings. - -Adding existing local repositories or repositories from removable drives -may have the same problems. Didn't check yet. - -[[!tag confirmed]] --[[Joey]] - -> Fixed for local repos and repos on removable drives. Still open for -> ssh remotes (incl gcrypt). --[[Joey]] - ->> Fixed for ssh (including gcrypt) too. ->> ->> Also affected enabling existing special remotes, like webdav; that's ->> also fixed. [[done]] --[[Joey]] diff --git a/doc/bugs/addurl_+_sync_vs_addurl_+_commit.mdwn b/doc/bugs/addurl_+_sync_vs_addurl_+_commit.mdwn deleted file mode 100644 index 21aa96952..000000000 --- a/doc/bugs/addurl_+_sync_vs_addurl_+_commit.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -I think this is what happened; I need to go back and check this again (maybe I was just misreading something) but I want to get it written down first. - -I've got a git repository, and I just ran git annex init. Then I ran git annex addurl a bunch of times, followed by git annex sync. The result was apparently a repository where the files downloaded by addurl were added using the SHA256 backend rather than the URL backend. I deleted the branches and tried again, but this time after calling git annex addurl a bunch of times I did a normal git commit. This time everything looked fine; the files were all listed in as present in the web remote. - -### What steps will reproduce the problem? - -[[!format sh """ -git annex init -git annex addurl "https://archive.org/download/emularity_engine_jsmess/messnapple2e.js.gz" --file "messnapple2e.js.gz" -git annex sync -"""]] - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20150412-g2be4834 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA TorrentParser - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL - remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 -This is on Linux. - -> In the lack of any followups, I'm confident this was a case of user -> error, so closing. [[done]] --[[Joey]] diff --git a/doc/bugs/addurl_+_sync_vs_addurl_+_commit/comment_1_513d89ddd728dc9c6cc9fbf8af18afb0._comment b/doc/bugs/addurl_+_sync_vs_addurl_+_commit/comment_1_513d89ddd728dc9c6cc9fbf8af18afb0._comment deleted file mode 100644 index 48ce2354d..000000000 --- a/doc/bugs/addurl_+_sync_vs_addurl_+_commit/comment_1_513d89ddd728dc9c6cc9fbf8af18afb0._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-18T18:44:16Z" - content=""" -If you use `git annex addurl`, the file will use the SHA256 backend. - -If you use `git annex addurl --fast`, it will use the URL backend. - -**Either way**, git-annex will know that you added the file from the web, -and `git-annex whereis` will tell you the file is in the web remote, -and tell you its url. - -I don't think there's a bug here. I think you got confused by -seeing URL some of the time and SHA256 some of the time. -If you disagree, please post a transcript demonstrating your problem. -"""]] diff --git a/doc/bugs/addurl_magnet_could_not_download_torrent_file.mdwn b/doc/bugs/addurl_magnet_could_not_download_torrent_file.mdwn deleted file mode 100644 index f00a63a7a..000000000 --- a/doc/bugs/addurl_magnet_could_not_download_torrent_file.mdwn +++ /dev/null @@ -1,49 +0,0 @@ -### Please describe the problem. - -Every time I try to `addurl` with `magnet:` I get this error message: - - could not download torrent file - -### What steps will reproduce the problem? - - git-annex addurl "magnet:?xt=urn:btih:b548b3b8efce813d71c9355832b4382680b8abf9" - -### What version of git-annex are you using? On what operating system? - -* git-annex 5.20150409 -* ubuntu 14.04 x64 - -### Please provide any additional information below. - -[[!format sh """ - -git-annex addurl magnet:?xt=urn:btih:b548b3b8efce813d71c9355832b4382680b8abf9 -(downloading torrent file...) - -04/13 17:16:15 [NOTICE] IPv4 DHT: listening on UDP port 6930 - -04/13 17:16:15 [NOTICE] IPv4 BitTorrent: listening on TCP port 6890 - -04/13 17:16:15 [NOTICE] IPv6 BitTorrent: listening on TCP port 6890 -[#3e3bb9 74KiB/74KiB(100%) CN:13 SD:1] -04/13 17:16:33 [NOTICE] Download complete: [METADATA]b548b3b8efce813d71c9355832b4382680b8abf9 - -04/13 17:16:33 [NOTICE] Saved metadata as ../.git/annex/misctmp/URL--magnet&c,63xt,61urn&cbtih&cb548b3b8efce813d71c9355832b4382680b8abf9/meta/b548b3b8efce813d71c9355832b4382680b8abf9.torrent. - -Download Results: -gid |stat|avg speed |path/URI -======+====+===========+======================================================= -3e3bb9|OK | 0B/s|[MEMORY][METADATA]b548b3b8efce813d71c9355832b4382680b8abf9 - -Status Legend: -(OK):download completed. -addurl magnet:?xt=urn:btih:b548b3b8efce813d71c9355832b4382680b8abf9 - could not download torrent file -failed -git-annex: addurl: 1 failed - -"""]] - -> Looking at the code, it was looking for a file prefixed by ".torrent", -> but of course that should be suffixed instead. So, [[fixed|done]] -> --[[Joey]] diff --git a/doc/bugs/android_4.2.1__44___galaxy_nexus_java.lang.SecurityException.mdwn b/doc/bugs/android_4.2.1__44___galaxy_nexus_java.lang.SecurityException.mdwn deleted file mode 100644 index e5f1873f0..000000000 --- a/doc/bugs/android_4.2.1__44___galaxy_nexus_java.lang.SecurityException.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. -The app fails to open after the install - -### What steps will reproduce the problem? -Downloaded, installed, chose open. - -### What version of git-annex are you using? On what operating system? -today's version. android 4.2.1 - -### Please provide any additional information below. - -I also sent this by email. - -Falling back to hardcoded app location; cannot find expected files in /data/app-lib -git annex webapp -u0_a72@android:/sdcard/git-annex.home $ git annex webapp -Launching web browser on http://127.0.0.1:48812/?auth=cf45448c3690730f05f1a9567e62c6a3cf8d25c43ed14362c8ae78601de0e96d32d2b02923ba95962e80c9bd8ffab621918dd582741f18160f6e2565af61aba5 -Starting: Intent { act=android.intent.action.VIEW dat=http://127.0.0.1:48812/?auth=cf45448c3690730f05f1a9567e62c6a3cf8d25c43ed14362c8ae78601de0e96d32d2b02923ba95962e80c9bd8ffab621918dd582741f18160f6e2565af61aba5 } -java.lang.SecurityException: Permission Denial: startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL - at android.os.Parcel.readException(Parcel.java:1425) - at android.os.Parcel.readException(Parcel.java:1379) - at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:1906) - at com.android.commands.am.Am.runStart(Am.java:494) - at com.android.commands.am.Am.run(Am.java:109) - at com.android.commands.am.Am.main(Am.java:82) - at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) - at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235) - at dalvik.system.NativeStart.main(Native Method) -failed to start web browser - -[[!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/debug.log - - -# End of transcript or log. -"""]] - -This is a duplicate of [[Android_app_permission_denial_on_startup]] - -[[closing|done]] as dup. --[[Joey]] diff --git a/doc/bugs/android_autobuild_broken.mdwn b/doc/bugs/android_autobuild_broken.mdwn deleted file mode 100644 index 6bbd1dfcd..000000000 --- a/doc/bugs/android_autobuild_broken.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -The android build is broken. Annoying evilsplicer failure in the new -bootstrap3 code. --[[Joey]] - -[[fixed|done]] diff --git a/doc/bugs/annex-rsync-transport_ignored.mdwn b/doc/bugs/annex-rsync-transport_ignored.mdwn deleted file mode 100644 index 1c6923a88..000000000 --- a/doc/bugs/annex-rsync-transport_ignored.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -### Please describe the problem. -I have an rsync remote with the following option in config: -annex-rsync-transport = ssh -i /path/to/private/key - -and git annex copy --to <remote> still asks for the remote's password. I've checked and I can ssh into the remote using that key with no problems, here's the --debug output: - - copy SHA256E-s152396--56bcf5e3f72daa1a194b16e42330fe82806cc1dbc6f3bb52888ff5e5c57b8d08.log (gpg) (checking <remote>...) [2014-09-05 13:12:41 CEST] read: rsync ["<user>@<remote>:<remote path>/81c/b5e/'GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d/GPGHMACSHA1--7d9470e207a5669e2d9120538b68815274dbf16d'"] - <user>@<remote>'s password: - - -Once it has asked for the password twice, it starts using the rsync options correctly to copy and the password is no longer needed, until the next "checking remote…". Maybe the "checking remote…" part ignores the configuration? - -### What steps will reproduce the problem? -Use an rsync remote with annex-rsync-transport config set. - -### What version of git-annex are you using? On what operating system? -git annex version gives: - - git-annex version: 5.20140814-g9b89b5c - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -which is the latest available linux-armel version. - -> Also removing didn't use the configured transport. Both [[fixed|done]] -> --[[Joey]] diff --git a/doc/bugs/annex_add_doesn__39__t_any_longer_by_default_commit_git-annex.mdwn b/doc/bugs/annex_add_doesn__39__t_any_longer_by_default_commit_git-annex.mdwn deleted file mode 100644 index 537fddef3..000000000 --- a/doc/bugs/annex_add_doesn__39__t_any_longer_by_default_commit_git-annex.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -### Please describe the problem. - -I thought it was just my failing memory but then our tests started to fail (e.g. https://travis-ci.org/datalad/datalad/builds/69776125#L810): previously (e.g. with 5.20150409+git126-ga29f683-1~ndall+1) git annex add (without -c alwayscommit=False) would commit git-annex branch with information about that file right away, but currently (e.g. with 5.20150610+gitg608172f-1~ndall+1) it doesn't happen any longer. I glanced through the logs but didn't find explicit doc on change of behavior so decided to check if that is intended change? - -### What version of git-annex are you using? On what operating system? - -5.20150610+gitg608172f-1~ndall+1 - - -### 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 -hopa:/tmp/XX -$> git init -Initialized empty Git repository in /tmp/XX/.git/ -2 14055.....................................:Mon 06 Jul 2015 06:12:41 PM EDT:. -(git)hopa:/tmp/XX[master] -$> git annex init -init ok -(recording state in git...) -2 14056.....................................:Mon 06 Jul 2015 06:12:43 PM EDT:. -(git)hopa:/tmp/XX[master] -$> echo 21234 > 2 -2 14057.....................................:Mon 06 Jul 2015 06:12:45 PM EDT:. -(git)hopa:/tmp/XX[master] -$> git annex add 2 -add 2 ok -(recording state in git...) -2 14058.....................................:Mon 06 Jul 2015 06:12:48 PM EDT:. -(git)hopa:/tmp/XX[master] -$> git annex log -fatal: unrecognized argument: -raw - - - -# End of transcript or log. -"""]] - -> `git annex log`, was broken in the last release, and has since been -> fixed (in git). The git-annex branxh is still being committed, as you can -> see with `git log`. [[done]] --[[Joey]] diff --git a/doc/bugs/assistant_committer_crash_on_OSX_when_adding_lots_of_files.mdwn b/doc/bugs/assistant_committer_crash_on_OSX_when_adding_lots_of_files.mdwn deleted file mode 100644 index 9fa44710c..000000000 --- a/doc/bugs/assistant_committer_crash_on_OSX_when_adding_lots_of_files.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -I've had a report of the assistant failing to commit when there are a lot -of files on OSX Yosemite. - -<pre> -Committer crashed: git: createProcess: runInteractiveProcess: exec: resource exhausted (Argument list too long) -[2015-03-22 23:14:42 CET] Committer: warning Committer crashed: git: createProcess: runInteractiveProcess: exec: resource exhausted (Argument list too -long) -</pre> - -Probably need to tune the command length limit for !linux. --[[Joey]] - -> Investigation suggests this is the problem: - - inRepo (Git.LsFiles.notInRepo False $ map changeFile pending) - -> If a lot of new files have been added, the `pending` list can be -> arbitrarily large, and this passes it to git ls-files as parameters.a -> -> It's not the actual commit that fails; that uses Git.Queue and xargs. -> --[[Joey]] - ->> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo.mdwn b/doc/bugs/assistant_creating_.git_directory_inside_bare_repo.mdwn deleted file mode 100644 index a35bc9c3d..000000000 --- a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo.mdwn +++ /dev/null @@ -1,90 +0,0 @@ -### Please describe the problem. -Setting up a git annex repo with the webapp. Adding a small archive removeable disk. -Adding a file to repo. Moving file to archive. The file seems to get copied to the removeable disk -but it is not removed (dropped)from my repo, as I would expect - -Before I add the file to the repo, the archive directory on the removeable drive looks like a bare repo. -After adding one file and moving it to the archive folder, a ".git" directory gets created inside the bare repo. -The .git directory contains an annex directory, and nothing else. - -Is this behaviour the expected one? As far as I have understood it, the files are supposed to "disapear" from my computer when I move them to the archive folder. - - -### What steps will reproduce the problem? -Se above - -### What version of git-annex are you using? On what operating system? -Version: 5.20131127-g736ce5e -Build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA - -Chakra linux -Linux black 3.10.18-1-CHAKRA #1 SMP PREEMPT Sat Nov 9 20:18:15 UTC 2013 x86_64 GNU/Linux - -git annex installed from prebuilt tar. - -### Please provide any additional information below. - -[[!format sh """ -[2013-11-28 23:25:59 CET] main: starting assistant version 5.20131127-g736ce5e -[2013-11-28 23:25:59 CET] Cronner: You should enable consistency checking to protect your data. -(scanning...) [2013-11-28 23:25:59 CET] Watcher: Performing startup scan -(started...) gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark -fatal: Not a git repository: '/run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark/.git' -[2013-11-28 23:26:21 CET] main: Syncing with 7090f0c1abf947a1a186ba243c498172 -warning: no common commits -From /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark - * [new branch] git-annex -> 7090f0c1abf947a1a186ba243c498172/git-annex - * [new branch] master -> 7090f0c1abf947a1a186ba243c498172/master -Already up-to-date. -To /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master -Already up-to-date. -Already up-to-date. -[2013-11-28 23:26:59 CET] Pusher: Syncing with test_ark -To /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark - 4d435e3..e548577 git-annex -> synced/git-annex -[2013-11-28 23:27:17 CET] Committer: Adding git-annex..64.tar.gz - -(Recording state in git...) -(merging 7090f0c1abf947a1a186ba243c498172/git-annex into git-annex...) -(Recording state in git...) - - - -(Recording state in git...) -add git-annex-standalone-amd64.tar.gz (checksum...) [2013-11-28 23:27:17 CET] Committer: Committing changes to git -[2013-11-28 23:27:17 CET] Pusher: Syncing with test_ark -Already up-to-date. -To /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark - e548577..b86f41c git-annex -> synced/git-annex - 658b0f2..f32a646 annex/direct/master -> synced/master -Already up-to-date. -[2013-11-28 23:27:27 CET] Committer: Adding git-annex..64.tar.gz -[2013-11-28 23:27:27 CET] Committer: Committing changes to git -[2013-11-28 23:27:27 CET] Pusher: Syncing with test_ark - -git-annex-standalone-amd64.tar.gz - - 32768 0% 0.00kB/s 0:00:00 Already up-to-date. -To /run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark - b86f41c..806a2dd git-annex -> synced/git-annex - f32a646..5e254e7 annex/direct/master -> synced/master -Already up-to-date. - - 20143752 100% 85.24MB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 20146306 bytes received 31 bytes 40292674.00 bytes/sec -total size is 20143752 speedup is 1.00 -fatal: Not a git repository: '/run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark/.git' -fatal: Not a git repository: '/run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark/.git' -fatal: Not a git repository: '/run/media/daniel/7090f0c1-abf9-47a1-a186-ba243c498172/test_ark/.git' -[2013-11-28 23:27:59 CET] Pusher: Syncing with test_ark -Everything up-to-date - - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_1_675210444f7801eb8c2c455a5accf8e9._comment b/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_1_675210444f7801eb8c2c455a5accf8e9._comment deleted file mode 100644 index 435d22903..000000000 --- a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_1_675210444f7801eb8c2c455a5accf8e9._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 1" - date="2013-11-30T20:18:53Z" - content=""" -This bug, introduced in version 5.20131118, caused `git annex init`, when run in a bare repository, to set `core.bare` to false. - -I have fixed the bug. I may need to make git-annex detect and automatically fix up after the problem. - -To manually fix a bare repository created by the buggy version of git-annex, run `git config core.bare true` in the repository. Then if there's a .git/annex/objects inside the bare git repository, you can move it to annex/objects. -"""]] diff --git a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_2_d7f1378bc75e7a8be9da2585acc6fd63._comment b/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_2_d7f1378bc75e7a8be9da2585acc6fd63._comment deleted file mode 100644 index 338faa357..000000000 --- a/doc/bugs/assistant_creating_.git_directory_inside_bare_repo/comment_2_d7f1378bc75e7a8be9da2585acc6fd63._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 2" - date="2013-12-02T16:35:41Z" - content=""" -I've now made git-annex automatically detect these problem repositories, and fix them up. You should not need to do anything to recover, just upgrade git-annex eventually, and use it. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU.mdwn b/doc/bugs/assistant_eats_all_CPU.mdwn deleted file mode 100644 index 719fca425..000000000 --- a/doc/bugs/assistant_eats_all_CPU.mdwn +++ /dev/null @@ -1,529 +0,0 @@ -[[!meta title="debian system runs assistant in tight loop, rather than using select"]] - -### Please describe the problem. - -After running for a while, the assistant maxes my CPU. I have evidence -here that it is just sitting there, doing apparently nothing (transfers -are finished), eating precious CPU. - -Nowadays, I do not let the assistant run on its own, otherwise it makes -my office noisy because the CPU fan starts. - -This makes the assistant and the webapp basically unuseable for me: -if i want to use its feature, I must remember to shut down the daemon -every time I am done with it, which seems contrary to the spirit of -the project. :) - -### What steps will reproduce the problem? - -It's a little unclear. There was a peculiar crash here (power cable -yanked out) during a `git annex copy`, which *was* eating up all CPU, -but mostly through I/O. - -That is the purple block in this graph: - -![CPU usage during the last 24 hours][cpu-day.png] - -Power was yanked out about right after that purple block was gone: - -![Uptime in the last 24 hours][uptime-day.png] - -Files were copied to an external drive at the time of the crash, -which explains the high iowait. The last lines in daemon.log are: - -[[!format txt """ -sent 184184937 bytes received 31 bytes 13643330.96 bytes/sec -total size is 184162304 speedup is 1.00 -[2013-12-31 23:56:47 EST] Transferrer: Uploaded American ..Queen.avi -[2013-12-31 23:56:47 EST] Pusher: Syncing with backup -To /backup/srv/video - 5155be4..7d904d5 git-annex -> synced/git-annex -"""]] - -And daemon.status: - -[[!format txt """ -lastRunning:1388569856.366405s -scanComplete:True -sanityCheckRunning:False -lastSanityCheck:1387169250.801117s -"""]] - -When the machine rebooted, I logged in, and resumed the transfer using -`git annex copy`. The assistant was also started automatically during -my session, but I wasn't aware of that until this morning (7AM) when i -came back to the terminal and noticed how noisy it was. - -At that point i did `killall git-annex` and CPU usage returned to -normal, as the frequency of the CPU: - -![CPU frequency scaling in the last 24 hours][cpuspeed-day.png] - -I am trying to see if I can reproduce this problem reliably - I -just started the assistant again now, and while the CPU usage is -already high, I will forgive it for now because it's doing its -initial scans... Let's see what happens in the afternoon! --[[anarcat]] - -Update: I seem to be able to reproduce. I just started the webapp and -the scans were performed. They are now finished, yet the CPU usage is -still high: - -[[!format txt """ -top - 14:10:20 up 1 day, 1:16, 7 users, load average: 5,51, 3,61, 2,53 -Tasks: 292 total, 2 running, 288 sleeping, 0 stopped, 2 zombie -%Cpu(s): 60,9 us, 7,8 sy, 0,6 ni, 29,5 id, 0,8 wa, 0,0 hi, 0,5 si, 0,0 st -KiB Mem: 8162960 total, 6943100 used, 1219860 free, 1065464 buffers -KiB Swap: 4022268 total, 15452 used, 4006816 free, 1983252 cached - - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND -18364 anarcat 20 0 152m 27m 18m S 53,7 0,3 0:35.61 git-annex - 8388 anarcat 20 0 192m 54m 21m S 47,8 0,7 12:55.19 git-annex -18671 anarcat 20 0 157m 33m 18m S 29,9 0,4 0:22.65 git-annex -"""]] - -An strace on 18364 yields: - -[[!format txt """ -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 537245076}) = 0 -[pid 18364] <... futex resumed> ) = ? ERESTARTSYS (To be restarted) -[pid 18364] --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -[pid 18364] rt_sigreturn(0x1a) = 202 -[pid 18364] futex(0x3de703c, FUTEX_WAIT_PRIVATE, 51, NULL <unfinished ...> -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 256339453}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 537670797}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 256748972}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 538079838}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 257202502}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 538533443}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 257611085}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 538941839}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 258018398}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 539349100}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 258433069}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 539763939}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 258863864}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 540195885}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 259295204}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 540626505}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 259729523}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 541060751}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 260131616}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 541463041}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 260539761}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 541871201}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 260970889}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 542302047}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 261378036}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 542709166}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 261780507}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 543111819}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 262194032}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 543525143}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 262610040}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 543941528}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 263042272}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 544374016}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18366] rt_sigprocmask(SIG_BLOCK, [TERM], [], 8) = 0 -[pid 18366] clock_gettime(0x2 /* CLOCK_??? */, {82, 263532359}) = 0 -[pid 18366] clock_gettime(0x3 /* CLOCK_??? */, {79, 544864814}) = 0 -[pid 18366] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -[pid 18364] <... futex resumed> ) = ? ERESTARTSYS (To be restarted) -[pid 18364] --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -[pid 18364] rt_sigreturn(0x1a) = 202 -[pid 18364] futex(0x3de703c, FUTEX_WAIT_PRIVATE, 51, NULL <unfinished ...> -"""]] - - [cpu-day.png]: http://paste.anarc.at/cpu-day.png - [uptime-day.png]: http://paste.anarc.at/uptime-day.png - [cpuspeed-day.png]: http://paste.anarc.at/cpuspeed-day.png - -### What version of git-annex are you using? On what operating system? - -Debian wheezy. - -[[!format sh """ -anarcat@marcos:~$ git annex version -git-annex version: 5.20131109-gf2cb5b9 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook -"""]] - -### Please provide any additional information below. - -This *may* be related to [[bugs/webapp_takes_100__37___of_the_cpu/]], -but I didn't observe both problems simultaneously so far - ie. the -webapp doesn't need to run for this bug to happen. - -Here's the output of top: - -[[!format sh """ -top - 04:55:01 up 16:01, 10 users, load average: 3,96, 3,72, 3,59 -Tasks: 293 total, 6 running, 284 sleeping, 0 stopped, 3 zombie -%Cpu(s): 87,4 us, 10,9 sy, 0,6 ni, 0,1 id, 0,3 wa, 0,0 hi, 0,7 si, 0,0 st -KiB Mem: 8162960 total, 6847120 used, 1315840 free, 1084756 buffers -KiB Swap: 4022268 total, 1320 used, 4020948 free, 2041108 cached - - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND - 8099 anarcat 20 0 144m 28m 18m S 34,0 0,4 460:10.96 git-annex - 6525 anarcat 20 0 436m 295m 18m S 28,4 3,7 448:50.71 git-annex -11146 munin 20 0 25376 6540 1896 R 28,4 0,1 0:00.05 munin-update - 8045 anarcat 20 0 165m 41m 18m S 22,7 0,5 455:14.41 git-annex -11142 root 20 0 32316 7356 2016 R 22,7 0,1 0:00.05 ikisite -11144 aegir 20 0 161m 16m 6608 R 22,7 0,2 0:00.05 php - 2649 liquidso 20 0 222m 54m 5516 S 5,7 0,7 40:40.61 liquidsoap -11149 anarcat 20 0 24448 1552 1072 R 5,7 0,0 0:00.01 top - 1 root 20 0 10644 784 652 S 0,0 0,0 0:01.10 init - 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd - 3 root 20 0 0 0 0 S 0,0 0,0 2:10.09 ksoftirqd/0 - 6 root rt 0 0 0 0 S 0,0 0,0 0:00.22 migration/0 - 7 root rt 0 0 0 0 S 0,0 0,0 0:00.59 watchdog/0 - 8 root rt 0 0 0 0 S 0,0 0,0 0:00.25 migration/1 - 10 root 20 0 0 0 0 S 0,0 0,0 2:11.10 ksoftirqd/1 - 12 root rt 0 0 0 0 S 0,0 0,0 0:00.17 watchdog/1 - 13 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 cpuset - 14 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 khelper - 15 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kdevtmpfs - 16 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 netns - 17 root 20 0 0 0 0 S 0,0 0,0 0:00.17 sync_supers - 18 root 20 0 0 0 0 S 0,0 0,0 0:00.00 bdi-default - 19 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kintegrityd - 20 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kblockd - 22 root 20 0 0 0 0 S 0,0 0,0 0:00.06 khungtaskd - 23 root 20 0 0 0 0 S 0,0 0,0 3:04.23 kswapd0 - 24 root 25 5 0 0 0 S 0,0 0,0 0:00.00 ksmd - 25 root 39 19 0 0 0 S 0,0 0,0 0:00.00 khugepaged - 26 root 20 0 0 0 0 S 0,0 0,0 0:00.00 fsnotify_mark - 27 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 crypto - 113 root 20 0 0 0 0 S 0,0 0,0 0:00.01 khubd - 133 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ata_sff - 153 root 20 0 0 0 0 S 0,0 0,0 0:05.68 scsi_eh_0 - 158 root 20 0 0 0 0 S 0,0 0,0 0:00.00 scsi_eh_1 - 160 root 20 0 0 0 0 S 0,0 0,0 0:00.09 kworker/u:2 - 161 root 20 0 0 0 0 S 0,0 0,0 0:00.00 scsi_eh_2 - 162 root 20 0 0 0 0 S 0,0 0,0 0:00.00 scsi_eh_3 - 163 root 20 0 0 0 0 S 0,0 0,0 0:01.43 kworker/u:3 - 294 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 295 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kcryptd_io - 296 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kcryptd - 305 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 307 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 311 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 313 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 341 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 342 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kcryptd_io - 343 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kcryptd - 352 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 354 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 356 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 358 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 361 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kdmflush - 400 root 20 0 0 0 0 S 0,0 0,0 0:00.00 jbd2/dm-1-8 - 401 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-dio-unwrit - 468 root 20 0 0 0 0 S 0,0 0,0 0:02.19 kworker/1:2 - 538 root 20 0 21804 1804 796 S 0,0 0,0 0:00.10 udevd - 705 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kpsmoused - 878 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 hd-audio0 - 890 postfix 20 0 44216 2460 1912 S 0,0 0,0 0:00.00 pickup - 939 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kvm-irqfd-clean - 1150 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 firewire - 1719 root 20 0 0 0 0 S 0,0 0,0 0:03.40 flush-254:3 - 1786 root 20 0 0 0 0 S 0,0 0,0 0:00.17 jbd2/dm-2-8 - 1787 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-dio-unwrit - 1788 root 20 0 0 0 0 S 0,0 0,0 0:06.60 jbd2/dm-3-8 - 1789 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-dio-unwrit - 1790 root 20 0 0 0 0 S 0,0 0,0 0:02.56 jbd2/dm-4-8 - 1791 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-dio-unwrit - 1792 root 20 0 0 0 0 S 0,0 0,0 0:01.19 jbd2/dm-8-8 - 1793 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-dio-unwrit - 2004 anarcat 20 0 0 0 0 Z 0,0 0,0 0:17.57 chromium - 2379 root 20 0 115m 1796 928 S 0,0 0,0 0:02.16 rsyslogd - 2435 icecast2 20 0 148m 4440 2780 S 0,0 0,1 0:56.15 icecast2 - 2488 root 20 0 4112 644 500 S 0,0 0,0 0:00.66 acpid - 2513 daemon 20 0 16668 156 0 S 0,0 0,0 0:00.00 atd - 2536 proxy 20 0 6884 344 196 S 0,0 0,0 0:00.00 polipo - 2573 messageb 20 0 31488 2548 884 S 0,0 0,0 0:00.79 dbus-daemon - 2626 bind 20 0 111m 15m 2276 S 0,0 0,2 0:00.46 named - 2694 root 20 0 82308 3112 2520 S 0,0 0,0 0:00.03 gdm3 - 2729 root 20 0 99,3m 4652 3608 S 0,0 0,1 0:00.02 gdm-simple-slav - 2731 root 20 0 178m 27m 9908 S 0,0 0,3 40:30.80 Xorg - 2738 root 20 0 282m 14m 6576 S 0,0 0,2 0:02.98 apache2 - 2763 root 20 0 0 0 0 S 0,0 0,0 0:00.92 flush-254:4 - 2779 root 20 0 21000 1164 904 S 0,0 0,0 0:00.00 bluetoothd - 2784 avahi 20 0 34236 1876 1460 S 0,0 0,0 0:00.15 avahi-daemon - 2786 avahi 20 0 34032 440 184 S 0,0 0,0 0:00.00 avahi-daemon - 2792 root 10 -10 0 0 0 S 0,0 0,0 0:00.00 krfcommd - 2829 bitlbee 20 0 45216 1136 712 S 0,0 0,0 0:00.00 bitlbee - 2973 root 20 0 136m 3572 2892 S 0,0 0,0 0:00.37 accounts-daemon - 2974 clamav 20 0 45432 2172 1260 S 0,0 0,0 0:26.77 freshclam - 2997 root 20 0 141m 4552 3072 S 0,0 0,1 0:00.21 polkitd - 3021 root 20 0 18876 984 740 S 0,0 0,0 0:00.48 cron - 3062 root 20 0 75948 3436 2304 S 0,0 0,0 0:00.03 cupsd - 3064 colord 20 0 152m 8672 3344 S 0,0 0,1 0:00.10 colord - 3069 root 20 0 126m 4116 2964 S 0,0 0,1 0:00.16 console-kit-dae - 3071 colord 20 0 300m 12m 7932 S 0,0 0,2 0:01.23 colord-sane - 3171 nobody 10 -10 44328 1672 1048 S 0,0 0,0 0:00.88 gpsd - 3178 root 20 0 9204 3508 380 S 0,0 0,0 0:39.47 haveged - 3192 ikiwiki- 20 0 13772 864 728 S 0,0 0,0 0:00.00 git-daemon - 3310 anarcat 20 0 91856 27m 2820 S 0,0 0,3 0:03.30 xterm - 3314 anarcat 20 0 24004 5452 1876 S 0,0 0,1 0:00.54 bash - 3336 root 20 0 152m 4172 3300 S 0,0 0,1 0:00.07 upowerd - 3437 root 20 0 0 0 0 S 0,0 0,0 0:00.00 scsi_eh_6 - 3438 root 20 0 0 0 0 S 0,0 0,0 6:52.70 usb-storage - 3470 anarcat 20 0 61648 2516 1912 S 0,0 0,0 0:00.01 gvfs-gphoto2-vo - 3474 anarcat 20 0 78024 2564 2048 S 0,0 0,0 0:02.04 gvfs-afc-volume - 3530 root 20 0 52400 10m 2064 S 0,0 0,1 0:03.34 munin-node - 3599 rtkit 21 1 39632 1344 1112 S 0,0 0,0 0:00.30 rtkit-daemon - 3721 root 20 0 4176 700 560 S 0,0 0,0 0:00.01 mysqld_safe - 3899 anarcat 20 0 85216 21m 2872 S 0,0 0,3 0:00.76 xterm - 3903 anarcat 20 0 23216 4688 1804 S 0,0 0,1 0:00.58 bash - 4108 mysql 30 10 434m 137m 4396 S 0,0 1,7 1:53.14 mysqld - 4109 root 20 0 4084 628 524 S 0,0 0,0 0:00.00 logger - 4209 anarcat 20 0 129m 23m 18m S 0,0 0,3 1:06.16 git-annex - 4226 root 20 0 183m 4888 3504 S 0,0 0,1 0:00.08 gdm-session-wor - 4240 anarcat 20 0 21360 2572 2188 S 0,0 0,0 0:00.34 git - 4431 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kauditd - 4447 anarcat 20 0 4176 664 548 S 0,0 0,0 0:00.03 sh - 4530 ntp 20 0 41052 2284 1644 S 0,0 0,0 0:02.71 ntpd - 4593 postgres 20 0 102m 9008 7680 S 0,0 0,1 0:01.04 postgres - 4667 anarcat 20 0 12384 1072 704 S 0,0 0,0 0:00.11 ssh-agent - 4668 anarcat 20 0 20164 372 156 S 0,0 0,0 0:01.03 gpg-agent - 4671 anarcat 20 0 24184 552 304 S 0,0 0,0 0:00.00 dbus-launch - 4672 anarcat 20 0 30668 1592 736 S 0,0 0,0 0:01.10 dbus-daemon - 4704 anarcat 20 0 49456 2740 2216 S 0,0 0,0 0:00.13 xfconfd - 4711 anarcat 20 0 63740 3124 2312 S 0,0 0,0 0:02.61 xscreensaver - 4713 anarcat 20 0 156m 8232 5856 S 0,0 0,1 0:06.14 xfce4-session - 4714 postgres 20 0 102m 1952 616 S 0,0 0,0 0:06.79 postgres - 4715 postgres 20 0 102m 1704 376 S 0,0 0,0 0:04.95 postgres - 4716 postgres 20 0 102m 3068 1128 S 0,0 0,0 0:01.32 postgres - 4717 postgres 20 0 72884 1800 416 S 0,0 0,0 0:00.99 postgres - 4735 postgrey 20 0 66452 14m 3136 S 0,0 0,2 0:00.40 /usr/sbin/postg - 4753 anarcat 20 0 124m 4060 2916 S 0,0 0,0 0:00.02 xfsettingsd - 4754 anarcat 20 0 166m 6496 5204 S 0,0 0,1 0:00.07 Thunar - 4778 anarcat 20 0 63364 2564 2096 S 0,0 0,0 0:00.03 gvfsd - 4783 anarcat 20 0 305m 14m 9568 S 0,0 0,2 0:52.46 xfce4-panel - 4790 anarcat 20 0 156m 7968 6232 S 0,0 0,1 0:00.23 xfdesktop - 4791 root 20 0 21516 804 496 S 0,0 0,0 0:00.00 dovecot - 4837 anarcat 20 0 148m 4296 2768 S 0,0 0,1 0:11.87 xfce4-settings- - 4856 anarcat 20 0 26620 1248 988 S 0,0 0,0 1:19.60 xcompmgr - 4873 anarcat 20 0 115m 8004 3872 S 0,0 0,1 0:07.42 awesome - 4887 anarcat 20 0 267m 12m 8664 S 0,0 0,2 0:02.51 update-notifier - 4899 anarcat 20 0 183m 5868 4708 S 0,0 0,1 0:00.18 polkit-gnome-au - 4905 anarcat 20 0 56320 4180 2040 S 0,0 0,1 0:00.10 gconfd-2 - 4908 anarcat 9 -11 300m 6912 4184 S 0,0 0,1 0:08.00 pulseaudio - 4916 root 20 0 126m 4208 3056 S 0,0 0,1 0:02.46 udisks-daemon - 4917 root 20 0 47408 776 428 S 0,0 0,0 0:06.61 udisks-daemon - 4921 anarcat 20 0 113m 3200 2448 S 0,0 0,0 0:00.00 gconf-helper - 4972 anarcat 20 0 145m 7432 5880 S 0,0 0,1 0:00.09 panel-16-systra - 4974 anarcat 20 0 148m 9328 7348 S 0,0 0,1 2:40.37 xfce4-weather-p - 4975 anarcat 20 0 174m 11m 8312 S 0,0 0,1 0:42.26 xfce4-xkb-plugi - 4978 mpd 20 0 503m 29m 2920 S 0,0 0,4 1:24.97 mpd - 5029 mpd 20 0 256m 6412 4008 S 0,0 0,1 0:11.74 pulseaudio - 5030 dovecot 20 0 13044 768 592 S 0,0 0,0 0:00.00 anvil - 5031 root 20 0 13172 944 628 S 0,0 0,0 0:00.00 log - 5034 root 20 0 23156 2536 768 S 0,0 0,0 0:00.00 config - 5040 mpd 20 0 113m 3192 2448 S 0,0 0,0 0:00.00 gconf-helper - 5234 root 20 0 0 0 0 S 0,0 0,0 0:01.19 kworker/0:1 - 5745 root 20 0 37788 2472 1912 S 0,0 0,0 0:00.68 master - 5756 postfix 20 0 44368 2700 2100 S 0,0 0,0 0:00.27 qmgr - 5807 root 20 0 49848 1216 608 S 0,0 0,0 0:00.05 sshd - 5908 debian-t 20 0 56008 21m 2988 S 0,0 0,3 0:21.87 tor - 5928 debian-t 30 10 190m 31m 2560 S 0,0 0,4 7:35.56 transmission-da - 5948 anarcat 20 0 71776 8204 2860 S 0,0 0,1 0:05.76 xterm - 5954 anarcat 20 0 22956 4540 1772 S 0,0 0,1 0:00.10 bash - 6019 spampd 20 0 147m 62m 1844 S 0,0 0,8 0:00.55 spampd - 6049 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 iprt - 6085 root 20 0 3948 84 0 S 0,0 0,0 0:00.00 minissdpd - 6095 root 20 0 17404 908 744 S 0,0 0,0 0:00.00 getty - 6096 root 20 0 17404 908 744 S 0,0 0,0 0:00.00 getty - 6097 root 20 0 17404 904 744 S 0,0 0,0 0:00.00 getty - 6098 root 20 0 17404 896 744 S 0,0 0,0 0:00.00 getty - 6099 root 20 0 17404 900 744 S 0,0 0,0 0:00.00 getty - 6100 root 20 0 17404 904 744 S 0,0 0,0 0:00.00 getty - 6108 anarcat 20 0 24248 1040 816 S 0,0 0,0 0:00.08 screen - 6109 anarcat 20 0 25864 2640 796 S 0,0 0,0 0:05.37 screen - 6110 anarcat 20 0 22868 4220 1624 S 0,0 0,1 0:00.06 bash - 6153 root 20 0 0 0 0 S 0,0 0,0 0:00.00 flush-254:8 - 6174 anarcat 20 0 22872 4224 1624 S 0,0 0,1 0:00.07 bash - 6238 anarcat 20 0 103m 12m 5232 S 0,0 0,2 0:20.80 irssi - 6252 anarcat 20 0 212m 40m 13m S 0,0 0,5 1:09.74 emacs23 - 6534 anarcat 20 0 22876 4400 1716 S 0,0 0,1 0:00.07 bash - 6598 anarcat 20 0 302m 163m 3864 S 0,0 2,0 17:19.63 offlineimap - 6616 anarcat 20 0 22408 2648 2228 S 0,0 0,0 0:05.04 git - 6662 root 20 0 0 0 0 S 0,0 0,0 0:01.25 kworker/1:1 - 6666 root 20 0 0 0 0 S 0,0 0,0 0:00.00 flush-254:2 - 6897 anarcat 20 0 1011m 159m 47m S 0,0 2,0 4:54.69 chromium - 6902 postfix 20 0 46744 3396 2400 S 0,0 0,0 0:00.09 tlsmgr - 6903 anarcat 20 0 283m 7952 2788 S 0,0 0,1 0:05.03 chromium - 6904 anarcat 20 0 6240 356 272 S 0,0 0,0 0:00.00 chrome-sandbox - 6905 anarcat 20 0 304m 17m 12m S 0,0 0,2 0:00.02 chromium - 6908 anarcat 20 0 320m 5800 764 S 0,0 0,1 0:00.16 chromium - 6950 anarcat 20 0 955m 31m 16m S 0,0 0,4 0:01.68 chromium - 6955 anarcat 20 0 953m 33m 17m S 0,0 0,4 0:01.25 chromium - 6960 anarcat 20 0 959m 36m 15m S 0,0 0,5 0:08.32 chromium - 6965 anarcat 20 0 957m 34m 14m S 0,0 0,4 0:10.25 chromium - 6970 anarcat 20 0 1029m 114m 17m S 0,0 1,4 0:46.99 chromium - 6975 anarcat 20 0 953m 26m 14m S 0,0 0,3 0:00.53 chromium - 6980 anarcat 20 0 959m 35m 16m S 0,0 0,4 0:14.68 chromium - 6985 anarcat 20 0 963m 45m 17m S 0,0 0,6 0:22.59 chromium - 6990 anarcat 20 0 952m 25m 13m S 0,0 0,3 0:00.70 chromium - 6995 anarcat 20 0 960m 36m 18m S 0,0 0,5 0:27.21 chromium - 7040 anarcat 20 0 979m 69m 22m S 0,0 0,9 0:05.41 chromium - 7055 anarcat 20 0 966m 51m 20m S 0,0 0,6 0:04.88 chromium - 7063 anarcat 20 0 967m 42m 18m S 0,0 0,5 0:04.46 chromium - 7072 anarcat 20 0 967m 49m 19m S 0,0 0,6 0:05.17 chromium - 7078 anarcat 20 0 971m 53m 19m S 0,0 0,7 0:05.68 chromium - 7087 anarcat 20 0 963m 51m 19m S 0,0 0,7 0:04.75 chromium - 7096 anarcat 20 0 961m 48m 18m S 0,0 0,6 0:04.75 chromium - 7107 anarcat 20 0 161m 4440 3252 S 0,0 0,1 0:02.90 gvfs-gdu-volume - 7127 anarcat 20 0 967m 55m 22m S 0,0 0,7 1:07.92 chromium - 7183 anarcat 20 0 912m 55m 20m S 0,0 0,7 0:04.97 chromium - 7213 anarcat 20 0 964m 47m 19m S 0,0 0,6 0:04.69 chromium - 7235 anarcat 20 0 965m 65m 21m S 0,0 0,8 0:05.26 chromium - 7258 anarcat 20 0 961m 57m 20m S 0,0 0,7 0:05.39 chromium - 7285 anarcat 20 0 18652 2484 1000 S 0,0 0,0 0:01.25 git - 7434 anarcat 39 19 18124 1960 964 S 0,0 0,0 0:00.29 git - 7445 www-data 20 0 141m 24m 5620 S 0,0 0,3 0:00.71 munin-cgi-graph - 7452 anarcat 20 0 980m 63m 22m S 0,0 0,8 0:02.50 chromium - 7492 anarcat 20 0 978m 64m 21m S 0,0 0,8 0:03.74 chromium - 7498 anarcat 20 0 978m 61m 21m S 0,0 0,8 0:01.42 chromium - 7518 anarcat 20 0 984m 63m 22m S 0,0 0,8 0:04.38 chromium - 7532 anarcat 20 0 973m 56m 21m S 0,0 0,7 0:02.28 chromium - 7813 root 20 0 0 0 0 S 0,0 0,0 0:01.22 kworker/0:2 - 7899 root 20 0 0 0 0 S 0,0 0,0 0:00.96 kworker/1:0 - 8058 anarcat 20 0 24488 1460 1104 S 0,0 0,0 0:28.34 git - 8107 anarcat 20 0 17412 1384 1100 S 0,0 0,0 0:00.00 git - 8130 anarcat 20 0 23792 7572 1004 S 0,0 0,1 0:41.63 git - 8236 anarcat 39 19 21152 4940 964 S 0,0 0,1 0:00.71 git - 8405 anarcat 20 0 17368 1364 1108 S 0,0 0,0 0:00.54 git - 8407 anarcat 20 0 17464 1336 964 S 0,0 0,0 0:00.03 git - 8610 anarcat 20 0 78228 14m 2860 S 0,0 0,2 0:00.37 xterm - 8614 anarcat 20 0 23084 4548 1796 S 0,0 0,1 0:00.28 bash - 8689 anarcat 20 0 72992 9224 2860 S 0,0 0,1 0:00.38 xterm - 8693 anarcat 20 0 22876 4380 1696 S 0,0 0,1 0:00.07 bash - 8735 root 20 0 99,3m 4616 3576 S 0,0 0,1 0:00.02 gdm-simple-slav - 8736 root 20 0 142m 15m 6664 S 0,0 0,2 0:00.56 Xorg - 8755 Debian-g 20 0 30196 1184 736 S 0,0 0,0 0:00.01 dbus-daemon - 8756 root 20 0 119m 4548 3432 S 0,0 0,1 0:00.08 gdm-session-wor - 8757 root 20 0 55872 2116 1572 S 0,0 0,0 0:00.00 sudo - 8759 aegir 20 0 20640 2248 1660 S 0,0 0,0 0:00.07 bash - 8769 Debian-g 20 0 266m 10m 7720 S 0,0 0,1 0:00.07 gnome-session - 8773 Debian-g 20 0 502m 24m 10m S 0,0 0,3 0:00.85 gnome-settings- - 8780 Debian-g 20 0 51980 2236 1836 S 0,0 0,0 0:00.00 gvfsd - 8784 Debian-g 9 -11 237m 6044 3644 S 0,0 0,1 0:00.07 pulseaudio - 8785 Debian-g 20 0 113m 3196 2448 S 0,0 0,0 0:00.00 gconf-helper - 8787 Debian-g 20 0 52956 3756 1932 S 0,0 0,0 0:00.06 gconfd-2 - 8790 Debian-g 20 0 279m 9124 6632 S 0,0 0,1 0:00.12 metacity - 8795 Debian-g 20 0 171m 9328 7056 S 0,0 0,1 0:00.04 polkit-gnome-au - 8796 Debian-g 20 0 362m 16m 11m S 0,0 0,2 0:00.68 gdm-simple-gree - 8812 root 20 0 72360 3916 2948 S 0,0 0,0 0:00.08 gdm-session-wor - 9129 root 20 0 0 0 0 S 0,0 0,0 0:00.74 kworker/0:0 - 9311 www-data 20 0 288m 44m 33m S 0,0 0,6 0:07.55 apache2 -10405 www-data 20 0 287m 42m 32m S 0,0 0,5 0:06.75 apache2 -10406 www-data 20 0 287m 44m 34m S 0,0 0,6 0:07.02 apache2 -10409 www-data 20 0 287m 41m 31m S 0,0 0,5 0:06.51 apache2 -10412 www-data 20 0 287m 42m 32m S 0,0 0,5 0:06.82 apache2 -10413 www-data 20 0 291m 40m 27m S 0,0 0,5 0:06.52 apache2 -10415 www-data 20 0 287m 39m 29m S 0,0 0,5 0:06.67 apache2 -10416 www-data 20 0 288m 42m 31m S 0,0 0,5 0:06.28 apache2 -10417 www-data 20 0 290m 50m 38m S 0,0 0,6 0:07.43 apache2 -10878 root 20 0 0 0 0 S 0,0 0,0 0:00.02 kworker/0:3 -11037 anarcat 20 0 4180 584 488 S 0,0 0,0 0:00.00 sh -11038 anarcat 20 0 62760 4964 3244 S 0,0 0,1 0:00.48 notmuch -11040 anarcat 20 0 4180 652 544 S 0,0 0,0 0:00.00 post-new -11133 root 20 0 52576 1468 1052 S 0,0 0,0 0:00.00 cron -11134 root 20 0 52576 1464 1052 S 0,0 0,0 0:00.00 cron -11135 root 20 0 52576 1468 1052 S 0,0 0,0 0:00.00 cron -11138 aegir 20 0 4176 576 484 S 0,0 0,0 0:00.00 sh -11139 root 20 0 4176 580 484 S 0,0 0,0 0:00.00 sh -11141 munin 20 0 4176 576 480 S 0,0 0,0 0:00.00 sh -11143 root 20 0 4240 324 248 S 0,0 0,0 0:00.00 xargs -11145 munin 20 0 4176 576 484 S 0,0 0,0 0:00.00 munin-cron -11166 anarcat 20 0 61364 2988 2468 R 0,0 0,0 0:00.00 notmuch -11167 anarcat 20 0 61364 752 212 R 0,0 0,0 0:00.00 notmuch -12004 www-data 20 0 292m 52m 37m S 0,0 0,7 0:09.05 apache2 -12172 anarcat 20 0 4092 580 480 S 0,0 0,0 0:00.00 emacsclient -12465 spampd 20 0 149m 65m 2840 S 0,0 0,8 0:01.41 spampd -12468 spampd 20 0 150m 67m 2840 S 0,0 0,8 0:01.07 spampd -12895 anarcat 20 0 970m 51m 21m S 0,0 0,6 0:01.80 chromium -13761 anarcat 20 0 0 0 0 Z 0,0 0,0 0:00.00 git -16056 root 20 0 21800 1464 452 S 0,0 0,0 0:00.00 udevd -16057 root 20 0 21800 1340 332 S 0,0 0,0 0:00.00 udevd -16655 www-data 20 0 147m 8232 700 S 0,0 0,1 0:00.04 apache2 -17006 anarcat 20 0 526m 29m 17m S 0,0 0,4 0:19.95 gmpc -17959 www-data 20 0 70828 24m 2172 S 0,0 0,3 1:22.37 munin-cgi-html -18082 anarcat 20 0 71776 8164 2820 S 0,0 0,1 0:00.12 xterm -18086 anarcat 20 0 23048 4664 1804 S 0,0 0,1 0:00.18 bash -18571 anarcat 20 0 258m 11m 8296 S 0,0 0,1 0:00.11 xfrun4 -19692 spampd 20 0 148m 64m 2832 S 0,0 0,8 0:00.63 spampd -25574 anarcat 20 0 952m 31m 15m S 0,0 0,4 0:00.71 chromium -25590 anarcat 20 0 0 0 0 Z 0,0 0,0 0:41.75 chromium -"""]] - -And here's the process tree: - -[[!format sh """ -$ ps -O start xf | grep git-annex - 8610 13:03:21 S ? 00:00:00 xterm -class UXTerm -title uxterm -u8 - 8614 13:03:21 S pts/4 00:00:00 \_ bash -12172 13:13:15 S pts/4 00:00:00 \_ emacsclient --alternate-editor=vim -c install.hostmaster.inc - 8099 13:00:20 S ? 07:40:31 /usr/local/bin/git-annex assistant --startdelay=5s - 8107 13:00:20 S ? 00:00:00 \_ git --git-dir=/srv/books/.git --work-tree=/srv/books -c core.bare=false cat-file --batch - 8405 13:00:28 S ? 00:00:00 \_ git --git-dir=/srv/books/.git --work-tree=/srv/books -c core.bare=false cat-file --batch - 8407 13:00:28 S ? 00:00:00 \_ git --git-dir=/srv/books/.git --work-tree=/srv/books -c core.bare=false check-ignore -z --stdin --verbose --non-matching - 8045 13:00:11 S ? 07:35:36 /usr/local/bin/git-annex assistant --startdelay=5s - 8058 13:00:11 S ? 00:00:28 \_ git --git-dir=/srv/mp3/.git --work-tree=/srv/mp3 cat-file --batch - 8130 13:00:21 S ? 00:00:41 \_ git --git-dir=/srv/mp3/.git --work-tree=/srv/mp3 check-ignore -z --stdin --verbose --non-matching - 8236 13:00:24 S ? 00:00:00 \_ git --git-dir=/srv/mp3/.git --work-tree=/srv/mp3 check-attr -z --stdin annex.backend annex.numcopies -- - 7107 12:58:40 S ? 00:00:02 /usr/lib/gvfs/gvfs-gdu-volume-monitor - 6525 12:57:25 S ? 07:29:13 /usr/local/bin/git-annex assistant --startdelay=5s - 6616 12:57:34 S ? 00:00:05 \_ git --git-dir=/srv/video/.git --work-tree=/srv/video cat-file --batch - 7285 12:58:45 S ? 00:00:01 \_ git --git-dir=/srv/video/.git --work-tree=/srv/video check-ignore -z --stdin --verbose --non-matching - 7434 12:58:51 S ? 00:00:00 \_ git --git-dir=/srv/video/.git --work-tree=/srv/video check-attr -z --stdin annex.backend annex.numcopies -- - 4209 19:30:17 S ? 00:01:06 \_ /usr/local/bin/git-annex transferkeys --readfd 25 --writefd 24 - 4240 19:30:17 S ? 00:00:00 \_ git --git-dir=/srv/video/.git --work-tree=/srv/video cat-file --batch -13761 23:56:38 Z ? 00:00:00 \_ [git] <defunct> - 6252 12:56:59 S ? 00:01:09 /usr/bin/emacs23 -"""]] - -#### This bug is fixed - -> [[fixed|done]]. This was a Cronner bug, triggered when you had a -> scheduled fsck job that runs monthly at any time, and the last time it ran was on a day of a -> month > 12. Workaround: Disable scheduled fsck jobs, or change them to -> run on a specific day of the month. Or upgrade. --[[Joey]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_10_4a9f149048e387e0a8b4ebb0838decfd._comment b/doc/bugs/assistant_eats_all_CPU/comment_10_4a9f149048e387e0a8b4ebb0838decfd._comment deleted file mode 100644 index 5b1675173..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_10_4a9f149048e387e0a8b4ebb0838decfd._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 10" - date="2014-01-15T21:14:07Z" - content=""" -I was unable to reproduce the problem with a Debian stable VM running in virtualbox. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_11_98be30621a8a435ed54662f7ea9654b4._comment b/doc/bugs/assistant_eats_all_CPU/comment_11_98be30621a8a435ed54662f7ea9654b4._comment deleted file mode 100644 index 2824a5905..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_11_98be30621a8a435ed54662f7ea9654b4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 11" - date="2014-01-15T21:30:36Z" - content=""" -In case the problem is fixed in a newer ghc than the 7.4.1 used to build the debian backport and the standalone builds, I have made a standalone build with 7.6.3, which is temporarily here: <http://tmp.kitenet.net/git-annex-standalone-i386.tar.gz> ff3e8a3c35301c8a625747f98435fe427be17f47345540f537ff47f6fc97bdb6 - -(That's a i386 build, which will also run on amd64. That could also be a difference as AFAICS it's only been reported happening with amd64 builds (although I was not able to reproduce the problem on amd64)) -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_12_a7d7141b81e73a989eb5c1233bcd1478._comment b/doc/bugs/assistant_eats_all_CPU/comment_12_a7d7141b81e73a989eb5c1233bcd1478._comment deleted file mode 100644 index cab94beef..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_12_a7d7141b81e73a989eb5c1233bcd1478._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 12" - date="2014-01-16T17:04:42Z" - content=""" -Again, I can reproduce with the standalone build, so there's clearly something going on here... Oddly enough, git-annex doesn't appear in top, but I see: - - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND - 21064 anarcat 20 0 111m 23m 14m S 83,0 0,3 9:59.91 ld-linux.so.2 - 20829 anarcat 20 0 133m 38m 15m S 76,4 0,5 8:54.88 ld-linux.so.2 - 21133 anarcat 20 0 130m 32m 14m S 14,9 0,4 5:00.55 ld-linux.so.2 - -ld-linux? -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_13_60f95e6e5d52f03727bd41f8419c9384._comment b/doc/bugs/assistant_eats_all_CPU/comment_13_60f95e6e5d52f03727bd41f8419c9384._comment deleted file mode 100644 index 0fe6cdb94..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_13_60f95e6e5d52f03727bd41f8419c9384._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 13" - date="2014-01-16T17:07:05Z" - content=""" -It's not clear from your comment if you tried my ghc 7.6.3 build. - -The hacks used to make the standalone build run everywhere cause ugly process names. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_14_a6d039ba95f92d9d0c3a343165ba7991._comment b/doc/bugs/assistant_eats_all_CPU/comment_14_a6d039ba95f92d9d0c3a343165ba7991._comment deleted file mode 100644 index f2fa7634c..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_14_a6d039ba95f92d9d0c3a343165ba7991._comment +++ /dev/null @@ -1,36 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 14" - date="2014-01-16T17:43:33Z" - content=""" -Sorry yes, I tried the 7.6.3 build: - - http://tmp.kitenet.net/git-annex-standalone-i386.tar.gz ff3e8a3c35301c8a625747f98435fe427be17f47345540f537ff47f6fc97bdb6 - - $ ps x -o user,pid,start,time,vsz,c,comm | grep ld - anarcat 20818 11:27:32 00:00:00 6640 0 ld-linux.so.2 - anarcat 20829 11:27:32 00:30:23 216608 40 ld-linux.so.2 - anarcat 20845 11:27:33 00:00:00 13804 0 ld-linux.so.2 - anarcat 20873 11:27:33 00:00:22 13804 0 ld-linux.so.2 - anarcat 20934 11:27:45 00:00:40 12060 0 ld-linux.so.2 - anarcat 20954 11:27:46 00:00:00 9944 0 ld-linux.so.2 - anarcat 20955 11:27:48 00:00:00 9948 0 ld-linux.so.2 - anarcat 21064 11:28:09 00:49:42 114204 67 ld-linux.so.2 - anarcat 21073 11:28:09 00:00:00 6772 0 ld-linux.so.2 - anarcat 21099 11:28:12 00:00:00 6684 0 ld-linux.so.2 - anarcat 21101 11:28:12 00:00:00 6780 0 ld-linux.so.2 - anarcat 21133 11:28:20 00:45:39 128544 62 ld-linux.so.2 - anarcat 21146 11:28:20 00:00:03 11172 0 ld-linux.so.2 - anarcat 21200 11:28:26 00:00:01 7704 0 ld-linux.so.2 - anarcat 21204 11:28:28 00:00:00 7308 0 ld-linux.so.2 - $ /home/anarcat/Downloads/git-annex.linux/git-annex version - git-annex version: 5.20140115-g7a86704 - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - local repository version: unknown - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_15_b7f9a8e214eefc3a6976065782157e81._comment b/doc/bugs/assistant_eats_all_CPU/comment_15_b7f9a8e214eefc3a6976065782157e81._comment deleted file mode 100644 index 78f9104fd..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_15_b7f9a8e214eefc3a6976065782157e81._comment +++ /dev/null @@ -1,28 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="188.193.209.7" - subject="Probably confirming this bug" - date="2014-01-16T19:59:56Z" - content=""" -I am trying around with the assistant and webapp for a few months now. -I have rather large git annex repos and even switched from direct ones to indirect repos to increase performance. - -The issue I'm seeing is that when using the assistant or webapp it does the initial startupscan, but only consumes 99-100% of one of my cores and doesn't use significant io. It's stuck in this state for hours (12+) or even days. The only thing standing out in the logs is that it puts a lot of files into the queue. (I suspected a not yet synced backup remote to be the issue) I stopped syncing with it, but that didn't speed up the startupScan at all. - -[2014-01-16 19:34:26 CET] TransferScanner: queued Upload NoUUID db/2012-07/1406469990005618750.meta Nothing : expensive scan found missing object -[2014-01-16 19:34:27 CET] TransferScanner: queued Upload NoUUID db/2012-07/1406471293790598760.eml.gz Nothing : expensive scan found missing object - - -Some additional information: -Total file count: ~100000 -Total size: ~500mb -SSD + i7 Quadcore running Ubuntu 13.10 -Latest build from 2014-01-16 as standalone built. - -Running git annex add && git annex sync from the cli returns within seconds 0.1s (no new files) and 10s (500-1000 new files). -Not understanding the main difference git annex add and git annex assistant (startupScan function) really have. - -Thanks for your help. - - -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_16_16382708d1683a7a9eaaf953f3cdb735._comment b/doc/bugs/assistant_eats_all_CPU/comment_16_16382708d1683a7a9eaaf953f3cdb735._comment deleted file mode 100644 index 66c2b2724..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_16_16382708d1683a7a9eaaf953f3cdb735._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 16" - date="2014-01-17T19:07:10Z" - content=""" -This bug is about cpu usage when git-annex assistant should be sitting idle, not about the statup scan. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_17_bfa64822ad9b48fbd4d06c3e3a185b59._comment b/doc/bugs/assistant_eats_all_CPU/comment_17_bfa64822ad9b48fbd4d06c3e3a185b59._comment deleted file mode 100644 index d44cb9ac9..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_17_bfa64822ad9b48fbd4d06c3e3a185b59._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 17" - date="2014-01-30T04:57:24Z" - content=""" -@joeyh - any other ideas? I still can't really use the assistant... -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_18_970899faca972af6795ae0d3be1ce444._comment b/doc/bugs/assistant_eats_all_CPU/comment_18_970899faca972af6795ae0d3be1ce444._comment deleted file mode 100644 index 6e9378154..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_18_970899faca972af6795ae0d3be1ce444._comment +++ /dev/null @@ -1,42 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm3ayIrWKe5SqLYomXiCL-l2CDpREvA-IE" - nickname="myownlittl" - subject="Seconding this Bug." - date="2014-02-19T02:04:34Z" - content=""" -Hi Joey, I have also experienced this bug. I put my \"~/my\" folder under gitannex's management, and I've since had gitannex's assistant consume a CPU (100% of one core) when starting my computer for 1 - 12 hours (at which point I get impatient and kill annex). If stack traces would help, I can email you those. Unfortunately, my \"my\" folder includes every important document I've created, coded, or needed, in the last six years. It has just under 30,000 files, and probably isn't using gitannex the way it's intended to be used. You can see the distribution of files and file sizes in the tables below. - -If gitannex isn't designed for this sort of use case, can you recommend any free software tools that might be able to help opportunistically keep files in sync at this sort of scale, like GA? - -Thanks for your time, - -Nick - ----- - -[[!table data=\"\"\" -Size<= | Bytes | Count | -0B | 0 | 1108 | -1B | 1 | 264 | -16B | 16 | 179 | -256B | 256 | 3414 | -4K | 4096 | 12771 | -65K | 65536 | 7402 | -1M | 1048576 | 2975 | -16M | 16777216 | 703 | -256M | 268435456 | 126 | -4G | 4294967296 | 5 | -\"\"\"]] - - | Size<= | Bytes | Count | - | 0B | 0 | 1108 | - | 1B | 1 | 264 | - | 16B | 16 | 179 | - | 256B | 256 | 3414 | - | 4K | 4096 | 12771 | - | 65K | 65536 | 7402 | - | 1M | 1048576 | 2975 | - | 16M | 16777216 | 703 | - | 256M | 268435456 | 126 | - | 4G | 4294967296 | 5 | -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_19_2b8241800ae265260506ac9c73cca209._comment b/doc/bugs/assistant_eats_all_CPU/comment_19_2b8241800ae265260506ac9c73cca209._comment deleted file mode 100644 index 9c39baad2..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_19_2b8241800ae265260506ac9c73cca209._comment +++ /dev/null @@ -1,56 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawntVnR-Z5ghYInvsElbDeADPSuCsF18iTY" - nickname="Thomas" - subject="XMPP something to do with it?" - date="2014-03-02T13:48:22Z" - content=""" -High (between 30 and 100%) processor load in my case seems to be related to lots of these logfile entries: - - [2014-03-02 14:36:54 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 75 \"<elided>\") - [2014-03-02 14:36:54 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:54 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 76 \"<elided>\") - [2014-03-02 14:36:54 CET] XMPPClient: received: [\"Ignorable Presence from s6/941d024438f7cd11 Just (Element {elementName = Name {nameLocalName = \\"git-annex\\", nameNamespace = Just \\"git-annex\\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})\"] - [2014-03-02 14:36:54 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:54 CET] XMPPClient: received: [\"Pushing \\"s34\\" (CanPush (UUID \\"005cc6c3-a4de-44d5-847e-58b5bc4e4c26\\") [Ref \\"d39375b2da76a05c13a8fdc2197a58af0a9812fc\\",Ref \\"5c0108dcad557ab48bfe335e533f13f29777ca7b\\"])\"] - [2014-03-02 14:36:54 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 77 \"<elided>\") - [2014-03-02 14:36:54 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:54 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 78 \"<elided>\") - [2014-03-02 14:36:54 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:55 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 79 \"<elided>\") - [2014-03-02 14:36:55 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:55 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 80 \"<elided>\") - [2014-03-02 14:36:55 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:55 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 81 \"<elided>\") - [2014-03-02 14:36:55 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:55 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 82 \"<elided>\") - [2014-03-02 14:36:55 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:56 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 83 \"<elided>\") - [2014-03-02 14:36:56 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:56 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 84 \"<elided>\") - [2014-03-02 14:36:56 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:56 CET] XMPPClient: received: [\"Presence from s6/a303a6cfb26b8e08 Just (Element {elementName = Name {nameLocalName = \\"git-annex\\", nameNamespace = Just \\"git-annex\\", namePrefix = Nothing}, elementAttributes = [(Name {nameLocalName = \\"query\\", nameNamespace = Nothing, namePrefix = Nothing},[ContentText \\"\\"])], elementNodes = []})\",\"QueryPresence\"] - [2014-03-02 14:36:56 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 85 \"<elided>\") - [2014-03-02 14:36:56 CET] XMPPClient: received: [\"Pushing \\"s34\\" (CanPush (UUID \\"005cc6c3-a4de-44d5-847e-58b5bc4e4c26\\") [Ref \\"d39375b2da76a05c13a8fdc2197a58af0a9812fc\\",Ref \\"f43c777aed404e1e98dcbf9b6499f4d056b6662a\\"])\"] - [2014-03-02 14:36:56 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:56 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 86 \"<elided>\") - [2014-03-02 14:36:56 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:57 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 87 \"<elided>\") - [2014-03-02 14:36:57 CET] XMPPClient: received: [\"Ignorable Presence from s6/941d024438f7cd11 Just (Element {elementName = Name {nameLocalName = \\"git-annex\\", nameNamespace = Just \\"git-annex\\", namePrefix = Nothing}, elementAttributes = [], elementNodes = []})\"] - [2014-03-02 14:36:57 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:57 CET] XMPPClient: received: [\"Pushing \\"s34\\" (CanPush (UUID \\"005cc6c3-a4de-44d5-847e-58b5bc4e4c26\\") [Ref \\"d39375b2da76a05c13a8fdc2197a58af0a9812fc\\",Ref \\"f43c777aed404e1e98dcbf9b6499f4d056b6662a\\"])\"] - [2014-03-02 14:36:57 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 88 \"<elided>\") - [2014-03-02 14:36:57 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:57 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 89 \"<elided>\") - [2014-03-02 14:36:57 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - [2014-03-02 14:36:57 CET] XMPPClient: sending: Pushing \"s34\" (SendPackOutput 90 \"<elided>\") - [2014-03-02 14:36:57 CET] XMPPClient: to client: s6/a303a6cfb26b8e08 - -This is after everything is uploaded to a ssh server (in the cloud, used for transfer) and while another computer is downloading from there (?). - -git-annex version: 5.20140227 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -Debian testing using jabber.org for xmpp -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment b/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment deleted file mode 100644 index cd14d9084..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_1_847ff393fe3a0227d61440f6be899907._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 1" - date="2014-01-01T20:13:04Z" - content=""" -This strongly resembles ghc RTS bugs such as <http://bugs.debian.org/677096> (except that one got fixed, and affected the non-threaded RTS, while this is using the threaded RTS). - -The assistant and the webapp are the same process. The only difference is whether a web browser is talking to it. Unless the other bug is regarding the CPU used by the web browser, that other bug is a duplicate of this one. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_20_1d9020679d66e6b4742df067cb9da4f1._comment b/doc/bugs/assistant_eats_all_CPU/comment_20_1d9020679d66e6b4742df067cb9da4f1._comment deleted file mode 100644 index c228560f2..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_20_1d9020679d66e6b4742df067cb9da4f1._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 20" - date="2014-03-02T16:33:57Z" - content=""" -This is still a problem in Debian jessie and version `5.20140210` from the debian packages. - -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_21_8ce65a701604b9d13941844c62f62f23._comment b/doc/bugs/assistant_eats_all_CPU/comment_21_8ce65a701604b9d13941844c62f62f23._comment deleted file mode 100644 index 2e74010df..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_21_8ce65a701604b9d13941844c62f62f23._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="strace or it didn't happen" - date="2014-03-05T21:02:17Z" - content=""" -This bug is about a particular sequence of system calls. It is not about every possible way that git-annex can use CPU! If you think you have reproduced this bug, you need to include a strace demonstrating the problem, or you're just adding noise. - -@Thomas your log shows git-annex doing a git pull over XMPP. This will take CPU, as will any git pull. It is not related to this bug. - -@myownlittl the assistant has to scan your repository when it's started to find any files you have modified since the last time it was run. That is not related to this bug. However, I will probably be adding a config knob to disable the startup scan. - -@Oliver, you said you had seen this same bug on Ubuntu, but did not show a strace, so I don't know if you are really experiencing the same bug. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_22_0d8de9a8e4b8e2ef3b9c7d839fbcad0c._comment b/doc/bugs/assistant_eats_all_CPU/comment_22_0d8de9a8e4b8e2ef3b9c7d839fbcad0c._comment deleted file mode 100644 index ccaf726b7..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_22_0d8de9a8e4b8e2ef3b9c7d839fbcad0c._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 22" - date="2014-03-05T21:08:34Z" - content=""" -@anarcat, it seems to me that you need to find a minumal way to reproduce this. - -What architecture, what specfic model of CPU? - -Can you reproduce it by running the assistant in a new, empty git annex repository? If not, find the difference between that repository and the repository it happens in. If so, it would probably make sense to build git-annex from source with most features disabled to see if one of them causes it, and if not, try to get it down to a minimal test case suitable to being submitted as a GHC bug. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_23_48a4c8d9dcc6cec243c6072090f26b6d._comment b/doc/bugs/assistant_eats_all_CPU/comment_23_48a4c8d9dcc6cec243c6072090f26b6d._comment deleted file mode 100644 index b6d2dec76..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_23_48a4c8d9dcc6cec243c6072090f26b6d._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 23" - date="2014-04-11T16:32:47Z" - content=""" -<maxy> the clock_gettime(0x2 and clock_gettime(0x3 are consistent with getCurrentTime and getTimeZone of nextTime - -So, that strongly points to the Cronner thread, and I doubt this is specific to stable at all. - -Please run git-annex vicfg, and paste all the \"schedule\" lines, from a repository that has the problem. That should allow me to reproduce and fix this bug. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_2_0d577d5ca22df14dadf21d4a1a5f9474._comment b/doc/bugs/assistant_eats_all_CPU/comment_2_0d577d5ca22df14dadf21d4a1a5f9474._comment deleted file mode 100644 index a11d9add8..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_2_0d577d5ca22df14dadf21d4a1a5f9474._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 2" - date="2014-01-01T20:29:59Z" - content=""" -Humm... it doesn't look like #677096 is fixed in wheezy, are you sure this isn't the problem I am seeing? - -I am considering upgrading this machine to jessie soon, would that help diagnosing the problem? - -Regarding the other bug, if you are refering to [[webapp takes 100% of the cpu]], i do believe it's a different issue because the CPU usage is lower in the assistant when it's *not* transfering lots of small files. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_3_498eee32426dfbaf9bda59a7c0f6fcc9._comment b/doc/bugs/assistant_eats_all_CPU/comment_3_498eee32426dfbaf9bda59a7c0f6fcc9._comment deleted file mode 100644 index 47964aee3..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_3_498eee32426dfbaf9bda59a7c0f6fcc9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 3" - date="2014-01-01T20:45:19Z" - content=""" -Note that I have installed the backports and autobuilds on systems and run the assistant without seeing this problem, so it may be particular to the system's configuration in some way. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_4_ce85b4715a2f7315b68bed62e26d4f0e._comment b/doc/bugs/assistant_eats_all_CPU/comment_4_ce85b4715a2f7315b68bed62e26d4f0e._comment deleted file mode 100644 index 3d4392c90..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_4_ce85b4715a2f7315b68bed62e26d4f0e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 4" - date="2014-01-02T19:04:26Z" - content=""" -I've tested with the current release's Linux standalone amd64 build, and once the webapp shows no activity, strace shows it sitting there waiting for a futex, which causes no cpu load at all. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_5_8cf846b9b7bd1c70a006163a9cc2d9de._comment b/doc/bugs/assistant_eats_all_CPU/comment_5_8cf846b9b7bd1c70a006163a9cc2d9de._comment deleted file mode 100644 index a688bcdf3..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_5_8cf846b9b7bd1c70a006163a9cc2d9de._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 5" - date="2014-01-02T22:21:34Z" - content=""" -I rebuilt using the current git head, i was expecting 20131230 but I got 5.20140102-gd93f946. The problem is still there: - -[[!format txt \"\"\" -anarcat@marcos:mp3$ top -b -n 1 | head -top - 17:18:23 up 2 days, 4:24, 9 users, load average: 4,01, 3,91, 3,80 -Tasks: 295 total, 1 running, 294 sleeping, 0 stopped, 0 zombie -%Cpu(s): 44,0 us, 4,9 sy, 0,6 ni, 49,7 id, 0,6 wa, 0,0 hi, 0,3 si, 0,0 st -KiB Mem: 8162960 total, 6778608 used, 1384352 free, 397144 buffers -KiB Swap: 4022268 total, 45752 used, 3976516 free, 2750720 cached - - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND -28910 anarcat 20 0 158m 37m 21m S 90,2 0,5 42:49.44 git-annex -29550 anarcat 20 0 173m 44m 21m S 72,2 0,6 36:49.59 git-annex -29673 anarcat 20 0 304m 175m 21m S 12,0 2,2 34:09.70 git-annex -\"\"\"]] - -This doesn't seem to be proportional to the repository size or anything. pid 28910 is /srv/books, a moderately small repository. 29550 is my video repository and 29673 is my music. - -I suspect this is because I build git-annex myself. I am guessing that the ghc version I am using doesn't build with the proper thread patches and so on. I will try the backport to see if it fixes the issue. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_6_a7c9f3262b6eca6258ba53324d321a7a._comment b/doc/bugs/assistant_eats_all_CPU/comment_6_a7c9f3262b6eca6258ba53324d321a7a._comment deleted file mode 100644 index e1f750170..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_6_a7c9f3262b6eca6258ba53324d321a7a._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 6" - date="2014-01-02T23:30:38Z" - content=""" -bad news: i can reproduce this with the backport: - -Version: 4.20131106~bpo70+1 -Build flags: Assistant Webapp Pairing Testsuite S3 Inotify DBus Feeds Quvi TDFA - -oddly enough, one of the repository saw some files be committed by the assistant during the startup scan that were not found by the 5.x version I was running earlier. - -but processor usage is still maxed out. - -i would be happy to provide you a shell here if you send me a OpenPGP-signed SSH public-key (or if you use monkeysphere). -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_7_340414e9c19903b16ab617d075fbb94e._comment b/doc/bugs/assistant_eats_all_CPU/comment_7_340414e9c19903b16ab617d075fbb94e._comment deleted file mode 100644 index bbd4c63dd..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_7_340414e9c19903b16ab617d075fbb94e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 7" - date="2014-01-09T23:51:02Z" - content=""" -Okay, so the current situation is this: joey can't reproduce this, but I can reliably can, with the backport. So there has to be something different in our setups. - -We are suspecting the kernel, so I'm trying to upgrade to the backport, we'll see. -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_8_e87dbb572eaf234bbaf48ed6790ab1fe._comment b/doc/bugs/assistant_eats_all_CPU/comment_8_e87dbb572eaf234bbaf48ed6790ab1fe._comment deleted file mode 100644 index e3a580bdb..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_8_e87dbb572eaf234bbaf48ed6790ab1fe._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkmBRpgz-elUViGzECtWiO9cRLUpxIuMmg" - nickname="Oliver" - subject="comment 8" - date="2014-01-11T19:31:35Z" - content=""" -I have two Ubuntu 13.10 boxes, both running 5.20131221 from the fmarier PPA. They both have a repository with my XBMC library, and these repositories are synced together (they run on the same network). Interestingly, one machine exhibits this behaviour and one doesn't. The only obvious relevant difference is that the kernel versions are slightly different: the one that behaves properly is running - -3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux - -The one where the assistant is running at full CPU is on - -3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux - -I'm not sure if this is significant or why the kernels are different versions (both machines are fully updated). - -I would like to try and help debug this problem if possible. Please let me know if there is any diagnostic output I can provide that will help. - -"""]] diff --git a/doc/bugs/assistant_eats_all_CPU/comment_9_1c129c924ef3a4a594de6580cf4224c7._comment b/doc/bugs/assistant_eats_all_CPU/comment_9_1c129c924ef3a4a594de6580cf4224c7._comment deleted file mode 100644 index f5c5d2749..000000000 --- a/doc/bugs/assistant_eats_all_CPU/comment_9_1c129c924ef3a4a594de6580cf4224c7._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="2001:1928:1:9::1" - subject="comment 9" - date="2014-01-15T04:29:55Z" - content=""" -I have upgraded to the 3.10 backport, and there was no change in this behavior. I still see unreasonable CPU usage. - - Linux marcos 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1 (2013-09-24) x86_64 GNU/Linux - -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit.mdwn b/doc/bugs/assistant_hangs_during_commit.mdwn deleted file mode 100644 index 12adf281d..000000000 --- a/doc/bugs/assistant_hangs_during_commit.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -What steps will reproduce the problem? - -Use git-annex and add file to repo. - - -What is the expected output? What do you see instead? - -File is committed and added to annex. - -Instead a command like this is run "git --git-dir=/home/jchu/annex/.git --work-tree=/home/jchu/annex commit --allow-empty-message -m --quiet" and for some reason git decides to open a COMMIT_EDITMSG file in my editor of choice "vim .git/COMMIT_EDITMSG". Since git annex doesn't give me access to the terminal, I don't see it. - -Depending on when it happens, the web interface could refuse to start (if the commit hang happens on startup) or if it happens during regular operation, then everything looks fine but the web interface doesn't update after that. - - -What version of git-annex are you using? On what operating system? - -git-annex (binary release) 4.20130405 -git 1.8.2.1 - -On Arch Linux. - - -Please provide any additional information below. - -I'm not sure if the git interface has changed, but I do see that --allow-empty-message does still exist. If I run the git commit command (with a '' after the -m), it does indeed start up vim for me. Would we benefit from just making a custom commit message ("Commit from date YYYYMMDDTHHMMSSZ")? - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_1_aacc15c589d2795254387e427b3afe0c._comment b/doc/bugs/assistant_hangs_during_commit/comment_1_aacc15c589d2795254387e427b3afe0c._comment deleted file mode 100644 index a2d78d703..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_1_aacc15c589d2795254387e427b3afe0c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE" - nickname="Jason" - subject="comment 1" - date="2013-04-15T15:58:04Z" - content=""" -Or if that solution isn't acceptable, it seems that git commit has a --no-edit option that will guarantee that an editor isn't started. -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_2_b9f1bf9fa919603dca28182c80d39a11._comment b/doc/bugs/assistant_hangs_during_commit/comment_2_b9f1bf9fa919603dca28182c80d39a11._comment deleted file mode 100644 index 4f0a20a02..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_2_b9f1bf9fa919603dca28182c80d39a11._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 2" - date="2013-04-16T19:04:34Z" - content=""" -Proving a commit message with -m, which git-annex already does, should be enough to prevent git opening an editor. You appear to have some broken version of git there if that is not the case. - -I see that you're using Arch. Where exactly did you download git-annex from? Have you tried the standalone tarball? -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_3_fb5be10fcf5e7c89da5c34f48539612f._comment b/doc/bugs/assistant_hangs_during_commit/comment_3_fb5be10fcf5e7c89da5c34f48539612f._comment deleted file mode 100644 index 35377cbcf..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_3_fb5be10fcf5e7c89da5c34f48539612f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE" - nickname="Jason" - subject="comment 3" - date="2013-04-17T02:19:02Z" - content=""" -I absolutely agree that the -m should stop git from requiring a commit message. I don't know if anything has changed in a newer version, but that's what I'm seeing. - -I'm using the git-annex-bin package from the AUR so it's already the standalone binary: https://aur.archlinux.org/packages/git-annex-bin/ - -As you can see by the PKGBUILD, it just copies the git-annex binary to /usr/bin/git-annex and creates a symlink for git-annex-shell. -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_4_9ba7efe9112578729d02ac4e6557b3cc._comment b/doc/bugs/assistant_hangs_during_commit/comment_4_9ba7efe9112578729d02ac4e6557b3cc._comment deleted file mode 100644 index 6bd85505e..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_4_9ba7efe9112578729d02ac4e6557b3cc._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 4" - date="2013-04-17T05:09:42Z" - content=""" -AUR git-annex-bin is a very different thing from the standalone tarball. The tarball carefully puts together a program and a set of libraries and utilities it will work with. The git-annex-bin in AUR yanks that binary out and puts it in an entirely foreign system. - -So, try the standalone tarball. -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_5_73b24c901c73d41e0e0abe91267d4920._comment b/doc/bugs/assistant_hangs_during_commit/comment_5_73b24c901c73d41e0e0abe91267d4920._comment deleted file mode 100644 index 4c001c908..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_5_73b24c901c73d41e0e0abe91267d4920._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE" - nickname="Jason" - subject="comment 5" - date="2013-04-17T16:01:56Z" - content=""" -Using the git annex standalone binary has exactly the same action. It seems that the git annex standalone uses the system git instead of the one that's included. - -The git command \"git --git-dir=/home/jchu/annex/.git --work-tree=/home/jchu/annex commit --allow-empty-message -m --quiet\" hangs because it's waiting for a commit message \"vim .git/COMMIT_EDITMSG\". - -Having not looked too closely at the git source, I think I may have found what happened. The change happened in git 1.8.2 development. a24a41ea9a928ccde2db074ab0835c4817223c9d changed the code to only add \"\n\n\" to a commit message if it's entirely necessary, which means a completely blank commit message looks to the code on line 978 of commit.c \"if (logfile || message.len || use_message || fixup_message)\" as if it were actually empty instead of being considered \"\n\n\". - -Since this change only happened in 1.8.2, that's why when you run this code, it doesn't happen (any version before 1.8.2 shouldn't have this regression) but when I run it it does open the commit message editor. The --no-edit option has existed since 1.7.8 (ca1ba201). I don't know if you want to detect this case somehow or what, but I don't know if/when it's going to be fixed in git. - -As it stands, the git annex assistant is useless to me because it keeps hanging when trying to commit (the thing that I really wish I could trust it on!). -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_6_1a30b8c82e58222f1366aa368c23e6d3._comment b/doc/bugs/assistant_hangs_during_commit/comment_6_1a30b8c82e58222f1366aa368c23e6d3._comment deleted file mode 100644 index 874d0a938..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_6_1a30b8c82e58222f1366aa368c23e6d3._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 6" - date="2013-04-18T20:30:10Z" - content=""" -Thank you for that investigation. Have you confirmed that --no-edit actually fixes it? I've made it pass that parameter. - -(BTW, the standalone tarball contains a `runshell` script that you use to set up an environment before running git-annex. This includes putting its bundled version of git before the system one in PATH.) -"""]] diff --git a/doc/bugs/assistant_hangs_during_commit/comment_7_56868b2a504ad0a60e8a8c1928330175._comment b/doc/bugs/assistant_hangs_during_commit/comment_7_56868b2a504ad0a60e8a8c1928330175._comment deleted file mode 100644 index 407fbd589..000000000 --- a/doc/bugs/assistant_hangs_during_commit/comment_7_56868b2a504ad0a60e8a8c1928330175._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkZktNHFhxC1kYA9KKdKpYJO4clq9WDsjE" - nickname="Jason" - subject="comment 7" - date="2013-04-18T23:22:51Z" - content=""" -Yes, in my initial testing, I found that --no-edit fixes the problem. -"""]] diff --git a/doc/bugs/assistant_ignore_.gitignore.mdwn b/doc/bugs/assistant_ignore_.gitignore.mdwn deleted file mode 100644 index 63d067e67..000000000 --- a/doc/bugs/assistant_ignore_.gitignore.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -What steps will reproduce the problem? - -1. have an existing directory with a bunch of files -2. create a `.gitignore` file that matches some files (*.log *.aux *~ etc.) -3. `git init .` -4. `git annex init work` -5. `git remote add server server:Blabla` -6. `ssh server` -7. `@server $ mkdir Blabla` -8. `@server $ cd Blabla` -9. `@server $ git init .` -10. `@server $ git annex init server` -11. `@server $ exit` -12. `git annex webapp` - -What is the expected output? What do you see instead? - -I expect that ingored files stay ignored, -I see instead that all the files (including the ignored) are transfered to the server - -What version of git-annex are you using? On what operating system? - -3.20130124, debian sid (on both machines) - -> As noted in [[design/assistant/inotify]]'s TODO list, this -> needs an efficient gitignore query interface in git (DNE) -> or a gitignore parser. --[[Joey]] - -[[!tag /design/assistant]] - -> [[fixed|done]]; with git 1.8.4 the assistant honors .gitignore --[[Joey]] diff --git a/doc/bugs/assistant_ignore_.gitignore/comment_1_3458b1342cb2e3ccc01eeedc7f0e48fc._comment b/doc/bugs/assistant_ignore_.gitignore/comment_1_3458b1342cb2e3ccc01eeedc7f0e48fc._comment deleted file mode 100644 index 83cb22ccc..000000000 --- a/doc/bugs/assistant_ignore_.gitignore/comment_1_3458b1342cb2e3ccc01eeedc7f0e48fc._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="Johannes" - ip="153.109.130.54" - subject="comment 1" - date="2013-07-30T11:34:15Z" - content=""" -Any news on this or this or any other way to exclude unwanted files? (e.g. all the temporary files created by latex) -"""]] diff --git a/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment b/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment deleted file mode 100644 index 893be9055..000000000 --- a/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnNqLKszWk9EoD4CDCqNXJRIklKFBCN1Ao" - nickname="maurizio" - subject="git-annex from wheezy-backports should depend on a more recent git version on debian wheezy (7.2) " - date="2013-11-12T18:57:52Z" - content=""" -It is correct that the bug is solved on the git-annex package found on wheezy-backports, but this package does not force an update of git to a more recent version. Therefore the bug still affects wheezy users. The way to solve it is to install git also from wheezy-backports. - - -"""]] diff --git a/doc/bugs/assistant_ignore_.gitignore/comment_3_8b2a400e1d44a1c9b183e2b7861efbe3._comment b/doc/bugs/assistant_ignore_.gitignore/comment_3_8b2a400e1d44a1c9b183e2b7861efbe3._comment deleted file mode 100644 index e58d46084..000000000 --- a/doc/bugs/assistant_ignore_.gitignore/comment_3_8b2a400e1d44a1c9b183e2b7861efbe3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 3" - date="2013-11-12T19:10:48Z" - content=""" -Agreed, I've made the changes so the next update of the backport will do so. -"""]] diff --git a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files.mdwn b/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files.mdwn deleted file mode 100644 index d009b55cd..000000000 --- a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files.mdwn +++ /dev/null @@ -1,68 +0,0 @@ -What steps will reproduce the problem? - -In one terminal, I created a new annex and started the assistant watching it. - -In another, I added a file file1; assistant noticed it and added it to the annex. - -I moved file1 to a directory directory1; the link broke and assistant did not fix it. - -I created a file called file2 inside directory 2; assistant noticed it and added it to the annex. - -I moved file2 back up to the annex root directory; the link broke and assistant did not fix it. - -I created a file file3 in the annex root directory; assistant noticed it and added it to the annex. - -Here is the content of the first terminal, where I created the annex and ran assistant: - - - ~$ mkdir testannex - ~$ cd testannex/ - testannex$ git init . - Initialized empty Git repository in /Users/ed/testannex/.git/ - testannex$ git annex init "test annex" - init test annex ok - (Recording state in git...) - testannex$ git annex assistant --foreground - assistant . (scanning...) (started...) add file1 (checksum...) ok - (Recording state in git...) - (Recording state in git...) - add directory1/file2 (checksum...) ok - (Recording state in git...) - (Recording state in git...) - add file3 (checksum...) - -here is the content of the second terminal, where I created and moved files: - - ~$ cd testannex - testannex$ echo "file1 content" > file1 - testannex$ mkdir directory1 - testannex$ ls -l file1 - lrwxr-xr-x 1 ed staff 180 Dec 13 15:40 file1 -> .git/annex/objects/FX/51/SHA256E-s14--edac79763e630b1b77aefb6c284bcb0362dea71c0548be0e793ffa8fd5907b80/SHA256E-s14--edac79763e630b1b77aefb6c284bcb0362dea71c0548be0e793ffa8fd5907b80 - testannex$ mv file1 directory1/ - testannex$ cd directory1/ - directory1$ cat file1 - cat: file1: No such file or directory - directory1$ echo "file2 content" > file2 - directory1$ cat file2 - file2 content - directory1$ cat file1 - cat: file1: No such file or directory - directory1$ mv file2 ../ - directory1$ cd .. - testannex$ echo "file3 content" > file3 - testannex$ - - -What is the expected output? What do you see instead? - -The links do not break when moved to another directory. - -What version of git-annex are you using? On what operating system? - -One compiled using cabal from checkout 739c937 - -Please provide any additional information below. - -> [[fixed|done]]; this turned out to be an kqueue specific bug, -> the kqueue code statted new files, but that files for a broken symlink. -> Using lstat instead fixed this. --[[Joey]] diff --git a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_1_e0dafc410ffd617d445bb9403c7bfafe._comment b/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_1_e0dafc410ffd617d445bb9403c7bfafe._comment deleted file mode 100644 index fef95243b..000000000 --- a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_1_e0dafc410ffd617d445bb9403c7bfafe._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="173.162.44.162" - subject="comment 1" - date="2012-12-13T20:50:18Z" - content=""" -(Operating system is OS X Lion) - -"""]] diff --git a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_2_2af247c8a1fcbde10795a990ef3303e9._comment b/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_2_2af247c8a1fcbde10795a990ef3303e9._comment deleted file mode 100644 index 6d93d7e61..000000000 --- a/doc/bugs/assistant_not_noticing_file_renames__44___not_fixing_files/comment_2_2af247c8a1fcbde10795a990ef3303e9._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="173.162.44.162" - subject="comment 2" - date="2012-12-15T05:47:25Z" - content=""" -thanks, fix worked for me! Now the links are fixed virtually instantaneously when the file is moved. - -"""]] diff --git a/doc/bugs/assistant_report_error_when_git_global_email+name_not_set.mdwn b/doc/bugs/assistant_report_error_when_git_global_email+name_not_set.mdwn deleted file mode 100644 index 7d7e3f0ce..000000000 --- a/doc/bugs/assistant_report_error_when_git_global_email+name_not_set.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -### Please describe the problem. -When setting git-annex on a device (a mac at least in my case), where git has never been used, you get a cryptic git error in the assistant which prevents you to create your first repo. -Going to the terminal and running git --global for email and name solved the problem. - - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[closing|done]] since no version was provided and the current version -> almost certianly deals with this. --[[Joey]] diff --git a/doc/bugs/assistant_report_error_when_git_global_email+name_not_set/comment_1_728cdb11f728527219dc8db485cd7204._comment b/doc/bugs/assistant_report_error_when_git_global_email+name_not_set/comment_1_728cdb11f728527219dc8db485cd7204._comment deleted file mode 100644 index cf78c8810..000000000 --- a/doc/bugs/assistant_report_error_when_git_global_email+name_not_set/comment_1_728cdb11f728527219dc8db485cd7204._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-25T18:01:35Z" - content=""" -You didn't say what version of git-annex you're using. - -Different versions of git-annex have gone to increasing lengths to work -around this problem of git not working out of the box on systems like -yours. Without a version number, or other infortmation, I have no way -of knowing why it didn't work. - -Since the current version's workarounds include noticing if commit fails, -and coniguring the user.name and user.email, I'll bet you're using some -old version.. -"""]] diff --git a/doc/bugs/assistant_syncs_with_remotes_even_when_all_remotes_disabled.mdwn b/doc/bugs/assistant_syncs_with_remotes_even_when_all_remotes_disabled.mdwn deleted file mode 100644 index 959620ba6..000000000 --- a/doc/bugs/assistant_syncs_with_remotes_even_when_all_remotes_disabled.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. - -I migrated a repo I set up by hand on my Android phone to use the assistant and webapp. That repo has two remotes, both full git-annex repos over SSH. I still want to control when I synchronize (cellular data is precious), so the vast majority of the time I disable syncing on both remotes. However, when I return to the webapp after it's been running for "a while," it shows a status message indicating it has synced with the remotes. - -It looks like it might be related to the NetWatcherFallback, because a NetWatcherFallback entry appears in the log approximately every hour, followed by the usual repo sync output. - -### What steps will reproduce the problem? - -1. Set up a repo with a git-annex over SSH remote, and set annex-sync on that remote to false. -2. Run the webapp. -3. Observe after a period of time that the webapp shows that the repo has been synced. - -### What version of git-annex are you using? On what operating system? - -git-annex 20130709 on Android (4.2) - -### Please provide any additional information below. - -[[!format sh """ -[2013-07-22 22:50:31 MST] NetWatcherFallback: Syncing with sigsegv, sigusr1 -Everything up-to-date -Everything up-to-date -[2013-07-22 23:52:57 MST] NetWatcherFallback: Syncing with sigsegv, sigusr1 -Everything up-to-date -Everything up-to-date -[2013-07-23 00:54:15 MST] NetWatcherFallback: Syncing with sigsegv, sigusr1 -Everything up-to-date -Everything up-to-date -"""]] - -> Excellent bug report! Especially useful that you tracked it -> down to the NetWatcher. Indeed it was not honoring the -> annex-sync setting. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn b/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn deleted file mode 100644 index b019d51b8..000000000 --- a/doc/bugs/assistant_unable_to_auth___40__windows__41__.mdwn +++ /dev/null @@ -1,85 +0,0 @@ -[[!meta title="windows assistant fails to set up rsync.net authorized keys"]] - -### Please describe the problem. -Having set up a key pair, the assistant is unable to use it to log in. The console only shows a single attempt to log in, when it's adding the key to the remote machine's authorized_keys file. This is evidently failing, as the key is not actually added to authorized_keys, possibly because the shell script it tries to execute is malformed (crazy quoting, I can't untangle it), or possibly because it failed to ask for a password (I expected it to, but it didn't prompt for one). Also, once I do add the key to authorized_keys, I can ssh in using it but asking the assistant to retry still fails. - -### What steps will reproduce the problem? -Set up a remote repository. - -### What version of git-annex are you using? On what operating system? -Windows 7, Version: 5.20131230-g192d991 - -### Please provide any additional information below. - - Failed to make repository - Something went wrong setting up the repository on the remote server. - Transcript: - Permission denied, please try again. - Permission denied, please try again. - Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). - -[[!format sh """ -[2014-01-01 03:28:05 Eastern Standard Time] call: ssh-keygen ["-P","","-f","C:\\ -Users\\FAMILY~1\\AppData\\Local\\Temp\\git-annex-keygen.5\\key"] -Generating public/private rsa key pair. -cygwin warning: - MS-DOS style path detected: C:\Users\FAMILY~1\AppData\Local\Temp\git-annex-key -gen.5\key - Preferred POSIX equivalent is: /cygdrive/c/Users/FAMILY~1/AppData/Local/Temp/g -it-annex-keygen.5/key - CYGWIN environment variable option "nodosfilewarning" turns off this warning. - Consult the user's guide for more details about POSIX paths: - http://cygwin.com/cygwin-ug-net/using.html#using-pathnames -Your identification has been saved in C:\Users\FAMILY~1\AppData\Local\Temp\git-a -nnex-keygen.5\key. -Your public key has been saved in C:\Users\FAMILY~1\AppData\Local\Temp\git-annex --keygen.5\key.pub. -The key fingerprint is: -c7:0f:81:19:c8:39:cc:e1:d3:6a:62:9a:d5:d2:9f:c1 Familyroom@Familyroom-PC -The key's randomart image is: -+--[ RSA 2048]----+ -| +.+. | -| .B. + | -| o.+ . | -| o + . . | -| = = E + | -| = + . + o | -| o o . | -| | -| | -+-----------------+ -[2014-01-01 03:28:07 Eastern Standard Time] chat: ssh ["-p","22","rlbrooks@celeb -dil.db48x.net","sh -c 'mkdir -p '\"'\"'annex/test'\"'\"'&&cd '\"'\"'annex/test'\ -"'\"'&&if [ ! -d .git ]; then git init --bare --shared && git config receive.den -yNonFastforwards false; fi&&git annex init&&mkdir -p ~/.ssh&&if [ ! -e ~/.ssh/gi -t-annex-shell ]; then (echo '\"'\"'#!/bin/sh'\"'\"';echo '\"'\"'set -e'\"'\"';ec -ho '\"'\"'if [ \"x$SSH_ORIGINAL_COMMAND\" != \"x\" ]; then'\"'\"';echo '\"'\"'ex -ec git-annex-shell -c \"$SSH_ORIGINAL_COMMAND\"'\"'\"';echo '\"'\"'else'\"'\"';e -cho '\"'\"'exec git-annex-shell -c \"$@\"'\"'\"';echo '\"'\"'fi'\"'\"') > ~/.ssh -/git-annex-shell; fi&&chmod 700 ~/.ssh/git-annex-shell&&touch ~/.ssh/authorized_ -keys&&chmod 600 ~/.ssh/authorized_keys&&echo '\"'\"'command=\"GIT_ANNEX_SHELL_DI -RECTORY='\"'\"'\"'\"'\"'\"'\"'\"'annex/test'\"'\"'\"'\"'\"'\"'\"'\"' ~/.ssh/git- -annex-shell\",no-agent-forwarding,no-port-forwarding,no-X11-forwarding ssh-rsa A -AAAB3NzaC1yc2EAAAADAQABAAABAQDeB64i+DhYBCq0mdet6sBr1JCtYR5zNc0E9NYaZbBVRBcpZDCRs -AS1z8mjyEnb49y7AnNgsx/f7xAWtyFHFr8AbrYnaHmJYicix0R6inDXZ42WJTusHVW47/1ysErHmEusZ -KWXNzN5bu8bOoz0FqCh4Ymo3QjgMzk6+PoWqSCmwewuX++RkB6q1IN1VTMqJguPtdQpTp3hCIV6GENf6 -HvnLUQ59JKg1sgt5UA88zDAMlXicmUeuHRSW7nVlVIBHFDJW8f5CyF66wiuGTLdhhMlaOqpUqIEHubPF -ZE4iTOC/uuOdWjGgySX681ub4seKyz7h8uDePPo0uz0BXJpt9vT Familyroom@Familyroom-PC\n'\ -"'\"' >>~/.ssh/authorized_keys'"] -"""]] - -[[!format sh """ -$ ssh rlbrooks@git-annex-celebdil.db48x.net-rlbrooks_annex -git-annex-shell: bad parameters - -Usage: git-annex-shell [-c] command [parameters ...] [option ..] - -Options: - --force allow actions that may lose annexed data - -F --fast avoid slow operations - -a --auto automatic mode - -q --quiet avoid verbose output -etc -"""]] - -> [[fixed|done]]; both for regular remote ssh servers, and for rsync.net --[[Joey]] diff --git a/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_1_3128b025d15d3af6e9c8725d4659cdfa._comment b/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_1_3128b025d15d3af6e9c8725d4659cdfa._comment deleted file mode 100644 index 66827bf8d..000000000 --- a/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_1_3128b025d15d3af6e9c8725d4659cdfa._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 1" - date="2014-01-01T19:56:32Z" - content=""" -I can reproduce this bug. Seems the problem is that sshTranscript is called with a string that is fed in on stdin. But I guess that on Windows, ssh password prompting is also done using stdin (on Linux it would use /dev/tty), and so this prevents it from prompting. - -I've fixed this for the remote ssh server setup in the webapp, which did not actually need to feed anything in on stdin. Confirmed ssh adding works! - -However, for rsync.net, the ssh pubkey is fed into dd using stdin, and so I was unable to fix it there yet. Since rsync.net does not support redirection to files in its shell, the only approach that would seem to work is to first download the authorized_keys file, add the line, and rsync in the new file. Until I get a chance to do that, I am leaving this bug report open. -"""]] diff --git a/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_2_e0b64ab2d19f0b0afbd466aad22c4df9._comment b/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_2_e0b64ab2d19f0b0afbd466aad22c4df9._comment deleted file mode 100644 index 6998c2b2d..000000000 --- a/doc/bugs/assistant_unable_to_auth___40__windows__41__/comment_2_e0b64ab2d19f0b0afbd466aad22c4df9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 2" - date="2014-01-01T19:59:11Z" - content=""" -Also, fixing rsync.net that way would mean two ssh connections to set up authorized_keys, so 2 password prompts. suboptimal.. -"""]] diff --git a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__.mdwn b/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__.mdwn deleted file mode 100644 index 1ad800522..000000000 --- a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__.mdwn +++ /dev/null @@ -1,45 +0,0 @@ -### Please describe the problem. -The assistant (or rather the programs it's running) appears to be using unix-style paths instead of cygwin paths, causing several types of errors. A selection of items from the terminal: - -[[!format sh """ -Launching web browser on file://C:\Users\Familyroom\annex\.git\annex\webapp.html -[2013-12-31 01:14:05 Eastern Standard Time] read: ssh-keygen ["-F","celebdil.db4 -8x.net"] -ssh-keygen: /home/Familyroom/.ssh/known_hosts: No such file or directory -[2013-12-31 01:14:05 Eastern Standard Time] read: ssh ["-oNumberOfPasswordPrompt -s=0","-oStrictHostKeyChecking=no","-n","-p","22","rlbrooks@celebdil.db48x.net"," -sh -c 'echo git-annex-probe loggedin;if which git-annex-shell; then echo git-ann -ex-probe git-annex-shell; fi;if which git; then echo git-annex-probe git; fi;if -which rsync; then echo git-annex-probe rsync; fi;if which ~/.ssh/git-annex-shell -; then echo git-annex-probe ~/.ssh/git-annex-shell; fi;cd '\"'\"'annex'\"'\"' && - git config --list'"] -[2013-12-31 01:14:08 Eastern Standard Time] read: ssh-keygen ["-F","celebdil.db4 -8x.net"] -ssh-keygen: /home/Familyroom/.ssh/known_hosts: No such file or directory -[2013-12-31 01:14:08 Eastern Standard Time] read: ssh ["-oStrictHostKeyChecking= -no","-n","-p","22","rlbrooks@celebdil.db48x.net","sh -c 'echo git-annex-probe lo -ggedin;if which git-annex-shell; then echo git-annex-probe git-annex-shell; fi;i -f which git; then echo git-annex-probe git; fi;if which rsync; then echo git-ann -ex-probe rsync; fi;if which ~/.ssh/git-annex-shell; then echo git-annex-probe ~/ -.ssh/git-annex-shell; fi;cd '\"'\"'annex'\"'\"' && git config --list'"] -rlbrooks@celebdil.db48x.net's password: -[2013-12-31 01:15:03 Eastern Standard Time] read: gpg ["--quiet","--trust-model" -,"always","--with-colons","--list-secret-keys","--fixed-list-mode"] -gpg: WARNING: using insecure memory! -gpg: please see http://www.gnupg.org/documentation/faqs.html for more informatio -n -gpg: fatal: can't create directory `/home/Familyroom/.gnupg': No such file or di -rectory -secmem usage: 0/0 bytes in 0/0 blocks of pool 0/65536 -"""]] - -Naturally, I don't have a /home/Familyroom, although I do have a /c/Users/Familyroom. - -### What steps will reproduce the problem? -Start creating a remote repository. - -### What version of git-annex are you using? On what operating system? -Windows 7, git-annex version 5.20131230-g192d991 - -> [[fixed|done]]; git-annex now ensures HOME is set when running cygwin -> commands that require it. --[[Joey]] diff --git a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_1_68be9ee77cc89fb72a4abc944f1da41d._comment b/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_1_68be9ee77cc89fb72a4abc944f1da41d._comment deleted file mode 100644 index 8e51d8509..000000000 --- a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_1_68be9ee77cc89fb72a4abc944f1da41d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA" - nickname="Daniel" - subject="comment 1" - date="2013-12-31T20:48:03Z" - content=""" -I neglected to mention that the assistant is failing when gpg fails, and that it worked last week in 5.20131221-gf8c928d (or at least it got past this point). -"""]] diff --git a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_2_6530d67e7d94ccbea9ce11ba1445035e._comment b/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_2_6530d67e7d94ccbea9ce11ba1445035e._comment deleted file mode 100644 index a68338d2d..000000000 --- a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_2_6530d67e7d94ccbea9ce11ba1445035e._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 2" - date="2013-12-31T21:17:32Z" - content=""" -It seems that both ssh-keygen and gpg are for some reason acting as if HOME is set to /home/Familyroom. -git-annex does not do anything to override the default home directory these programs use, and AFAIK, nothing has changed in the Windows build between the working and broken versions that could have anything to do with this. -"""]] diff --git a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_3_682556a8182abd5bd6abb57b519d4c76._comment b/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_3_682556a8182abd5bd6abb57b519d4c76._comment deleted file mode 100644 index 49e040d5a..000000000 --- a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_3_682556a8182abd5bd6abb57b519d4c76._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA" - nickname="Daniel" - subject="comment 3" - date="2013-12-31T23:47:43Z" - content=""" -Yea, the only relevant change I noticed was 5c834daf5, and it's not particularly relevant. - -However, its occurred to me that I started the webapp differently this time than last; I used the start menu shortcut this time rather than typing git annex webapp in the git shell. It's not surprising that the environment variables would be quite different between the two. -"""]] diff --git a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_4_331cdacb099a8c7b170c37715bbca895._comment b/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_4_331cdacb099a8c7b170c37715bbca895._comment deleted file mode 100644 index 7debf8ea8..000000000 --- a/doc/bugs/assistant_using_the_incorrect_path_on_windows__63__/comment_4_331cdacb099a8c7b170c37715bbca895._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA" - nickname="Daniel" - subject="comment 4" - date="2013-12-31T23:56:24Z" - content=""" -Yea, if I start it from the Git Bash command line, it continues past this to a completely different error. -"""]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote.mdwn b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote.mdwn deleted file mode 100644 index 657a4dd3d..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -I am running 3.20121112 and this bug appeared when I upgraded to that from 3.20121017. - -After performing the startup scan after I login, git-annex gets GPG to sends me a pinentry pop-up asking for my GPG passphrase. However, I know that there is nothing to be dropped or copied to the encrypted SSH remote that I am being asked to provide access to. So I can't see any good reason why I would be asked for the passphrase. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_1_10a9570a5d762ba2da271b38dc63edb6._comment b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_1_10a9570a5d762ba2da271b38dc63edb6._comment deleted file mode 100644 index 548db2386..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_1_10a9570a5d762ba2da271b38dc63edb6._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.6.49" - subject="comment 1" - date="2012-11-29T20:13:53Z" - content=""" -Hmm, is this an encrypted rsync remote? - -I have not been able to reproduce the problem so fat. - -If you start the assistant with --debug, and look in .git/annex/daemon.log, you should find where it runs gpg, and the lines showing what it's doing just before/after that should provide a hint what it's doing. -"""]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_2_57d50955b038c2e2405068536c7e83f3._comment b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_2_57d50955b038c2e2405068536c7e83f3._comment deleted file mode 100644 index ce57194c9..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_2_57d50955b038c2e2405068536c7e83f3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="spwhitton" - ip="163.1.167.50" - subject="comment 2" - date="2012-12-01T18:34:10Z" - content=""" -Thanks for the log advice. I looked and it wants to drop a file `ttmik/TTMIK-Lesson-L1L1.mp3` from the encrypted rsync remote ma. So I did `git annex whereis ttmik/TTMIK-Lesson-L1L1.mp3` and learnt that the file is not on ma. I tried `git annex drop --from ma ttmik` to be sure, and the command was successful, but it still tries to drop the file from ma on startup. Presumably it would try all the other files in the ttmik directory if I gave it the chance to try to drop this first one. The only thing special about the ttmik directory is that every file in there was added using addurl, so I guess the problem has something to do with that. -"""]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_3_a66f34daaba421c87eb404ef933e5191._comment b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_3_a66f34daaba421c87eb404ef933e5191._comment deleted file mode 100644 index 9bfade666..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_3_a66f34daaba421c87eb404ef933e5191._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.6.49" - subject="comment 3" - date="2012-12-01T18:59:45Z" - content=""" -How is this rsync remote configured? Is it configured as a transfer remote? If not, the assistant's default behavior is to sync all files to it, and since you say the file is not there, it'd make sense it would start transferring it to there on startup. - -OTOH, this could be a complete red herring. You haven't shown me the log file. Perhaps the drop you're seeing in the log is before the operation that is asking for the GPG passphrase. I can't tell until you show me the log. -"""]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_4_094a3272eca1c6d2b4d264911ffe96e5._comment b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_4_094a3272eca1c6d2b4d264911ffe96e5._comment deleted file mode 100644 index 8f9f54610..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_4_094a3272eca1c6d2b4d264911ffe96e5._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="spwhitton" - ip="163.1.167.50" - subject="comment 4" - date="2012-12-02T18:27:09Z" - content=""" -The rsync remote is in the archive group but it has the preferred content string `exclude=video/* and exclude=ttmik/*`. So it ought to be dropping the files, but not over and over again. - -Here is the log file, showing me hitting Escape on the pinentry dialog: - - (scanning...) Already up-to-date. - Already up-to-date. - Already up-to-date. - drop ma ttmik/TTMIK-Lesson-L1L1.mp3 (gpg) gpg: cancelled by user - gpg: decryption failed: secret key not available - TransferScanner crashed: user error (gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"-- - quiet\",\"--trust-model\",\"always\",\"--decrypt\"] exited 2) - (started...) -"""]] diff --git a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_5_0161410d042a3421addd4a1fc7c1cd01._comment b/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_5_0161410d042a3421addd4a1fc7c1cd01._comment deleted file mode 100644 index 89ef87c2a..000000000 --- a/doc/bugs/assistant_wants_my_gpg_passphrase_when_it_has_nothing_to_drop_or_copy_to_that_remote/comment_5_0161410d042a3421addd4a1fc7c1cd01._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.108.72" - subject="comment 5" - date="2012-12-05T16:34:24Z" - content=""" -Aha, I see the bug now. It is indeed trying to drop from every remote, even ones without the data. - -(Also, the thread should not crash here if the drop fails.. I've fixed that.) -"""]] diff --git a/doc/bugs/assistant_windows_does_not_start.mdwn b/doc/bugs/assistant_windows_does_not_start.mdwn deleted file mode 100644 index 6aaafc57e..000000000 --- a/doc/bugs/assistant_windows_does_not_start.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -webapp does not start. - -Reports the following error: - -Script: c:\Programm Files(x86)\Git\git-annex-webapp.vbs -Line: 2 -Character: 1 -Error: System can not fine the specified File -Code: 80070002 -Source: null - - -### What steps will reproduce the problem? - -1. Downloaded the installer. -2. Run the installer -3. In folder c:\Programm Files(x86)\Git doubleclick on git-annex-webapp -4. Content vbs: - Set objshell=CreateObject("Wscript.Shell") - objShell.Run("git-annex webapp"), 0, False -4. -### What version of git-annex are you using? On what operating system? -Version 2014-11-05 14:38 -Server Windows Server 2008 R2 -### 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. -"""]] - -> [[done]]; never heard back, so I assume my comment is right. --[[Joey]] diff --git a/doc/bugs/assistant_windows_does_not_start/comment_1_007c2d489a521115d0e679d0130748fb._comment b/doc/bugs/assistant_windows_does_not_start/comment_1_007c2d489a521115d0e679d0130748fb._comment deleted file mode 100644 index 2d994433e..000000000 --- a/doc/bugs/assistant_windows_does_not_start/comment_1_007c2d489a521115d0e679d0130748fb._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-12-02T17:16:09Z" - content=""" -I think you have either forgotten to install msysgit, or if you did install -it, you didn't tell its installer to add git to the PATH. - -Git-annex relies on that to be located in the search path itself. - -You can probably fix the problem by (re)installing msysgit. -"""]] diff --git a/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them.mdwn b/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them.mdwn deleted file mode 100644 index 530a8da5d..000000000 --- a/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -Found this out the hard way. See the comment in the below post for what happens. - -[[/forum/git_annex_add_crash_and_subsequent_recovery/]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them/comment_1_92dfe6e9089c79eb64e2177fb135ef55._comment b/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them/comment_1_92dfe6e9089c79eb64e2177fb135ef55._comment deleted file mode 100644 index 7ff8f8e3d..000000000 --- a/doc/bugs/bad_behaviour_with_file_names_with_newline_in_them/comment_1_92dfe6e9089c79eb64e2177fb135ef55._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2011-12-06T16:49:32Z" - content=""" -This only happens with the WORM backend (or possibly with SHA1E if the file's extension has a newline). - -The problem is not the newline in the file, but the newline in the key generated for the file. It's probably best to just disallow such keys being created. -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files.mdwn b/doc/bugs/bad_merge_commit_deleting_all_files.mdwn deleted file mode 100644 index affabdb02..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files.mdwn +++ /dev/null @@ -1,78 +0,0 @@ -In our family repository, we had an event where git-annex committed a bad -merge commit. This had the effect of seeming to delete all the files -in the repository. However, it is completely recoverable with no file loss. - -Other users have reported apparently the same problem. ---[[Joey]] - -> This appears to be a race, and I have put in a fix for that. -> It will be released in git-annex 5.20140709. -> -> It's a little bit difficult to say for sure that the bug is fixed, since -> I don't have a good way to reproduce it. However, everything I am seeing -> is consistent with my analysis, at least as far as the people who -> reported this happening with versions 5.20140613-5.20140707. -> Calling this [[done]]. --[[Joey]] - -## recovery - -Look through the git log for the bad commit. It will be the one -that deletes a lot of files. Since the bad commit is a merge commit, -you need to include the -c switch: - - git log -c --stat - -Once the bad commit sha is found, revert it. Since it's a merge commit, -you will need to pass -m 1 to git revert. If the repository you're working -is uses direct mode, you will first need to switch it to indirect mode. - - git annex indirect - git revert -m 1 a36077cf1234eeb755fec8f699d3cbaaee817bac - -(It's possible, but I think unlikely that this will pick the wrong -branch of the merge to revert. If it did, "git reset --hard HEAD@{1}" and -redo, passing `-m 2` instead.) - -Once the revert is done, all your files should be back. You can switch -the repository back to direct mode if desired (`git annex direct`) -and can `git annex sync` to push the fix out to all other clones. -Everywhere the fix lands should restore the deleted files. - -Note that it's possible that some repositories may have pruned the deleted -files as unused. This is most likely to happen in the repository that made -the bad merge commit in the first place. - -If you have any problems following these instructions, please contact -<urgent2014@joeyh.name> for support. - -[[!tag confirmed urgent]] - -## analysis - -In the one case I have of this happening, the commit was made by the -git-annex assistant, in direct mode. It was git-annex version 5.20140613. -This version had a bug that caused it to do unncessary merge commits. -That bug has been fixed in 5.20140707. -That is apparently related, in that it caused the assistant to do much more -work than normal. - -But, I don't think that bug is fully responsible for the -problem. I think a few users have run into this bug before, although I have -never succeeded in getting a full problem description from anyone who might -have. I think that the unncessary commit bug made it more likely to happen. -(This suggests a race may be involved.) - -The bad merge commit looked like this: - -<pre> -commit a36077cf1234eeb755fec8f699d3cbaaee817bac -Merge: 52ecff2 9d8bfd4 -Author: xxx -Date: Mon Jul 7 19:58:18 2014 -0400 - - merge refs/heads/synced/master -</pre> - -Both parent trees were good and contained all files. In fact, the 2 -parent trees contained the same set of files. But the merge commit -"resolved" the merge by deleting all the files. diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_1_3503644244e39c65d531807769365f50._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_1_3503644244e39c65d531807769365f50._comment deleted file mode 100644 index 6b24ea958..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_1_3503644244e39c65d531807769365f50._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-09T18:20:13Z" - content=""" -mergeDirect locks .git/index, so no other git command should use it while the merge is in progress. - -However, if the index file is deleted, and stageMerge runs, it stages deletion of all files. So that looks likely to be part of the story. -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_2_9c4c950da0c07bf7c7edfcc7cc3b6011._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_2_9c4c950da0c07bf7c7edfcc7cc3b6011._comment deleted file mode 100644 index 19dcf1ca0..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_2_9c4c950da0c07bf7c7edfcc7cc3b6011._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-09T18:25:08Z" - content=""" -Also pointing in the direction of a race: The bad commit happened 3 seconds after another commit did. The other commit was an empty commit, so caused by the bug in 5.20140613. -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_3_be42de12faf15562265ad6cf8964f5db._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_3_be42de12faf15562265ad6cf8964f5db._comment deleted file mode 100644 index dd689eae7..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_3_be42de12faf15562265ad6cf8964f5db._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="theory" - date="2014-07-09T18:31:07Z" - content=""" -Suppose we have 2 mergeDirect's A and B running at the same time somehow, with B around 3 seconds behind A, and this sequence of events occurs: - -1. A copies index file to index.lock -2. A stages an empty commit -3. B copies index file to index.lock -4. A finishes its commit, and so renames index.lock back to index. -5. B runs stageMerge - -So, B is now running stageMerge with `GIT_INDEX_FILE` pointing to an index.lock that DNE. As noted above, this causes a deletion of all files to get staged by B. - -If this is the problem, git-annex could fix it using a real lock file. (The index.lock only prevents other git commands from manipulating the index during the merge.) -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_4_d5cbd1440e4d6706eb14644a4ff1883b._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_4_d5cbd1440e4d6706eb14644a4ff1883b._comment deleted file mode 100644 index 1440ee46b..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_4_d5cbd1440e4d6706eb14644a4ff1883b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 4" - date="2014-07-09T18:36:36Z" - content=""" -The above race was first introduced in version 5.20140613. -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c532859deb682dff9e59037d08f66a51._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c532859deb682dff9e59037d08f66a51._comment deleted file mode 100644 index b1a5d32a6..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c532859deb682dff9e59037d08f66a51._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 6" - date="2014-07-09T19:01:33Z" - content=""" -Note that [[Assistant_merge_loop]], which contributes to this bug, is not actually fixed in 5.20140707, it seems. -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c946d2793fe0354151c447ddd0e59fd7._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c946d2793fe0354151c447ddd0e59fd7._comment deleted file mode 100644 index 20006ff6c..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_6_c946d2793fe0354151c447ddd0e59fd7._comment +++ /dev/null @@ -1,41 +0,0 @@ -[[!comment format=mdwn - username="http://jamesjustjames.wordpress.com/" - nickname="purpleidea" - subject="The guy with this bug." - date="2014-07-09T18:50:36Z" - content=""" -* Sure enough looking though the git log, I found one that removed 81 -files. It was useful to grep for 'deletions'. - -* It turned out there were actually two, one from each of the two -git-annex-assistant machines. I had to do the revert separately on each -machine for the corresponding commit that it had made. - -* I typically run the latest version that the webapp offers, within -about a week or so of it prompting me (unless I'm away for a while). -This means that maybe you can track down the approximate version where -this occured by looking at the two commit dates of the \"bad\" merges: - -commit bbe43fb638d101d5b9bfa65a4023e7f9d90e72e6 -Merge: 351cca8 95935ce -Author: James <james@computer1> -Date: Tue Jul 8 02:15:57 2014 -0400 - -commit 1902a3af25b1ce3723c38877c7f25907885040e4 -Merge: 125b984 efcece7 -Author: James <james@computer2> -Date: Tue Jul 8 02:15:27 2014 -0400 - -* I use the command line for pretty much most of what I do. Funny enough -though I only really use git-annex through the webapp. - -* Bug wise I don't know if this is relevant, but I have done the -following: -> added/changed/removed files to ~/annex on computer one while git-annex -wasn't running -> added/changed/removed files to ~/annex on computer two while it wasn't -running -> started git-annex on computer one -> started git-annex on computer two -> and similar combinations of the above... -"""]] diff --git a/doc/bugs/bad_merge_commit_deleting_all_files/comment_7_24dea380fcf470e0ea488dece0410f37._comment b/doc/bugs/bad_merge_commit_deleting_all_files/comment_7_24dea380fcf470e0ea488dece0410f37._comment deleted file mode 100644 index 0cb39e7c8..000000000 --- a/doc/bugs/bad_merge_commit_deleting_all_files/comment_7_24dea380fcf470e0ea488dece0410f37._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="more confirmation of race theory" - date="2014-07-09T19:26:55Z" - content=""" -@purpleidea showed me his git log, and as I had expected, there were previous empty commits immediately before the 2 commits that removes all of his files (which happened independenctly on 2 different machines running the assistant). This is consistent with my suspicion it's a race. Note that the assistant's git ref watcher can easily run multiple merges concurrently if multiple refs change. -"""]] diff --git a/doc/bugs/bencode.mdwn b/doc/bugs/bencode.mdwn deleted file mode 100644 index 92257b7d8..000000000 --- a/doc/bugs/bencode.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -### Please describe the problem. - -I have been packaging bencode as a dependency for git-annex on Debian. - -I contacted the upstream authors in reference to getting some licensing issues fixed and they pointed me to a package called "AttoBencode" which -might be a more recent and maintained option for bencode parsing in Git Annex. - -http://hackage.haskell.org/package/AttoBencode - -This isn't actually a bug, I just thought this would be a good place to bring this up. - -For what it's worth, I like the idea that packages can become stable (or old) and still serve their purpose so if bencode works just fine I think that's great. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> Closing, since it's been over a month with no followup to my question, -> and I cannot find any license problems at all with bencode. --[[Joey]] -> [[done]] diff --git a/doc/bugs/bencode/comment_1_24bc8c996eb32f344b3f091e14171a15._comment b/doc/bugs/bencode/comment_1_24bc8c996eb32f344b3f091e14171a15._comment deleted file mode 100644 index 822139471..000000000 --- a/doc/bugs/bencode/comment_1_24bc8c996eb32f344b3f091e14171a15._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-01-05T15:53:32Z" - content=""" -Rewriting the torrent library to use attobencode feels like yak shaving. -It's not like parsing torrents is a performance bottleneck in this -situation, that would need an attoparsec based parser for speed. - -I don't see any licensing problems in bencode. -"""]] diff --git a/doc/bugs/bittorrent_special_url_double-encoding.mdwn b/doc/bugs/bittorrent_special_url_double-encoding.mdwn deleted file mode 100644 index ebbf76a34..000000000 --- a/doc/bugs/bittorrent_special_url_double-encoding.mdwn +++ /dev/null @@ -1,177 +0,0 @@ -[[!meta title="mojibake in aria2c output"]] - -### Please describe the problem. - -French messages in the `aria2c` client called from `git-annex` are garbled, probably double utf-8 encoded. - -### What steps will reproduce the problem? - -download a bittorrent url with git-torrent using a UTF8 locale. - -### What version of git-annex are you using? On what operating system? - -`5.20150205-gbf9058a` on current debian jessie. - -### 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 - -anarcat@marcos:iso(master)$ /srv/downloads.kitenet.net/git-annex/linux/current/git-annex.linux/git-annex addurl http://images.kali.org/kali-linux-1.1.0-amd64-mini.torrent -(downloading torrent file...) ---2015-02-09 22:08:58-- http://images.kali.org/kali-linux-1.1.0-amd64-mini.torrent -Résolution de images.kali.org (images.kali.org)… 50.7.37.130 -Connexion à images.kali.org (images.kali.org)|50.7.37.130|:80… connecté. -requête HTTP transmise, en attente de la réponse… 200 OK -Taille : 2668 (2,6K) [application/octet-stream] -Sauvegarde en : « ../.git/annex/misctmp/torrent31107 » - -100%[=====================================================================================================================================================================================================>] 2 668 --.-K/s ds 0,002s - -2015-02-09 22:08:59 (1,56 MB/s) — « ../.git/annex/misctmp/torrent31107 » sauvegardé [2668/2668] - -addurl images.kali.org_kali_linux_1.1.0_amd64_mini.torrent/kali_linux_1.1.0_amd64_mini.iso (from bittorrent) - - -02/09 22:08:59 [ERROR] Exception caught while loading DHT routing table from /home/anarcat/.aria2/dht.dat -Exception: [DHTRoutingTableDeserializer.cc:83] errorCode=1 Failed to load DHT routing table from /home/anarcat/.aria2/dht.dat - -02/09 22:08:59 [NOTICE] IPv4 DHT: listening on UDP port 6912 - -02/09 22:08:59 [ERROR] Erreur d'intégrité détectée. fichier=../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini - -02/09 22:08:59 [NOTICE] IPv4 BitTorrent: listening on TCP port 6910 - -02/09 22:08:59 [NOTICE] IPv6 BitTorrent: listening on TCP port 6910 -[#9acd0a 0B/27MiB(0%) CN:0 SD:0 DL:0B] -[#9acd0a 0B/27MiB(0%) CN:29 SD:0 DL:0B] -[#9acd0a 0B/27MiB(0%) CN:29 SD:1 DL:0B] -[#9acd0a 0B/27MiB(0%) CN:27 SD:5 DL:0B] -[#9acd0a 464KiB/27MiB(1%) CN:27 SD:6 DL:612KiB ETA:44s] -[#9acd0a 1.0MiB/27MiB(3%) CN:27 SD:6 DL:604KiB ETA:44s] -[#9acd0a 1.5MiB/27MiB(5%) CN:27 SD:7 DL:583KiB ETA:44s] -[#9acd0a 2.2MiB/27MiB(8%) CN:26 SD:8 DL:600KiB ETA:42s] -[#9acd0a 2.7MiB/27MiB(10%) CN:26 SD:10 DL:596KiB ETA:41s] -[#9acd0a 3.2MiB/27MiB(12%) CN:26 SD:11 DL:579KiB ETA:41s] -[#9acd0a 3.8MiB/27MiB(14%) CN:27 SD:11 DL:584KiB ETA:40s] -[#9acd0a 4.4MiB/27MiB(16%) CN:27 SD:11 DL:584KiB ETA:39s] -[#9acd0a 5.0MiB/27MiB(18%) CN:26 SD:11 DL:589KiB ETA:38s] -[#9acd0a 5.5MiB/27MiB(20%) CN:26 SD:11 DL:590KiB ETA:37s] -[#9acd0a 6.2MiB/27MiB(23%) CN:26 SD:11 DL:595KiB ETA:35s] -[#9acd0a 6.8MiB/27MiB(25%) CN:26 SD:11 DL:596KiB ETA:34s] -[#9acd0a 7.3MiB/27MiB(27%) CN:24 SD:9 DL:594KiB ETA:33s] -[#9acd0a 7.9MiB/27MiB(29%) CN:24 SD:9 DL:594KiB ETA:32s] -[#9acd0a 8.4MiB/27MiB(31%) CN:24 SD:10 DL:591KiB ETA:32s] -[#9acd0a 9.1MiB/27MiB(33%) CN:24 SD:10 DL:595KiB ETA:30s] -[#9acd0a 9.7MiB/27MiB(35%) CN:24 SD:10 DL:596KiB ETA:29s] -[#9acd0a 10MiB/27MiB(37%) CN:22 SD:9 DL:589KiB ETA:29s] -[#9acd0a 10MiB/27MiB(39%) CN:10 SD:8 DL:588KiB ETA:28s] -[#9acd0a 11MiB/27MiB(41%) CN:9 SD:8 DL:583KiB ETA:27s] -[#9acd0a 11MiB/27MiB(43%) CN:9 SD:8 DL:587KiB ETA:26s] -[#9acd0a 12MiB/27MiB(45%) CN:8 SD:7 DL:586KiB ETA:25s] -[#9acd0a 12MiB/27MiB(48%) CN:8 SD:7 DL:584KiB ETA:24s] -[#9acd0a 13MiB/27MiB(50%) CN:8 SD:8 DL:585KiB ETA:23s] -[#9acd0a 14MiB/27MiB(52%) CN:8 SD:8 DL:574KiB ETA:23s] -[#9acd0a 14MiB/27MiB(53%) CN:8 SD:8 DL:567KiB ETA:22s] -[#9acd0a 14MiB/27MiB(55%) CN:8 SD:8 DL:556KiB ETA:22s] -[#9acd0a 15MiB/27MiB(57%) CN:8 SD:8 DL:555KiB ETA:21s] -[#9acd0a 15MiB/27MiB(59%) CN:8 SD:8 DL:550KiB ETA:20s] -[#9acd0a 16MiB/27MiB(60%) CN:8 SD:8 DL:543KiB ETA:19s] -[#9acd0a 16MiB/27MiB(62%) CN:8 SD:8 DL:540KiB ETA:18s] -[#9acd0a 17MiB/27MiB(64%) CN:8 SD:8 DL:537KiB ETA:18s] -[#9acd0a 18MiB/27MiB(66%) CN:8 SD:8 DL:535KiB ETA:17s] -[#9acd0a 18MiB/27MiB(68%) CN:8 SD:8 DL:525KiB ETA:16s] -[#9acd0a 18MiB/27MiB(70%) CN:8 SD:8 DL:522KiB ETA:15s] -[#9acd0a 19MiB/27MiB(72%) CN:8 SD:8 DL:522KiB ETA:14s] -[#9acd0a 19MiB/27MiB(74%) CN:8 SD:8 DL:523KiB ETA:13s] -[#9acd0a 20MiB/27MiB(76%) CN:8 SD:8 DL:517KiB ETA:12s] -[#9acd0a 21MiB/27MiB(78%) CN:8 SD:8 DL:522KiB ETA:11s] -[#9acd0a 21MiB/27MiB(80%) CN:13 SD:8 DL:532KiB ETA:10s] -[#9acd0a 22MiB/27MiB(82%) CN:13 SD:8 DL:541KiB ETA:8s] -[#9acd0a 22MiB/27MiB(84%) CN:13 SD:8 DL:544KiB ETA:7s] -[#9acd0a 23MiB/27MiB(86%) CN:13 SD:8 DL:552KiB ETA:6s] -[#9acd0a 23MiB/27MiB(88%) CN:13 SD:8 DL:549KiB ETA:5s] -[#9acd0a 24MiB/27MiB(91%) CN:13 SD:8 DL:558KiB ETA:4s] -[#9acd0a 25MiB/27MiB(93%) CN:13 SD:8 DL:570KiB ETA:3s] -[#9acd0a 25MiB/27MiB(95%) CN:13 SD:8 DL:576KiB ETA:2s] -[#9acd0a 26MiB/27MiB(97%) CN:13 SD:8 DL:587KiB ETA:1s] -[#9acd0a 26MiB/27MiB(99%) CN:13 SD:8 DL:592KiB] - -02/09 22:09:53 [NOTICE] Le téléchargement des fichiers sélectionnés est terminé. - -02/09 22:09:53 [NOTICE] Le partage (seeding) est terminé -[#9acd0a SEED(0.0) CN:9 SD:4] -[#9acd0a SEED(0.0) CN:0 SD:0] - -02/09 22:09:55 [NOTICE] Téléchargement terminé: ../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini - -02/09 22:09:55 [NOTICE] Votre ratio de partage était de 0.0, envoyé/téléchargé=0B/27MiB - - -Résultats du téléchargement: -gid |stat|avg speed |path/URI -======+====+===========+======================================================= -9acd0a|OK | 518KiB/s|../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini/kali-linux-1.1.0-amd64-mini.iso - -Légende du statut: -(OK): téléchargement terminé. -ok -addurl images.kali.org_kali_linux_1.1.0_amd64_mini.torrent/kali_linux_1.1.0_amd64_mini.txt.sha1sum (from bittorrent) - - -02/09 22:09:56 [NOTICE] IPv4 DHT: listening on UDP port 6990 - -02/09 22:09:56 [NOTICE] Le fichier de contrôle défectueux ../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini.aria2 a été supprimé car le fichier téléchargé ../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini n'existe pas. - -02/09 22:09:56 [ERROR] Erreur d'intégrité détectée. fichier=../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini - -02/09 22:09:56 [NOTICE] IPv4 BitTorrent: listening on TCP port 6899 - -02/09 22:09:56 [NOTICE] IPv6 BitTorrent: listening on TCP port 6899 -[#5f49f7 0B/75B(0%) CN:0 SD:0 DL:0B] -[#5f49f7 0B/75B(0%) CN:28 SD:0 DL:0B] -[#5f49f7 0B/75B(0%) CN:28 SD:1 DL:0B] - -02/09 22:10:00 [NOTICE] Le téléchargement des fichiers sélectionnés est terminé. - -02/09 22:10:00 [NOTICE] Le partage (seeding) est terminé -[#5f49f7 SEED(0.0) CN:22 SD:3] -[#5f49f7 SEED(0.0) CN:0 SD:0] - -02/09 22:10:02 [NOTICE] Téléchargement terminé: ../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini - -02/09 22:10:02 [NOTICE] Votre ratio de partage était de 0.0, envoyé/téléchargé=0B/75B - - -Résultats du téléchargement: -gid |stat|avg speed |path/URI -======+====+===========+======================================================= -5f49f7|OK | 19B/s|../.git/annex/misctmp/URL--http&c%%images.kali.org%kali-linux-1.1.0-amd64-mini.torrent/kali-linux-1.1.0-amd64-mini/kali-linux-1.1.0-amd64-mini.txt.sha1sum - -Légende du statut: -(OK): téléchargement terminé. -ok -(recording state in git...) -anarcat@marcos:iso(master +)$ locale -LANG=fr_CA.UTF-8 -LANGUAGE= -LC_CTYPE="fr_CA.UTF-8" -LC_NUMERIC="fr_CA.UTF-8" -LC_TIME="fr_CA.UTF-8" -LC_COLLATE="fr_CA.UTF-8" -LC_MONETARY="fr_CA.UTF-8" -LC_MESSAGES="fr_CA.UTF-8" -LC_PAPER="fr_CA.UTF-8" -LC_NAME="fr_CA.UTF-8" -LC_ADDRESS="fr_CA.UTF-8" -LC_TELEPHONE="fr_CA.UTF-8" -LC_MEASUREMENT="fr_CA.UTF-8" -LC_IDENTIFICATION="fr_CA.UTF-8" -LC_ALL= -# End of transcript or log. -"""]] - -Previous similar UTF-8 bug: [[forget_corrupts_non-ascii_chars]]. Looks similar. --[[anarcat]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/box.com.mdwn b/doc/bugs/box.com.mdwn deleted file mode 100644 index aab8ebdbb..000000000 --- a/doc/bugs/box.com.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. - -I´m trying to use an box.com acount as special remote repository for transfering data amoung my clients. Adding the box.com is possible. On the box.com website i see that git-annex has create an folder, but there is no syncing. - -When i try to enable the box.com Repository on an another client i get an Internal Error Server: bad creds. - - -### What version of git-annex are you using? On what operating system? - -Git-Annex Version: git-annex version 5.20140830-g3c96b79 - -Mac OS X 10.9.4 - -### 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 - -03/Sep/2014:20:41:31 +0200 [Error#yesod-core] bad creds @(yesod-core-1.2.19:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:503:5) - -[2014-09-03 20:41:47 CEST] main: Syncing with Box.com - - bad creds - - bad creds - - bad creds - - bad creds - -# End of transcript or log. -"""]] - -> [[done]]; fixed in [[!commit d84eab8a8af0c8cfa85de5baabfd9a2cf306f968]] diff --git a/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment b/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment deleted file mode 100644 index d230e52aa..000000000 --- a/doc/bugs/box.com/comment_1_d904a08519424cb9f599b2154d1ef953._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-09-18T19:28:56Z" - content=""" -Ok, I managed to reproduce this. In my case, there was no \"Bad creds\" message because the broken creds data it used happened to contain a newline, but same problem; the creds stored by the webapp are not used properly when re-enabling the box.com remote elsewhere. Same problem would affect other special remotes using embedded creds and shared encryption. - -Seems to be a bug introduced in [[!commit fbdeeeed5fa276d94be587c8916d725eddcaf546]]. Despite what the commit says, the embedded creds did get encrypted with the shared gpg key. I have reverted that commit to fix this problem. -"""]] diff --git a/doc/bugs/broken_git_annex_map_on_direct_mode.mdwn b/doc/bugs/broken_git_annex_map_on_direct_mode.mdwn deleted file mode 100644 index 40005a60a..000000000 --- a/doc/bugs/broken_git_annex_map_on_direct_mode.mdwn +++ /dev/null @@ -1,58 +0,0 @@ -### Please describe the problem. - -`git annex map` shows broken graph when direct mode is used - -### What steps will reproduce the problem? - -See transcript - -### What version of git-annex are you using? On what operating system? - -[[!format sh """ -$ git annex version -git-annex version: 5.20140107 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook external - -$ LANG=C apt-cache policy git-annex -git-annex: - Installed: 5.20140107 - Candidate: 5.20140107 - Version table: - *** 5.20140107 0 - 50 http://http.debian.net/debian/ sid/main amd64 Packages - 100 /var/lib/dpkg/status -"""]] - - -### 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 - -git init a -cd a -git annex init - -cd .. -git clone a b -cd b -git annex init - - -# OK -git annex map - -cd ../a -git annex direct -cd ../b - -# NOT OK -git annex map - -# End of transcript or log. -"""]] - -> [[fixed|done]]; thanks for a good test case. --[[Joey]] diff --git a/doc/bugs/build_fails_in_Assistant__47__WebApp__47__Gpg.hs.mdwn b/doc/bugs/build_fails_in_Assistant__47__WebApp__47__Gpg.hs.mdwn deleted file mode 100644 index 172f28143..000000000 --- a/doc/bugs/build_fails_in_Assistant__47__WebApp__47__Gpg.hs.mdwn +++ /dev/null @@ -1,57 +0,0 @@ -### Please describe the problem. - -Building from git fails in Assistant/WebApp/Gpg.hs - -### What steps will reproduce the problem? - -Follow instructions at <http://git-annex.branchable.com/install/cabal/> for building from git: - -[[!format sh """ -cabal update -PATH=$HOME/bin:$PATH -cabal install c2hs --bindir=$HOME/bin -cabal install --only-dependencies -cabal configure -cabal build -"""]] - -### What version of git-annex are you using? On what operating system? - -git master (7da58f3ebf8), openSUSE 12.3 - -### Please provide any additional information below. - -[[!format txt """ -# 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 - -Assistant/WebApp/Configurators/Fsck.hs:69:35: - Warning: This binding for `u' shadows the existing binding - bound at Assistant/WebApp/Configurators/Fsck.hs:60:17 - -Assistant/WebApp/Configurators/Fsck.hs:126:11: - Warning: This binding for `check' shadows the existing binding - imported from `Assistant.WebApp.Common' at Assistant/WebApp/Configurators/Fsck.hs:16:1 --30 - (and originally defined in `Yesod.Form.Functions') -[322 of 371] Compiling Assistant.TransferQueue ( Assistant/TransferQueue.hs, dist/build/git-annex/git --annex-tmp/Assistant/TransferQueue.o ) -[323 of 371] Compiling Assistant.Threads.Glacier ( Assistant/Threads/Glacier.hs, dist/build/git-annex -/git-annex-tmp/Assistant/Threads/Glacier.o ) -[324 of 371] Compiling Assistant.Threads.Merger ( Assistant/Threads/Merger.hs, dist/build/git-annex/g -it-annex-tmp/Assistant/Threads/Merger.o ) -[325 of 371] Compiling Assistant.Threads.Cronner ( Assistant/Threads/Cronner.hs, dist/build/git-annex -/git-annex-tmp/Assistant/Threads/Cronner.o ) -[326 of 371] Compiling Assistant.MakeRemote ( Assistant/MakeRemote.hs, dist/build/git-annex/git-annex --tmp/Assistant/MakeRemote.o ) -[327 of 371] Compiling Assistant.WebApp.Gpg ( Assistant/WebApp/Gpg.hs, dist/build/git-annex/git-annex --tmp/Assistant/WebApp/Gpg.o ) - -Assistant/WebApp/Gpg.hs:88:40: - Not in scope: type constructor or class `MonadIO' - Perhaps you meant `Monad' (imported from Assistant.WebApp.Common) - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/build_failure_with_kqueue_code__44___first_commit_that_breaks_is_3dce75fb23fca94ad86c3f0ee816bb0ad2ecb27c.mdwn b/doc/bugs/build_failure_with_kqueue_code__44___first_commit_that_breaks_is_3dce75fb23fca94ad86c3f0ee816bb0ad2ecb27c.mdwn deleted file mode 100644 index d0551c151..000000000 --- a/doc/bugs/build_failure_with_kqueue_code__44___first_commit_that_breaks_is_3dce75fb23fca94ad86c3f0ee816bb0ad2ecb27c.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -Here goes... - -<pre> -laplace:git-annex jtang$ make -ghc -O2 -threaded -Wall -ignore-package monads-fd -ignore-package monads-tf -outputdir tmp -IUtility -DWITH_ASSISTANT -DWITH_S3 -DWITH_WEBAPP -DWITH_KQUEUE -DOSX --make git-annex Utility/libdiskfree.o Utility/libmounts.o Utility/libkqueue.o - -Assistant/Threads/MountWatcher.hs:40:0: - warning: #warning Building without dbus support; will use mtab polling -[165 of 208] Compiling Assistant.Alert ( Assistant/Alert.hs, tmp/Assistant/Alert.o ) -[173 of 208] Compiling Assistant.DaemonStatus ( Assistant/DaemonStatus.hs, tmp/Assistant/DaemonStatus.o ) -[174 of 208] Compiling Assistant.TransferQueue ( Assistant/TransferQueue.hs, tmp/Assistant/TransferQueue.o ) -[175 of 208] Compiling Assistant.Threads.Watcher ( Assistant/Threads/Watcher.hs, tmp/Assistant/Threads/Watcher.o ) - -Assistant/Threads/Watcher.hs:61:43: - Couldn't match expected type `Utility.Kqueue.Kqueue' - with actual type `()' - Expected type: IO Utility.Kqueue.Kqueue -> IO Utility.Kqueue.Kqueue - Actual type: IO Utility.Kqueue.Kqueue -> IO () - In the fourth argument of `watchDir', namely `startup' - In the second argument of `($)', namely - `watchDir "." ignored hooks startup' -make: *** [git-annex] Error 1 -</pre> - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/build_issue_with_8baff14054e65ecbe801eb66786a55fa5245cb30.mdwn b/doc/bugs/build_issue_with_8baff14054e65ecbe801eb66786a55fa5245cb30.mdwn deleted file mode 100644 index 34c2eef5f..000000000 --- a/doc/bugs/build_issue_with_8baff14054e65ecbe801eb66786a55fa5245cb30.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -Building commit 8baff14054e65ecbe801eb66786a55fa5245cb30 yields this... - - -<pre> -[164 of 189] Compiling Command.Sync ( Command/Sync.hs, tmp/Command/Sync.o ) -Command/Sync.hs:268:34: -Not in scope: `vermarker' -Perhaps you meant `varmarker' (line 267) -make: *** [git-annex] Error 1 -</pre> - -Supplied fix... - -<pre> - -From a23a1af99c7a95c316a87f9c6f5f67a6f8ff6937 Mon Sep 17 00:00:00 2001 -From: Jimmy Tang <jtang@tchpc.tcd.ie> -Date: Wed, 27 Jun 2012 21:55:22 +0100 -Subject: [PATCH 14/14] fix build issue introduced in - 8baff14054e65ecbe801eb66786a55fa5245cb30 - ---- - Command/Sync.hs | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/Command/Sync.hs b/Command/Sync.hs -index b2bf24d..dfaed59 100644 ---- a/Command/Sync.hs -+++ b/Command/Sync.hs -@@ -265,7 +265,7 @@ mergeFile file key - | otherwise = go $ shortHash $ show key - where - varmarker = ".variant-" -- doubleconflict = vermarker `isSuffixOf` (dropExtension file) -+ doubleconflict = varmarker `isSuffixOf` (dropExtension file) - go v = takeDirectory file - </> dropExtension (takeFileName file) - ++ varmarker ++ v --- -1.7.11.1 -</pre> - -[[fixed|done]] diff --git a/doc/bugs/cannot_link_executable_on_android.mdwn b/doc/bugs/cannot_link_executable_on_android.mdwn deleted file mode 100644 index cb660dd9c..000000000 --- a/doc/bugs/cannot_link_executable_on_android.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. -Then starting git-annex on my Galaxy Nexus Android device, in the terminal window I get: - -[[!format sh """ -Falling back to hardcoded app location: cannot find expected files in /data/app-lib -git annex webapp -u0_a123@maguro:/sdcad/git-annex.home $ git annex webapp -CANNOT LINK EXECUTABLE: git-annex invalid R_ARM_COPY relocation against DT_SYMBOLIC shared library libc.so (built with -Bsymbolic?) -u0_a123@maguro:/sdcad/git-annex.home $ -"""]] - -### What steps will reproduce the problem? -Start git-annex. - -### What version of git-annex are you using? On what operating system? -Nightly build and release from a few days ago - 1.0.52 - -### 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. -"""]] - -> [[dup|done]] of [[git-annex_broken_on_Android_4.3]].--[[Joey]] diff --git a/doc/bugs/case-insensitive.mdwn b/doc/bugs/case-insensitive.mdwn deleted file mode 100644 index a917f64c2..000000000 --- a/doc/bugs/case-insensitive.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -What steps will reproduce the problem? - -> Building git-annex on the ghc7.0 branch on a Mac with the default case-insensitive file system - -What is the expected output? What do you see instead? - -> Expected: build successfully; instead: - - ld: duplicate symbol _UtilityziDiskFree_zdwa_info in dist/build/git-annex/git-annex-tmp/Utility/diskfree.o and dist/build/git-annex/git-annex-tmp/Utility/DiskFree.o for architecture x86_64 - -What version of git-annex are you using? On what operating system? - -> commit `0bd5c90ef0518f75d52f0c5889422d8233df847d` on a Mac OS 10.6 and 10.7, using the Haskell Platform 2012.04 - -Please provide any additional information below. - -> The problem is that since `DiskFree.hs` generates `DiskFree.o` and `diskfree.c` generates `diskfree.o`, a case-insensitive file system overwrites one object file with the other. Renaming `diskfree.c` to `diskfreec.c` and changing the corresponding filenames in `git-annex.cabal` fixes the problem. - ->> Man, not this again. The 80's called, they want their ->> unix portability wars back. [[fixed|done]]. --[[Joey]] diff --git a/doc/bugs/clean-duplicates_causes_data_loss.mdwn b/doc/bugs/clean-duplicates_causes_data_loss.mdwn deleted file mode 100644 index c5d545420..000000000 --- a/doc/bugs/clean-duplicates_causes_data_loss.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -### Please describe the problem. - -Use of git-annex import --clean-duplicates can cause data loss, where git-annex deletes content that it doesn't actually have a copy of (i.e. there is no duplicate). - -### What steps will reproduce the problem? - -I've written a quick'n'dirty test script which goes through a bunch of combinations and tests --clean-duplicates. Given an 'origin' repo containing 'a' and 'b' content and a clone of it ('import') which doesn't contain 'a' and 'b' content. - -g-a import --clean-duplicates ~/tmp/importme (containing a, b and c) into 'import' after: - - Origin is set to trusted in import, b is dropped from within origin: - b is deleted from importme even though no annexes have copies (reasonable, as origin is set to trusted and import thinks it has the content). - - Origin is set to semitrusted in import, b is dropped within origin: - b is deleted from importme even though no annexes have copies (this is most likely one to bite people). - - Origin is set to untrusted in import, b is dropped within origin: - b is deleted from importme even though no annexes have copies and git-annex has been explicitly told to not trust information about origin :( This is really surprising behaviour! - -### What version of git-annex are you using? On what operating system? - -* 5.20150409 -* Arch Linux (git-annex-bin) - -### Please provide any additional information below. - -I can provide the script if it is wanted (coded in Perl, couple of non-core dependencies). - -> Decided to go ahead and make it check remotes like drop does, so [[done]] -> --[[Joey]] diff --git a/doc/bugs/clean-duplicates_causes_data_loss/comment_1_0c5da8b1285d16967a0423a0e259e06b._comment b/doc/bugs/clean-duplicates_causes_data_loss/comment_1_0c5da8b1285d16967a0423a0e259e06b._comment deleted file mode 100644 index 689cef97a..000000000 --- a/doc/bugs/clean-duplicates_causes_data_loss/comment_1_0c5da8b1285d16967a0423a0e259e06b._comment +++ /dev/null @@ -1,36 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 1" - date="2015-04-24T11:57:35Z" - content=""" -Command to exemplify the \"worst case\" (untrusted causing deletion): - - mkdir /tmp/ga-icd - cd /tmp/ga-icd - - git init origin - cd origin - git commit -m create - git annex init origin - echo a > a - echo b > b - git annex add . - git commit -m files - - mkdir /tmp/ga-icd/importme - echo a > a - echo b > b - echo c > c - - cd /tmp/ga-icd - git clone origin import - git annex init import - -So we now have origin (with content for 2 files), import which knows origin has content for both files and directory we want to clean up. The following causes 'b' to be lost (hope you have backups!). - - cd /tmp/ga-icd/origin - git annex drop b --force - cd /tmp/ga-icd/import - git annex untrust origin - git annex import --clean-duplicates /tmp/ga-icd/importme -"""]] diff --git a/doc/bugs/clean-duplicates_causes_data_loss/comment_2_14c5c3417f107a3619a4402f75bc0002._comment b/doc/bugs/clean-duplicates_causes_data_loss/comment_2_14c5c3417f107a3619a4402f75bc0002._comment deleted file mode 100644 index c99c7699f..000000000 --- a/doc/bugs/clean-duplicates_causes_data_loss/comment_2_14c5c3417f107a3619a4402f75bc0002._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-04-29T17:18:17Z" - content=""" ---clean-duplicates is not really intended to go do a full verification -that the annexed content is present. I can see how this is surprising; -it would probably be better if it were named "--clean-seen-content" -or something like that. - -But, --deduplicate has the same behavior for such files, and I can't see a -way to rename that more effectively. - -For now I have improved the git-annex-import man page to note that -annexed content that's been removed would make a file be considered a -duplicate. -"""]] diff --git a/doc/bugs/clean-duplicates_causes_data_loss/comment_3_ed3f40b5798d9e770657e9c6b8e28039._comment b/doc/bugs/clean-duplicates_causes_data_loss/comment_3_ed3f40b5798d9e770657e9c6b8e28039._comment deleted file mode 100644 index f4c367d9c..000000000 --- a/doc/bugs/clean-duplicates_causes_data_loss/comment_3_ed3f40b5798d9e770657e9c6b8e28039._comment +++ /dev/null @@ -1,62 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 3" - date="2015-04-29T18:42:38Z" - content=""" -Well, yeah, it is quite surprising as you don't like git-annex messing about with files outside the annex, but one of the commands that does so will cause wanton destruction with barely any checks against data loss. - -Oddly, if the origin is marked as dead instead of untrusted, --clean-duplicates doesn't remove anything from /tmp/ga-icd/importme, even though 'import' still knows about the files and has enough information to delete them. Weird. - - + mkdir /tmp/ga-icd - + cd /tmp/ga-icd - + git init origin - Initialized empty Git repository in /tmp/ga-icd/origin/.git/ - + cd origin - + git commit -m create --allow-empty - [master (root-commit) 6cfdbc1] create - + git annex init origin - init origin ok - (recording state in git...) - + echo a - + echo b - + git annex add . - add a ok - add b ok - (recording state in git...) - + git commit -m files - [master 2c2ed64] files - 2 files changed, 2 insertions(+) - create mode 120000 a - create mode 120000 b - + mkdir /tmp/ga-icd/importme - + cd /tmp/ga-icd/importme - + echo a - + echo b - + echo c - + cd /tmp/ga-icd - + git clone origin import - Cloning into 'import'... - done. - + cd import - + git annex init import - init import (merging origin/git-annex into git-annex...) - ok - (recording state in git...) - + cd /tmp/ga-icd/origin - + git annex drop b --force - drop b ok - (recording state in git...) - + cd /tmp/ga-icd/import - + git annex dead origin - dead origin ok - (recording state in git...) - + git annex import --clean-duplicates /tmp/ga-icd/importme - + ls /tmp/ga-icd/import - a b - + ls /tmp/ga-icd/importme/ - a b c - -I'm think I'm just going to steer clear of it completely (and roll my own) until it is as fussy about preserving data as the rest of git-annex. - -(Also, apologies for the original name, I didn't realise it would cause any problems.) -"""]] diff --git a/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates.mdwn b/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates.mdwn deleted file mode 100644 index 70a54da85..000000000 --- a/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates.mdwn +++ /dev/null @@ -1,113 +0,0 @@ -This feels really sucky, seeing as I am the one that asked for these checks to be implemented.. - -### Please describe the problem. - ---clean-duplicates now refuses to remove a file due to not being able to verify its presence in the local repo, even though it is present in the local repo and git-annex knows it is present (whereis and fsck on the keys complete correctly). - -### What steps will reproduce the problem? - -See transcript - -### What version of git-annex are you using? On what operating system? - -git-annex versions: -* 2015-05-08 -* 2015-05-28 - -OS: Arch Linux - -### 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 - - #### gemma@spearmint (0) ~ - ## mkdir ~/tmp/annextest - mkdir: created directory ?tmp/annextest? - #### gemma@spearmint (0) ~ - ## cd ~/tmp/annextest - #### gemma@spearmint (0) ~/tmp/annextest - ## git init annex - Initialized empty Git repository in /home/gemma/tmp/annextest/annex/.git/ - #### gemma@spearmint (0) ~/tmp/annextest - ## cd annex/ - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git annex init test - init test ok - (recording state in git...) - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## echo a > a - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## echo b > b - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git annex add * - add a ok - add b ok - (recording state in git...) - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git commit -m "files" - [master (root-commit) ce31ccf] files - 2 files changed, 2 insertions(+) - create mode 120000 a - create mode 120000 b - - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## mkdir ../import - mkdir: created directory ?import? - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## cd ../import - #### gemma@spearmint (0) ~/tmp/annextest/import - ## echo b > b - #### gemma@spearmint (0) ~/tmp/annextest/import - ## echo a > a - #### gemma@spearmint (0) ~/tmp/annextest/import - ## cd ../annex - - - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git annex import --clean-duplicates ../import/ - import import/b (duplicate of SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f) (unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Could not verify that the content is still present in the annex; not removing from the import location. - failed - import import/a (duplicate of SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7) (unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Could not verify that the content is still present in the annex; not removing from the import location. - failed - git-annex: import: 2 failed - - - - - #### gemma@spearmint (1) ~/tmp/annextest/annex - ## git annex whereis --key SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f - whereis SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f (1 copy) - 8d91925d-f3d2-493b-a79b-1a18658060a1 -- test [here] - ok - - - - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git annex fsck --key SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f - fsck SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f (checksum...) - ok - (recording state in git...) - - - - #### gemma@spearmint (0) ~/tmp/annextest/annex - ## git annex import --clean-duplicates ../import/ - import import/b (duplicate of SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f) (unsafe) - Could only verify the existence of 0 out of 1 necessary copies - - Could not verify that the content is still present in the annex; not removing from the import location. - failed - -# End of transcript or log. -"""]] - -> Indeed, I seem to have broken it while refactoring. [[fixed|done]] -> --[[Joey]] diff --git a/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates/comment_1_0f30ccf6a78bdbec4d7d756d2b088036._comment b/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates/comment_1_0f30ccf6a78bdbec4d7d756d2b088036._comment deleted file mode 100644 index a1bf011f7..000000000 --- a/doc/bugs/clean-duplicates_doesn__39__t_delete_duplicates/comment_1_0f30ccf6a78bdbec4d7d756d2b088036._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 1" - date="2015-06-03T17:27:12Z" - content=""" -Thank you for fixing it so quickly! -"""]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell.mdwn b/doc/bugs/configurable_path_to_git-annex-shell.mdwn deleted file mode 100644 index af2474451..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -On one of my ssh remotes I had to install git-annex using cabal. No system-wide installation possible. Hence `git-annex` and `git-annex-shell` are not in the default `$PATH` but in `$HOME/.cabal/bin`. - -Right now the command run by git-annex when ssh'ing to a remote is hardcoded to "`git-annex-shell`", which doesn't work for me. It would be nice to be able to change this per remote, for example with an option named `annex.<remote>.annex-shell-command`. Changing "`git-annex-shell`" in `Remote/Helper/Ssh.hs` to "`~/.cabal/bin/git-annex-shell`" worked for me, but it's obviously very ugly :) - -Could you do that please? I'll try to hack it myself and send you a patch in the next few days, but I'm pretty new to Haskell so it may take me a while... Thanks! - -> [[closing|done]], see comments --[[Joey]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell/comment_1_fb6771f902b57f2b690e7cc46fdac47e._comment b/doc/bugs/configurable_path_to_git-annex-shell/comment_1_fb6771f902b57f2b690e7cc46fdac47e._comment deleted file mode 100644 index 50349363b..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell/comment_1_fb6771f902b57f2b690e7cc46fdac47e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2012-03-22T22:26:02Z" - content=""" -It doesn't need to be installed into the system PATH; just the user PATH. Which you should be able to control. - -Exactly how to do this surely varies, but here I have a `~/.bashrc` containing `PATH=$HOME/bin:$PATH; export PATH` and I keep git-annex-shell in bin and it's available to eg \"ssh mybox git-annex-shell\" -"""]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell/comment_2_2b856f4f0b65c2331be7d565f0e4e8a8._comment b/doc/bugs/configurable_path_to_git-annex-shell/comment_2_2b856f4f0b65c2331be7d565f0e4e8a8._comment deleted file mode 100644 index adea95ecf..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell/comment_2_2b856f4f0b65c2331be7d565f0e4e8a8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://schnouki.net/" - nickname="Schnouki" - subject="comment 2" - date="2012-03-23T13:27:12Z" - content=""" -Hmm, ok, solved. I'm using zsh, which is a little different: `.zshrc` is only read for interactive shells, so `ssh mybox 'echo $PATH'` displayed `/usr/bin:/bin:/usr/sbin:/sbin`. Using `.zshenv`, which is used even for non-interactive shells, did the trick. Thanks! -"""]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell/comment_3_aea42acc039a82efc6bb3a8f173a632e._comment b/doc/bugs/configurable_path_to_git-annex-shell/comment_3_aea42acc039a82efc6bb3a8f173a632e._comment deleted file mode 100644 index 399c46bc2..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell/comment_3_aea42acc039a82efc6bb3a8f173a632e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="carlo" - ip="130.102.158.18" - subject="comment 3" - date="2013-07-01T04:20:22Z" - content=""" -For anyone who comes across this, make sure that you modify your $PATH before these lines in ~/.bashrc: - - # If not running interactively, don't do anything - [ -z \"$PS1\" ] && return - -"""]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell/comment_5_178452f3c2671830d1a9f5e1d11accb4._comment b/doc/bugs/configurable_path_to_git-annex-shell/comment_5_178452f3c2671830d1a9f5e1d11accb4._comment deleted file mode 100644 index cc4742587..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell/comment_5_178452f3c2671830d1a9f5e1d11accb4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 5" - date="2014-05-27T16:13:09Z" - content=""" -See [[devblog/day_166__catching_up]] -"""]] diff --git a/doc/bugs/configurable_path_to_git-annex-shell/comment_5_77b2269936f740cacbc955b95f9da51d._comment b/doc/bugs/configurable_path_to_git-annex-shell/comment_5_77b2269936f740cacbc955b95f9da51d._comment deleted file mode 100644 index a30f2fff9..000000000 --- a/doc/bugs/configurable_path_to_git-annex-shell/comment_5_77b2269936f740cacbc955b95f9da51d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8" - nickname="Maarten" - subject="comment 5" - date="2014-05-26T11:52:27Z" - content=""" -when doing ssh host 'echo $PATH', the remote shell running the command is not an interactive shell and thus does NOT source .bashrc, neither is it a login shell and as such does not source .profile or .bash_profile. Which leaves me wondering: how does git annex log in to the remote machine to run git-annex-shell? Does it do so via an interactive shell, a login shell, or neither? Because if it does it via ssh host 'git-annex-shell', then neither .bashrc or .profile can configure its PATH. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation.mdwn b/doc/bugs/copy_fails_for_some_fails_without_explanation.mdwn deleted file mode 100644 index f4489de27..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -I have a large direct-mode repository whose files I'm trying to copy to a non-direct-mode repository. Both repositories live on an HDD attached to an rpi. - -When I do $ git annex copy --to pi dirs/to/copy, the copy starts out OK, but eventually many files fail to copy. The only diagnostic I get is "failed". Judging from the backscroll, I don't see a strong pattern to the files which fail to copy; they're kind of interspersed amongst files which were successfully copied. If I try to copy one of these failed files explicitly (git annex copy --to pi file/which/failed), this succeeds. I have plenty of free space on the disk. - -Is there a way to get more diagnostics out of git annex so I can see why these files are failing to copy? - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_10_0c1a5837305b721fc4a529cae3f4c3fb._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_10_0c1a5837305b721fc4a529cae3f4c3fb._comment deleted file mode 100644 index b0127ed82..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_10_0c1a5837305b721fc4a529cae3f4c3fb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 10" - date="2014-03-06T21:38:53Z" - content=""" -Thanks a lot, Joey. - -Compiling all of the dependencies for git-annex was taking forever on my pi, so I'll probably wait until the next release to test this out. But I'll report back here if I have any problems. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_11_dabfec2d74fb847f3b40093a2866045b._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_11_dabfec2d74fb847f3b40093a2866045b._comment deleted file mode 100644 index 09fabcf1c..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_11_dabfec2d74fb847f3b40093a2866045b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 11" - date="2014-03-10T19:20:42Z" - content=""" -Well you can always grab one of the daily builds, which include this fix. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment deleted file mode 100644 index dba07bfd5..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_1_e456604b26ed9c72b0a88cfb57f1a475._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 1" - date="2014-03-05T16:11:27Z" - content=""" -I tried git annex sync --content, and it failed to copy some files with - - git: createProcess: resource exhausted (Resource temporarily unavailable) - -So this sounds like fork is failing; I'm probably exhausting my poor pi's RAM. Maybe the same thing is happening for git annex copy. I'll run strace to see. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_2_4823d66bfb569605868af5cefe0d94dc._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_2_4823d66bfb569605868af5cefe0d94dc._comment deleted file mode 100644 index 5bcd0e92e..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_2_4823d66bfb569605868af5cefe0d94dc._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 2" - date="2014-03-05T20:31:57Z" - content=""" -How many files copied are we talking about before it begins to fail? - -You can try passing --debug, which will make git-annex show every external command it runs, which includes `cp` for a copy to another repo on the same machine. - -Might also check memory usage in top during the run. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_3_46305aa2d43da000c1a7cb003c822572._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_3_46305aa2d43da000c1a7cb003c822572._comment deleted file mode 100644 index 297c28a40..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_3_46305aa2d43da000c1a7cb003c822572._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 3" - date="2014-03-06T18:21:53Z" - content=""" -> How many files copied are we talking about before it begins to fail? - -Tens of thousands of files processed, but many of them were already on the other remote so didn't invoke cp (or anything else). ~3300 invocations of cp. - -I saved a log of ps aux, and, while the memory used by git annex remains relatively constant, I do observe /tons/ of zombie processes. 3300, actually. - -I didn't check all of them, but all of the zombie pids I checked appear to have corresponded to this command: - - /home/pi/git-annex.linux/shimmed/git/git --git-dir=/home/pi/hdd/annex/.git --work-tree=/home/pi/hdd/annex cat-file --batch - -Perhaps git annex is forgetting to reap this processes? -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_4_1dbdeded7f587e8fc2d1ac5170ecb928._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_4_1dbdeded7f587e8fc2d1ac5170ecb928._comment deleted file mode 100644 index 537736a72..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_4_1dbdeded7f587e8fc2d1ac5170ecb928._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 4" - date="2014-03-06T18:32:33Z" - content=""" -Old versions of git-annex have known bugs involving zombies. What version? -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_5_1e0c06a07345d85b3712339e6f0d9a9f._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_5_1e0c06a07345d85b3712339e6f0d9a9f._comment deleted file mode 100644 index ad2b80d66..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_5_1e0c06a07345d85b3712339e6f0d9a9f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 5" - date="2014-03-06T18:35:00Z" - content=""" -5.20140221-g1a47f5f -- I just downloaded it a week or two ago. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_6_41798e92068eb227c5e75cae2edef68a._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_6_41798e92068eb227c5e75cae2edef68a._comment deleted file mode 100644 index a0554cd8a..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_6_41798e92068eb227c5e75cae2edef68a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 6" - date="2014-03-06T18:38:43Z" - content=""" -Hmm, that version should only start git cat-file --batch a maximum of 10 times (if it is crashing for some reason), and appears to wait on the process if it does crash. And if not, should only start one. - -I think you need to post some git-annex --debug output , to show when it's running this command. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_7_1f33d694a08d8dcbf04595e3442b8cd5._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_7_1f33d694a08d8dcbf04595e3442b8cd5._comment deleted file mode 100644 index f846e290d..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_7_1f33d694a08d8dcbf04595e3442b8cd5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 7" - date="2014-03-06T18:40:26Z" - content=""" -Actually, NM, I have reproduced the bug. -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_8_884f31ce917c8e5ce9a32a55da9b42d6._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_8_884f31ce917c8e5ce9a32a55da9b42d6._comment deleted file mode 100644 index 5ba7442dc..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_8_884f31ce917c8e5ce9a32a55da9b42d6._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 8" - date="2014-03-06T20:21:16Z" - content=""" -Analysis: Remote.Git's onLocal calls Annex.new to make a new AnnexState for the local remote. This state is not cached, and is regenerated for each file. Since it runs a Annex.Branch check of the location log on the remote, it needs to start catFile, and since the state is not reused, a new CatFileHandle is allocated each time. I'm not sure, but there may have been a recent-ish change that caused the location log to get checked and so catfile to be run; the general inneficiency of making a new AnnexState each time is not new. - -Fixing this by caching the AnnexState will not only fix the resource leak, but should speed up local to local copies significantly! -"""]] diff --git a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_9_ab770dafee3bd9212f553db222adbfe6._comment b/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_9_ab770dafee3bd9212f553db222adbfe6._comment deleted file mode 100644 index e6a23eed5..000000000 --- a/doc/bugs/copy_fails_for_some_fails_without_explanation/comment_9_ab770dafee3bd9212f553db222adbfe6._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 9" - date="2014-03-06T21:17:14Z" - content=""" -Fixed in git. Also reduced the non-data-transfer work done by `git-annex copy` by around 8%. - -I'm going to move this thread to [[bugs]] so I can close it. ;) -"""]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks.mdwn b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks.mdwn deleted file mode 100644 index 81d84b300..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -When copying files to s3 using, - - git annex copy --quiet --to mys3 --fast - -No information whatsoever is printed during upload when ran without `--quite` it prints a line for each file in the repo creating page after page of output for repos with thousands of file basically no way to tell which files got uploaded. Is it possible to have a verbosity level between quite and verbose that only reports progress on actual copy/move operations. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -[[!meta title="copy --fast --to remote should be quiet when nothing to do"]] - -> [[fixed|done]]; Avoided the unnecessary output in this situation. -> --[[Joey]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_1_5f51452d939d61496e97805310746ea3._comment b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_1_5f51452d939d61496e97805310746ea3._comment deleted file mode 100644 index 07cb1b780..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_1_5f51452d939d61496e97805310746ea3._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 1" - date="2013-12-11T15:31:34Z" - content=""" -So, `git annex copy --to remote` currently does an active check that the remote has each file. This is a bit inneficient, and I have never been 100% sure that's the best thing, but from time to time I see a situation where trusting the location log when doing a `cp` would not be ideal. - -It would be easy to omit the output for files that the check finds on the remote, but I think it's good because it tells you git-annex is doing actual work. Otherwise, `git annex copy --to remote` might seem to take a long time for no reason. - -Anyway, you can disable the active check, with --fast. And I agree that in this case it would be better to not print anything. I looked at the code and it would be a little tricky to do it. - -There's a simple workaround: `git annex copy --to remote --not --in remote` -"""]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_2_2cd3e9561c4442259c765743b423a7df._comment b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_2_2cd3e9561c4442259c765743b423a7df._comment deleted file mode 100644 index cc86240f4..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_2_2cd3e9561c4442259c765743b423a7df._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" - nickname="Hamza" - subject="comment 2" - date="2013-12-11T16:18:27Z" - content=""" -Joey thanks for tip. This actually made copy operation faster than `copy --fast`, and only provides the info that I need. -"""]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9._comment b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9._comment deleted file mode 100644 index d26afbb10..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="jason@bbebec708d192ae9848ef6d0c6983e2b37127df1" - nickname="jason" - subject="--not --in doesn't work anymore" - date="2015-07-31T15:28:04Z" - content=""" -Hi, I've been happily using --to=h2 --not --in h2 for a long time, and now it fails: - - > git annex copy --to h2 --not --in h2 - Usage: git-annex copy [PATH ...] ((-f|--from REMOTE) | (-t|--to REMOTE)) - ([-A|--all] | [-U|--unused] | [--key KEY]) [-a|--auto] - zsh: exit 1 - -I've been using git-annex from debian unstable (x86) for a long time. I think it recently got a significant version upgrade. Currently I'm running: git-annex 5.20150727-2 - -I'm not married to this particular commandline, it was posted as a workaround after all. - -How can I copy files without checking if each exists on the remote, instead trusting the local cache of what the remote has? - -I have many thousands of files annexed, and this remote is a bare repo that is only accessed from this host, so the local info about what the remote has is trustworthy. -"""]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9/comment_1_8808e06ea50c8deb1226e31c40cc6703._comment b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9/comment_1_8808e06ea50c8deb1226e31c40cc6703._comment deleted file mode 100644 index f04375c9a..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_3_e1ecf85a79b7b2b21881be00a48be6c9/comment_1_8808e06ea50c8deb1226e31c40cc6703._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-31T15:31:56Z" - content=""" -That's a bug. It happens to be fixed in git head and there will be an -updated release with the fix soon. - -I appreacite you trying to find a related bug to the problem you're having, -but this bug report is not actually related, and was in fact closed in -2014. Opening a new bug report is better than commenting in the wrong -place.. -"""]] diff --git a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_4_b1cefd6259ecce0bd154c509825fb17a._comment b/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_4_b1cefd6259ecce0bd154c509825fb17a._comment deleted file mode 100644 index 265b749c0..000000000 --- a/doc/bugs/copy_to_--fast_should_not_mention_every_file_it_checks/comment_4_b1cefd6259ecce0bd154c509825fb17a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="jason@bbebec708d192ae9848ef6d0c6983e2b37127df1" - nickname="jason" - subject="Never mind" - date="2015-08-17T18:00:06Z" - content=""" -I'm writing again to confirm that this has been fixed. - -I assume it was due to a short-lived release bug that accidentally removed some copy options. -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing.mdwn b/doc/bugs/copy_unused_and_unused_not_agreeing.mdwn deleted file mode 100644 index 3790a0edf..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing.mdwn +++ /dev/null @@ -1,50 +0,0 @@ -[[!format sh """ -greg@x200s:~/Documents$ git-annex unused -unused . (checking for unused data...) (checking annex/direct/master...) (checking synced/annex/direct/master...) (checking synology/master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s16367--0b00ef0154c42a0bf94e5be8d92d8af27455d59794f26c33dfc39c09178521c9.pdf - 2 SHA256E-s84--b08e1c831863bb43c02158bd5e8f3f5416c3a5203d89fa94a22149460142c273.odt - 3 SHA256E-s84--ec4caae451180a29721f2b6667eec8ec80eaa724f0727cf99d2bb21bf9218e9d.odt - ... - 88 SHA256E-s84--710d69bef61674b04974ac550d713e5928563b2a12b902b64fe451705b967452.doc - 89 SHA256E-s3830--1348d6248e35625da3e22f73d2a0017185bb5e1aa37f65bbca5dfcb3c7f53034 - 90 SHA256E-s119822--7c1b53ab6402b8835473f0b5c326f3cc300ac9372be79694942c1efa4bcdc621.pdf - 91 SHA256E-s84--63b6188696795885ff6570a76a3a74799396787f7058cbcfd4a2c40b22982420.odt - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -greg@x200s:~/Documents$ git-annex copy --unused --to synology -"""]] - -Is that correct behavior? I would assume the last command would at least run through the 91 files and check my synology remote that they are there. Like this repo did: - -[[!format sh """ -$ git-annex unused -unused . (checking for unused data...) (checking master...) (checking 60justin/master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s9390266--7ed16c9423b331dbe63bb3b4278b8c94a6754a07177c53fceb3b24e9610e8054.NEF - 2 SHA256E-s10435713--49cbfe8466eada2c3787c9a7e158a7dfb9845a0aa8ef862ed2578b59c889dc4d.NEF - 3 SHA256E-s9442044--85c314e318f643237df5e3adf7559e9bf268ee28f1f92d4102161865323ddeb6.NEF - 4 SHA256E-s290672--c5822c3ef16bd62b5752b2dace81182ce00d64bd4d2d994ba93e3cb94e645708.JPG - 5 SHA256E-s293288--30f1367fc326f7b053012818863151206f9e3ddeab3c3fc5b5c1c573d120d50a.JPG - 6 SHA256E-s3672986--be960f6dc247df2496f634f7d788bd4a180fe556230e2dafc23ebc8fc1f10af3.JPG - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -$ git-annex copy --unused --to synology -copy SHA256E-s9390266--7ed16c9423b331dbe63bb3b4278b8c94a6754a07177c53fceb3b24e9610e8054.NEF (checking synology...) ok -copy SHA256E-s10435713--49cbfe8466eada2c3787c9a7e158a7dfb9845a0aa8ef862ed2578b59c889dc4d.NEF (checking synology...) ok -copy SHA256E-s9442044--85c314e318f643237df5e3adf7559e9bf268ee28f1f92d4102161865323ddeb6.NEF (checking synology...) ok -copy SHA256E-s290672--c5822c3ef16bd62b5752b2dace81182ce00d64bd4d2d994ba93e3cb94e645708.JPG (checking synology...) ok -copy SHA256E-s293288--30f1367fc326f7b053012818863151206f9e3ddeab3c3fc5b5c1c573d120d50a.JPG (checking synology...) ok -copy SHA256E-s3672986--be960f6dc247df2496f634f7d788bd4a180fe556230e2dafc23ebc8fc1f10af3.JPG (checking synology...) ok -$ -"""]] - -> [[fixed|done]] per my comment --[[Joey]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_1_a11a45868867361fcff61471ffe0ce39._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_1_a11a45868867361fcff61471ffe0ce39._comment deleted file mode 100644 index cedc0f7f9..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_1_a11a45868867361fcff61471ffe0ce39._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="indirect vs direct" - date="2014-02-20T06:25:31Z" - content=""" -Aha! The issue is that the first repo (the one not copying unused files to synology) was in direct mode. I switched it to indirect and not only are there now a lot more files listed in unused, but copy --unused is working as expected. - -Should there be a warning in git-annex unused when in direct mode about this? I'm not exactly sure what is happening (not sure why the number of unused would go up from 91 to 296). -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_2_15559ba19393f5c061f77bc56379f8e1._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_2_15559ba19393f5c061f77bc56379f8e1._comment deleted file mode 100644 index a3a3c119f..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_2_15559ba19393f5c061f77bc56379f8e1._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="Could I get a "version", brethren?" - date="2014-02-20T17:58:32Z" - content=""" -I think there are two bugs here. I just reproduced and fixed a bug that would caused `git annex unused` to sometimes not notice certain unused keys when in direct mode. That's why the number you were finding in direct and indirect was different. - -That does not explain why `copy --unused` would not operate on unused files when in direct mode. A problem I have not managed to reproduce.. - -There was a recent change to the format of the .git/annex/unused.log, which temporarily broke reading it (fixed in 5.20140210). This could be some version skew problem, as while the new git-annex version can read the old log format, the old git-annex version will ignore the new log format. -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_3_9b1340e0f6a107695849c04374aaeae2._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_3_9b1340e0f6a107695849c04374aaeae2._comment deleted file mode 100644 index 4fb2b3d39..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_3_9b1340e0f6a107695849c04374aaeae2._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 3" - date="2014-02-20T19:31:56Z" - content=""" -heh, I *just* dist-upgraded this morning on the box that was showing the problem from git-annex_5.20140127_amd64.deb to git-annex_5.20140210_amd64.deb. So what you say is probably right (re unused.log). - -The only other annex I have in direct mode right now is one that I also am using the standalone build with (version 5.20131224-g6ca5271 right now). It has unused content in it (in fact, it's the synology annex, where I'm moving all the unused data to). I can do testing there if needed (and since it's a standalone build, it's easy for me to switch around git-annex versions with symlinks). The only problem is that it is dog slow when running git-annex unused. :) -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_4_b88530080fd90686cfa7e336f8328dcb._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_4_b88530080fd90686cfa7e336f8328dcb._comment deleted file mode 100644 index 9deb87d24..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_4_b88530080fd90686cfa7e336f8328dcb._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 4" - date="2014-02-20T19:49:21Z" - content=""" -Well, if you had a newer git-annex than 5.20140127 temporarily in path, it would certianly explain it. I have tested --unused in direct mode and am not seeing any problems. -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment deleted file mode 100644 index d5e56151d..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_5_792ab128a91c66e4ddeaa69d09430a78._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!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. -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment deleted file mode 100644 index eae21f79d..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_6_e44a16ef3358a6fbcc6ed6b3a31f3273._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!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. -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment deleted file mode 100644 index 52cfc575c..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_7_635acd64b524c682c58f26ae96ae0d7d._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!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/` -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_8_1aaeb808e20c67f89eaac5e45d9309f0._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_8_1aaeb808e20c67f89eaac5e45d9309f0._comment deleted file mode 100644 index 3480ffa7e..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_8_1aaeb808e20c67f89eaac5e45d9309f0._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 8" - date="2014-03-06T18:54:08Z" - content=""" -The last key listed by unused (111 of 111): - -[[!format sh \"\"\" -greg@x200s:~/Documents/.git/annex/objects/q4/22/SHA256E-s12289--68a93144e03274664d50754882bdaf196134e06ec2b912157bdccae436d577d6.ods$ ls -SHA256E-s12289--68a93144e03274664d50754882bdaf196134e06ec2b912157bdccae436d577d6.ods.cache -SHA256E-s12289--68a93144e03274664d50754882bdaf196134e06ec2b912157bdccae436d577d6.ods.map -greg@x200s:~/Documents/.git/annex/objects/q4/22/SHA256E-s12289--68a93144e03274664d50754882bdaf196134e06ec2b912157bdccae436d577d6.ods$ -\"\"\"]] -"""]] diff --git a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_9_6abca5f4927e09089cdc5f0bd27b798f._comment b/doc/bugs/copy_unused_and_unused_not_agreeing/comment_9_6abca5f4927e09089cdc5f0bd27b798f._comment deleted file mode 100644 index 25edfd5ed..000000000 --- a/doc/bugs/copy_unused_and_unused_not_agreeing/comment_9_6abca5f4927e09089cdc5f0bd27b798f._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="analysis" - date="2014-03-06T21:37:15Z" - content=""" -[[!format haskell \"\"\" - {- In indirect mode, look for the key. In direct mode, - - the inode cache file is only present when a key's content - - is present, so can be used as a surrogate if the content - - is not located in the annex directory. -} -\"\"\"]] - -Seems that is wrong. - -I think that comment was based on removeAnnex calling removeInodeCache, which it does do. -And that is, afaik, the only point in git-annex where content files are removed from the annex. - -However, in direct mode, removeAnnex is not the only way to delete a key's content -- the user can simply delete the file! -(Or a disk error could put it in lost+found, or whatever.) - -That leaves the inode cache file present. unused will then behave as you describe. Also, uninit throws an ugly warning message -due to getKeysPresent giving it bad data. The only other caller of getKeysPresent is info, which will also operate on bad data and so generate slightly wrong stats. - -I'm leaning toward making getKeysPresent do a full check of the cache and map, checking that the work tree still contains a key's content. This will make it somewhat slower (by 2 file reads and a stat() per key). So it would make sense to make a variant that only lists keys with content present in .git/annex/objects/. That could be used by `unused`, since by definition unused keys cannot have their content located in the work tree, so must have it in the object directory. uninit could also use it, since it's only interested in cleaning out .git/annex/objects. Only `info` will be slowed down. -"""]] diff --git a/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn b/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn deleted file mode 100644 index c017cf1a6..000000000 --- a/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn +++ /dev/null @@ -1,77 +0,0 @@ -### Please describe the problem. - -While the assistant is synchronizing (to local USB backup disks or remote repositories) I am continually prompted for GPG passphrase when it is most definitely already in the gpg-agent. - -### What steps will reproduce the problem? - -Set up some remote gcrypt repositores using an existing GPG key, add some files, use the system, you are prompted for the passphrase far more often than the timeout of the passphrase in the agent (every few minutes). The number of times you are prompted also seems to increase linearly with the number of repositories - I am guessing they all exhibit the same need for the passphrase and all request at once, resulting in a string of 10+ pinentry popups. - -I am wondering if there is something specific in my gpg setup that git annex isn't expecting. Always encrypt to self? Signing subkeys? Either way, standard tools manage to call gpg to encrypt/decrypt using gpg-agent and not prompting for the passphrase, so git annex should be able to as well. - -### What version of git-annex are you using? On what operating system? - -Arch Linux, 5.20140831-g62e6ad8 - -### Please provide any additional information below. - -I have read the various discussions about using -R or -r for the recipients, and I can see in the logs that -r is being used, but there is definitely something not working correctly. At the same time that git annex is making a gpg-agent request that results in a passphrase request, I can encrypt and decrypt whatever files I want manually with no prompting. - -[[!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 - -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gcrypt: Decrypting manifest -gpg: anonymous recipient; trying secret key 7426266D ... -gpg: anonymous recipient; trying secret key 7426266D ... -gpg: okay, we are the anonymous recipient. -gpg: Signature made Thu 11 Sep 2014 06:21:58 BST using RSA key ID AC305414 -gpg: Good signature from "user <XXXXXX>" [ultimate] -gpg: aka "[jpeg image of size 2004]" [ultimate] -gpg: okay, we are the anonymous recipient. -gpg: Signature made Thu 11 Sep 2014 06:21:58 BST using RSA key ID AC305414 -gpg: Good signature from "user <XXXXXX>" [ultimate] -gpg: aka "[jpeg image of size 2004]" [ultimate] -gcrypt: WARNING: -gcrypt: WARNING: Remote ID has changed! -gcrypt: WARNING: from :id:QydYJR8dPq7y7kMUQDG1 -gcrypt: WARNING: to :id:gU3sc34/rhmta4xfSm3O -gcrypt: WARNING: -gcrypt: Encrypting to: -r 49AFD42BB9E8CD9D -gcrypt: Requesting manifest signature -gcrypt: Encrypting to: -r 49AFD42BB9E8CD9D -gcrypt: Requesting manifest signature -gcrypt: Decrypting manifest -gpg: anonymous recipient; trying secret key 7426266D ... -gpg: okay, we are the anonymous recipient. -gpg: Signature made Thu 11 Sep 2014 06:22:58 BST using RSA key ID AC305414 -gpg: Good signature from "user <XXXXXXX>" [ultimate] -gpg: aka "[jpeg image of size 2004]" [ultimate] -gcrypt: Encrypting to: -r 49AFD42BB9E8CD9D -gcrypt: Requesting manifest signature -gpg: cancelled by user -gpg: skipped "49AFD42BB9E8CD9D": Operation cancelled -gpg: [stdin]: sign+encrypt failed: Operation cancelled -error: failed to push some refs to 'gcrypt::/autofs/ext/wdpassport0/annexes/user/docs' -[2014-09-11 06:36:18 BST] read: git ["--git-dir=/home/user/docs/.git","--work-tree=/home/user/docs","-c","core.bare=false","push","wdpassport0","master"] -... - -# End of transcript or log. -"""]] - -The section above I clicked cancel on the pinentry dialog as can be seen. The question is, why was it asking me anyway? - -> gpg: anonymous recipient; trying secret key 7426266D ... -> -> That means that you have git-remote-gcrypt configured to use anonymous -> recipients. This causes gpg to try a bunch of gpg keys until it finds one -> that works, rather than immediately trying the right key. -> -> I modified git-remote-gcrypt in July so you can configure -> gcrypt.publish-participants to avoid this problem. -> -> There may also be a local confguration problem; I don't know. In any -> case, it's not git-annex responsible, but git-remote-gcrypt. [[done]] --[[Joey]] diff --git a/doc/bugs/creds_directory_not_automatically_created.mdwn b/doc/bugs/creds_directory_not_automatically_created.mdwn deleted file mode 100644 index d4e436da4..000000000 --- a/doc/bugs/creds_directory_not_automatically_created.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -I just compiled ff7810eb83d8372e6206d487c63482d678e0b3d4 and created a new git-annex repository through the setup steps of "git-annex webapp". Then I tried configuring a Jabber account from the webapp. It then failed to create $REPO/.git/annex/creds/xmpp with a "No such file or directory" message because $REPO/.git/annex/creds did not get created. After doing a manual mkdir the Jabber setup went through fine. - -> [[Fixed|done]], thanks. --[[Joey]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__.mdwn b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__.mdwn deleted file mode 100644 index a7b634554..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -### Please describe the problem. - -Was trying to create a prelim package for datalad but unittests failed. Apparently under cowbuilder (I guess it is the culprit) annex decides that the filesystem is crippled. Looking at the code, annex does two tests: - -1. either it can create a symlink (which it should be able to -- I can create symlinks no problem there) -2. either it can't write to a file with write permissions removed - -But that is where I am getting confused ;) since it seems that I can write to a file, when write permissions were removed, if I am root (that is how package is built in that chroot): - -[[!format sh """ -root@hopa:/tmp# echo 123 > 123; chmod a-w 123; echo "add" >> 123; -root@hopa:/tmp# echo $? -0 -root@hopa:/tmp# cat 123 -123 -add -root@hopa:/tmp# ls -ld 123 --r-------- 1 root root 8 Aug 17 07:32 123 -root@hopa:/tmp# python -c 'open("123", "w")' -root@hopa:/tmp# python -c 'open("123", "w").write("asdf")' -root@hopa:/tmp# cat 123 -asdfroot@hopa:/tmp# - -"""]] - -but annex doesn't detect file system as crippled when merely in a root session. So I guess there is something more to it (cowbuilder?) - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - -Debian sid 5.20150812-2 - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] - - diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_1_82480202831a08388f9f716abfaa0340._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_1_82480202831a08388f9f716abfaa0340._comment deleted file mode 100644 index 237418506..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_1_82480202831a08388f9f716abfaa0340._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-08-19T16:22:31Z" - content=""" -Actually, it does detect a crippled FS when run as root here. I guess you -had some version confusion going on, since this problem was introduced in a -recent release. Fixing.. -"""]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_2_6d63ac06a231ec5c03d6c9b62b261131._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_2_6d63ac06a231ec5c03d6c9b62b261131._comment deleted file mode 100644 index 57e5ec71a..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_2_6d63ac06a231ec5c03d6c9b62b261131._comment +++ /dev/null @@ -1,54 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="I don't think it is fixed -- doesn't detect as crippled when ran as root (under sudo or su) with 5.20150826+gitg87972f5-1~ndall+1" - date="2015-09-02T17:12:48Z" - content=""" -[[!format bash \"\"\" -$> git annex version -git-annex version: 5.20150826+gitg87972f5-1~ndall+1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA Database -key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -\"\"\"]] - -so if running as non-root, I can't indeed remove the file and annex doesn't detect it as crippled: - -[[!format bash \"\"\" -$> bash -c \"rm -rf /tmp/123; mkdir /tmp/123; cd /tmp/123; git init; git annex init; echo 123 > 1.dat; git annex add 1.dat; git commit -m 'initial'; ls -l /tmp/123 ;readlink -f /tmp/123/1.dat | xargs rm; rm -rf /tmp/123; ls -l /tmp/123\" -rm: cannot remove ‘/tmp/123/.git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat’: Permission denied -mkdir: cannot create directory ‘/tmp/123’: File exists -Initialized empty Git repository in /tmp/123/.git/ -init ok -(recording state in git...) -add 1.dat ok -(recording state in git...) -[master (root-commit) b94089e] initial - 1 file changed, 1 insertion(+) - create mode 120000 1.dat -total 4 -lrwxrwxrwx 1 yoh yoh 186 Sep 2 13:06 1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -rm: cannot remove ‘/tmp/123/.git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat’: Permission denied -rm: cannot remove ‘/tmp/123/.git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat’: Permission denied -total 0 -\"\"\"]] - -if ran under sudo or even straight root (via su) I can remove the file, and entire directory, and annex didn't detect it as crippled - -[[!format bash \"\"\" -$> sudo -E bash -c \"rm -rf /tmp/123; mkdir /tmp/123; cd /tmp/123; git init; git annex init; echo 123 > 1.dat; git annex add 1.dat; git commit -m 'initial'; ls -l /tmp/123 ;readlink -f /tmp/123/1.dat | xargs rm; rm -rf /tmp/123; ls -l /tmp/123\" -Initialized empty Git repository in /tmp/123/.git/ -init ok -(recording state in git...) -add 1.dat ok -(recording state in git...) -[master (root-commit) 44f142c] initial - 1 file changed, 1 insertion(+) - create mode 120000 1.dat -total 4 -lrwxrwxrwx 1 root root 186 Sep 2 13:06 1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -ls: cannot access /tmp/123: No such file or directory -\"\"\"]] -"""]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_3_0ee5eafbd4bcaf59d4530d0603ef0281._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_3_0ee5eafbd4bcaf59d4530d0603ef0281._comment deleted file mode 100644 index 5014f9368..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_3_0ee5eafbd4bcaf59d4530d0603ef0281._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 3" - date="2015-09-02T18:54:23Z" - content=""" -Of course root can delete anything no matter what git-annex does with directory permissions. This does not mean the FS is crippled; it's just an ability of the root user. I don't see any problem with the examples given above. -"""]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_4_9bfddab898d96639c426218dc58aa786._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_4_9bfddab898d96639c426218dc58aa786._comment deleted file mode 100644 index 1e5074404..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_4_9bfddab898d96639c426218dc58aa786._comment +++ /dev/null @@ -1,72 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="comment 4" - date="2015-09-02T19:14:18Z" - content=""" -I am confused then. You said - -> it does detect a crippled FS when run as root here. - -which I took as the indication that on any FS if ran as root annex would detect it as \"crippled\" since then user (root) has ability to change even read only files/directories (thus removal was to demonstrate ability to overcome permissions protection). Was I wrong? - -Here is redone script which instead of removing augments the file... and again annex doesn't consider file system crippled while I can augment file inplace - -[[!format bash \"\"\" -$> cat /tmp/test-crippled.sh -#!/bin/bash - -rm -rf /tmp/123; -mkdir /tmp/123; -cd /tmp/123; -git init; git annex init; -echo 123 > 1.dat; -git annex add 1.dat; -git commit -m 'initial'; -ls -l /tmp/123 ; - -ff=$(readlink /tmp/123/1.dat) -echo cripple >> /tmp/123/1.dat && echo CRIPPLED - -echo \"new content: \" -cat /tmp/123/1.dat -ls -l /tmp/123/1.dat -rm -rf /tmp/123 - - -# sudo run -$> sudo /tmp/test-crippled.sh -Initialized empty Git repository in /tmp/123/.git/ -init ok -(recording state in git...) -add 1.dat ok -(recording state in git...) -[master (root-commit) 01ffc3b] initial - 1 file changed, 1 insertion(+) - create mode 120000 1.dat -total 4 -lrwxrwxrwx 1 root root 186 Sep 2 15:10 1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -CRIPPLED -new content: -123 -cripple -lrwxrwxrwx 1 root root 186 Sep 2 15:10 /tmp/123/1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat - -# normal run -$> /tmp/test-crippled.sh -Initialized empty Git repository in /tmp/123/.git/ -init ok -(recording state in git...) -add 1.dat ok -(recording state in git...) -[master (root-commit) 74a1759] initial - 1 file changed, 1 insertion(+) - create mode 120000 1.dat -total 4 -lrwxrwxrwx 1 yoh yoh 186 Sep 2 15:10 1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -/tmp/test-crippled.sh: line 13: /tmp/123/1.dat: Permission denied -new content: -123 -lrwxrwxrwx 1 yoh yoh 186 Sep 2 15:10 /tmp/123/1.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -rm: cannot remove ‘/tmp/123/.git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat’: Permission denied -\"\"\"]] -"""]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_5_4d04acb0afc055fd7c5135746aee8747._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_5_4d04acb0afc055fd7c5135746aee8747._comment deleted file mode 100644 index 5a8daebfe..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_5_4d04acb0afc055fd7c5135746aee8747._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 5" - date="2015-09-02T21:05:09Z" - content=""" -Accidentially detecting a cripped FS when ran as root was a bug, which is why this bug report was filed. After reproducing it, I fixed it, in [[!commit c242e248e8ef350f7ab2474583b3f3d197c4ce4d]] -"""]] diff --git a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_6_939f40d1dc9f5c68597391054ed353cf._comment b/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_6_939f40d1dc9f5c68597391054ed353cf._comment deleted file mode 100644 index 44b2df2c4..000000000 --- a/doc/bugs/decides_that_FS_is_crippled_under_cowbuilder___40__symlinks_supported_etc__41__/comment_6_939f40d1dc9f5c68597391054ed353cf._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="thanks for the explanation" - date="2015-09-03T00:55:38Z" - content=""" -Thanks for chewing it up for me. So FS is not considered crippled even if you can commit a crime as a privileged user. I will mark it back now as fixed ;) -"""]] diff --git a/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn b/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn deleted file mode 100644 index a705e434f..000000000 --- a/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -I ran the assistant in a subdir in direct mode, and it seemed to move files from other places outside that subdir -into it, and commit them there. These may have been files that needed to be committed, and it just staged them to the wrong place. - -I'm pretty sure this does not affect indirect mode. - ---[[Joey]] - -The relevant commit, in my family's annex is -22e694549d698922389deb017c39c2b40371cdf0 --[[Joey]] - -Was able to reproduce this as follows: - -1. Make 2 repositories A and B, with B in direct mode. -2. In A, touch topfile; git annex add topfile; git annex sync -3. In B: mkdir subdir; cd subdir; git annex assistant - -Result is a subdir/topfile appearing in B, which is wrong. - -<pre> - subdir/topfile | 1 + - topfile | 1 - -</pre> - -Note that manually doing a git-annex sync in B's subdir does not cause this -to happen. It's specific to the assistant somehow. - ---[[Joey]] - -Before 2407170eaf78d9aa38d73d1af68c20da9882779b, git-annex sync in a subdir -had the same problem. That made it always run from the top of the work -tree, which its code actually assumes is the case. - -The assistant, however, does not do that, and it's useful in general to -only run it in a subdir. - -> Made sync merge code handle this correctly. Conflicted merge handing code -> was already ok. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/direct_mode_assistant_in_subdir_confusion/comment_1_351143deec29e712f8718a373ad650d7._comment b/doc/bugs/direct_mode_assistant_in_subdir_confusion/comment_1_351143deec29e712f8718a373ad650d7._comment deleted file mode 100644 index aa134bd8e..000000000 --- a/doc/bugs/direct_mode_assistant_in_subdir_confusion/comment_1_351143deec29e712f8718a373ad650d7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.108.145" - subject="comment 1" - date="2013-08-03T20:15:17Z" - content=""" -Only seems to affect initial startup scan; files added outside the subdir after it was started up were not committed (which is the desired behavior when running the webapp in a subdir). -"""]] diff --git a/doc/bugs/direct_mode_merge_can_overwrite_local__44___non-annexed_files.mdwn b/doc/bugs/direct_mode_merge_can_overwrite_local__44___non-annexed_files.mdwn deleted file mode 100644 index 081dd414b..000000000 --- a/doc/bugs/direct_mode_merge_can_overwrite_local__44___non-annexed_files.mdwn +++ /dev/null @@ -1,14 +0,0 @@ -Direct mode merge handles the case where there's a conflict between local and remote files, that are checked into git. - -However, the the local file (or directory, or symlink, whatever) -is not checked into git, the merge will overwrite it with the remote file from git. - -> That's fixed; now this is detected and the local variant -> is renamed with ".variant-local", and possibly a number to make it -> unique. - -New problem: If the merge pulls in a directory, and a file exists with -the name of the directory, locally, not annexed, the file is left alone, -but the directory is thus not checked out, and will be deleted on commit. - -> [[fixed|done]]; regression test in place. --[[Joey]] diff --git a/doc/bugs/direct_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn b/doc/bugs/direct_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn deleted file mode 100644 index 1afb9ac14..000000000 --- a/doc/bugs/direct_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. - -git-annex attempts to create files with question marks in them on my direct repository on a FAT32 drive. This fails. - -### What steps will reproduce the problem? - -git annex addurl 'http://rf.proxycast.org/m/media/273073201426.mp3?c=culture&p=La+t%C3%AAte+au+carr%C3%A9_10212&l3=20131002&l4=&media_url=http%3A%2F%2Fmedia.radiofrance-podcast.net%2Fpodcast09%2F10212-02.10.2013-ITEMA_20531825-0.mp3' - -### What version of git-annex are you using? On what operating system? - -[[!format sh """ -$ cat /etc/lsb-release -DISTRIB_ID=Ubuntu -DISTRIB_RELEASE=12.04 -DISTRIB_CODENAME=precise -DISTRIB_DESCRIPTION="Ubuntu 12.04.3 LTS" - -$ git annex version -git-annex version: 4.20130922-g7dc188a -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi -local repository version: 4 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -"""]] - -### 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 - -$ git annex addurl 'http://rf.proxycast.org/m/media/273073201426.mp3?c=culture&p=La+t%C3%AAte+au+carr%C3%A9_10212&l3=20131002&l4=&media_url=http%3A%2F%2Fmedia.radiofrance-podcast.net%2Fpodcast09%2F10212-02.10.2013-ITEMA_20531825-0.mp3' -addurl rf.proxycast.org_m_media_273073201426.mp3_c=culture&p=La+t%C3%AAte+au+carr%C3%A9_10212&l3=20131002&l4=&media_url=http%3A%2F%2Fmedia.radiofrance-podcast.net%2Fpodcast09%2F10212-02.10.2013-ITEMA_20531825-0.mp3 (downloading http://rf.proxycast.org/m/media/273073201426.mp3?c=culture&p=La+t%C3%AAte+au+carr%C3%A9_10212&l3=20131002&l4=&media_url=http%3A%2F%2Fmedia.radiofrance-podcast.net%2Fpodcast09%2F10212-02.10.2013-ITEMA_20531825-0.mp3 ...) -/media/sixtyfour/audio/.git/annex/tmp/URL--http&c%%rf.proxycast.org%m%media%273073201426.mp3?c=culture&ap=La+t&sC3&sAAte+au+carr&sC3&sA9_10212&al3=20131002&al4=&amedia_url=http&s3A-86e83c2aaa925b3bc337c1d6a27bd300: Argument invalide - -git-annex: /media/sixtyfour/audio/.git/annex/transfer/failed/download/00000000-0000-0000-0000-000000000001/URL--http&c%%rf.proxycast.org%m%media%273073201426.mp3?c=culture&ap=La+t&sC3&sAAte+au+carr&sC3&sA9_10212&al3=20131002&al4=&amedia_url=http&s3A-86e83c2aaa925b3bc337c1d6a27bd300: openFile: invalid argument (Invalid argument) -failed -git-annex: addurl: 1 failed - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/dolphin_integration_file_is_broken.mdwn b/doc/bugs/dolphin_integration_file_is_broken.mdwn deleted file mode 100644 index 2f2fc1c4e..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -git annex will automatically create the file - -.kde/share/kde4/services/ServiceMenus/git-annex.desktop - -However the actions created do not work because the variable used is %U (file:/// style URL) which git annex does not understand. - -According to http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s06.html - -Also the escaping seems broken. The following line is one that works for me. - - Exec=sh -c 'cd "$(dirname -- "$1")" && git-annex get --notify-start --notify-finish -- "$1"' command_string_is_ignored %f - -or simply - - Exec=git-annex get --notify-start --notify-finish -- %F - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - -5.20141125 - -### 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. -"""]] - -> [[fixed|done]]; confirmed the new version still works on filenames with -> spaces in them. --[[Joey]] diff --git a/doc/bugs/dolphin_integration_file_is_broken/comment_1_65c4fd7547be9c16abadaf5fc9d0b793._comment b/doc/bugs/dolphin_integration_file_is_broken/comment_1_65c4fd7547be9c16abadaf5fc9d0b793._comment deleted file mode 100644 index 15077277e..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken/comment_1_65c4fd7547be9c16abadaf5fc9d0b793._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-29T16:49:22Z" - content=""" -You forgot to say what version of dolphin you are having trouble with. -I've tested it working with version 4.14.2. - -I don't understand what the "command_string_is_ignored" in your example -is supposed to do, or why you'd not want to quote the filename. -"""]] diff --git a/doc/bugs/dolphin_integration_file_is_broken/comment_2_237fdaddaa80c1e4d262d724d9aed82b._comment b/doc/bugs/dolphin_integration_file_is_broken/comment_2_237fdaddaa80c1e4d262d724d9aed82b._comment deleted file mode 100644 index 3dcaa7c21..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken/comment_2_237fdaddaa80c1e4d262d724d9aed82b._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="silvio" - subject="comment 2" - date="2015-04-29T19:24:55Z" - content=""" -I currently use dolphin Version 14.12.3 but it's been broken for me forever. I always had my own fix but now it keeps getting overwritten by git-annex. - -the current line in my git-annex version is: - -sh -c 'cd \"$(dirname '%U')\" && git-annex get --notify-start --notify-finish -- %U' - -The problem is that %U gives an url style file (file:///some/path) which git-annex doesn't understand. - -Further more the quoting is broken because and i quote: - -\"Field codes (%F,%U) must not be used inside a quoted argument, the result of field code expansion inside a quoted argument is undefined.\" - -Additionally I don't think it's possible to prevent an arbitrary command injection unless you have the Field code as a single argument. - -The command_string_is_ignored is just the string that will be assigned to $0 which is not used. You could use it instead of $1 but didn't like using the command string as an argument. -"""]] diff --git a/doc/bugs/dolphin_integration_file_is_broken/comment_3_89c166c4e44380b8f354f2c6b5e42fad._comment b/doc/bugs/dolphin_integration_file_is_broken/comment_3_89c166c4e44380b8f354f2c6b5e42fad._comment deleted file mode 100644 index fdbc3beb1..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken/comment_3_89c166c4e44380b8f354f2c6b5e42fad._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-04-29T19:37:42Z" - content=""" -So a much newer version than the one in Debian yet.. - -I tried your command line with the old version in Debian, and it seems to -work ok, so thanks for the improvement! -"""]] diff --git a/doc/bugs/dolphin_integration_file_is_broken/comment_3_f7624258e8c2269f3ccdab683df8bb3d._comment b/doc/bugs/dolphin_integration_file_is_broken/comment_3_f7624258e8c2269f3ccdab683df8bb3d._comment deleted file mode 100644 index a6437e470..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken/comment_3_f7624258e8c2269f3ccdab683df8bb3d._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="silvio" - subject="comment 3" - date="2015-04-29T19:39:33Z" - content=""" -Also %U gives a list of urls and basename of a list doesn't give back anything useful. I don't see how this could possibly work for you. -"""]] diff --git a/doc/bugs/dolphin_integration_file_is_broken/comment_4_3e12372915c4c72b05db2a1c28a9daf7._comment b/doc/bugs/dolphin_integration_file_is_broken/comment_4_3e12372915c4c72b05db2a1c28a9daf7._comment deleted file mode 100644 index 783fd6cb1..000000000 --- a/doc/bugs/dolphin_integration_file_is_broken/comment_4_3e12372915c4c72b05db2a1c28a9daf7._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="silvio" - subject="comment 4" - date="2015-04-29T19:47:21Z" - content=""" -sorry for so many posts :) - -As for not quoting the file name I think it doesn't need to be. It will still be just one argument. Exec doesn't work like sh. The standard doesn't mention anything about single quote quoting either but it seems to work and there is no good alternative. -"""]] diff --git a/doc/bugs/downloads_load___40__from_url__41___to_incorrect_directory_in_a_submodule.mdwn b/doc/bugs/downloads_load___40__from_url__41___to_incorrect_directory_in_a_submodule.mdwn deleted file mode 100644 index 7b219e926..000000000 --- a/doc/bugs/downloads_load___40__from_url__41___to_incorrect_directory_in_a_submodule.mdwn +++ /dev/null @@ -1,59 +0,0 @@ -### Please describe the problem. - -downloads load to under parent's repository .git/ directory, thus making it unreachable since original symlinks would point within current directory (rightfully) - -### What version of git-annex are you using? On what operating system? - -Debian jessie/sid -- see transcript - -### Please provide any additional information below. - -[[!format sh """ - -> git clone --recurse git://github.com/yarikoptic/datalad -b nf-test-repos -... -> cd datalad/datalad/tests/testrepos/basic/r1 -> ls -l test-annex.dat -lrwxrwxrwx 1 yoh yoh 186 Feb 23 15:56 test-annex.dat -> .git/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat -> git co master -Switched to branch 'master' - -$> git annex get test-annex.dat -(merging origin/git-annex into git-annex...) -(recording state in git...) -get test-annex.dat (from web...) -../../../../../.git/modules/datalad/te 100%[=============================================================================>] 4 --.-KB/s in 0s -ok -(recording state in git...) - -# indeed upstairs -$> ls -l ../../../../../.git/modules/datalad/tests/testrepos/modules/basic/r1/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca -38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat --r-------- 1 yoh yoh 4 Feb 23 15:57 ../../../../../.git/modules/datalad/tests/testrepos/modules/basic/r1/annex/objects/zk/71/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat/SHA256E-s4--181210f8f9c779c26da1d9b2075bde0127302ee0e3fca38c9a83f5b1dd8e5d3b.dat - -$> acpolicy git-annex -git-annex: - Installed: 5.20150205+git57-gc05b522-1~nd80+1 - Candidate: 5.20150205+git57-gc05b522-1~nd1 - Version table: - *** 5.20150205+git57-gc05b522-1~nd80+1 0 - 500 http://neuro.debian.net/debian-devel/ jessie/main amd64 Packages - 100 /var/lib/dpkg/status - -$> acpolicy git -git: - Installed: 1:2.1.4-2.1 - Candidate: 1:2.1.4-2.1 - Version table: - 1:2.1.4+next.20141218-2 0 - 300 http://http.debian.net/debian/ experimental/main amd64 Packages - *** 1:2.1.4-2.1 0 - 900 http://http.debian.net/debian/ jessie/main amd64 Packages - 600 http://http.debian.net/debian/ sid/main amd64 Packages - 100 /var/lib/dpkg/status - -"""]] - -and as a result we have no load reachable in this double-nested submodulea - -> This is a duplicate of <http://git-annex.branchable.com/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/>. [[done]] --[[Joey]] diff --git a/doc/bugs/dropping_files_with_a_URL_backend_fails.mdwn b/doc/bugs/dropping_files_with_a_URL_backend_fails.mdwn deleted file mode 100644 index c6ef13f84..000000000 --- a/doc/bugs/dropping_files_with_a_URL_backend_fails.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -I was trying out the example with the walkthrough using_the_URL_backend. I tried dropping files that I had after doing an "git annex get ." which have the URL backend associated with the files it fails with - - -<pre> -[jtang@lenny gc]$ git annex drop -v curl-7.21.4.tar.gz -drop curl-7.21.4.tar.gz -failed -git-annex: 1 failed -</pre> - -At first I thought it was just my OSX machine not having the coreutils stuff load up before the BSD utils, but I then tried the same thing on my archlinux machine and it showed the same behaviour, that is I could not drop a file with the URL backend as shown in the walkthrough. - -> Whoops, got some logic backwards. [[fixed|done]]! --[[Joey]] diff --git a/doc/bugs/enabling_existing_gitlab_repo_in_webapp_broken.mdwn b/doc/bugs/enabling_existing_gitlab_repo_in_webapp_broken.mdwn deleted file mode 100644 index 35ebc40a0..000000000 --- a/doc/bugs/enabling_existing_gitlab_repo_in_webapp_broken.mdwn +++ /dev/null @@ -1,8 +0,0 @@ -Enabling a gitlab repo that was set up elsewhere in the webapp doesn't -work. - -This is a SMOP; it needs to detect that the repo is on gitlab and use a -custom enabling process and no the generic one, which doesn't work. ---[[Joey]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/encfs_accused_of_being_crippled.mdwn b/doc/bugs/encfs_accused_of_being_crippled.mdwn deleted file mode 100644 index 617233670..000000000 --- a/doc/bugs/encfs_accused_of_being_crippled.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. - -I tried to create an annex (``git annex init foo``) inside a ``encfs`` mount, and git-annex says that it's crippled, and disables core.symlinks and goes into direct mode - -### What steps will reproduce the problem? - - apt-get install encfs - encfs -o kernel_cache empty_dir other_empty_dir - cd other_empty_dir - git init - git annex init foo - -### Expected results - - init foo ok - (Recording state in git...) - -### Actual results - - init foo - Detected a crippled filesystem. - - Disabling core.symlinks. - - Enabling direct mode. - ok - (Recording state in git...) - -### What version of git-annex are you using? On what operating system? - -4.20130601 on debian unstable - - -### P.S. - -This was particularly annoying when I tried this on a bare repository. I'm pretty sure bare repositories don't need symlinks, and should definitely not be in direct mode. Hopefully you can fix it before I have time to file another bug report :) - -Thank you! - - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment b/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment deleted file mode 100644 index aa6eb9345..000000000 --- a/doc/bugs/encfs_accused_of_being_crippled/comment_1_5c5be012e1171ef108f38825d72791b6._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-06-10T17:22:11Z" - content=""" -encfs appears to not allow creation of hard links to files: - -[[!format sh \"\"\" -joey@gnu:~/tmp/other_empty_dir>ln me me2 -ln: failed to create hard link `me2' => `me': Operation not permitted -\"\"\"]] - -According to the documentation, this is a limitation when using External IV Chaining. And only a problem if you choose paranoia mode when setting up encfs. - -git-annex uses hard links in a limited number of code paths, most notably `git annex add` uses them when locking down files. - -encfs seems like something I'd like to interoperate well with git-annex. So, it seems worthwhile to break out lack of hard links support from the other limitations currently lumped into \"cripped file system\". I've done so. - ----- - -Also made it stop setting direct mode on bare repositories, although that configuration had no effect anyway. -"""]] diff --git a/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn b/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn deleted file mode 100644 index ed269277c..000000000 --- a/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -### Please describe the problem. -Could not get ssh-askpass running on macosx. -Transfered the publich key with scp. -certificate based ssh from macosx to ssh server (debian testing) works. -After successfull login to ssh server git annex stops with the following errors: - -Browser Error Message: -user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2) - -### What steps will reproduce the problem? -1. git annex on debian gnu linux -2. git annex on macosx -3. set up "share with a friend" -4. create rsa keys on macosx "ssh-kegen -t rsa" -5. scp public key to server with hosts encrypted ssh remote -6. configure the server use a encrypted ssh remote in tranport mode - -### What version of git-annex are you using? On what operating system? -current debian testing (20130827) -macosx 20130827 -### 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 - -(scanning...) [2013-09-28 17:39:25 CEST] Watcher: Performing startup scan -(started...) [2013-09-28 17:39:26 CEST] XMPPSendPack: Syncing with jlueters -Everything up-to-date -[2013-09-28 17:39:30 CEST] XMPPSendPack: Unable to download files from jlueters. - -(encryption setup) gpg: /Users/lambert/.gnupg/gpg.conf:241: invalid auto-key-locate list -28/Sep/2013:17:40:06 +0200 [Error#yesod-core] user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2) @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) -(encryption setup) gpg: /Users/lambert/.gnupg/gpg.conf:241: invalid auto-key-locate list -28/Sep/2013:17:40:48 +0200 [Error#yesod-core] user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--gen-random","--armor","1","512"] exited 2) @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) - - - -# End of transcript or log. -"""]] - -> [[dup|done]] --[[Joey]] diff --git a/doc/bugs/encrpyted_ssh_remote_on_macosx/comment_1_46c37aacb7ae41864488fb7c7d87d437._comment b/doc/bugs/encrpyted_ssh_remote_on_macosx/comment_1_46c37aacb7ae41864488fb7c7d87d437._comment deleted file mode 100644 index 948b2c110..000000000 --- a/doc/bugs/encrpyted_ssh_remote_on_macosx/comment_1_46c37aacb7ae41864488fb7c7d87d437._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.153.8.80" - subject="comment 1" - date="2013-09-29T19:13:59Z" - content=""" -This is a duplicate of this bug report: [[Error_creating_encrypted_cloud_repository: \"internal_server_error\"]] - -To work around, you need to edit ~/.gnupg/gpg.conf and remove or edit the `auto-key-locate` line. -"""]] diff --git a/doc/bugs/endless_loop_when_PWD_gone.mdwn b/doc/bugs/endless_loop_when_PWD_gone.mdwn deleted file mode 100644 index 2df9e9c14..000000000 --- a/doc/bugs/endless_loop_when_PWD_gone.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -`git annex get` becomes very unhappy as soon as `$PWD` is gone. -The easiest way is to `git checkout git-annex` while you are getting in another tab. - -This results in git-annex entering an endless loop: - - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - fatal: Unable to read current working directory: No such file or directory - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/endless_loop_when_PWD_gone/comment_1_0943cffa39d48e4dddde3b7aedc4e3b1._comment b/doc/bugs/endless_loop_when_PWD_gone/comment_1_0943cffa39d48e4dddde3b7aedc4e3b1._comment deleted file mode 100644 index 734798cb8..000000000 --- a/doc/bugs/endless_loop_when_PWD_gone/comment_1_0943cffa39d48e4dddde3b7aedc4e3b1._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 1" - date="2014-01-02T01:11:15Z" - content=""" -This is due to the code that restarts git hash-object if it crashes (because it has been known to crash before). Utility.CoProcess needs to have a limit to the number of times it retries when something is failing. -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM.mdwn b/doc/bugs/enormous_fsck_output_OOM.mdwn deleted file mode 100644 index b06655354..000000000 --- a/doc/bugs/enormous_fsck_output_OOM.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -Hi, - -My Webapp isn't working: - - $ git-annex webapp error: refs/gcrypt/gitception+ does not point to a valid object! - error: refs/remotes/Beta/git-annex does not point to a valid object! - error: refs/remotes/Beta/master does not point to a valid object! - fatal: unable to read tree 656e7db5be172f01c0b6994d01f1a08d1273af12 - -So I tried to repair it: - - $ git-annex repair Running git fsck ... - Stack space overflow: current size 8388608 bytes. Use `+RTS -Ksize -RTS' to increase it. - -So I tried to follow your advice here and increase the stack: - - $ git-annex +RTS -K35000000 -RTS fsck - git-annex: Most RTS options are disabled. Link with -rtsopts to enable them. - -I wasn't sure what to do next, so any help would be appreciated. - -> Now only 20k problem shas max (more likely 10k) are collected from fsck, -> so it won't use much memory (60 mb or so). If it had to truncate -> shas from fsck, it will re-run fsck after the repair process, -> which should either find no problems left (common when eg when all missing shas -> were able to be fetched from remotes), or find a new set of problem -> shas, which it can feed back through the repair process. -> -> If the repository is very large, this means more work, but it shouldn't -> run out of memory now. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_1_490b8bfe95b01a23408ecb5d63dcd40b._comment b/doc/bugs/enormous_fsck_output_OOM/comment_1_490b8bfe95b01a23408ecb5d63dcd40b._comment deleted file mode 100644 index 73d218bac..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_1_490b8bfe95b01a23408ecb5d63dcd40b._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 1" - date="2014-02-23T18:51:45Z" - content=""" -I suspect that git fsck is outputting so many lines about problems that it's taking more memory than it's limited to using to hold them all. - -Can you paste the output of: git fsck --no-dangling --no-reflogs -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_2_2666c135dd3378cf6301aa4957049fbd._comment b/doc/bugs/enormous_fsck_output_OOM/comment_2_2666c135dd3378cf6301aa4957049fbd._comment deleted file mode 100644 index f2028c91f..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_2_2666c135dd3378cf6301aa4957049fbd._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 2" - date="2014-02-23T19:09:30Z" - content=""" -Erm, that output is liable to be big, I only care how many lines and characters of output there are! - - git fsck --no-dangling --no-reflogs |wc -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_3_dfb169c441215b671f8c971184de3e16._comment b/doc/bugs/enormous_fsck_output_OOM/comment_3_dfb169c441215b671f8c971184de3e16._comment deleted file mode 100644 index 96b1ac9cd..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_3_dfb169c441215b671f8c971184de3e16._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 3" - date="2014-02-23T19:12:10Z" - content=""" -Also, you can build git-annex from source with the RTS options enabled by running `cabal install git-annex --ghc-options=-rtsopts` - -(or just build git-repair which has the repository repair parts of git-annex) -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_4_19ef90803aa7ce158bce02378e18ea0f._comment b/doc/bugs/enormous_fsck_output_OOM/comment_4_19ef90803aa7ce158bce02378e18ea0f._comment deleted file mode 100644 index 69774073d..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_4_19ef90803aa7ce158bce02378e18ea0f._comment +++ /dev/null @@ -1,30 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnFjuvfPpi1kf6l54bxfFUm0Aw_Gf_IO0o" - nickname="Aaron" - subject="Didn't work" - date="2014-03-01T22:40:36Z" - content=""" -Many thanks for your input, Joey. - -That didn't seem to work. - -$ git fsck --no-dangling --no-reflogs |wc -error: unknown option `no-dangling' -usage: git fsck [options] [<object>...] - - -v, --verbose be verbose - --unreachable show unreachable objects - --tags report tags - --root report root nodes - --cache make index objects head nodes - --reflogs make reflogs head nodes (default) - --full also consider packs and alternate objects - --strict enable more strict checking - --lost-found write dangling objects in .git/lost-found - --progress show progress - - 0 0 0 - -$ git --version -git version 1.7.9.5 -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_5_2b5406768fff2834f7aefa76ef949de2._comment b/doc/bugs/enormous_fsck_output_OOM/comment_5_2b5406768fff2834f7aefa76ef949de2._comment deleted file mode 100644 index 923e1ccba..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_5_2b5406768fff2834f7aefa76ef949de2._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.146" - subject="comment 5" - date="2014-03-05T16:53:33Z" - content=""" -You have an older version of git, which does not support --no-dangling. - -git-annex will detect that, and omit the option. This does make it more likely that git fsck is outputing a ton of information, so I continue to think that's the most likely cause of the memory use. - -Please verify with: git fsck --no-reflogs |wc -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_6_0997f1a94c2fda9fe69824e074011518._comment b/doc/bugs/enormous_fsck_output_OOM/comment_6_0997f1a94c2fda9fe69824e074011518._comment deleted file mode 100644 index ddf69f94b..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_6_0997f1a94c2fda9fe69824e074011518._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnFjuvfPpi1kf6l54bxfFUm0Aw_Gf_IO0o" - nickname="Aaron" - subject="comment 6" - date="2014-03-08T00:08:22Z" - content=""" -That seemed to work, thanks: - - $ git fsck --no-reflogs |wc - Checking object directories: 100% (256/256), done. - error: refs/gcrypt/gitception+ does not point to a valid object! - error: refs/remotes/Beta/git-annex does not point to a valid object! - error: refs/remotes/Beta/master does not point to a valid object! - Checking connectivity: 128728, done. - 369082 1165340 20898546 - -Thanks for your help! -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment b/doc/bugs/enormous_fsck_output_OOM/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment deleted file mode 100644 index 14bdc17b8..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_7_2cdc79f1e0f72693814e91dc88a758e1._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 7" - date="2014-03-10T18:02:46Z" - content=""" -Ok, that verifies my hypothesis that fsck is outputting a lot of lines. 369082 lines to be precise, comprising 20 mb of data in all. So it's not too surprising this ends up blowing up into a bad amount of memory use. - -I'm going to move this from a forum post over to a bug: <http://git-annex.branchable.com/bugs/enormous_fsck_output_OOM> -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment b/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment deleted file mode 100644 index fa437311f..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_8_b9aab0aba4dab30260371b4762e0e51d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 8" - date="2014-03-10T18:12:29Z" - content=""" -In a quick test with a 32 mb dummy fsck output, git-repair ballooned up to 1.7 gb. Clearly something not happy there, although in my case this did not cause it to crash. -"""]] diff --git a/doc/bugs/enormous_fsck_output_OOM/comment_9_8de694dff75e27856c8282d1f2d120b6._comment b/doc/bugs/enormous_fsck_output_OOM/comment_9_8de694dff75e27856c8282d1f2d120b6._comment deleted file mode 100644 index a26e58c58..000000000 --- a/doc/bugs/enormous_fsck_output_OOM/comment_9_8de694dff75e27856c8282d1f2d120b6._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 9" - date="2014-03-10T19:17:34Z" - content=""" -I've gotten this down to 900 mb used, in the case where every single line lists a different sha. Possibly more important, if lines repeat shas, or are extraneous, memory usage will be significantly lower. This might be enough to get it working in Aaron's repository, especially if the bulk of the git fsck output was about dangling objects, which are now ignored without buffering them all in memory. - -The memory usage is just about as low as is possible; it takes a fair amount of memory just to hold 300 thousand shas in memory. And the git repair process needs to keep track of every broken sha. (Maybe there's a way to stream them, but I don't immediately see one.) - -I hesitate to say this means the problem is truly fixed. I have some much larger repositories with eg, `git count-objects -v` reporting 2 million objects. If they all went corrupt, it would still use too much memory. - -One improvement would be to store Shas in packed memory, rather than as strings like they are now. That would probably half the memory used. It still does not seem like a full solution. -"""]] diff --git a/doc/bugs/error_compiling_network-info_when_compiling_git-annex.mdwn b/doc/bugs/error_compiling_network-info_when_compiling_git-annex.mdwn deleted file mode 100644 index 99f480e70..000000000 --- a/doc/bugs/error_compiling_network-info_when_compiling_git-annex.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -### Please describe the problem. -I'm not sure if you'll consider this a bug, or if I'm just doing something wrong, but I'm having trouble compiling git-annex on OmniOS (a derivative of OpenSolaris). I've got GHC 7.6.3 built and installed (bootstrapped using the Solaris binaries for GHC 7.0.3). I used it to build haskell-platform (although I had to disable the OpenGL-related packages to do so), and now I'm trying to use cabal to build git-annex and its dependencies. I've started with a minimal build; this will end up as an archive remote so it should be sufficient. The instructions <http://git-annex.branchable.com/install/cabal/> say to run - - cabal install git-annex --bindir=$HOME/bin -f"-assistant -webapp -webdav -pairing -xmpp -dns" - -This builds a bunch of stuff but then fails to compile the network-info package. As I understand it, the git-annex package only needs network-info if it's compiled with pairing supoort (I'm looking at <https://github.com/joeyh/git-annex/blob/master/git-annex.cabal>), and this command is telling it to disable pairing. - -Is there some other dependency that needs network-info? Is there a way to find out? - -Thanks - -> fowarded 2 ways; [[done]] --[[Joey]] diff --git a/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_1_1b5d236567123300924427624e0e48c8._comment b/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_1_1b5d236567123300924427624e0e48c8._comment deleted file mode 100644 index 8ee7885a6..000000000 --- a/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_1_1b5d236567123300924427624e0e48c8._comment +++ /dev/null @@ -1,53 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-06T16:53:21Z" - content=""" -http://packdeps.haskellers.com/reverse/network-info - -It's uuid which needs network-info -- but not for the parts of uuid which git-annex uses. (git-annex does not use the uuids that include the MAC address). - -It's not hard to avoid that dependency. The attached patch will do. I've forwarded this to the author of uuid. - -<pre> -diff --git a/uuid.cabal b/uuid.cabal -index 0a53059..f00e887 100644 ---- a/uuid.cabal -+++ b/uuid.cabal -@@ -24,6 +24,9 @@ Extra-Source-Files: - CHANGES - CONTRIBUTORS - -+Flag NetworkInfo -+ Description: Enable UUIDs that need network-info -+ Default: True - - Library - Build-Depends: base >=3 && < 5, -@@ -32,17 +35,20 @@ Library - cryptohash >= 0.7 && < 0.12, - deepseq == 1.3.*, - hashable (>= 1.1.1.0 && < 1.2.0) || (>= 1.2.1 && < 1.3), -- network-info == 0.2.*, - random >= 1.0.1 && < 1.1, - time >= 1.1 && < 1.5 -+ if flag(NetworkInfo) -+ Build-Depends: network-info == 0.2.* - - Exposed-Modules: - Data.UUID -- Data.UUID.Util -- Data.UUID.V1 - Data.UUID.V3 - Data.UUID.V4 - Data.UUID.V5 -+ if flag(NetworkInfo) -+ Exposed-Modules: -+ Data.UUID.Util -+ Data.UUID.V1 - - Other-Modules: - Data.UUID.Builder -</pre> -"""]] diff --git a/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment b/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment deleted file mode 100644 index 8e631a115..000000000 --- a/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA" - nickname="Daniel" - subject="a different fix" - date="2014-06-07T04:27:47Z" - content=""" -Thanks. I also went back and took a closer look at the error; it looks like fixing network-info is pretty easy as well. <https://github.com/jystic/network-info/pull/10> -"""]] diff --git a/doc/bugs/extraneous_shell_escaping_for_rsync_remotes.mdwn b/doc/bugs/extraneous_shell_escaping_for_rsync_remotes.mdwn deleted file mode 100644 index c4ee8d5bd..000000000 --- a/doc/bugs/extraneous_shell_escaping_for_rsync_remotes.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -When using `git annex get foo` where foo is available in a rsync remote with encryption I got an error saying that rsync cannot -find the required file but extra ' are here. - -I attached a patch for this. - -> But you didn't, sadly. :( -> -> I don't seem to see the problem, set up a rsync over ssh with encryption -> and sent over a file "foo", and then got it back from rsync, without -> trouble. -> -> Ah, you're not using rsync over ssh, but just to a local directory, -> right? --[[Joey]] - ->> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/failed_sync_with_direct_mode_repo.mdwn b/doc/bugs/failed_sync_with_direct_mode_repo.mdwn deleted file mode 100644 index 879146deb..000000000 --- a/doc/bugs/failed_sync_with_direct_mode_repo.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -Two clients, both in direct mode, both running assistant. - -When a change is made on A, the assistant commits it to annex/direct/master. But, the master branch is not changed. - -B notices there is a change, pulls from A. Gets annex/direct/master, but does not merge it into its local branch at all. - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/failed_sync_with_direct_mode_repo/comment_1_fb4026cc81eb0ec1e656e4a81ffacc4f._comment b/doc/bugs/failed_sync_with_direct_mode_repo/comment_1_fb4026cc81eb0ec1e656e4a81ffacc4f._comment deleted file mode 100644 index 8b75fa67c..000000000 --- a/doc/bugs/failed_sync_with_direct_mode_repo/comment_1_fb4026cc81eb0ec1e656e4a81ffacc4f._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-16T15:10:42Z" - content=""" -Reproduced this as described. - -Only happens when using the assistant in the second repository, which is a ssh remote of the first, and when there is not also a remote going the other way (so does not affect pairing). - -As I thought, the problem is that the master branch is not updated by the assistant when in direct mode, and while annex/direct/master is pulled by the other assistant, it does not merge it. - -"""]] diff --git a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows.mdwn b/doc/bugs/fails_to_get_content_from_bare_repo_on_windows.mdwn deleted file mode 100644 index b54cbb444..000000000 --- a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows.mdwn +++ /dev/null @@ -1,143 +0,0 @@ -### Please describe the problem. - -I have a annex repo in external drive (a bare repo), usually synced with a macbook. When I'm trying to sync the drive over to a Windows machine, all contents fail to sync over. I managed to reproduce the problem with a set of instructions locally: - - C:\Temp\test>dir - Volume in drive C is Windows - Volume Serial Number is 6839-6E71 - - Directory of C:\Temp\test - - 2014/05/08 23:08 <DIR> . - 2014/05/08 23:08 <DIR> .. - 2014/05/08 23:08 14 file.txt - 1 File(s) 14 bytes - 2 Dir(s) 164,943,056,896 bytes free - - C:\Temp\test>git init - Initialized empty Git repository in C:/Temp/test/.git/ - - C:\Temp\test>git annex init - init - Detected a filesystem without fifo support. - - Disabling ssh connection caching. - - Detected a crippled filesystem. - - Enabling direct mode. - ok - (Recording state in git...) - - C:\Temp\test>git annex add . - add file.txt ok - (Recording state in git...) - - C:\Temp\test>cd .. - - C:\Temp>mkdir bare - - C:\Temp>cd bare - - C:\Temp\bare>git init --bare - Initialized empty Git repository in C:/Temp/bare/ - C:\Temp\bare>git annex init - init - Detected a filesystem without fifo support. - - Disabling ssh connection caching. - - Detected a crippled filesystem. - ok - (Recording state in git...) - - C:\Temp\bare>cd ../test - - C:\Temp\test>git remote add mybare C:\Temp\bare - - C:\Temp\test>git annex sync --content mybare - commit ok - pull mybare - warning: no common commits - remote: Counting objects: 5, done. - remote: Compressing objects: 100% (3/3), done. - remote: Total 5 (delta 0), reused 0 (delta 0) - Unpacking objects: 100% (5/5), done. - From C:\Temp\bare - * [new branch] git-annex -> mybare/git-annex - ok - (merging mybare/git-annex into git-annex...) - (Recording state in git...) - copy file.txt copy file.txt (to mybare...) - file.txt - 14 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - - sent 86 bytes received 31 bytes 234.00 bytes/sec - total size is 14 speedup is 0.12 - ok - pull mybare - ok - (Recording state in git...) - push mybare - Counting objects: 23, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (16/16), done. - Writing objects: 100% (21/21), 1.94 KiB | 0 bytes/s, done. - Total 21 (delta 1), reused 0 (delta 0) - To C:\Temp\bare - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master - ok - - C:\Temp\test>cd .. - - C:\Temp>git clone C:\Temp\bare test2 - Cloning into 'test2'... - done. - - C:\Temp>cd test2 - - C:\Temp\test2>ls -l - total 1 - ----------+ 1 Ruo None 188 May 8 23:10 file.txt - - C:\Temp\test2>git annex init - init - Detected a filesystem without fifo support. - - Disabling ssh connection caching. - - Detected a crippled filesystem. - - Enabling direct mode. - ok - (Recording state in git...) - - C:\Temp\test2>git annex get file.txt - get file.txt (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - - Unable to access these remotes: origin - - Try making some of these repositories available: - f2af6f52-18d5-4a54-ae5c-c4bef5fab00c -- origin (MY-PC:C:\Temp\bare) - fc00306a-157c-439b-a5c3-37aabf9d61fb -- MY-PC:C:\Temp\test - failed - git-annex: get: 1 failed - - - C:\Temp\test2>git version - git version 1.9.2.msysgit.0 - - C:\Temp\test2>git annex version - git-annex version: 5.20140421-g78d6aa1 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 2 3 4 - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_1_31cf32ef2d597573ed3c5f06a1b40a1c._comment b/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_1_31cf32ef2d597573ed3c5f06a1b40a1c._comment deleted file mode 100644 index b57af9b17..000000000 --- a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_1_31cf32ef2d597573ed3c5f06a1b40a1c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-05T17:37:08Z" - content=""" -I've reproduced this. - -More simply: git annex move --to mybare and then git annex get will fail -"""]] diff --git a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_2_7d64382c66555ec9c5531840aa19e809._comment b/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_2_7d64382c66555ec9c5531840aa19e809._comment deleted file mode 100644 index fc978e28d..000000000 --- a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_2_7d64382c66555ec9c5531840aa19e809._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 2" - date="2014-06-05T18:29:15Z" - content=""" -Appears to be a corrupt uuid log issue. At least, the bug I am seeing is. When retriving the uuid of the remote that has the key from the location log, it seems to get a uuid with one or more \r appended to it. Which smells of windows. - -However, the bug I am seeing makes `git annex get` print out the uuids of the remotes without the description it normally shows (because these are not really the same uuids due to the \r). In the example above, this is not the case; the description is shown. I don't understand that. -"""]] diff --git a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_3_850a917a3d1ae50ba8f0e81a64168268._comment b/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_3_850a917a3d1ae50ba8f0e81a64168268._comment deleted file mode 100644 index d44825324..000000000 --- a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_3_850a917a3d1ae50ba8f0e81a64168268._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 3" - date="2014-06-05T19:06:36Z" - content=""" -The bug I was seeing with the \r was a recent reversion caused by [[!commit 95ca3bb02215744f3dbcaebd48844e1909c577f3]]. So, not related to original bug report. (And fixed now!) - -I can now reproduce the original bug, including seeing the description of the bare repo when it says it cannot get the file from it. -"""]] diff --git a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_4_7c4660ea44178cba7f7a4cc5f1bebae4._comment b/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_4_7c4660ea44178cba7f7a4cc5f1bebae4._comment deleted file mode 100644 index 5d8b4d978..000000000 --- a/doc/bugs/fails_to_get_content_from_bare_repo_on_windows/comment_4_7c4660ea44178cba7f7a4cc5f1bebae4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 4" - date="2014-06-05T19:20:20Z" - content=""" -Analysis: inAnnexSafe on Windows simply does not have indirect mode checking enabled. Bare repositories use indirect mode (essentially; same storage). So it fails. -"""]] diff --git a/doc/bugs/failure_during_ssh_key_setup___40__windows__41__.mdwn b/doc/bugs/failure_during_ssh_key_setup___40__windows__41__.mdwn deleted file mode 100644 index 7f1f26e04..000000000 --- a/doc/bugs/failure_during_ssh_key_setup___40__windows__41__.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -### Please describe the problem. -While attempting to create a remote repository, the assistant is trying to set up public key authentication, but fails when trying to delete the temporary files. Perhaps this doesn't need to be a fatal error; it could warn the user instead, or try again later. - -DeleteFile "C:\\Users\\FAMILY~1\\AppData\\Local\\Temp\\git-annex-keygen.1\\key.pub": permission denied (The process cannot access the file because it is being used by another process.) - -### What steps will reproduce the problem? -Create a remote repository - -### What version of git-annex are you using? On what operating system? -Windows 7, git-annex version 5.20131221-gf8c928d - -> [[fixed|done]].. thanks for testing the assistant on windows! --[[Joey]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent.mdwn b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent.mdwn deleted file mode 100644 index 6197861e1..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -### Please describe the problem. - -One of my remotes (a USB drive) actually did not have a large number of files that should have been there, according to git annex's records. When the assistant would try to fetch files from there, it would silently fail and go get them from another remote. I noticed this behavior and was very puzzled by it. I eventually went to the command line and started trying to fetch these files. If I remember correctly, "getting" them would also fail silently. "git annex whereis" said they were there on the drive. - -Finally I did a "git annex fsck --fast" which quickly revealed the problem (several hundred files were gone, all in "archives") - -I am not sure how this happened, though I have some vague ideas -- it could be relics of a time when an ordinary directory had been created where a mountpoint for the USB drive should have existed, and it was trying to copy files there. Or it could have been a side effect of the somewhat confused process where I migrated to a new macbook using OS X's migration assistant and so I suddenly had two copies of the same archive, and some time was spent fiddling around trying to fix that situation up. Maybe during that point I accidentally flipped that USB repo into being a client instead of a backup repo, and it started dropping archive content, and maybe I stopped it from recording that by impatiently killing what seemed to be a hung git-annex process.... In any case, I don't know how the situation came into existence, but once it existed, the silent failures made it difficult for me to realize that it was happening. I thought the content really was there (trusting git annex whereis) and it was refusing to transfer it for some reason. - -It would have been useful to get some feedback, either in the assistant or the commandline, to the effect that the files which were supposed to be there according to git-annex's information, were not in fact there, and a fsck was called for. - -### What steps will reproduce the problem? - -Create an annex, with content. Clone the annex. Sync. Delete the files by force from the .git/annex/objects directory in the original. Go to the clone, and try and "git annex get" the content. It fails silently. - - -### What version of git-annex are you using? On what operating system? - - [12:17:03 PM]$ git annex version - git-annex version: 4.20130709-ga2269ee - - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS - local repository version: 3 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - -My particular issue has probably existed through a few version upgrades though. - -### 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. -"""]] - -> Since neither of us can think of a better behavior for `git annex -> get/copy > --from remote` in this case, I've been reduced to documenting -> it better. The docs now mention that --from will cause it to silently -> skip files that are not present in the specified remote. So, [[done]] -> --[[Joey]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_1_c686df2824d3f588c0bfb339c99168b7._comment b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_1_c686df2824d3f588c0bfb339c99168b7._comment deleted file mode 100644 index 64bc18b71..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_1_c686df2824d3f588c0bfb339c99168b7._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.246.110" - subject="comment 1" - date="2013-07-26T21:08:02Z" - content=""" -Tried to reproduce this, following your instructions. It did not seem to work: - -<pre> -joey@gnu:~/tmp/mydir2>git annex get disk2 -get disk2 - Unable to access these remotes: origin - - Try making some of these repositories available: - 21606444-98f9-4c40-aa60-3ebfba936758 -- origin (joey@gnu:~/tmp/mydir) -failed -git-annex: get: 1 failed -- exit 1 -joey@gnu:~/tmp/mydir2>git annex whereis disk2 -whereis disk2 (1 copy) - 21606444-98f9-4c40-aa60-3ebfba936758 -- origin (joey@gnu:~/tmp/mydir) -ok -joey@gnu:~/tmp/mydir2> -</pre> - -So, not a silent failure. It is a little unclear about why it can't get the file (in this case because I moved .git/annex/objects out of the way), but it's pretty clear it can't. - -AFAIK, the only way `git annex get` can silently not do anything is if you already have the file locally. Perhaps you got confused? OTOH, if you can provide a better way to reproduce this, I'm curious to see it. -"""]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_2_22edfac4ce25cd9f4e4c85e0a8a52bc1._comment b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_2_22edfac4ce25cd9f4e4c85e0a8a52bc1._comment deleted file mode 100644 index 2d500288f..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_2_22edfac4ce25cd9f4e4c85e0a8a52bc1._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="99.54.57.201" - subject="comment 2" - date="2013-07-27T06:03:55Z" - content=""" -I actually ran through the test I described to you and got the silent failure, but now I'm doing it again and getting the \"Try making some of these repositories available\" error. (Along with inaccurate \"whereis\" info, as you're seeing there.) I'm baffled. Unless something changed with respect to this behavior in the most recent version, which I've installed since then, I don't know what I was doing differently. Maybe I was confused. - -I can guarantee that I was getting silent failures in \"gets\" from my USB drive. I was \"getting\" \"--from\" my USB drive, nothing was showing up (the symlink was broken), and no error was printed to the console, including the \"try making it available\" one we're getting now. It's only when I went to the drive and did a \"git annex fsck\" that I realized that those files were actually missing from that remote, and it wasn't just a failure to \"get\" them. The behavior was alarming enough that I made sure of what was happening before I made the bug report. I wish I'd actually cut and pasted the demo, instead of just describing it! - -It'd still be nice to have some kind of feedback in the assistant (and maybe more understandable feedback in the command line) that something was amiss. What I would see in the assistant, because of this, is a bunch of queued downloads from the USB drive, but as each one was ready to execute, it would disappear (because it failed) and be replaced by a download from the (lower priority) SSH repo. This happened a number of times and I found it baffling. - -My first instinct in a situation like this is to say \"yeah, I must have been confused\" but I honestly did check this out pretty carefully before sending it in, so I wonder if a recent update improved matters, perhaps inadvertently? In any case, I'm glad there's some kind of error right now. -"""]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_3_74fc0e41a6bd5c4d8c4b2f15e5ed8d2f._comment b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_3_74fc0e41a6bd5c4d8c4b2f15e5ed8d2f._comment deleted file mode 100644 index 5abbe99c3..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_3_74fc0e41a6bd5c4d8c4b2f15e5ed8d2f._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.246.110" - subject="comment 3" - date="2013-07-27T22:39:12Z" - content=""" -The --from is the missing piece to reproduce: - -[[!format sh \"\"\" -joey@gnu:~/tmp/old/mydir2>git annex get disk2 --from origin -joey@gnu:~/tmp/old/mydir2> -\"\"\"]] - -What's going on here is that `get --from` is essentially an alias to `copy --from`, and that skips copying files that it knows are not present on the remote. Since the remote is a local directory, it's inexpensive for it to check if the file is really there, rather than relying on the location log. - -This seems suboptimal, but I'm not sure which part of the behavior it makes sense to change. It seems nice for `copy --from` to silently skip files that the remote does not have, to avoid much unnecessary output when processing a lot of files. Maybe `get --from` should behave differently? -"""]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_4_7d642fc65040a7b583cdece33db01826._comment b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_4_7d642fc65040a7b583cdece33db01826._comment deleted file mode 100644 index 18c9b6668..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_4_7d642fc65040a7b583cdece33db01826._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.246.110" - subject="comment 4" - date="2013-07-27T22:40:58Z" - content=""" -I should add that it also seems to make sense to stat the file to see if it's present, like it does now. The location log can be out of date, and when more accurate info is right there, it should use it. And nor is the location log being out of date something that it should complain about, because it can easily happen eg when `git annex sync` has not been run recently. -"""]] diff --git a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_5_49be366b6af6db595fa538373a61e650._comment b/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_5_49be366b6af6db595fa538373a61e650._comment deleted file mode 100644 index 6ba31d562..000000000 --- a/doc/bugs/failure_to_find_file_that___34__should__34___exist_in_remote_is_silent/comment_5_49be366b6af6db595fa538373a61e650._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="99.54.57.201" - subject="comment 5" - date="2013-07-28T05:29:00Z" - content=""" -Oh yeah! That makes sense now. It's not exactly that it's failing, it's just that the command \"git annex get --from=bar foo\" means \"get any copies of foo which might exist in the bar remote.\" Not \"get the copy of foo which I happen to know exists in the bar remote.\" - -I'm not sure either exactly what \"better\" behavior would be. -"""]] diff --git a/doc/bugs/failure_to_return_to_indirect_mode_on_usb.mdwn b/doc/bugs/failure_to_return_to_indirect_mode_on_usb.mdwn deleted file mode 100644 index a61c67254..000000000 --- a/doc/bugs/failure_to_return_to_indirect_mode_on_usb.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -### Please describe the problem. -In a usb drive with a repository in direct mode, when I converted to indirect mode it fails - -### What steps will reproduce the problem? -cd /Volumes/usb -git annex indirect - -### What version of git-annex are you using? On what operating system? -git-annex version: 4.20130627 - -### Please provide any additional information below. - -[[!format sh """ -openFile: resource busy (file is locked) -failed -git-annex: indirect: 1 failed -"""]] - -[[!tag moreinfo]] - -> I don't like closing bug reports, but after over a year with no followup, -> and with the original bug report lacking even an error message, closing -> it seems like the best course of action. [[done]] --[[Joey]] diff --git a/doc/bugs/failure_to_return_to_indirect_mode_on_usb/comment_1_d7822b90c68bf845572b0a04a378d0bb._comment b/doc/bugs/failure_to_return_to_indirect_mode_on_usb/comment_1_d7822b90c68bf845572b0a04a378d0bb._comment deleted file mode 100644 index e0cf8ca84..000000000 --- a/doc/bugs/failure_to_return_to_indirect_mode_on_usb/comment_1_d7822b90c68bf845572b0a04a378d0bb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.4.193" - subject="comment 1" - date="2013-07-02T16:38:14Z" - content=""" -What filesystem is in use on this USB drive? For example, is it a FAT filesystem? - -What operating system are you using? -"""]] diff --git a/doc/bugs/feeding_git_annex_with_xargs_can_fail.mdwn b/doc/bugs/feeding_git_annex_with_xargs_can_fail.mdwn deleted file mode 100644 index c4199d3b9..000000000 --- a/doc/bugs/feeding_git_annex_with_xargs_can_fail.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -Feeding git-annex a long list off directories, eg with xargs can have -2 bad behaviors: - -* git-annex runs git ls-files and passes it the same long list. But the git - ls-files command is longer than the git-annex command often, so it gets - truncated and some files are not processed. - - > fixed --[[Joey]] - -* It can take a really long time for git-annex to chew through the - git-ls-files results. There is probably an exponential blowup in the time - relative to the number of parameters. Some of the stuff being done to - preserve original ordering etc is likely at fault. - - > [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/file_in_manual_mode_repository_is_dropped_when_it_is_copied_to_another_manual_mode_repository.mdwn b/doc/bugs/file_in_manual_mode_repository_is_dropped_when_it_is_copied_to_another_manual_mode_repository.mdwn deleted file mode 100644 index fed5080f6..000000000 --- a/doc/bugs/file_in_manual_mode_repository_is_dropped_when_it_is_copied_to_another_manual_mode_repository.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -Hi, - -### Please describe the problem. -I have a distant repository in backup mode acting as origin and 2 computers at home containing that repository in manual mode. Everything is in indirect mode and watched by git annex assistant. -If I get a file on one local computer from origin, everything act as expected, I have a copy on that file on origin and on the local computer. -But, if I then want to copy the file over to the other local computer by issuing a git annex get on the second computer with a --from option specifying the first local computer, the file is transferred but when the transfer is completed the file is dropped on the first local computer. - -If I try and retrieve the file from origin, I don't have that problem and the file is kept on every repository I issued the git annex get command. - -A bigger problem is that if, still on the second local computer, I start transferring a file from the first local computer and I interrupt the rsync process, the file is still dropped by the first local computer although it is not yet on the second. -It is still on the origin so no data is lost but I don't think this behavior is really intended. - -The version of git-annex I use is as follows: - -On the two local computers (from the ArchLinux aur): -git-annex version: 5.20140716-g8c14ba8 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -On the server (debian stable, standalone git-annex archive): -git-annex version: 5.20140716-g8c14ba8 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -It should be the same version everywhere. - -Please ask me if you need more information. - -> According to the bug reporter, -> [[Assistant_drops_files_from_remote_repos_that_it_shouldn__39__t]] -> is a report of this same problem. So, let's close this report -> as a duplicate. [[done]] --[[Joey]] diff --git a/doc/bugs/file_not_found.mdwn b/doc/bugs/file_not_found.mdwn deleted file mode 100644 index e12ec1e6d..000000000 --- a/doc/bugs/file_not_found.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -### Please describe the problem. -Unable to use webapp after creating annex. Error `The file /annex/webapp.html does not exist.` is shown. - - -### What steps will reproduce the problem? -Create annex, either using webapp or command line. Kill the webapp and attempt to relaunch. - - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20150205 - -OS X Version: 10.10.3 (14D136) - -Installed using homebrew - -### Please provide any additional information below. - - -It appears that git-annex is using an absolute path, rather than a relative path pointing to `.git/annex/webapp.html`. -Manually opening the file at `.git/annex/webapp.html` does however show the correct web interface. - -[[!format sh """ - git-annex webapp -Launching web browser on file://.git/annex/webapp.html -The file /annex/webapp.html does not exist. -"""]] - -> This is an old version of git-annex and there was known breakage around -> that time from the relative path conversion, since fixed, which IIRC -> would manifest this way. [[done]] --[[Joey]] diff --git a/doc/bugs/files_lost_during_upgrade.mdwn b/doc/bugs/files_lost_during_upgrade.mdwn deleted file mode 100644 index afab38d81..000000000 --- a/doc/bugs/files_lost_during_upgrade.mdwn +++ /dev/null @@ -1,2191 +0,0 @@ -### Please describe the problem. -I'm running git annex on two laptops sharing data with a shared server all running ubuntu and the binary distributions of git annex (different versions the server seems to be running 5.20140529-gb71f9bf right now). One of the laptops tried to upgrade to 5.20140613 (something) from 5.20140610-g5ec8bcf, which kind of fails since that version does not exist on the site, only the signature making it download and upgrade and then decide it still needs to upgrade, took a few times before I figured this out. - -During one of the upgrades I guess something died and it started to complain about an index.lock file that should be removed after all git instances were dead, so I killed git annex and removed the file (a few times maybe) just to get the upgrade through. After realizing it was trying to upgrade to the same version over and over again I realized it had somehow managed merge away all files and the git history looked like crazy. - -Had to "git annex indirect; git annex checkout GOODVERSION . ; git annex direct ; git annex assistant" to get the files back (I think that did it, I'm a little unsure what the best way to restore files are). - -### What steps will reproduce the problem? - -I don't know. Just posting this in case someone else can figure it out. - -Might be relevant that upgrade never works out of the box, it removes the old version of git annex and untars the new version in my home directory (which isn't on the path), so I can't use it from the command line. So I shut it down, copy it back to where it should go, and then update the .config/git-annex/program to point to the correct location. - -### What version of git-annex are you using? On what operating system? - -5.20140610-g5ec8bcf (maybe, I'm not sure if that was the one I upgraded from initially). - -### 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 - -I think this is the log from before the files where removed - -[2014-06-18 13:41:14 CEST] main: starting assistant version 5.20140610-g5ec8bcf -[2014-06-18 13:41:14 CEST] UpgradeWatcher: Finished upgrading git-annex to version 5.20140610-g5ec8bcf -[2014-06-18 13:41:14 CEST] TransferScanner: Syncing with born - -(scanning...) [2014-06-18 13:41:14 CEST] Watcher: Performing startup scan - -(started...) fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - f8f8217..ff8ecb1 git-annex -> synced/git-annex - bd2e43b..e88b148 annex/direct/master -> synced/master -fatal: pathspec 'music.txt' did not match any files -fatal: Unable to create '/home/jwiklund/Documents/.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: Unable to create '/home/jwiklund/Documents/.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files - -(Recording state in git...) - -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) - -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -ufatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -ser error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -[2014-06-18 13:41:16 CEST] Committer: Committing changesfatal: pathspec 'music.txt' did not match any files - to git -fatal: pathspec 'music.txt' did not match any files -[2014-06-18 13:41:16 CEST] Pusher: Syncing with born -fatal: Unable to create '/home/jwiklund/Documents/.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -(Recording state in git...) -(Recording state in git...) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) - -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user error (xargs ["-0","git","--git-dir=/home/jwiklund/Documents/.git","--work-tree=/home/jwiklund/Documents","-c","core.bare=false","add","--force","--"] exited 123) -user errfatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -fatal: pathspec 'music.txt' did not match any files -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - ff8ecb1..c93e415 git-annex -> synced/git-annex - e88b148..220161f annex/direct/master -> synced/master - - -This is what it said when it wanted me to remove the index file after a failed upgrade - -[2014-06-18 13:38:31 CEST] main: starting assistant version 5.20140610-g5ec8bcf -[2014-06-18 13:38:31 CEST] UpgradeWatcher: Finished upgrading git-annex to version 5.20140610-g5ec8bcf -[2014-06-18 13:38:31 CEST] TransferScanner: Syncing with born -error: duplicate parent 294b61a3dce1e87a62e4d675deac2a9130b819e6 ignored - -(scanning...) [2014-06-18 13:38:31 CEST] Watcher: Performing startup scan - -(started...) error: duplicate parent 76407052287ba54b350e56e36353a53a3dbc5d4f ignored -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - fdae080..cf9f2a9 git-annex -> synced/git-annex - 294b61a..7640705 annex/direct/master -> synced/master -fatal: Could not switch to '/home/jwiklund/Documents/.git/annex/merge/': No such file or directory -[2014-06-18 13:38:33 CEST] Committer: Committing changes to git -fatal: Unable to create '/home/jwiklund/Documents/.git/index.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -[2014-06-18 13:38:33 CEST] Pusher: Syncing with born -fatal: Could not switch to '/home/jwiklund/Documents/.git/annex/merge/': No such file or directory -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - 7640705..6b9d33e annex/direct/master -> synced/master -fatal: Could not switch to '/home/jwiklund/Documents/.git/annex/merge/': No such file or directory -[2014-06-18 13:39:20 CEST] main: warning git-annex has been shut down - -Here is the upgrade - -error: duplicate parent 6b9d33ef3a16e6245f21f3948aa96691c2b8453b ignored -(scanning...) [2014 --06-18 13:40:55 CEST] Watcher: Performing startup scan -(started...) - -error: duplicate parent 80254c9c048a35064ba42ae6a79610da6deac0ae ignored -gpg: WARNING: unsafe permissions on homedir `/tmp/git-annex-gpg.tmp.0' -gpg: Signature made fre 13 jun 2014 17:28:22 CEST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -[2014-06-18 13:40:56 CEST] Upgrader: An upgrade of git-annex is available. (version 5.20140613) -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - 6b9d33e..80254c9 annex/direct/master -> synced/master - -[2014-06-18 13:40:57 CEST] Committer: Committing changes to git -(Recording state in git...) -[2014-06-18 13:40:57 CEST] Pusher: Syncing with born - -error: duplicate parent 6be6bb32164e7103c44077ce6fa450b7c0d36e0c ignored -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - 80254c9..6be6bb3 annex/direct/master -> synced/master - ---2014-06-18 13:41:07-- https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz -Resolving downloads.kitenet.net (downloads.kitenet.net)... 107.170.31.195 -Connecting to downloads.kitenet.net (downloads.kitenet.net)|107.170.31.195|:443... connected. -HTTP request sent, awaiting response... 200 OK -Length: 42645638 (41M) [application/x-gzip] -Saving to: ‘/home/jwiklund/Documents/.git/annex/tmp/SHA256E-s42645638--4ae41fb29bd26339ea10f53ea2b7cf3132e53d5e8fbfde7b43b912aa52b3d319.tar.gz’ - - 0K .......... .......... .......... .......... .......... 0% 171K 4m3s - 50K .......... .......... .......... .......... .......... 0% 505K 2m43s - 100K .......... .......... .......... .......... .......... 0% 258K 2m42s - 150K .......... .......... .......... .......... .......... 0% 510K 2m22s - 200K .......... .......... .......... .......... .......... 0% 505K 2m10s - 250K .......... .......... .......... .......... .......... 0% 516K 2m1s - 300K .......... .......... .......... .......... .......... 0% 512K 1m55s - 350K .......... .......... .......... .......... .......... 0% 31,1M 1m41s - 400K .......... .......... .......... .......... .......... 1% 512K 99s - 450K .......... .......... .......... .......... .......... 1% 515K 97s - 500K .......... .......... .......... .......... .......... 1% 1,25M 91s - 550K .......... .......... .......... .......... .......... 1% 843K 87s - 600K .......... .......... .......... .......... .......... 1% 1,25M 83s - 650K .......... .......... .......... .......... .......... 1% 858K 80s - 700K .......... .......... .......... .......... .......... 1% 1,25M 77s - 750K .......... .......... .......... .......... .......... 1% 840K 75s - 800K .......... .......... .......... .......... .......... 2% 59,4M 70s - 850K .......... .......... .......... .......... .......... 2% 518K 71s - 900K .......... .......... .......... .......... .......... 2% 39,5M 67s - 950K .......... .......... .......... .......... .......... 2% 74,5M 64s - 1000K .......... .......... .......... .......... .......... 2% 520K 64s - 1050K .......... .......... .......... .......... .......... 2% 57,3M 61s - 1100K .......... .......... .......... .......... .......... 2% 1,31M 60s - 1150K .......... .......... .......... .......... .......... 2% 855K 59s - 1200K .......... .......... .......... .......... .......... 3% 22,5M 57s - 1250K .......... .......... .......... .......... .......... 3% 1,33M 56s - 1300K .......... .......... .......... .......... .......... 3% 848K 55s - 1350K .......... .......... .......... .......... .......... 3% 9,76M 54s - 1400K .......... .......... .......... .......... .......... 3% 48,8M 52s - 1450K .......... .......... .......... .......... .......... 3% 1,45M 51s - 1500K .......... .......... .......... .......... .......... 3% 837K 51s - 1550K .......... .......... .......... .......... .......... 3% 13,4M 49s - 1600K .......... .......... .......... .......... .......... 3% 1,47M 48s - 1650K .......... .......... .......... .......... .......... 4% 861K 48s - 1700K .......... .......... .......... .......... .......... 4% 14,3M 47s - 1750K .......... .......... .......... .......... .......... 4% 13,0M 46s - 1800K .......... .......... .......... .......... .......... 4% 1,49M 45s - 1850K .......... .......... .......... .......... .......... 4% 863K 45s - 1900K .......... .......... .......... .......... .......... 4% 62,3M 44s - 1950K .......... .......... .......... .......... .......... 4% 7,64M 43s - 2000K .......... .......... .......... .......... .......... 4% 10,3M 42s - 2050K .......... .......... .......... .......... .......... 5% 582K 42s - 2100K .......... .......... .......... .......... .......... 5% 8,34M 41s - 2150K .......... .......... .......... .......... .......... 5% 48,7M 40s - 2200K .......... .......... .......... .......... .......... 5% 61,6M 39s - 2250K .......... .......... .......... .......... .......... 5% 1,52M 39s - 2300K .......... .......... .......... .......... .......... 5% 860K 39s - 2350K .......... .......... .......... .......... .......... 5% 60,4M 38s - 2400K .......... .......... .......... .......... .......... 5% 8,20M 38s - 2450K .......... .......... .......... .......... .......... 6% 87,7M 37s - 2500K .......... .......... .......... .......... .......... 6% 1,54M 37s - 2550K .......... .......... .......... .......... .......... 6% 855K 37s - 2600K .......... .......... .......... .......... .......... 6% 89,2M 36s - 2650K .......... .......... .......... .......... .......... 6% 7,38M 35s - 2700K .......... .......... .......... .......... .......... 6% 168M 35s - 2750K .......... .......... .......... .......... .......... 6% 1,44M 34s - 2800K .......... .......... .......... .......... .......... 6% 1,37M 34s - 2850K .......... .......... .......... .......... .......... 6% 2,21M 34s - 2900K .......... .......... .......... .......... .......... 7% 6,19M 33s - 2950K .......... .......... .......... .......... .......... 7% 174M 33s - 3000K .......... .......... .......... .......... .......... 7% 174M 32s - 3050K .......... .......... .......... .......... .......... 7% 196M 32s - 3100K .......... .......... .......... .......... .......... 7% 1,57M 32s - 3150K .......... .......... .......... .......... .......... 7% 1,36M 31s - 3200K .......... .......... .......... .......... .......... 7% 1,67M 31s - 3250K .......... .......... .......... .......... .......... 7% 70,5M 31s - 3300K .......... .......... .......... .......... .......... 8% 109M 30s - 3350K .......... .......... .......... .......... .......... 8% 84,8M 30s - 3400K .......... .......... .......... .......... .......... 8% 1,61M 30s - 3450K .......... .......... .......... .......... .......... 8% 8,23M 29s - 3500K .......... .......... .......... .......... .......... 8% 1,47M 29s - 3550K .......... .......... .......... .......... .......... 8% 2,77M 29s - 3600K .......... .......... .......... .......... .......... 8% 5,14M 29s - 3650K .......... .......... .......... .......... .......... 8% 28,0M 28s - 3700K .......... .......... .......... .......... .......... 9% 169M 28s - 3750K .......... .......... .......... .......... .......... 9% 1,85M 28s - 3800K .......... .......... .......... .......... .......... 9% 86,5M 27s - 3850K .......... .......... .......... .......... .......... 9% 7,14M 27s - 3900K .......... .......... .......... .......... .......... 9% 1,55M 27s - 3950K .......... .......... .......... .......... .......... 9% 2,53M 27s - 4000K .......... .......... .......... .......... .......... 9% 5,08M 26s - 4050K .......... .......... .......... .......... .......... 9% 37,6M 26s - 4100K .......... .......... .......... .......... .......... 9% 45,6M 26s - 4150K .......... .......... .......... .......... .......... 10% 86,2M 25s - 4200K .......... .......... .......... .......... .......... 10% 1,80M 25s - 4250K .......... .......... .......... .......... .......... 10% 99,6M 25s - 4300K .......... .......... .......... .......... .......... 10% 171M 25s - 4350K .......... .......... .......... .......... .......... 10% 7,41M 24s - 4400K .......... .......... .......... .......... .......... 10% 1,55M 24s - 4450K .......... .......... .......... .......... .......... 10% 2,53M 24s - 4500K .......... .......... .......... .......... .......... 10% 59,5M 24s - 4550K .......... .......... .......... .......... .......... 11% 5,43M 24s - 4600K .......... .......... .......... .......... .......... 11% 25,3M 23s - 4650K .......... .......... .......... .......... .......... 11% 138M 23s - 4700K .......... .......... .......... .......... .......... 11% 90,7M 23s - 4750K .......... .......... .......... .......... .......... 11% 116M 23s - 4800K .......... .......... .......... .......... .......... 11% 1,81M 23s - 4850K .......... .......... .......... .......... .......... 11% 64,4M 22s - 4900K .......... .......... .......... .......... .......... 11% 7,76M 22s - 4950K .......... .......... .......... .......... .......... 12% 67,2M 22s - 5000K .......... .......... .......... .......... .......... 12% 1,60M 22s - 5050K .......... .......... .......... .......... .......... 12% 2,53M 22s - 5100K .......... .......... .......... .......... .......... 12% 5,14M 22s - 5150K .......... .......... .......... .......... .......... 12% 90,4M 21s - 5200K .......... .......... .......... .......... .......... 12% 27,7M 21s - 5250K .......... .......... .......... .......... .......... 12% 41,7M 21s - 5300K .......... .......... .......... .......... .......... 12% 91,5M 21s - 5350K .......... .......... .......... .......... .......... 12% 1,85M 21s - 5400K .......... .......... .......... .......... .......... 13% 109M 20s - 5450K .......... .......... .......... .......... .......... 13% 79,2M 20s - 5500K .......... .......... .......... .......... .......... 13% 6,84M 20s - 5550K .......... .......... .......... .......... .......... 13% 32,4M 20s - 5600K .......... .......... .......... .......... .......... 13% 5,70M 20s - 5650K .......... .......... .......... .......... .......... 13% 2,36M 20s - 5700K .......... .......... .......... .......... .......... 13% 2,53M 20s - 5750K .......... .......... .......... .......... .......... 13% 5,15M 19s - 5800K .......... .......... .......... .......... .......... 14% 31,1M 19s - 5850K .......... .......... .......... .......... .......... 14% 23,0M 19s - 5900K .......... .......... .......... .......... .......... 14% 45,3M 19s - 5950K .......... .......... .......... .......... .......... 14% 73,7M 19s - 6000K .......... .......... .......... .......... .......... 14% 1,96M 19s - 6050K .......... .......... .......... .......... .......... 14% 51,7M 18s - 6100K .......... .......... .......... .......... .......... 14% 8,10M 18s - 6150K .......... .......... .......... .......... .......... 14% 45,9M 18s - 6200K .......... .......... .......... .......... .......... 15% 23,5M 18s - 6250K .......... .......... .......... .......... .......... 15% 7,66M 18s - 6300K .......... .......... .......... .......... .......... 15% 2,29M 18s - 6350K .......... .......... .......... .......... .......... 15% 2,46M 18s - 6400K .......... .......... .......... .......... .......... 15% 46,8M 18s - 6450K .......... .......... .......... .......... .......... 15% 5,73M 17s - 6500K .......... .......... .......... .......... .......... 15% 23,0M 17s - 6550K .......... .......... .......... .......... .......... 15% 21,1M 17s - 6600K .......... .......... .......... .......... .......... 15% 48,4M 17s - 6650K .......... .......... .......... .......... .......... 16% 74,1M 17s - 6700K .......... .......... .......... .......... .......... 16% 2,07M 17s - 6750K .......... .......... .......... .......... .......... 16% 30,3M 17s - 6800K .......... .......... .......... .......... .......... 16% 7,81M 17s - 6850K .......... .......... .......... .......... .......... 16% 59,1M 16s - 6900K .......... .......... .......... .......... .......... 16% 24,6M 16s - 6950K .......... .......... .......... .......... .......... 16% 8,11M 16s - 7000K .......... .......... .......... .......... .......... 16% 7,57M 16s - 7050K .......... .......... .......... .......... .......... 17% 3,19M 16s - 7100K .......... .......... .......... .......... .......... 17% 2,35M 16s - 7150K .......... .......... .......... .......... .......... 17% 5,56M 16s - 7200K .......... .......... .......... .......... .......... 17% 51,4M 16s - 7250K .......... .......... .......... .......... .......... 17% 45,5M 16s - 7300K .......... .......... .......... .......... .......... 17% 61,6M 16s - 7350K .......... .......... .......... .......... .......... 17% 22,7M 15s - 7400K .......... .......... .......... .......... .......... 17% 53,6M 15s - 7450K .......... .......... .......... .......... .......... 18% 2,12M 15s - 7500K .......... .......... .......... .......... .......... 18% 32,2M 15s - 7550K .......... .......... .......... .......... .......... 18% 61,0M 15s - 7600K .......... .......... .......... .......... .......... 18% 7,22M 15s - 7650K .......... .......... .......... .......... .......... 18% 23,6M 15s - 7700K .......... .......... .......... .......... .......... 18% 7,39M 15s - 7750K .......... .......... .......... .......... .......... 18% 53,7M 15s - 7800K .......... .......... .......... .......... .......... 18% 8,51M 15s - 7850K .......... .......... .......... .......... .......... 18% 8,28M 14s - 7900K .......... .......... .......... .......... .......... 19% 1,26M 15s - 7950K .......... .......... .......... .......... .......... 19% 59,8M 14s - 8000K .......... .......... .......... .......... .......... 19% 58,8M 14s - 8050K .......... .......... .......... .......... .......... 19% 54,2M 14s - 8100K .......... .......... .......... .......... .......... 19% 70,3M 14s - 8150K .......... .......... .......... .......... .......... 19% 26,5M 14s - 8200K .......... .......... .......... .......... .......... 19% 54,8M 14s - 8250K .......... .......... .......... .......... .......... 19% 73,9M 14s - 8300K .......... .......... .......... .......... .......... 20% 2,11M 14s - 8350K .......... .......... .......... .......... .......... 20% 21,6M 14s - 8400K .......... .......... .......... .......... .......... 20% 8,29M 14s - 8450K .......... .......... .......... .......... .......... 20% 29,6M 14s - 8500K .......... .......... .......... .......... .......... 20% 59,6M 13s - 8550K .......... .......... .......... .......... .......... 20% 6,65M 13s - 8600K .......... .......... .......... .......... .......... 20% 8,50M 13s - 8650K .......... .......... .......... .......... .......... 20% 10,1M 13s - 8700K .......... .......... .......... .......... .......... 21% 44,0M 13s - 8750K .......... .......... .......... .......... .......... 21% 1,42M 13s - 8800K .......... .......... .......... .......... .......... 21% 11,1M 13s - 8850K .......... .......... .......... .......... .......... 21% 78,9M 13s - 8900K .......... .......... .......... .......... .......... 21% 50,5M 13s - 8950K .......... .......... .......... .......... .......... 21% 73,1M 13s - 9000K .......... .......... .......... .......... .......... 21% 77,6M 13s - 9050K .......... .......... .......... .......... .......... 21% 20,2M 13s - 9100K .......... .......... .......... .......... .......... 21% 25,2M 13s - 9150K .......... .......... .......... .......... .......... 22% 117M 12s - 9200K .......... .......... .......... .......... .......... 22% 2,23M 12s - 9250K .......... .......... .......... .......... .......... 22% 22,4M 12s - 9300K .......... .......... .......... .......... .......... 22% 8,59M 12s - 9350K .......... .......... .......... .......... .......... 22% 24,5M 12s - 9400K .......... .......... .......... .......... .......... 22% 79,6M 12s - 9450K .......... .......... .......... .......... .......... 22% 7,10M 12s - 9500K .......... .......... .......... .......... .......... 22% 8,02M 12s - 9550K .......... .......... .......... .......... .......... 23% 8,69M 12s - 9600K .......... .......... .......... .......... .......... 23% 8,16M 12s - 9650K .......... .......... .......... .......... .......... 23% 63,0M 12s - 9700K .......... .......... .......... .......... .......... 23% 1,72M 12s - 9750K .......... .......... .......... .......... .......... 23% 10,1M 12s - 9800K .......... .......... .......... .......... .......... 23% 60,2M 12s - 9850K .......... .......... .......... .......... .......... 23% 61,9M 12s - 9900K .......... .......... .......... .......... .......... 23% 62,9M 12s - 9950K .......... .......... .......... .......... .......... 24% 76,6M 11s - 10000K .......... .......... .......... .......... .......... 24% 23,8M 11s - 10050K .......... .......... .......... .......... .......... 24% 30,4M 11s - 10100K .......... .......... .......... .......... .......... 24% 3,50M 11s - 10150K .......... .......... .......... .......... .......... 24% 6,05M 11s - 10200K .......... .......... .......... .......... .......... 24% 14,9M 11s - 10250K .......... .......... .......... .......... .......... 24% 10,5M 11s - 10300K .......... .......... .......... .......... .......... 24% 21,5M 11s - 10350K .......... .......... .......... .......... .......... 24% 79,7M 11s - 10400K .......... .......... .......... .......... .......... 25% 8,60M 11s - 10450K .......... .......... .......... .......... .......... 25% 6,92M 11s - 10500K .......... .......... .......... .......... .......... 25% 11,0M 11s - 10550K .......... .......... .......... .......... .......... 25% 6,96M 11s - 10600K .......... .......... .......... .......... .......... 25% 66,9M 11s - 10650K .......... .......... .......... .......... .......... 25% 10,9M 11s - 10700K .......... .......... .......... .......... .......... 25% 1,71M 11s - 10750K .......... .......... .......... .......... .......... 25% 60,4M 11s - 10800K .......... .......... .......... .......... .......... 26% 39,6M 11s - 10850K .......... .......... .......... .......... .......... 26% 62,6M 11s - 10900K .......... .......... .......... .......... .......... 26% 65,0M 10s - 10950K .......... .......... .......... .......... .......... 26% 137M 10s - 11000K .......... .......... .......... .......... .......... 26% 37,8M 10s - 11050K .......... .......... .......... .......... .......... 26% 82,1M 10s - 11100K .......... .......... .......... .......... .......... 26% 36,9M 10s - 11150K .......... .......... .......... .......... .......... 26% 3,47M 10s - 11200K .......... .......... .......... .......... .......... 27% 4,59M 10s - 11250K .......... .......... .......... .......... .......... 27% 10,3M 10s - 11300K .......... .......... .......... .......... .......... 27% 105M 10s - 11350K .......... .......... .......... .......... .......... 27% 21,8M 10s - 11400K .......... .......... .......... .......... .......... 27% 8,57M 10s - 11450K .......... .......... .......... .......... .......... 27% 6,57M 10s - 11500K .......... .......... .......... .......... .......... 27% 60,3M 10s - 11550K .......... .......... .......... .......... .......... 27% 11,5M 10s - 11600K .......... .......... .......... .......... .......... 27% 7,50M 10s - 11650K .......... .......... .......... .......... .......... 28% 72,7M 10s - 11700K .......... .......... .......... .......... .......... 28% 7,61M 10s - 11750K .......... .......... .......... .......... .......... 28% 2,31M 10s - 11800K .......... .......... .......... .......... .......... 28% 6,77M 10s - 11850K .......... .......... .......... .......... .......... 28% 66,3M 10s - 11900K .......... .......... .......... .......... .......... 28% 69,9M 10s - 11950K .......... .......... .......... .......... .......... 28% 73,3M 9s - 12000K .......... .......... .......... .......... .......... 28% 59,8M 9s - 12050K .......... .......... .......... .......... .......... 29% 62,8M 9s - 12100K .......... .......... .......... .......... .......... 29% 72,4M 9s - 12150K .......... .......... .......... .......... .......... 29% 38,9M 9s - 12200K .......... .......... .......... .......... .......... 29% 8,31M 9s - 12250K .......... .......... .......... .......... .......... 29% 6,24M 9s - 12300K .......... .......... .......... .......... .......... 29% 4,90M 9s - 12350K .......... .......... .......... .......... .......... 29% 8,21M 9s - 12400K .......... .......... .......... .......... .......... 29% 20,0M 9s - 12450K .......... .......... .......... .......... .......... 30% 9,55M 9s - 12500K .......... .......... .......... .......... .......... 30% 49,5M 9s - 12550K .......... .......... .......... .......... .......... 30% 6,87M 9s - 12600K .......... .......... .......... .......... .......... 30% 60,8M 9s - 12650K .......... .......... .......... .......... .......... 30% 11,6M 9s - 12700K .......... .......... .......... .......... .......... 30% 68,3M 9s - 12750K .......... .......... .......... .......... .......... 30% 7,84M 9s - 12800K .......... .......... .......... .......... .......... 30% 41,8M 9s - 12850K .......... .......... .......... .......... .......... 30% 8,13M 9s - 12900K .......... .......... .......... .......... .......... 31% 2,43M 9s - 12950K .......... .......... .......... .......... .......... 31% 6,04M 9s - 13000K .......... .......... .......... .......... .......... 31% 47,7M 9s - 13050K .......... .......... .......... .......... .......... 31% 56,9M 9s - 13100K .......... .......... .......... .......... .......... 31% 59,0M 9s - 13150K .......... .......... .......... .......... .......... 31% 49,4M 8s - 13200K .......... .......... .......... .......... .......... 31% 61,2M 8s - 13250K .......... .......... .......... .......... .......... 31% 56,6M 8s - 13300K .......... .......... .......... .......... .......... 32% 69,6M 8s - 13350K .......... .......... .......... .......... .......... 32% 9,89M 8s - 13400K .......... .......... .......... .......... .......... 32% 51,2M 8s - 13450K .......... .......... .......... .......... .......... 32% 3,68M 8s - 13500K .......... .......... .......... .......... .......... 32% 10,9M 8s - 13550K .......... .......... .......... .......... .......... 32% 9,06M 8s - 13600K .......... .......... .......... .......... .......... 32% 22,0M 8s - 13650K .......... .......... .......... .......... .......... 32% 56,2M 8s - 13700K .......... .......... .......... .......... .......... 33% 8,24M 8s - 13750K .......... .......... .......... .......... .......... 33% 7,93M 8s - 13800K .......... .......... .......... .......... .......... 33% 46,0M 8s - 13850K .......... .......... .......... .......... .......... 33% 140M 8s - 13900K .......... .......... .......... .......... .......... 33% 12,6M 8s - 13950K .......... .......... .......... .......... .......... 33% 8,45M 8s - 14000K .......... .......... .......... .......... .......... 33% 25,4M 8s - 14050K .......... .......... .......... .......... .......... 33% 8,48M 8s - 14100K .......... .......... .......... .......... .......... 33% 115M 8s - 14150K .......... .......... .......... .......... .......... 34% 2,37M 8s - 14200K .......... .......... .......... .......... .......... 34% 6,80M 8s - 14250K .......... .......... .......... .......... .......... 34% 41,9M 8s - 14300K .......... .......... .......... .......... .......... 34% 59,1M 8s - 14350K .......... .......... .......... .......... .......... 34% 134M 8s - 14400K .......... .......... .......... .......... .......... 34% 181M 8s - 14450K .......... .......... .......... .......... .......... 34% 107M 8s - 14500K .......... .......... .......... .......... .......... 34% 61,9M 7s - 14550K .......... .......... .......... .......... .......... 35% 24,4M 7s - 14600K .......... .......... .......... .......... .......... 35% 148M 7s - 14650K .......... .......... .......... .......... .......... 35% 8,76M 7s - 14700K .......... .......... .......... .......... .......... 35% 8,29M 7s - 14750K .......... .......... .......... .......... .......... 35% 3,92M 7s - 14800K .......... .......... .......... .......... .......... 35% 9,53M 7s - 14850K .......... .......... .......... .......... .......... 35% 143M 7s - 14900K .......... .......... .......... .......... .......... 35% 19,0M 7s - 14950K .......... .......... .......... .......... .......... 36% 7,80M 7s - 15000K .......... .......... .......... .......... .......... 36% 7,87M 7s - 15050K .......... .......... .......... .......... .......... 36% 60,1M 7s - 15100K .......... .......... .......... .......... .......... 36% 55,7M 7s - 15150K .......... .......... .......... .......... .......... 36% 12,2M 7s - 15200K .......... .......... .......... .......... .......... 36% 11,5M 7s - 15250K .......... .......... .......... .......... .......... 36% 23,0M 7s - 15300K .......... .......... .......... .......... .......... 36% 50,4M 7s - 15350K .......... .......... .......... .......... .......... 36% 51,4M 7s - 15400K .......... .......... .......... .......... .......... 37% 9,26M 7s - 15450K .......... .......... .......... .......... .......... 37% 7,03M 7s - 15500K .......... .......... .......... .......... .......... 37% 3,39M 7s - 15550K .......... .......... .......... .......... .......... 37% 6,82M 7s - 15600K .......... .......... .......... .......... .......... 37% 33,2M 7s - 15650K .......... .......... .......... .......... .......... 37% 56,0M 7s - 15700K .......... .......... .......... .......... .......... 37% 52,0M 7s - 15750K .......... .......... .......... .......... .......... 37% 55,0M 7s - 15800K .......... .......... .......... .......... .......... 38% 66,8M 7s - 15850K .......... .......... .......... .......... .......... 38% 62,0M 7s - 15900K .......... .......... .......... .......... .......... 38% 62,8M 7s - 15950K .......... .......... .......... .......... .......... 38% 192M 7s - 16000K .......... .......... .......... .......... .......... 38% 164M 7s - 16050K .......... .......... .......... .......... .......... 38% 16,4M 7s - 16100K .......... .......... .......... .......... .......... 38% 28,9M 7s - 16150K .......... .......... .......... .......... .......... 38% 8,73M 6s - 16200K .......... .......... .......... .......... .......... 39% 51,7M 6s - 16250K .......... .......... .......... .......... .......... 39% 4,07M 6s - 16300K .......... .......... .......... .......... .......... 39% 8,88M 6s - 16350K .......... .......... .......... .......... .......... 39% 30,0M 6s - 16400K .......... .......... .......... .......... .......... 39% 10,2M 6s - 16450K .......... .......... .......... .......... .......... 39% 6,47M 6s - 16500K .......... .......... .......... .......... .......... 39% 49,7M 6s - 16550K .......... .......... .......... .......... .......... 39% 57,1M 6s - 16600K .......... .......... .......... .......... .......... 39% 5,99M 6s - 16650K .......... .......... .......... .......... .......... 40% 47,3M 6s - 16700K .......... .......... .......... .......... .......... 40% 50,5M 6s - 16750K .......... .......... .......... .......... .......... 40% 80,4M 6s - 16800K .......... .......... .......... .......... .......... 40% 49,6M 6s - 16850K .......... .......... .......... .......... .......... 40% 61,4M 6s - 16900K .......... .......... .......... .......... .......... 40% 9,92M 6s - 16950K .......... .......... .......... .......... .......... 40% 97,6M 6s - 17000K .......... .......... .......... .......... .......... 40% 2,35M 6s - 17050K .......... .......... .......... .......... .......... 41% 6,43M 6s - 17100K .......... .......... .......... .......... .......... 41% 41,0M 6s - 17150K .......... .......... .......... .......... .......... 41% 56,3M 6s - 17200K .......... .......... .......... .......... .......... 41% 46,3M 6s - 17250K .......... .......... .......... .......... .......... 41% 59,6M 6s - 17300K .......... .......... .......... .......... .......... 41% 51,6M 6s - 17350K .......... .......... .......... .......... .......... 41% 84,3M 6s - 17400K .......... .......... .......... .......... .......... 41% 62,6M 6s - 17450K .......... .......... .......... .......... .......... 42% 81,4M 6s - 17500K .......... .......... .......... .......... .......... 42% 80,4M 6s - 17550K .......... .......... .......... .......... .......... 42% 20,1M 6s - 17600K .......... .......... .......... .......... .......... 42% 26,4M 6s - 17650K .......... .......... .......... .......... .......... 42% 68,5M 6s - 17700K .......... .......... .......... .......... .......... 42% 12,3M 6s - 17750K .......... .......... .......... .......... .......... 42% 30,3M 6s - 17800K .......... .......... .......... .......... .......... 42% 3,98M 6s - 17850K .......... .......... .......... .......... .......... 42% 89,6M 6s - 17900K .......... .......... .......... .......... .......... 43% 9,68M 6s - 17950K .......... .......... .......... .......... .......... 43% 34,4M 6s - 18000K .......... .......... .......... .......... .......... 43% 7,09M 6s - 18050K .......... .......... .......... .......... .......... 43% 9,29M 6s - 18100K .......... .......... .......... .......... .......... 43% 88,7M 6s - 18150K .......... .......... .......... .......... .......... 43% 43,6M 5s - 18200K .......... .......... .......... .......... .......... 43% 10,3M 5s - 18250K .......... .......... .......... .......... .......... 43% 12,4M 5s - 18300K .......... .......... .......... .......... .......... 44% 113M 5s - 18350K .......... .......... .......... .......... .......... 44% 23,2M 5s - 18400K .......... .......... .......... .......... .......... 44% 96,5M 5s - 18450K .......... .......... .......... .......... .......... 44% 119M 5s - 18500K .......... .......... .......... .......... .......... 44% 70,8M 5s - 18550K .......... .......... .......... .......... .......... 44% 9,12M 5s - 18600K .......... .......... .......... .......... .......... 44% 66,7M 5s - 18650K .......... .......... .......... .......... .......... 44% 7,63M 5s - 18700K .......... .......... .......... .......... .......... 45% 2,25M 5s - 18750K .......... .......... .......... .......... .......... 45% 112M 5s - 18800K .......... .......... .......... .......... .......... 45% 61,9M 5s - 18850K .......... .......... .......... .......... .......... 45% 79,6M 5s - 18900K .......... .......... .......... .......... .......... 45% 60,4M 5s - 18950K .......... .......... .......... .......... .......... 45% 110M 5s - 19000K .......... .......... .......... .......... .......... 45% 81,0M 5s - 19050K .......... .......... .......... .......... .......... 45% 77,1M 5s - 19100K .......... .......... .......... .......... .......... 45% 107M 5s - 19150K .......... .......... .......... .......... .......... 46% 59,2M 5s - 19200K .......... .......... .......... .......... .......... 46% 12,9M 5s - 19250K .......... .......... .......... .......... .......... 46% 31,5M 5s - 19300K .......... .......... .......... .......... .......... 46% 59,1M 5s - 19350K .......... .......... .......... .......... .......... 46% 8,48M 5s - 19400K .......... .......... .......... .......... .......... 46% 70,5M 5s - 19450K .......... .......... .......... .......... .......... 46% 6,40M 5s - 19500K .......... .......... .......... .......... .......... 46% 47,7M 5s - 19550K .......... .......... .......... .......... .......... 47% 5,84M 5s - 19600K .......... .......... .......... .......... .......... 47% 54,2M 5s - 19650K .......... .......... .......... .......... .......... 47% 34,6M 5s - 19700K .......... .......... .......... .......... .......... 47% 8,77M 5s - 19750K .......... .......... .......... .......... .......... 47% 45,6M 5s - 19800K .......... .......... .......... .......... .......... 47% 8,46M 5s - 19850K .......... .......... .......... .......... .......... 47% 53,9M 5s - 19900K .......... .......... .......... .......... .......... 47% 10,0M 5s - 19950K .......... .......... .......... .......... .......... 48% 41,3M 5s - 20000K .......... .......... .......... .......... .......... 48% 15,0M 5s - 20050K .......... .......... .......... .......... .......... 48% 25,6M 5s - 20100K .......... .......... .......... .......... .......... 48% 75,2M 5s - 20150K .......... .......... .......... .......... .......... 48% 118M 5s - 20200K .......... .......... .......... .......... .......... 48% 106M 5s - 20250K .......... .......... .......... .......... .......... 48% 122M 5s - 20300K .......... .......... .......... .......... .......... 48% 9,40M 5s - 20350K .......... .......... .......... .......... .......... 48% 82,8M 5s - 20400K .......... .......... .......... .......... .......... 49% 2,31M 5s - 20450K .......... .......... .......... .......... .......... 49% 102M 5s - 20500K .......... .......... .......... .......... .......... 49% 7,52M 5s - 20550K .......... .......... .......... .......... .......... 49% 59,3M 5s - 20600K .......... .......... .......... .......... .......... 49% 108M 4s - 20650K .......... .......... .......... .......... .......... 49% 37,9M 4s - 20700K .......... .......... .......... .......... .......... 49% 120M 4s - 20750K .......... .......... .......... .......... .......... 49% 84,2M 4s - 20800K .......... .......... .......... .......... .......... 50% 67,8M 4s - 20850K .......... .......... .......... .......... .......... 50% 100M 4s - 20900K .......... .......... .......... .......... .......... 50% 71,7M 4s - 20950K .......... .......... .......... .......... .......... 50% 73,8M 4s - 21000K .......... .......... .......... .......... .......... 50% 15,5M 4s - 21050K .......... .......... .......... .......... .......... 50% 21,8M 4s - 21100K .......... .......... .......... .......... .......... 50% 11,0M 4s - 21150K .......... .......... .......... .......... .......... 50% 64,5M 4s - 21200K .......... .......... .......... .......... .......... 51% 29,8M 4s - 21250K .......... .......... .......... .......... .......... 51% 8,28M 4s - 21300K .......... .......... .......... .......... .......... 51% 9,12M 4s - 21350K .......... .......... .......... .......... .......... 51% 9,08M 4s - 21400K .......... .......... .......... .......... .......... 51% 42,5M 4s - 21450K .......... .......... .......... .......... .......... 51% 67,7M 4s - 21500K .......... .......... .......... .......... .......... 51% 37,9M 4s - 21550K .......... .......... .......... .......... .......... 51% 9,20M 4s - 21600K .......... .......... .......... .......... .......... 51% 11,2M 4s - 21650K .......... .......... .......... .......... .......... 52% 21,7M 4s - 21700K .......... .......... .......... .......... .......... 52% 71,1M 4s - 21750K .......... .......... .......... .......... .......... 52% 8,58M 4s - 21800K .......... .......... .......... .......... .......... 52% 15,8M 4s - 21850K .......... .......... .......... .......... .......... 52% 49,8M 4s - 21900K .......... .......... .......... .......... .......... 52% 26,0M 4s - 21950K .......... .......... .......... .......... .......... 52% 84,1M 4s - 22000K .......... .......... .......... .......... .......... 52% 75,1M 4s - 22050K .......... .......... .......... .......... .......... 53% 91,9M 4s - 22100K .......... .......... .......... .......... .......... 53% 90,4M 4s - 22150K .......... .......... .......... .......... .......... 53% 11,7M 4s - 22200K .......... .......... .......... .......... .......... 53% 40,0M 4s - 22250K .......... .......... .......... .......... .......... 53% 86,5M 4s - 22300K .......... .......... .......... .......... .......... 53% 80,8M 4s - 22350K .......... .......... .......... .......... .......... 53% 2,36M 4s - 22400K .......... .......... .......... .......... .......... 53% 8,03M 4s - 22450K .......... .......... .......... .......... .......... 54% 44,6M 4s - 22500K .......... .......... .......... .......... .......... 54% 44,3M 4s - 22550K .......... .......... .......... .......... .......... 54% 46,1M 4s - 22600K .......... .......... .......... .......... .......... 54% 59,6M 4s - 22650K .......... .......... .......... .......... .......... 54% 64,5M 4s - 22700K .......... .......... .......... .......... .......... 54% 52,4M 4s - 22750K .......... .......... .......... .......... .......... 54% 64,6M 4s - 22800K .......... .......... .......... .......... .......... 54% 56,7M 4s - 22850K .......... .......... .......... .......... .......... 54% 75,7M 4s - 22900K .......... .......... .......... .......... .......... 55% 35,7M 4s - 22950K .......... .......... .......... .......... .......... 55% 30,3M 4s - 23000K .......... .......... .......... .......... .......... 55% 11,0M 4s - 23050K .......... .......... .......... .......... .......... 55% 102M 4s - 23100K .......... .......... .......... .......... .......... 55% 25,4M 4s - 23150K .......... .......... .......... .......... .......... 55% 8,53M 4s - 23200K .......... .......... .......... .......... .......... 55% 29,8M 4s - 23250K .......... .......... .......... .......... .......... 55% 11,5M 4s - 23300K .......... .......... .......... .......... .......... 56% 93,9M 4s - 23350K .......... .......... .......... .......... .......... 56% 8,20M 4s - 23400K .......... .......... .......... .......... .......... 56% 83,3M 4s - 23450K .......... .......... .......... .......... .......... 56% 32,7M 4s - 23500K .......... .......... .......... .......... .......... 56% 103M 3s - 23550K .......... .......... .......... .......... .......... 56% 9,54M 3s - 23600K .......... .......... .......... .......... .......... 56% 8,14M 3s - 23650K .......... .......... .......... .......... .......... 56% 76,8M 3s - 23700K .......... .......... .......... .......... .......... 57% 8,68M 3s - 23750K .......... .......... .......... .......... .......... 57% 63,7M 3s - 23800K .......... .......... .......... .......... .......... 57% 13,3M 3s - 23850K .......... .......... .......... .......... .......... 57% 29,7M 3s - 23900K .......... .......... .......... .......... .......... 57% 61,6M 3s - 23950K .......... .......... .......... .......... .......... 57% 71,7M 3s - 24000K .......... .......... .......... .......... .......... 57% 62,1M 3s - 24050K .......... .......... .......... .......... .......... 57% 75,3M 3s - 24100K .......... .......... .......... .......... .......... 57% 14,1M 3s - 24150K .......... .......... .......... .......... .......... 58% 48,4M 3s - 24200K .......... .......... .......... .......... .......... 58% 43,5M 3s - 24250K .......... .......... .......... .......... .......... 58% 91,5M 3s - 24300K .......... .......... .......... .......... .......... 58% 117M 3s - 24350K .......... .......... .......... .......... .......... 58% 2,39M 3s - 24400K .......... .......... .......... .......... .......... 58% 8,97M 3s - 24450K .......... .......... .......... .......... .......... 58% 102M 3s - 24500K .......... .......... .......... .......... .......... 58% 42,4M 3s - 24550K .......... .......... .......... .......... .......... 59% 64,6M 3s - 24600K .......... .......... .......... .......... .......... 59% 35,3M 3s - 24650K .......... .......... .......... .......... .......... 59% 113M 3s - 24700K .......... .......... .......... .......... .......... 59% 120M 3s - 24750K .......... .......... .......... .......... .......... 59% 38,7M 3s - 24800K .......... .......... .......... .......... .......... 59% 58,8M 3s - 24850K .......... .......... .......... .......... .......... 59% 73,9M 3s - 24900K .......... .......... .......... .......... .......... 59% 24,8M 3s - 24950K .......... .......... .......... .......... .......... 60% 63,1M 3s - 25000K .......... .......... .......... .......... .......... 60% 32,9M 3s - 25050K .......... .......... .......... .......... .......... 60% 11,0M 3s - 25100K .......... .......... .......... .......... .......... 60% 24,1M 3s - 25150K .......... .......... .......... .......... .......... 60% 85,0M 3s - 25200K .......... .......... .......... .......... .......... 60% 9,09M 3s - 25250K .......... .......... .......... .......... .......... 60% 122M 3s - 25300K .......... .......... .......... .......... .......... 60% 30,1M 3s - 25350K .......... .......... .......... .......... .......... 60% 11,4M 3s - 25400K .......... .......... .......... .......... .......... 61% 95,0M 3s - 25450K .......... .......... .......... .......... .......... 61% 7,94M 3s - 25500K .......... .......... .......... .......... .......... 61% 125M 3s - 25550K .......... .......... .......... .......... .......... 61% 42,5M 3s - 25600K .......... .......... .......... .......... .......... 61% 9,23M 3s - 25650K .......... .......... .......... .......... .......... 61% 66,0M 3s - 25700K .......... .......... .......... .......... .......... 61% 8,38M 3s - 25750K .......... .......... .......... .......... .......... 61% 70,8M 3s - 25800K .......... .......... .......... .......... .......... 62% 8,71M 3s - 25850K .......... .......... .......... .......... .......... 62% 69,5M 3s - 25900K .......... .......... .......... .......... .......... 62% 15,6M 3s - 25950K .......... .......... .......... .......... .......... 62% 26,2M 3s - 26000K .......... .......... .......... .......... .......... 62% 60,0M 3s - 26050K .......... .......... .......... .......... .......... 62% 71,0M 3s - 26100K .......... .......... .......... .......... .......... 62% 73,0M 3s - 26150K .......... .......... .......... .......... .......... 62% 71,9M 3s - 26200K .......... .......... .......... .......... .......... 63% 64,3M 3s - 26250K .......... .......... .......... .......... .......... 63% 17,0M 3s - 26300K .......... .......... .......... .......... .......... 63% 67,3M 3s - 26350K .......... .......... .......... .......... .......... 63% 35,5M 3s - 26400K .......... .......... .......... .......... .......... 63% 80,0M 3s - 26450K .......... .......... .......... .......... .......... 63% 110M 3s - 26500K .......... .......... .......... .......... .......... 63% 10,7M 3s - 26550K .......... .......... .......... .......... .......... 63% 3,01M 3s - 26600K .......... .......... .......... .......... .......... 63% 8,05M 3s - 26650K .......... .......... .......... .......... .......... 64% 107M 3s - 26700K .......... .......... .......... .......... .......... 64% 70,1M 3s - 26750K .......... .......... .......... .......... .......... 64% 71,8M 3s - 26800K .......... .......... .......... .......... .......... 64% 30,4M 3s - 26850K .......... .......... .......... .......... .......... 64% 109M 3s - 26900K .......... .......... .......... .......... .......... 64% 57,8M 3s - 26950K .......... .......... .......... .......... .......... 64% 47,2M 3s - 27000K .......... .......... .......... .......... .......... 64% 81,2M 3s - 27050K .......... .......... .......... .......... .......... 65% 74,9M 3s - 27100K .......... .......... .......... .......... .......... 65% 72,4M 3s - 27150K .......... .......... .......... .......... .......... 65% 32,0M 3s - 27200K .......... .......... .......... .......... .......... 65% 34,8M 2s - 27250K .......... .......... .......... .......... .......... 65% 10,5M 2s - 27300K .......... .......... .......... .......... .......... 65% 65,5M 2s - 27350K .......... .......... .......... .......... .......... 65% 27,9M 2s - 27400K .......... .......... .......... .......... .......... 65% 9,96M 2s - 27450K .......... .......... .......... .......... .......... 66% 58,0M 2s - 27500K .......... .......... .......... .......... .......... 66% 97,2M 2s - 27550K .......... .......... .......... .......... .......... 66% 30,3M 2s - 27600K .......... .......... .......... .......... .......... 66% 11,2M 2s - 27650K .......... .......... .......... .......... .......... 66% 8,92M 2s - 27700K .......... .......... .......... .......... .......... 66% 49,0M 2s - 27750K .......... .......... .......... .......... .......... 66% 65,0M 2s - 27800K .......... .......... .......... .......... .......... 66% 65,9M 2s - 27850K .......... .......... .......... .......... .......... 66% 9,76M 2s - 27900K .......... .......... .......... .......... .......... 67% 8,10M 2s - 27950K .......... .......... .......... .......... .......... 67% 68,7M 2s - 28000K .......... .......... .......... .......... .......... 67% 60,7M 2s - 28050K .......... .......... .......... .......... .......... 67% 71,4M 2s - 28100K .......... .......... .......... .......... .......... 67% 9,13M 2s - 28150K .......... .......... .......... .......... .......... 67% 17,5M 2s - 28200K .......... .......... .......... .......... .......... 67% 59,7M 2s - 28250K .......... .......... .......... .......... .......... 67% 25,1M 2s - 28300K .......... .......... .......... .......... .......... 68% 67,3M 2s - 28350K .......... .......... .......... .......... .......... 68% 70,4M 2s - 28400K .......... .......... .......... .......... .......... 68% 60,6M 2s - 28450K .......... .......... .......... .......... .......... 68% 74,6M 2s - 28500K .......... .......... .......... .......... .......... 68% 74,9M 2s - 28550K .......... .......... .......... .......... .......... 68% 19,6M 2s - 28600K .......... .......... .......... .......... .......... 68% 29,3M 2s - 28650K .......... .......... .......... .......... .......... 68% 67,6M 2s - 28700K .......... .......... .......... .......... .......... 69% 93,7M 2s - 28750K .......... .......... .......... .......... .......... 69% 140M 2s - 28800K .......... .......... .......... .......... .......... 69% 11,5M 2s - 28850K .......... .......... .......... .......... .......... 69% 6,48M 2s - 28900K .......... .......... .......... .......... .......... 69% 3,54M 2s - 28950K .......... .......... .......... .......... .......... 69% 33,1M 2s - 29000K .......... .......... .......... .......... .......... 69% 83,1M 2s - 29050K .......... .......... .......... .......... .......... 69% 59,5M 2s - 29100K .......... .......... .......... .......... .......... 69% 31,8M 2s - 29150K .......... .......... .......... .......... .......... 70% 129M 2s - 29200K .......... .......... .......... .......... .......... 70% 117M 2s - 29250K .......... .......... .......... .......... .......... 70% 69,8M 2s - 29300K .......... .......... .......... .......... .......... 70% 56,8M 2s - 29350K .......... .......... .......... .......... .......... 70% 89,9M 2s - 29400K .......... .......... .......... .......... .......... 70% 81,7M 2s - 29450K .......... .......... .......... .......... .......... 70% 102M 2s - 29500K .......... .......... .......... .......... .......... 70% 32,2M 2s - 29550K .......... .......... .......... .......... .......... 71% 62,2M 2s - 29600K .......... .......... .......... .......... .......... 71% 9,95M 2s - 29650K .......... .......... .......... .......... .......... 71% 61,8M 2s - 29700K .......... .......... .......... .......... .......... 71% 27,6M 2s - 29750K .......... .......... .......... .......... .......... 71% 9,47M 2s - 29800K .......... .......... .......... .......... .......... 71% 49,6M 2s - 29850K .......... .......... .......... .......... .......... 71% 61,8M 2s - 29900K .......... .......... .......... .......... .......... 71% 79,8M 2s - 29950K .......... .......... .......... .......... .......... 72% 43,6M 2s - 30000K .......... .......... .......... .......... .......... 72% 12,1M 2s - 30050K .......... .......... .......... .......... .......... 72% 9,44M 2s - 30100K .......... .......... .......... .......... .......... 72% 62,0M 2s - 30150K .......... .......... .......... .......... .......... 72% 34,3M 2s - 30200K .......... .......... .......... .......... .......... 72% 85,1M 2s - 30250K .......... .......... .......... .......... .......... 72% 10,4M 2s - 30300K .......... .......... .......... .......... .......... 72% 60,9M 2s - 30350K .......... .......... .......... .......... .......... 72% 8,51M 2s - 30400K .......... .......... .......... .......... .......... 73% 52,0M 2s - 30450K .......... .......... .......... .......... .......... 73% 121M 2s - 30500K .......... .......... .......... .......... .......... 73% 9,72M 2s - 30550K .......... .......... .......... .......... .......... 73% 66,8M 2s - 30600K .......... .......... .......... .......... .......... 73% 15,5M 2s - 30650K .......... .......... .......... .......... .......... 73% 27,7M 2s - 30700K .......... .......... .......... .......... .......... 73% 43,3M 2s - 30750K .......... .......... .......... .......... .......... 73% 122M 2s - 30800K .......... .......... .......... .......... .......... 74% 95,3M 2s - 30850K .......... .......... .......... .......... .......... 74% 75,0M 2s - 30900K .......... .......... .......... .......... .......... 74% 137M 2s - 30950K .......... .......... .......... .......... .......... 74% 14,7M 2s - 31000K .......... .......... .......... .......... .......... 74% 78,5M 2s - 31050K .......... .......... .......... .......... .......... 74% 139M 2s - 31100K .......... .......... .......... .......... .......... 74% 27,4M 2s - 31150K .......... .......... .......... .......... .......... 74% 86,3M 2s - 31200K .......... .......... .......... .......... .......... 75% 106M 2s - 31250K .......... .......... .......... .......... .......... 75% 12,0M 2s - 31300K .......... .......... .......... .......... .......... 75% 61,8M 2s - 31350K .......... .......... .......... .......... .......... 75% 2,48M 2s - 31400K .......... .......... .......... .......... .......... 75% 19,5M 2s - 31450K .......... .......... .......... .......... .......... 75% 110M 2s - 31500K .......... .......... .......... .......... .......... 75% 122M 2s - 31550K .......... .......... .......... .......... .......... 75% 126M 2s - 31600K .......... .......... .......... .......... .......... 75% 28,2M 2s - 31650K .......... .......... .......... .......... .......... 76% 83,6M 2s - 31700K .......... .......... .......... .......... .......... 76% 81,5M 2s - 31750K .......... .......... .......... .......... .......... 76% 94,8M 2s - 31800K .......... .......... .......... .......... .......... 76% 83,4M 2s - 31850K .......... .......... .......... .......... .......... 76% 100M 1s - 31900K .......... .......... .......... .......... .......... 76% 70,2M 1s - 31950K .......... .......... .......... .......... .......... 76% 121M 1s - 32000K .......... .......... .......... .......... .......... 76% 61,4M 1s - 32050K .......... .......... .......... .......... .......... 77% 43,4M 1s - 32100K .......... .......... .......... .......... .......... 77% 37,1M 1s - 32150K .......... .......... .......... .......... .......... 77% 11,7M 1s - 32200K .......... .......... .......... .......... .......... 77% 83,8M 1s - 32250K .......... .......... .......... .......... .......... 77% 22,5M 1s - 32300K .......... .......... .......... .......... .......... 77% 9,99M 1s - 32350K .......... .......... .......... .......... .......... 77% 39,0M 1s - 32400K .......... .......... .......... .......... .......... 77% 62,6M 1s - 32450K .......... .......... .......... .......... .......... 78% 117M 1s - 32500K .......... .......... .......... .......... .......... 78% 44,7M 1s - 32550K .......... .......... .......... .......... .......... 78% 14,5M 1s - 32600K .......... .......... .......... .......... .......... 78% 8,11M 1s - 32650K .......... .......... .......... .......... .......... 78% 61,7M 1s - 32700K .......... .......... .......... .......... .......... 78% 31,2M 1s - 32750K .......... .......... .......... .......... .......... 78% 57,9M 1s - 32800K .......... .......... .......... .......... .......... 78% 54,3M 1s - 32850K .......... .......... .......... .......... .......... 78% 13,1M 1s - 32900K .......... .......... .......... .......... .......... 79% 54,3M 1s - 32950K .......... .......... .......... .......... .......... 79% 8,54M 1s - 33000K .......... .......... .......... .......... .......... 79% 46,9M 1s - 33050K .......... .......... .......... .......... .......... 79% 71,3M 1s - 33100K .......... .......... .......... .......... .......... 79% 94,1M 1s - 33150K .......... .......... .......... .......... .......... 79% 11,0M 1s - 33200K .......... .......... .......... .......... .......... 79% 14,1M 1s - 33250K .......... .......... .......... .......... .......... 79% 26,0M 1s - 33300K .......... .......... .......... .......... .......... 80% 71,5M 1s - 33350K .......... .......... .......... .......... .......... 80% 70,9M 1s - 33400K .......... .......... .......... .......... .......... 80% 66,6M 1s - 33450K .......... .......... .......... .......... .......... 80% 72,1M 1s - 33500K .......... .......... .......... .......... .......... 80% 88,0M 1s - 33550K .......... .......... .......... .......... .......... 80% 17,3M 1s - 33600K .......... .......... .......... .......... .......... 80% 52,4M 1s - 33650K .......... .......... .......... .......... .......... 80% 70,5M 1s - 33700K .......... .......... .......... .......... .......... 81% 81,7M 1s - 33750K .......... .......... .......... .......... .......... 81% 77,3M 1s - 33800K .......... .......... .......... .......... .......... 81% 67,6M 1s - 33850K .......... .......... .......... .......... .......... 81% 69,8M 1s - 33900K .......... .......... .......... .......... .......... 81% 91,4M 1s - 33950K .......... .......... .......... .......... .......... 81% 15,6M 1s - 34000K .......... .......... .......... .......... .......... 81% 3,40M 1s - 34050K .......... .......... .......... .......... .......... 81% 6,13M 1s - 34100K .......... .......... .......... .......... .......... 82% 73,9M 1s - 34150K .......... .......... .......... .......... .......... 82% 46,6M 1s - 34200K .......... .......... .......... .......... .......... 82% 51,9M 1s - 34250K .......... .......... .......... .......... .......... 82% 51,7M 1s - 34300K .......... .......... .......... .......... .......... 82% 53,6M 1s - 34350K .......... .......... .......... .......... .......... 82% 44,7M 1s - 34400K .......... .......... .......... .......... .......... 82% 41,9M 1s - 34450K .......... .......... .......... .......... .......... 82% 44,0M 1s - 34500K .......... .......... .......... .......... .......... 82% 43,0M 1s - 34550K .......... .......... .......... .......... .......... 83% 74,0M 1s - 34600K .......... .......... .......... .......... .......... 83% 51,1M 1s - 34650K .......... .......... .......... .......... .......... 83% 54,0M 1s - 34700K .......... .......... .......... .......... .......... 83% 62,2M 1s - 34750K .......... .......... .......... .......... .......... 83% 74,9M 1s - 34800K .......... .......... .......... .......... .......... 83% 119M 1s - 34850K .......... .......... .......... .......... .......... 83% 136M 1s - 34900K .......... .......... .......... .......... .......... 83% 62,2M 1s - 34950K .......... .......... .......... .......... .......... 84% 20,3M 1s - 35000K .......... .......... .......... .......... .......... 84% 54,3M 1s - 35050K .......... .......... .......... .......... .......... 84% 11,2M 1s - 35100K .......... .......... .......... .......... .......... 84% 28,9M 1s - 35150K .......... .......... .......... .......... .......... 84% 54,5M 1s - 35200K .......... .......... .......... .......... .......... 84% 99,8M 1s - 35250K .......... .......... .......... .......... .......... 84% 169M 1s - 35300K .......... .......... .......... .......... .......... 84% 13,1M 1s - 35350K .......... .......... .......... .......... .......... 85% 7,96M 1s - 35400K .......... .......... .......... .......... .......... 85% 50,9M 1s - 35450K .......... .......... .......... .......... .......... 85% 47,9M 1s - 35500K .......... .......... .......... .......... .......... 85% 52,4M 1s - 35550K .......... .......... .......... .......... .......... 85% 57,5M 1s - 35600K .......... .......... .......... .......... .......... 85% 70,1M 1s - 35650K .......... .......... .......... .......... .......... 85% 14,8M 1s - 35700K .......... .......... .......... .......... .......... 85% 11,2M 1s - 35750K .......... .......... .......... .......... .......... 85% 10,8M 1s - 35800K .......... .......... .......... .......... .......... 86% 90,7M 1s - 35850K .......... .......... .......... .......... .......... 86% 68,4M 1s - 35900K .......... .......... .......... .......... .......... 86% 22,4M 1s - 35950K .......... .......... .......... .......... .......... 86% 62,0M 1s - 36000K .......... .......... .......... .......... .......... 86% 15,4M 1s - 36050K .......... .......... .......... .......... .......... 86% 26,6M 1s - 36100K .......... .......... .......... .......... .......... 86% 86,4M 1s - 36150K .......... .......... .......... .......... .......... 86% 43,3M 1s - 36200K .......... .......... .......... .......... .......... 87% 89,9M 1s - 36250K .......... .......... .......... .......... .......... 87% 100M 1s - 36300K .......... .......... .......... .......... .......... 87% 84,9M 1s - 36350K .......... .......... .......... .......... .......... 87% 16,9M 1s - 36400K .......... .......... .......... .......... .......... 87% 75,4M 1s - 36450K .......... .......... .......... .......... .......... 87% 98,4M 1s - 36500K .......... .......... .......... .......... .......... 87% 94,8M 1s - 36550K .......... .......... .......... .......... .......... 87% 4,17M 1s - 36600K .......... .......... .......... .......... .......... 88% 236M 1s - 36650K .......... .......... .......... .......... .......... 88% 271M 1s - 36700K .......... .......... .......... .......... .......... 88% 263M 1s - 36750K .......... .......... .......... .......... .......... 88% 273M 1s - 36800K .......... .......... .......... .......... .......... 88% 220M 1s - 36850K .......... .......... .......... .......... .......... 88% 26,3M 1s - 36900K .......... .......... .......... .......... .......... 88% 4,03M 1s - 36950K .......... .......... .......... .......... .......... 88% 15,4M 1s - 37000K .......... .......... .......... .......... .......... 88% 87,5M 1s - 37050K .......... .......... .......... .......... .......... 89% 96,7M 1s - 37100K .......... .......... .......... .......... .......... 89% 103M 1s - 37150K .......... .......... .......... .......... .......... 89% 82,8M 1s - 37200K .......... .......... .......... .......... .......... 89% 76,2M 1s - 37250K .......... .......... .......... .......... .......... 89% 145M 1s - 37300K .......... .......... .......... .......... .......... 89% 36,0M 1s - 37350K .......... .......... .......... .......... .......... 89% 98,7M 1s - 37400K .......... .......... .......... .......... .......... 89% 90,8M 1s - 37450K .......... .......... .......... .......... .......... 90% 99,7M 1s - 37500K .......... .......... .......... .......... .......... 90% 145M 1s - 37550K .......... .......... .......... .......... .......... 90% 99,3M 1s - 37600K .......... .......... .......... .......... .......... 90% 30,2M 1s - 37650K .......... .......... .......... .......... .......... 90% 149M 1s - 37700K .......... .......... .......... .......... .......... 90% 69,9M 1s - 37750K .......... .......... .......... .......... .......... 90% 12,5M 1s - 37800K .......... .......... .......... .......... .......... 90% 66,3M 1s - 37850K .......... .......... .......... .......... .......... 91% 88,5M 1s - 37900K .......... .......... .......... .......... .......... 91% 24,3M 0s - 37950K .......... .......... .......... .......... .......... 91% 11,8M 0s - 38000K .......... .......... .......... .......... .......... 91% 20,9M 0s - 38050K .......... .......... .......... .......... .......... 91% 60,5M 0s - 38100K .......... .......... .......... .......... .......... 91% 118M 0s - 38150K .......... .......... .......... .......... .......... 91% 114M 0s - 38200K .......... .......... .......... .......... .......... 91% 17,3M 0s - 38250K .......... .......... .......... .......... .......... 91% 8,87M 0s - 38300K .......... .......... .......... .......... .......... 92% 70,9M 0s - 38350K .......... .......... .......... .......... .......... 92% 26,9M 0s - 38400K .......... .......... .......... .......... .......... 92% 94,6M 0s - 38450K .......... .......... .......... .......... .......... 92% 99,7M 0s - 38500K .......... .......... .......... .......... .......... 92% 97,3M 0s - 38550K .......... .......... .......... .......... .......... 92% 96,8M 0s - 38600K .......... .......... .......... .......... .......... 92% 12,2M 0s - 38650K .......... .......... .......... .......... .......... 92% 52,0M 0s - 38700K .......... .......... .......... .......... .......... 93% 6,15M 0s - 38750K .......... .......... .......... .......... .......... 93% 68,5M 0s - 38800K .......... .......... .......... .......... .......... 93% 82,7M 0s - 38850K .......... .......... .......... .......... .......... 93% 16,7M 0s - 38900K .......... .......... .......... .......... .......... 93% 117M 0s - 38950K .......... .......... .......... .......... .......... 93% 20,1M 0s - 39000K .......... .......... .......... .......... .......... 93% 71,4M 0s - 39050K .......... .......... .......... .......... .......... 93% 19,6M 0s - 39100K .......... .......... .......... .......... .......... 94% 131M 0s - 39150K .......... .......... .......... .......... .......... 94% 48,5M 0s - 39200K .......... .......... .......... .......... .......... 94% 36,2M 0s - 39250K .......... .......... .......... .......... .......... 94% 65,7M 0s - 39300K .......... .......... .......... .......... .......... 94% 136M 0s - 39350K .......... .......... .......... .......... .......... 94% 24,8M 0s - 39400K .......... .......... .......... .......... .......... 94% 63,1M 0s - 39450K .......... .......... .......... .......... .......... 94% 79,9M 0s - 39500K .......... .......... .......... .......... .......... 94% 123M 0s - 39550K .......... .......... .......... .......... .......... 95% 6,16M 0s - 39600K .......... .......... .......... .......... .......... 95% 14,5M 0s - 39650K .......... .......... .......... .......... .......... 95% 19,8M 0s - 39700K .......... .......... .......... .......... .......... 95% 103M 0s - 39750K .......... .......... .......... .......... .......... 95% 104M 0s - 39800K .......... .......... .......... .......... .......... 95% 98,2M 0s - 39850K .......... .......... .......... .......... .......... 95% 91,2M 0s - 39900K .......... .......... .......... .......... .......... 95% 4,90M 0s - 39950K .......... .......... .......... .......... .......... 96% 116M 0s - 40000K .......... .......... .......... .......... .......... 96% 9,96M 0s - 40050K .......... .......... .......... .......... .......... 96% 93,2M 0s - 40100K .......... .......... .......... .......... .......... 96% 100M 0s - 40150K .......... .......... .......... .......... .......... 96% 147M 0s - 40200K .......... .......... .......... .......... .......... 96% 114M 0s - 40250K .......... .......... .......... .......... .......... 96% 99,1M 0s - 40300K .......... .......... .......... .......... .......... 96% 92,2M 0s - 40350K .......... .......... .......... .......... .......... 97% 98,0M 0s - 40400K .......... .......... .......... .......... .......... 97% 71,4M 0s - 40450K .......... .......... .......... .......... .......... 97% 96,9M 0s - 40500K .......... .......... .......... .......... .......... 97% 96,5M 0s - 40550K .......... .......... .......... .......... .......... 97% 92,0M 0s - 40600K .......... .......... .......... .......... .......... 97% 88,5M 0s - 40650K .......... .......... .......... .......... .......... 97% 96,6M 0s - 40700K .......... .......... .......... .......... .......... 97% 43,2M 0s - 40750K .......... .......... .......... .......... .......... 97% 81,9M 0s - 40800K .......... .......... .......... .......... .......... 98% 11,4M 0s - 40850K .......... .......... .......... .......... .......... 98% 25,4M 0s - 40900K .......... .......... .......... .......... .......... 98% 79,8M 0s - 40950K .......... .......... .......... .......... .......... 98% 11,8M 0s - 41000K .......... .......... .......... .......... .......... 98% 25,7M 0s - 41050K .......... .......... .......... .......... .......... 98% 57,9M 0s - 41100K .......... .......... .......... .......... .......... 98% 103M 0s - 41150K .......... .......... .......... .......... .......... 98% 41,8M 0s - 41200K .......... .......... .......... .......... .......... 99% 50,4M 0s - 41250K .......... .......... .......... .......... .......... 99% 6,45M 0s - 41300K .......... .......... .......... .......... .......... 99% 43,8M 0s - 41350K .......... .......... .......... .......... .......... 99% 65,6M 0s - 41400K .......... .......... .......... .......... .......... 99% 39,4M 0s - 41450K .......... .......... .......... .......... .......... 99% 48,9M 0s - 41500K .......... .......... .......... .......... .......... 99% 64,9M 0s - 41550K .......... .......... .......... .......... .......... 99% 74,2M 0s - 41600K .......... .......... .......... .......... ...... 100% 69,8M=5,2s - -2014-06-18 13:41:12 (7,77 MB/s) - ‘/home/jwiklund/Documents/.git/annex/tmp/SHA256E-s42645638--4ae41fb29bd26339ea10f53ea2b7cf3132e53d5e8fbfde7b43b912aa52b3d319.tar.gz’ saved [42645638/42645638] - -[2014-06-18 13:41:12 CEST] main(checksum...) -: Downloaded git-annex.. upgrade) -[2014-06-18 13:41:12 CEST] Pusher: Syncing with born -(Recording state in git...) - -error: duplicate parent bd2e43b03fcc307166df1ab23cecb0eafe9ca3a5 ignored -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - cf9f2a9..f8f8217 git-annex -> synced/git-annex - 6be6bb3..bd2e43b annex/direct/master -> synced/master - -git-annex version: 5.20140610-g5ec8bcf -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -[2014-06-18 13:41:14 CEST] main: Upgrading git-annex -[2014-06-18 13:41:14 CEST] UpgradeWatcher: A new version of git-annex has been installed. - -error: duplicate parent e88b1485767e39ac05de700219d31011b7ac7022 ignored - - -error: duplicate parent 220161f6ad836cfc581a9dd575d76c0d9e814826 ignored - - -Another upgrade - -[2014-06-18 13:38:15 CEST] main: starting assistant version 5.20140606-g48793b6 -[2014-06-18 13:38:16 CEST] TransferScanner: Syncing with born - -Already up-to-date. -(scanning...) [20 -14-06-18 13:38:16 CEST] Watcher: Performing startup scan -Already up-to-date. -(started...) -gpg: WARNING: unsafe permissions on homedir `/tmp/git-annex-gpg.tmp.0' -gpg: Signature made fre 13 jun 2014 17:28:22 CEST using DSA key ID 89C809CB -gpg: /tmp/git-annex-gpg.tmp.0/trustdb.gpg: trustdb created -gpg: Good signature from "git-annex distribution signing key (for Joey Hess) <id@joeyh.name>" -gpg: WARNING: This key is not certified with a trusted signature! -gpg: There is no indication that the signature belongs to the owner. -Primary key fingerprint: 4005 5C6A FD2D 526B 2961 E78F 5EE1 DBA7 89C8 09CB -[2014-06-18 13:38:17 CEST] Upgrader: An upgrade of git-annex is available. (version 5.20140613) -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - 9537540..38006f5 git-annex -> synced/git-annex -[2014-06-18 13:38:18 CEST] Committer: Committing changes to git -(Recording state in git...) -[2014-06-18 13:38:18 CEST] Pusher: Syncing with born -Everything up-to-date ---2014-06-18 13:38:22-- https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz -Resolving downloads.kitenet.net (downloads.kitenet.net)... 107.170.31.195 -Connecting to downloads.kitenet.net (downloads.kitenet.net)|107.170.31.195|:443... connected. -HTTP request sent, awaiting response... 200 OK -Length: 42645638 (41M) [application/x-gzip] -Saving to: ‘/home/jwiklund/Documents/.git/annex/tmp/SHA256E-s42645638--4ae41fb29bd26339ea10f53ea2b7cf3132e53d5e8fbfde7b43b912aa52b3d319.tar.gz’ - - 0K .......... .......... .......... .......... .......... 0% 165K 4m12s - 50K .......... .......... .......... .......... .......... 0% 165K 4m12s - 100K .......... .......... .......... .......... .......... 0% 248K 3m43s - 150K .......... .......... .......... .......... .......... 0% 247K 3m29s - 200K .......... .......... .......... .......... .......... 0% 493K 3m4s - 250K .......... .......... .......... .......... .......... 0% 248K 3m1s - 300K .......... .......... .......... .......... .......... 0% 493K 2m47s - 350K .......... .......... .......... .......... .......... 0% 495K 2m36s - 400K .......... .......... .......... .......... .......... 1% 248K 2m37s - 450K .......... .......... .......... .......... .......... 1% 494K 2m30s - 500K .......... .......... .......... .......... .......... 1% 147M 2m16s - 550K .......... .......... .......... .......... .......... 1% 493K 2m11s - 600K .......... .......... .......... .......... .......... 1% 495K 2m7s - 650K .......... .......... .......... .......... .......... 1% 494K 2m4s - 700K .......... .......... .......... .......... .......... 1% 495K 2m1s - 750K .......... .......... .......... .......... .......... 1% 1,30M 1m55s - 800K .......... .......... .......... .......... .......... 2% 497K 1m53s - 850K .......... .......... .......... .......... .......... 2% 779K 1m50s - 900K .......... .......... .......... .......... .......... 2% 1,32M 1m45s - 950K .......... .......... .......... .......... .......... 2% 495K 1m44s - 1000K .......... .......... .......... .......... .......... 2% 48,8M 99s - 1050K .......... .......... .......... .......... .......... 2% 497K 98s - 1100K .......... .......... .......... .......... .......... 2% 8,40M 94s - 1150K .......... .......... .......... .......... .......... 2% 524K 93s - 1200K .......... .......... .......... .......... .......... 3% 786K 91s - 1250K .......... .......... .......... .......... .......... 3% 1,31M 89s - 1300K .......... .......... .......... .......... .......... 3% 8,46M 86s - 1350K .......... .......... .......... .......... .......... 3% 526K 85s - 1400K .......... .......... .......... .......... .......... 3% 8,23M 82s - 1450K .......... .......... .......... .......... .......... 3% 53,9M 80s - 1500K .......... .......... .......... .......... .......... 3% 523K 79s - 1550K .......... .......... .......... .......... .......... 3% 10,7M 77s - 1600K .......... .......... .......... .......... .......... 3% 865K 76s - 1650K .......... .......... .......... .......... .......... 4% 1,12M 75s - 1700K .......... .......... .......... .......... .......... 4% 59,8M 72s - 1750K .......... .......... .......... .......... .......... 4% 875K 72s - 1800K .......... .......... .......... .......... .......... 4% 1,26M 70s - 1850K .......... .......... .......... .......... .......... 4% 5,14M 69s - 1900K .......... .......... .......... .......... .......... 4% 968K 68s - 1950K .......... .......... .......... .......... .......... 4% 1,24M 67s - 2000K .......... .......... .......... .......... .......... 4% 4,91M 65s - 2050K .......... .......... .......... .......... .......... 5% 969K 65s - 2100K .......... .......... .......... .......... .......... 5% 1,13M 64s - 2150K .......... .......... .......... .......... .......... 5% 38,0M 62s - 2200K .......... .......... .......... .......... .......... 5% 9,06M 61s - 2250K .......... .......... .......... .......... .......... 5% 525K 61s - 2300K .......... .......... .......... .......... .......... 5% 72,7M 60s - 2350K .......... .......... .......... .......... .......... 5% 70,4M 59s - 2400K .......... .......... .......... .......... .......... 5% 9,59M 57s - 2450K .......... .......... .......... .......... .......... 6% 528K 58s - 2500K .......... .......... .......... .......... .......... 6% 62,6M 56s - 2550K .......... .......... .......... .......... .......... 6% 10,0M 55s - 2600K .......... .......... .......... .......... .......... 6% 88,8M 54s - 2650K .......... .......... .......... .......... .......... 6% 521K 55s - 2700K .......... .......... .......... .......... .......... 6% 133M 54s - 2750K .......... .......... .......... .......... .......... 6% 11,6M 53s - 2800K .......... .......... .......... .......... .......... 6% 7,35M 52s - 2850K .......... .......... .......... .......... .......... 6% 554K 52s - 2900K .......... .......... .......... .......... .......... 7% 22,5M 51s - 2950K .......... .......... .......... .......... .......... 7% 18,7M 50s - 3000K .......... .......... .......... .......... .......... 7% 8,07M 49s - 3050K .......... .......... .......... .......... .......... 7% 548K 50s - 3100K .......... .......... .......... .......... .......... 7% 56,1M 49s - 3150K .......... .......... .......... .......... .......... 7% 38,2M 48s - 3200K .......... .......... .......... .......... .......... 7% 25,9M 47s - 3250K .......... .......... .......... .......... .......... 7% 8,37M 46s - 3300K .......... .......... .......... .......... .......... 8% 7,57M 46s - 3350K .......... .......... .......... .......... .......... 8% 585K 46s - 3400K .......... .......... .......... .......... .......... 8% 28,9M 45s - 3450K .......... .......... .......... .......... .......... 8% 35,6M 45s - 3500K .......... .......... .......... .......... .......... 8% 8,14M 44s - 3550K .......... .......... .......... .......... .......... 8% 72,0M 43s - 3600K .......... .......... .......... .......... .......... 8% 4,17M 43s - 3650K .......... .......... .......... .......... .......... 8% 619K 43s - 3700K .......... .......... .......... .......... .......... 9% 28,8M 42s - 3750K .......... .......... .......... .......... .......... 9% 8,04M 42s - 3800K .......... .......... .......... .......... .......... 9% 57,3M 41s - 3850K .......... .......... .......... .......... .......... 9% 12,1M 41s - 3900K .......... .......... .......... .......... .......... 9% 6,22M 40s - 3950K .......... .......... .......... .......... .......... 9% 620K 40s - 4000K .......... .......... .......... .......... .......... 9% 19,1M 40s - 4050K .......... .......... .......... .......... .......... 9% 55,1M 39s - 4100K .......... .......... .......... .......... .......... 9% 9,63M 39s - 4150K .......... .......... .......... .......... .......... 10% 12,0M 38s - 4200K .......... .......... .......... .......... .......... 10% 8,14M 38s - 4250K .......... .......... .......... .......... .......... 10% 15,8M 37s - 4300K .......... .......... .......... .......... .......... 10% 625K 38s - 4350K .......... .......... .......... .......... .......... 10% 24,5M 37s - 4400K .......... .......... .......... .......... .......... 10% 8,66M 37s - 4450K .......... .......... .......... .......... .......... 10% 13,0M 36s - 4500K .......... .......... .......... .......... .......... 10% 71,5M 36s - 4550K .......... .......... .......... .......... .......... 11% 8,28M 36s - 4600K .......... .......... .......... .......... .......... 11% 6,10M 35s - 4650K .......... .......... .......... .......... .......... 11% 653K 35s - 4700K .......... .......... .......... .......... .......... 11% 50,6M 35s - 4750K .......... .......... .......... .......... .......... 11% 8,95M 35s - 4800K .......... .......... .......... .......... .......... 11% 11,5M 34s - 4850K .......... .......... .......... .......... .......... 11% 8,84M 34s - 4900K .......... .......... .......... .......... .......... 11% 53,4M 33s - 4950K .......... .......... .......... .......... .......... 12% 7,17M 33s - 5000K .......... .......... .......... .......... .......... 12% 53,7M 33s - 5050K .......... .......... .......... .......... .......... 12% 649K 33s - 5100K .......... .......... .......... .......... .......... 12% 9,07M 33s - 5150K .......... .......... .......... .......... .......... 12% 10,7M 32s - 5200K .......... .......... .......... .......... .......... 12% 9,40M 32s - 5250K .......... .......... .......... .......... .......... 12% 47,5M 32s - 5300K .......... .......... .......... .......... .......... 12% 68,6M 31s - 5350K .......... .......... .......... .......... .......... 12% 7,06M 31s - 5400K .......... .......... .......... .......... .......... 13% 11,4M 31s - 5450K .......... .......... .......... .......... .......... 13% 688K 31s - 5500K .......... .......... .......... .......... .......... 13% 8,70M 31s - 5550K .......... .......... .......... .......... .......... 13% 11,1M 30s - 5600K .......... .......... .......... .......... .......... 13% 8,83M 30s - 5650K .......... .......... .......... .......... .......... 13% 58,9M 30s - 5700K .......... .......... .......... .......... .......... 13% 83,1M 29s - 5750K .......... .......... .......... .......... .......... 13% 7,21M 29s - 5800K .......... .......... .......... .......... .......... 14% 66,1M 29s - 5850K .......... .......... .......... .......... .......... 14% 4,65M 29s - 5900K .......... .......... .......... .......... .......... 14% 757K 29s - 5950K .......... .......... .......... .......... .......... 14% 7,62M 29s - 6000K .......... .......... .......... .......... .......... 14% 10,4M 28s - 6050K .......... .......... .......... .......... .......... 14% 8,59M 28s - 6100K .......... .......... .......... .......... .......... 14% 51,4M 28s - 6150K .......... .......... .......... .......... .......... 14% 74,5M 28s - 6200K .......... .......... .......... .......... .......... 15% 6,84M 27s - 6250K .......... .......... .......... .......... .......... 15% 67,2M 27s - 6300K .......... .......... .......... .......... .......... 15% 5,40M 27s - 6350K .......... .......... .......... .......... .......... 15% 63,4M 27s - 6400K .......... .......... .......... .......... .......... 15% 706K 27s - 6450K .......... .......... .......... .......... .......... 15% 9,08M 27s - 6500K .......... .......... .......... .......... .......... 15% 9,43M 26s - 6550K .......... .......... .......... .......... .......... 15% 70,0M 26s - 6600K .......... .......... .......... .......... .......... 15% 65,4M 26s - 6650K .......... .......... .......... .......... .......... 16% 67,7M 26s - 6700K .......... .......... .......... .......... .......... 16% 7,02M 25s - 6750K .......... .......... .......... .......... .......... 16% 65,8M 25s - 6800K .......... .......... .......... .......... .......... 16% 4,77M 25s - 6850K .......... .......... .......... .......... .......... 16% 64,7M 25s - 6900K .......... .......... .......... .......... .......... 16% 783K 25s - 6950K .......... .......... .......... .......... .......... 16% 4,63M 25s - 7000K .......... .......... .......... .......... .......... 16% 9,00M 25s - 7050K .......... .......... .......... .......... .......... 17% 69,7M 24s - 7100K .......... .......... .......... .......... .......... 17% 64,8M 24s - 7150K .......... .......... .......... .......... .......... 17% 53,1M 24s - 7200K .......... .......... .......... .......... .......... 17% 6,69M 24s - 7250K .......... .......... .......... .......... .......... 17% 70,3M 24s - 7300K .......... .......... .......... .......... .......... 17% 8,28M 23s - 7350K .......... .......... .......... .......... .......... 17% 12,7M 23s - 7400K .......... .......... .......... .......... .......... 17% 765K 23s - 7450K .......... .......... .......... .......... .......... 18% 9,09M 23s - 7500K .......... .......... .......... .......... .......... 18% 4,85M 23s - 7550K .......... .......... .......... .......... .......... 18% 61,3M 23s - 7600K .......... .......... .......... .......... .......... 18% 61,6M 23s - 7650K .......... .......... .......... .......... .......... 18% 74,1M 23s - 7700K .......... .......... .......... .......... .......... 18% 73,6M 22s - 7750K .......... .......... .......... .......... .......... 18% 7,79M 22s - 7800K .......... .......... .......... .......... .......... 18% 49,1M 22s - 7850K .......... .......... .......... .......... .......... 18% 72,2M 22s - 7900K .......... .......... .......... .......... .......... 19% 8,42M 22s - 7950K .......... .......... .......... .......... .......... 19% 732K 22s - 8000K .......... .......... .......... .......... .......... 19% 8,99M 22s - 8050K .......... .......... .......... .......... .......... 19% 50,7M 22s - 8100K .......... .......... .......... .......... .......... 19% 5,19M 21s - 8150K .......... .......... .......... .......... .......... 19% 47,4M 21s - 8200K .......... .......... .......... .......... .......... 19% 48,4M 21s - 8250K .......... .......... .......... .......... .......... 19% 52,5M 21s - 8300K .......... .......... .......... .......... .......... 20% 80,5M 21s - 8350K .......... .......... .......... .......... .......... 20% 8,32M 21s - 8400K .......... .......... .......... .......... .......... 20% 40,0M 21s - 8450K .......... .......... .......... .......... .......... 20% 8,81M 20s - 8500K .......... .......... .......... .......... .......... 20% 75,7M 20s - 8550K .......... .......... .......... .......... .......... 20% 718K 20s - 8600K .......... .......... .......... .......... .......... 20% 46,3M 20s - 8650K .......... .......... .......... .......... .......... 20% 15,7M 20s - 8700K .......... .......... .......... .......... .......... 21% 81,4M 20s - 8750K .......... .......... .......... .......... .......... 21% 4,92M 20s - 8800K .......... .......... .......... .......... .......... 21% 44,6M 20s - 8850K .......... .......... .......... .......... .......... 21% 32,6M 20s - 8900K .......... .......... .......... .......... .......... 21% 94,8M 19s - 8950K .......... .......... .......... .......... .......... 21% 104M 19s - 9000K .......... .......... .......... .......... .......... 21% 8,37M 19s - 9050K .......... .......... .......... .......... .......... 21% 77,8M 19s - 9100K .......... .......... .......... .......... .......... 21% 76,5M 19s - 9150K .......... .......... .......... .......... .......... 22% 88,5M 19s - 9200K .......... .......... .......... .......... .......... 22% 4,91M 19s - 9250K .......... .......... .......... .......... .......... 22% 762K 19s - 9300K .......... .......... .......... .......... .......... 22% 57,2M 19s - 9350K .......... .......... .......... .......... .......... 22% 15,2M 19s - 9400K .......... .......... .......... .......... .......... 22% 4,79M 18s - 9450K .......... .......... .......... .......... .......... 22% 69,4M 18s - 9500K .......... .......... .......... .......... .......... 22% 66,2M 18s - 9550K .......... .......... .......... .......... .......... 23% 29,9M 18s - 9600K .......... .......... .......... .......... .......... 23% 58,8M 18s - 9650K .......... .......... .......... .......... .......... 23% 9,77M 18s - 9700K .......... .......... .......... .......... .......... 23% 45,1M 18s - 9750K .......... .......... .......... .......... .......... 23% 64,3M 18s - 9800K .......... .......... .......... .......... .......... 23% 59,4M 18s - 9850K .......... .......... .......... .......... .......... 23% 10,2M 17s - 9900K .......... .......... .......... .......... .......... 23% 55,9M 17s - 9950K .......... .......... .......... .......... .......... 24% 93,7M 17s - 10000K .......... .......... .......... .......... .......... 24% 730K 17s - 10050K .......... .......... .......... .......... .......... 24% 66,3M 17s - 10100K .......... .......... .......... .......... .......... 24% 13,6M 17s - 10150K .......... .......... .......... .......... .......... 24% 86,6M 17s - 10200K .......... .......... .......... .......... .......... 24% 4,97M 17s - 10250K .......... .......... .......... .......... .......... 24% 33,2M 17s - 10300K .......... .......... .......... .......... .......... 24% 34,1M 17s - 10350K .......... .......... .......... .......... .......... 24% 158M 17s - 10400K .......... .......... .......... .......... .......... 25% 65,6M 16s - 10450K .......... .......... .......... .......... .......... 25% 9,12M 16s - 10500K .......... .......... .......... .......... .......... 25% 101M 16s - 10550K .......... .......... .......... .......... .......... 25% 65,6M 16s - 10600K .......... .......... .......... .......... .......... 25% 44,4M 16s - 10650K .......... .......... .......... .......... .......... 25% 8,78M 16s - 10700K .......... .......... .......... .......... .......... 25% 97,5M 16s - 10750K .......... .......... .......... .......... .......... 25% 7,92M 16s - 10800K .......... .......... .......... .......... .......... 26% 6,88M 16s - 10850K .......... .......... .......... .......... .......... 26% 886K 16s - 10900K .......... .......... .......... .......... .......... 26% 66,7M 16s - 10950K .......... .......... .......... .......... .......... 26% 12,5M 16s - 11000K .......... .......... .......... .......... .......... 26% 5,70M 16s - 11050K .......... .......... .......... .......... .......... 26% 65,8M 15s - 11100K .......... .......... .......... .......... .......... 26% 25,5M 15s - 11150K .......... .......... .......... .......... .......... 26% 35,3M 15s - 11200K .......... .......... .......... .......... .......... 27% 55,0M 15s - 11250K .......... .......... .......... .......... .......... 27% 9,19M 15s - 11300K .......... .......... .......... .......... .......... 27% 58,9M 15s - 11350K .......... .......... .......... .......... .......... 27% 64,1M 15s - 11400K .......... .......... .......... .......... .......... 27% 57,1M 15s - 11450K .......... .......... .......... .......... .......... 27% 9,39M 15s - 11500K .......... .......... .......... .......... .......... 27% 84,9M 15s - 11550K .......... .......... .......... .......... .......... 27% 89,1M 15s - 11600K .......... .......... .......... .......... .......... 27% 8,04M 15s - 11650K .......... .......... .......... .......... .......... 28% 85,4M 14s - 11700K .......... .......... .......... .......... .......... 28% 815K 15s - 11750K .......... .......... .......... .......... .......... 28% 44,9M 14s - 11800K .......... .......... .......... .......... .......... 28% 131M 14s - 11850K .......... .......... .......... .......... .......... 28% 12,7M 14s - 11900K .......... .......... .......... .......... .......... 28% 5,71M 14s - 11950K .......... .......... .......... .......... .......... 28% 19,3M 14s - 12000K .......... .......... .......... .......... .......... 28% 22,0M 14s - 12050K .......... .......... .......... .......... .......... 29% 111M 14s - 12100K .......... .......... .......... .......... .......... 29% 44,5M 14s - 12150K .......... .......... .......... .......... .......... 29% 10,8M 14s - 12200K .......... .......... .......... .......... .......... 29% 169M 14s - 12250K .......... .......... .......... .......... .......... 29% 102M 14s - 12300K .......... .......... .......... .......... .......... 29% 97,9M 14s - 12350K .......... .......... .......... .......... .......... 29% 8,70M 14s - 12400K .......... .......... .......... .......... .......... 29% 47,2M 13s - 12450K .......... .......... .......... .......... .......... 30% 9,37M 13s - 12500K .......... .......... .......... .......... .......... 30% 77,2M 13s - 12550K .......... .......... .......... .......... .......... 30% 44,6M 13s - 12600K .......... .......... .......... .......... .......... 30% 84,0M 13s - 12650K .......... .......... .......... .......... .......... 30% 2,51M 13s - 12700K .......... .......... .......... .......... .......... 30% 1,15M 13s - 12750K .......... .......... .......... .......... .......... 30% 60,1M 13s - 12800K .......... .......... .......... .......... .......... 30% 12,1M 13s - 12850K .......... .......... .......... .......... .......... 30% 5,66M 13s - 12900K .......... .......... .......... .......... .......... 31% 22,1M 13s - 12950K .......... .......... .......... .......... .......... 31% 56,1M 13s - 13000K .......... .......... .......... .......... .......... 31% 27,4M 13s - 13050K .......... .......... .......... .......... .......... 31% 45,7M 13s - 13100K .......... .......... .......... .......... .......... 31% 10,4M 13s - 13150K .......... .......... .......... .......... .......... 31% 69,7M 13s - 13200K .......... .......... .......... .......... .......... 31% 60,2M 13s - 13250K .......... .......... .......... .......... .......... 31% 39,8M 12s - 13300K .......... .......... .......... .......... .......... 32% 11,8M 12s - 13350K .......... .......... .......... .......... .......... 32% 66,0M 12s - 13400K .......... .......... .......... .......... .......... 32% 48,4M 12s - 13450K .......... .......... .......... .......... .......... 32% 9,81M 12s - 13500K .......... .......... .......... .......... .......... 32% 23,9M 12s - 13550K .......... .......... .......... .......... .......... 32% 54,2M 12s - 13600K .......... .......... .......... .......... .......... 32% 54,2M 12s - 13650K .......... .......... .......... .......... .......... 32% 10,8M 12s - 13700K .......... .......... .......... .......... .......... 33% 908K 12s - 13750K .......... .......... .......... .......... .......... 33% 34,0M 12s - 13800K .......... .......... .......... .......... .......... 33% 14,8M 12s - 13850K .......... .......... .......... .......... .......... 33% 5,88M 12s - 13900K .......... .......... .......... .......... .......... 33% 44,5M 12s - 13950K .......... .......... .......... .......... .......... 33% 22,8M 12s - 14000K .......... .......... .......... .......... .......... 33% 22,8M 12s - 14050K .......... .......... .......... .......... .......... 33% 60,0M 12s - 14100K .......... .......... .......... .......... .......... 33% 10,5M 12s - 14150K .......... .......... .......... .......... .......... 34% 66,9M 11s - 14200K .......... .......... .......... .......... .......... 34% 63,9M 11s - 14250K .......... .......... .......... .......... .......... 34% 68,9M 11s - 14300K .......... .......... .......... .......... .......... 34% 11,4M 11s - 14350K .......... .......... .......... .......... .......... 34% 50,6M 11s - 14400K .......... .......... .......... .......... .......... 34% 54,7M 11s - 14450K .......... .......... .......... .......... .......... 34% 74,5M 11s - 14500K .......... .......... .......... .......... .......... 34% 10,4M 11s - 14550K .......... .......... .......... .......... .......... 35% 33,4M 11s - 14600K .......... .......... .......... .......... .......... 35% 62,0M 11s - 14650K .......... .......... .......... .......... .......... 35% 35,2M 11s - 14700K .......... .......... .......... .......... .......... 35% 75,6M 11s - 14750K .......... .......... .......... .......... .......... 35% 11,9M 11s - 14800K .......... .......... .......... .......... .......... 35% 908K 11s - 14850K .......... .......... .......... .......... .......... 35% 37,1M 11s - 14900K .......... .......... .......... .......... .......... 35% 12,6M 11s - 14950K .......... .......... .......... .......... .......... 36% 7,11M 11s - 15000K .......... .......... .......... .......... .......... 36% 13,5M 11s - 15050K .......... .......... .......... .......... .......... 36% 71,6M 11s - 15100K .......... .......... .......... .......... .......... 36% 24,4M 11s - 15150K .......... .......... .......... .......... .......... 36% 69,1M 10s - 15200K .......... .......... .......... .......... .......... 36% 63,0M 10s - 15250K .......... .......... .......... .......... .......... 36% 10,1M 10s - 15300K .......... .......... .......... .......... .......... 36% 37,9M 10s - 15350K .......... .......... .......... .......... .......... 36% 69,2M 10s - 15400K .......... .......... .......... .......... .......... 37% 68,1M 10s - 15450K .......... .......... .......... .......... .......... 37% 10,4M 10s - 15500K .......... .......... .......... .......... .......... 37% 64,3M 10s - 15550K .......... .......... .......... .......... .......... 37% 81,2M 10s - 15600K .......... .......... .......... .......... .......... 37% 71,2M 10s - 15650K .......... .......... .......... .......... .......... 37% 13,3M 10s - 15700K .......... .......... .......... .......... .......... 37% 43,7M 10s - 15750K .......... .......... .......... .......... .......... 37% 28,3M 10s - 15800K .......... .......... .......... .......... .......... 38% 59,9M 10s - 15850K .......... .......... .......... .......... .......... 38% 84,3M 10s - 15900K .......... .......... .......... .......... .......... 38% 12,2M 10s - 15950K .......... .......... .......... .......... .......... 38% 8,59M 10s - 16000K .......... .......... .......... .......... .......... 38% 926K 10s - 16050K .......... .......... .......... .......... .......... 38% 65,0M 10s - 16100K .......... .......... .......... .......... .......... 38% 70,3M 10s - 16150K .......... .......... .......... .......... .......... 38% 7,79M 10s - 16200K .......... .......... .......... .......... .......... 39% 14,6M 10s - 16250K .......... .......... .......... .......... .......... 39% 71,5M 10s - 16300K .......... .......... .......... .......... .......... 39% 21,6M 9s - 16350K .......... .......... .......... .......... .......... 39% 73,9M 9s - 16400K .......... .......... .......... .......... .......... 39% 56,4M 9s - 16450K .......... .......... .......... .......... .......... 39% 9,36M 9s - 16500K .......... .......... .......... .......... .......... 39% 69,8M 9s - 16550K .......... .......... .......... .......... .......... 39% 67,0M 9s - 16600K .......... .......... .......... .......... .......... 39% 58,4M 9s - 16650K .......... .......... .......... .......... .......... 40% 9,56M 9s - 16700K .......... .......... .......... .......... .......... 40% 71,2M 9s - 16750K .......... .......... .......... .......... .......... 40% 74,3M 9s - 16800K .......... .......... .......... .......... .......... 40% 63,4M 9s - 16850K .......... .......... .......... .......... .......... 40% 17,3M 9s - 16900K .......... .......... .......... .......... .......... 40% 60,6M 9s - 16950K .......... .......... .......... .......... .......... 40% 67,8M 9s - 17000K .......... .......... .......... .......... .......... 40% 30,6M 9s - 17050K .......... .......... .......... .......... .......... 41% 44,2M 9s - 17100K .......... .......... .......... .......... .......... 41% 92,3M 9s - 17150K .......... .......... .......... .......... .......... 41% 87,8M 9s - 17200K .......... .......... .......... .......... .......... 41% 14,1M 9s - 17250K .......... .......... .......... .......... .......... 41% 1,92M 9s - 17300K .......... .......... .......... .......... .......... 41% 1,41M 9s - 17350K .......... .......... .......... .......... .......... 41% 72,0M 9s - 17400K .......... .......... .......... .......... .......... 41% 61,9M 9s - 17450K .......... .......... .......... .......... .......... 42% 7,98M 9s - 17500K .......... .......... .......... .......... .......... 42% 18,0M 9s - 17550K .......... .......... .......... .......... .......... 42% 18,5M 9s - 17600K .......... .......... .......... .......... .......... 42% 60,6M 8s - 17650K .......... .......... .......... .......... .......... 42% 74,3M 8s - 17700K .......... .......... .......... .......... .......... 42% 71,4M 8s - 17750K .......... .......... .......... .......... .......... 42% 9,08M 8s - 17800K .......... .......... .......... .......... .......... 42% 67,1M 8s - 17850K .......... .......... .......... .......... .......... 42% 88,4M 8s - 17900K .......... .......... .......... .......... .......... 43% 63,0M 8s - 17950K .......... .......... .......... .......... .......... 43% 90,2M 8s - 18000K .......... .......... .......... .......... .......... 43% 9,69M 8s - 18050K .......... .......... .......... .......... .......... 43% 90,6M 8s - 18100K .......... .......... .......... .......... .......... 43% 88,4M 8s - 18150K .......... .......... .......... .......... .......... 43% 83,2M 8s - 18200K .......... .......... .......... .......... .......... 43% 20,2M 8s - 18250K .......... .......... .......... .......... .......... 43% 55,5M 8s - 18300K .......... .......... .......... .......... .......... 44% 24,3M 8s - 18350K .......... .......... .......... .......... .......... 44% 100M 8s - 18400K .......... .......... .......... .......... .......... 44% 31,8M 8s - 18450K .......... .......... .......... .......... .......... 44% 90,8M 8s - 18500K .......... .......... .......... .......... .......... 44% 16,1M 8s - 18550K .......... .......... .......... .......... .......... 44% 4,01M 8s - 18600K .......... .......... .......... .......... .......... 44% 60,9M 8s - 18650K .......... .......... .......... .......... .......... 44% 3,78M 8s - 18700K .......... .......... .......... .......... .......... 45% 1,39M 8s - 18750K .......... .......... .......... .......... .......... 45% 8,10M 8s - 18800K .......... .......... .......... .......... .......... 45% 60,9M 8s - 18850K .......... .......... .......... .......... .......... 45% 69,6M 8s - 18900K .......... .......... .......... .......... .......... 45% 15,8M 8s - 18950K .......... .......... .......... .......... .......... 45% 22,2M 8s - 19000K .......... .......... .......... .......... .......... 45% 63,8M 8s - 19050K .......... .......... .......... .......... .......... 45% 73,8M 7s - 19100K .......... .......... .......... .......... .......... 45% 75,6M 7s - 19150K .......... .......... .......... .......... .......... 46% 10,4M 7s - 19200K .......... .......... .......... .......... .......... 46% 48,1M 7s - 19250K .......... .......... .......... .......... .......... 46% 34,6M 7s - 19300K .......... .......... .......... .......... .......... 46% 108M 7s - 19350K .......... .......... .......... .......... .......... 46% 121M 7s - 19400K .......... .......... .......... .......... .......... 46% 10,9M 7s - 19450K .......... .......... .......... .......... .......... 46% 42,3M 7s - 19500K .......... .......... .......... .......... .......... 46% 63,6M 7s - 19550K .......... .......... .......... .......... .......... 47% 73,5M 7s - 19600K .......... .......... .......... .......... .......... 47% 25,8M 7s - 19650K .......... .......... .......... .......... .......... 47% 56,0M 7s - 19700K .......... .......... .......... .......... .......... 47% 49,8M 7s - 19750K .......... .......... .......... .......... .......... 47% 52,2M 7s - 19800K .......... .......... .......... .......... .......... 47% 61,9M 7s - 19850K .......... .......... .......... .......... .......... 47% 34,3M 7s - 19900K .......... .......... .......... .......... .......... 47% 50,3M 7s - 19950K .......... .......... .......... .......... .......... 48% 25,2M 7s - 20000K .......... .......... .......... .......... .......... 48% 7,45M 7s - 20050K .......... .......... .......... .......... .......... 48% 8,22M 7s - 20100K .......... .......... .......... .......... .......... 48% 3,67M 7s - 20150K .......... .......... .......... .......... .......... 48% 3,41M 7s - 20200K .......... .......... .......... .......... .......... 48% 1,78M 7s - 20250K .......... .......... .......... .......... .......... 48% 66,9M 7s - 20300K .......... .......... .......... .......... .......... 48% 74,2M 7s - 20350K .......... .......... .......... .......... .......... 48% 12,8M 7s - 20400K .......... .......... .......... .......... .......... 49% 29,9M 7s - 20450K .......... .......... .......... .......... .......... 49% 50,4M 7s - 20500K .......... .......... .......... .......... .......... 49% 63,1M 7s - 20550K .......... .......... .......... .......... .......... 49% 63,9M 7s - 20600K .......... .......... .......... .......... .......... 49% 15,6M 7s - 20650K .......... .......... .......... .......... .......... 49% 21,4M 7s - 20700K .......... .......... .......... .......... .......... 49% 54,6M 6s - 20750K .......... .......... .......... .......... .......... 49% 78,0M 6s - 20800K .......... .......... .......... .......... .......... 50% 93,0M 6s - 20850K .......... .......... .......... .......... .......... 50% 115M 6s - 20900K .......... .......... .......... .......... .......... 50% 13,9M 6s - 20950K .......... .......... .......... .......... .......... 50% 91,8M 6s - 21000K .......... .......... .......... .......... .......... 50% 33,4M 6s - 21050K .......... .......... .......... .......... .......... 50% 116M 6s - 21100K .......... .......... .......... .......... .......... 50% 28,1M 6s - 21150K .......... .......... .......... .......... .......... 50% 113M 6s - 21200K .......... .......... .......... .......... .......... 51% 39,4M 6s - 21250K .......... .......... .......... .......... .......... 51% 108M 6s - 21300K .......... .......... .......... .......... .......... 51% 30,8M 6s - 21350K .......... .......... .......... .......... .......... 51% 64,5M 6s - 21400K .......... .......... .......... .......... .......... 51% 75,7M 6s - 21450K .......... .......... .......... .......... .......... 51% 81,5M 6s - 21500K .......... .......... .......... .......... .......... 51% 16,2M 6s - 21550K .......... .......... .......... .......... .......... 51% 107M 6s - 21600K .......... .......... .......... .......... .......... 51% 4,12M 6s - 21650K .......... .......... .......... .......... .......... 52% 80,1M 6s - 21700K .......... .......... .......... .......... .......... 52% 3,73M 6s - 21750K .......... .......... .......... .......... .......... 52% 5,47M 6s - 21800K .......... .......... .......... .......... .......... 52% 1,50M 6s - 21850K .......... .......... .......... .......... .......... 52% 48,4M 6s - 21900K .......... .......... .......... .......... .......... 52% 65,3M 6s - 21950K .......... .......... .......... .......... .......... 52% 12,9M 6s - 22000K .......... .......... .......... .......... .......... 52% 34,5M 6s - 22050K .......... .......... .......... .......... .......... 53% 79,9M 6s - 22100K .......... .......... .......... .......... .......... 53% 75,7M 6s - 22150K .......... .......... .......... .......... .......... 53% 92,5M 6s - 22200K .......... .......... .......... .......... .......... 53% 14,2M 6s - 22250K .......... .......... .......... .......... .......... 53% 78,3M 6s - 22300K .......... .......... .......... .......... .......... 53% 23,3M 6s - 22350K .......... .......... .......... .......... .......... 53% 51,2M 6s - 22400K .......... .......... .......... .......... .......... 53% 35,1M 6s - 22450K .......... .......... .......... .......... .......... 54% 59,3M 6s - 22500K .......... .......... .......... .......... .......... 54% 84,3M 6s - 22550K .......... .......... .......... .......... .......... 54% 22,4M 6s - 22600K .......... .......... .......... .......... .......... 54% 66,5M 5s - 22650K .......... .......... .......... .......... .......... 54% 37,8M 5s - 22700K .......... .......... .......... .......... .......... 54% 81,6M 5s - 22750K .......... .......... .......... .......... .......... 54% 68,9M 5s - 22800K .......... .......... .......... .......... .......... 54% 29,8M 5s - 22850K .......... .......... .......... .......... .......... 54% 49,7M 5s - 22900K .......... .......... .......... .......... .......... 55% 68,8M 5s - 22950K .......... .......... .......... .......... .......... 55% 44,2M 5s - 23000K .......... .......... .......... .......... .......... 55% 56,1M 5s - 23050K .......... .......... .......... .......... .......... 55% 88,3M 5s - 23100K .......... .......... .......... .......... .......... 55% 87,2M 5s - 23150K .......... .......... .......... .......... .......... 55% 75,9M 5s - 23200K .......... .......... .......... .......... .......... 55% 20,9M 5s - 23250K .......... .......... .......... .......... .......... 55% 65,3M 5s - 23300K .......... .......... .......... .......... .......... 56% 99,4M 5s - 23350K .......... .......... .......... .......... .......... 56% 4,19M 5s - 23400K .......... .......... .......... .......... .......... 56% 6,24M 5s - 23450K .......... .......... .......... .......... .......... 56% 2,81M 5s - 23500K .......... .......... .......... .......... .......... 56% 6,61M 5s - 23550K .......... .......... .......... .......... .......... 56% 2,22M 5s - 23600K .......... .......... .......... .......... .......... 56% 31,8M 5s - 23650K .......... .......... .......... .......... .......... 56% 13,2M 5s - 23700K .......... .......... .......... .......... .......... 57% 27,7M 5s - 23750K .......... .......... .......... .......... .......... 57% 38,7M 5s - 23800K .......... .......... .......... .......... .......... 57% 56,6M 5s - 23850K .......... .......... .......... .......... .......... 57% 71,8M 5s - 23900K .......... .......... .......... .......... .......... 57% 20,8M 5s - 23950K .......... .......... .......... .......... .......... 57% 42,8M 5s - 24000K .......... .......... .......... .......... .......... 57% 60,5M 5s - 24050K .......... .......... .......... .......... .......... 57% 58,8M 5s - 24100K .......... .......... .......... .......... .......... 57% 31,7M 5s - 24150K .......... .......... .......... .......... .......... 58% 56,4M 5s - 24200K .......... .......... .......... .......... .......... 58% 94,3M 5s - 24250K .......... .......... .......... .......... .......... 58% 154M 5s - 24300K .......... .......... .......... .......... .......... 58% 166M 5s - 24350K .......... .......... .......... .......... .......... 58% 21,3M 5s - 24400K .......... .......... .......... .......... .......... 58% 28,9M 5s - 24450K .......... .......... .......... .......... .......... 58% 60,2M 5s - 24500K .......... .......... .......... .......... .......... 58% 99,0M 5s - 24550K .......... .......... .......... .......... .......... 59% 51,9M 5s - 24600K .......... .......... .......... .......... .......... 59% 109M 5s - 24650K .......... .......... .......... .......... .......... 59% 24,6M 5s - 24700K .......... .......... .......... .......... .......... 59% 78,5M 5s - 24750K .......... .......... .......... .......... .......... 59% 150M 5s - 24800K .......... .......... .......... .......... .......... 59% 58,7M 5s - 24850K .......... .......... .......... .......... .......... 59% 60,5M 4s - 24900K .......... .......... .......... .......... .......... 59% 95,2M 4s - 24950K .......... .......... .......... .......... .......... 60% 98,6M 4s - 25000K .......... .......... .......... .......... .......... 60% 88,9M 4s - 25050K .......... .......... .......... .......... .......... 60% 23,0M 4s - 25100K .......... .......... .......... .......... .......... 60% 61,5M 4s - 25150K .......... .......... .......... .......... .......... 60% 105M 4s - 25200K .......... .......... .......... .......... .......... 60% 6,64M 4s - 25250K .......... .......... .......... .......... .......... 60% 7,11M 4s - 25300K .......... .......... .......... .......... .......... 60% 4,75M 4s - 25350K .......... .......... .......... .......... .......... 60% 2,81M 4s - 25400K .......... .......... .......... .......... .......... 61% 50,6M 4s - 25450K .......... .......... .......... .......... .......... 61% 2,10M 4s - 25500K .......... .......... .......... .......... .......... 61% 26,6M 4s - 25550K .......... .......... .......... .......... .......... 61% 13,6M 4s - 25600K .......... .......... .......... .......... .......... 61% 16,6M 4s - 25650K .......... .......... .......... .......... .......... 61% 37,4M 4s - 25700K .......... .......... .......... .......... .......... 61% 69,9M 4s - 25750K .......... .......... .......... .......... .......... 61% 75,8M 4s - 25800K .......... .......... .......... .......... .......... 62% 32,8M 4s - 25850K .......... .......... .......... .......... .......... 62% 92,0M 4s - 25900K .......... .......... .......... .......... .......... 62% 163M 4s - 25950K .......... .......... .......... .......... .......... 62% 30,3M 4s - 26000K .......... .......... .......... .......... .......... 62% 35,2M 4s - 26050K .......... .......... .......... .......... .......... 62% 95,9M 4s - 26100K .......... .......... .......... .......... .......... 62% 55,0M 4s - 26150K .......... .......... .......... .......... .......... 62% 105M 4s - 26200K .......... .......... .......... .......... .......... 63% 142M 4s - 26250K .......... .......... .......... .......... .......... 63% 111M 4s - 26300K .......... .......... .......... .......... .......... 63% 17,8M 4s - 26350K .......... .......... .......... .......... .......... 63% 150M 4s - 26400K .......... .......... .......... .......... .......... 63% 41,1M 4s - 26450K .......... .......... .......... .......... .......... 63% 40,0M 4s - 26500K .......... .......... .......... .......... .......... 63% 90,6M 4s - 26550K .......... .......... .......... .......... .......... 63% 91,6M 4s - 26600K .......... .......... .......... .......... .......... 63% 69,6M 4s - 26650K .......... .......... .......... .......... .......... 64% 24,8M 4s - 26700K .......... .......... .......... .......... .......... 64% 94,8M 4s - 26750K .......... .......... .......... .......... .......... 64% 83,2M 4s - 26800K .......... .......... .......... .......... .......... 64% 42,4M 4s - 26850K .......... .......... .......... .......... .......... 64% 88,3M 4s - 26900K .......... .......... .......... .......... .......... 64% 88,8M 4s - 26950K .......... .......... .......... .......... .......... 64% 91,1M 4s - 27000K .......... .......... .......... .......... .......... 64% 35,7M 4s - 27050K .......... .......... .......... .......... .......... 65% 88,5M 4s - 27100K .......... .......... .......... .......... .......... 65% 83,5M 4s - 27150K .......... .......... .......... .......... .......... 65% 84,8M 4s - 27200K .......... .......... .......... .......... .......... 65% 6,73M 4s - 27250K .......... .......... .......... .......... .......... 65% 9,14M 4s - 27300K .......... .......... .......... .......... .......... 65% 28,7M 4s - 27350K .......... .......... .......... .......... .......... 65% 4,70M 4s - 27400K .......... .......... .......... .......... .......... 65% 2,82M 4s - 27450K .......... .......... .......... .......... .......... 66% 6,37M 4s - 27500K .......... .......... .......... .......... .......... 66% 3,01M 3s - 27550K .......... .......... .......... .......... .......... 66% 21,2M 3s - 27600K .......... .......... .......... .......... .......... 66% 13,7M 3s - 27650K .......... .......... .......... .......... .......... 66% 14,9M 3s - 27700K .......... .......... .......... .......... .......... 66% 55,1M 3s - 27750K .......... .......... .......... .......... .......... 66% 55,6M 3s - 27800K .......... .......... .......... .......... .......... 66% 67,1M 3s - 27850K .......... .......... .......... .......... .......... 66% 88,1M 3s - 27900K .......... .......... .......... .......... .......... 67% 61,5M 3s - 27950K .......... .......... .......... .......... .......... 67% 78,6M 3s - 28000K .......... .......... .......... .......... .......... 67% 28,8M 3s - 28050K .......... .......... .......... .......... .......... 67% 42,3M 3s - 28100K .......... .......... .......... .......... .......... 67% 46,7M 3s - 28150K .......... .......... .......... .......... .......... 67% 97,7M 3s - 28200K .......... .......... .......... .......... .......... 67% 72,4M 3s - 28250K .......... .......... .......... .......... .......... 67% 101M 3s - 28300K .......... .......... .......... .......... .......... 68% 104M 3s - 28350K .......... .......... .......... .......... .......... 68% 121M 3s - 28400K .......... .......... .......... .......... .......... 68% 21,7M 3s - 28450K .......... .......... .......... .......... .......... 68% 92,8M 3s - 28500K .......... .......... .......... .......... .......... 68% 99,8M 3s - 28550K .......... .......... .......... .......... .......... 68% 33,8M 3s - 28600K .......... .......... .......... .......... .......... 68% 114M 3s - 28650K .......... .......... .......... .......... .......... 68% 83,6M 3s - 28700K .......... .......... .......... .......... .......... 69% 142M 3s - 28750K .......... .......... .......... .......... .......... 69% 126M 3s - 28800K .......... .......... .......... .......... .......... 69% 9,03M 3s - 28850K .......... .......... .......... .......... .......... 69% 115M 3s - 28900K .......... .......... .......... .......... .......... 69% 101M 3s - 28950K .......... .......... .......... .......... .......... 69% 83,4M 3s - 29000K .......... .......... .......... .......... .......... 69% 88,0M 3s - 29050K .......... .......... .......... .......... .......... 69% 94,5M 3s - 29100K .......... .......... .......... .......... .......... 69% 122M 3s - 29150K .......... .......... .......... .......... .......... 70% 97,3M 3s - 29200K .......... .......... .......... .......... .......... 70% 91,8M 3s - 29250K .......... .......... .......... .......... .......... 70% 113M 3s - 29300K .......... .......... .......... .......... .......... 70% 35,7M 3s - 29350K .......... .......... .......... .......... .......... 70% 19,6M 3s - 29400K .......... .......... .......... .......... .......... 70% 110M 3s - 29450K .......... .......... .......... .......... .......... 70% 22,9M 3s - 29500K .......... .......... .......... .......... .......... 70% 6,27M 3s - 29550K .......... .......... .......... .......... .......... 71% 5,42M 3s - 29600K .......... .......... .......... .......... .......... 71% 5,40M 3s - 29650K .......... .......... .......... .......... .......... 71% 5,61M 3s - 29700K .......... .......... .......... .......... .......... 71% 3,47M 3s - 29750K .......... .......... .......... .......... .......... 71% 3,94M 3s - 29800K .......... .......... .......... .......... .......... 71% 17,8M 3s - 29850K .......... .......... .......... .......... .......... 71% 50,3M 3s - 29900K .......... .......... .......... .......... .......... 71% 15,4M 3s - 29950K .......... .......... .......... .......... .......... 72% 56,6M 3s - 30000K .......... .......... .......... .......... .......... 72% 39,4M 3s - 30050K .......... .......... .......... .......... .......... 72% 62,8M 3s - 30100K .......... .......... .......... .......... .......... 72% 49,8M 3s - 30150K .......... .......... .......... .......... .......... 72% 75,4M 3s - 30200K .......... .......... .......... .......... .......... 72% 63,8M 3s - 30250K .......... .......... .......... .......... .......... 72% 102M 3s - 30300K .......... .......... .......... .......... .......... 72% 79,7M 3s - 30350K .......... .......... .......... .......... .......... 72% 58,3M 3s - 30400K .......... .......... .......... .......... .......... 73% 36,5M 3s - 30450K .......... .......... .......... .......... .......... 73% 123M 3s - 30500K .......... .......... .......... .......... .......... 73% 21,5M 3s - 30550K .......... .......... .......... .......... .......... 73% 122M 3s - 30600K .......... .......... .......... .......... .......... 73% 121M 2s - 30650K .......... .......... .......... .......... .......... 73% 83,1M 2s - 30700K .......... .......... .......... .......... .......... 73% 122M 2s - 30750K .......... .......... .......... .......... .......... 73% 71,4M 2s - 30800K .......... .......... .......... .......... .......... 74% 30,6M 2s - 30850K .......... .......... .......... .......... .......... 74% 132M 2s - 30900K .......... .......... .......... .......... .......... 74% 89,6M 2s - 30950K .......... .......... .......... .......... .......... 74% 115M 2s - 31000K .......... .......... .......... .......... .......... 74% 117M 2s - 31050K .......... .......... .......... .......... .......... 74% 90,4M 2s - 31100K .......... .......... .......... .......... .......... 74% 9,46M 2s - 31150K .......... .......... .......... .......... .......... 74% 108M 2s - 31200K .......... .......... .......... .......... .......... 75% 51,7M 2s - 31250K .......... .......... .......... .......... .......... 75% 74,9M 2s - 31300K .......... .......... .......... .......... .......... 75% 104M 2s - 31350K .......... .......... .......... .......... .......... 75% 111M 2s - 31400K .......... .......... .......... .......... .......... 75% 102M 2s - 31450K .......... .......... .......... .......... .......... 75% 77,7M 2s - 31500K .......... .......... .......... .......... .......... 75% 104M 2s - 31550K .......... .......... .......... .......... .......... 75% 92,5M 2s - 31600K .......... .......... .......... .......... .......... 75% 94,8M 2s - 31650K .......... .......... .......... .......... .......... 76% 112M 2s - 31700K .......... .......... .......... .......... .......... 76% 23,4M 2s - 31750K .......... .......... .......... .......... .......... 76% 95,5M 2s - 31800K .......... .......... .......... .......... .......... 76% 21,2M 2s - 31850K .......... .......... .......... .......... .......... 76% 7,00M 2s - 31900K .......... .......... .......... .......... .......... 76% 5,33M 2s - 31950K .......... .......... .......... .......... .......... 76% 98,7M 2s - 32000K .......... .......... .......... .......... .......... 76% 5,87M 2s - 32050K .......... .......... .......... .......... .......... 77% 3,46M 2s - 32100K .......... .......... .......... .......... .......... 77% 3,11M 2s - 32150K .......... .......... .......... .......... .......... 77% 8,76M 2s - 32200K .......... .......... .......... .......... .......... 77% 47,3M 2s - 32250K .......... .......... .......... .......... .......... 77% 17,2M 2s - 32300K .......... .......... .......... .......... .......... 77% 13,4M 2s - 32350K .......... .......... .......... .......... .......... 77% 80,2M 2s - 32400K .......... .......... .......... .......... .......... 77% 75,5M 2s - 32450K .......... .......... .......... .......... .......... 78% 96,5M 2s - 32500K .......... .......... .......... .......... .......... 78% 63,6M 2s - 32550K .......... .......... .......... .......... .......... 78% 100M 2s - 32600K .......... .......... .......... .......... .......... 78% 30,2M 2s - 32650K .......... .......... .......... .......... .......... 78% 79,5M 2s - 32700K .......... .......... .......... .......... .......... 78% 91,0M 2s - 32750K .......... .......... .......... .......... .......... 78% 44,3M 2s - 32800K .......... .......... .......... .......... .......... 78% 49,2M 2s - 32850K .......... .......... .......... .......... .......... 78% 86,4M 2s - 32900K .......... .......... .......... .......... .......... 79% 20,8M 2s - 32950K .......... .......... .......... .......... .......... 79% 50,1M 2s - 33000K .......... .......... .......... .......... .......... 79% 86,0M 2s - 33050K .......... .......... .......... .......... .......... 79% 118M 2s - 33100K .......... .......... .......... .......... .......... 79% 121M 2s - 33150K .......... .......... .......... .......... .......... 79% 128M 2s - 33200K .......... .......... .......... .......... .......... 79% 103M 2s - 33250K .......... .......... .......... .......... .......... 79% 121M 2s - 33300K .......... .......... .......... .......... .......... 80% 39,0M 2s - 33350K .......... .......... .......... .......... .......... 80% 114M 2s - 33400K .......... .......... .......... .......... .......... 80% 95,3M 2s - 33450K .......... .......... .......... .......... .......... 80% 86,6M 2s - 33500K .......... .......... .......... .......... .......... 80% 116M 2s - 33550K .......... .......... .......... .......... .......... 80% 11,0M 2s - 33600K .......... .......... .......... .......... .......... 80% 76,4M 2s - 33650K .......... .......... .......... .......... .......... 80% 124M 2s - 33700K .......... .......... .......... .......... .......... 81% 43,7M 2s - 33750K .......... .......... .......... .......... .......... 81% 103M 2s - 33800K .......... .......... .......... .......... .......... 81% 86,7M 2s - 33850K .......... .......... .......... .......... .......... 81% 90,0M 2s - 33900K .......... .......... .......... .......... .......... 81% 47,6M 2s - 33950K .......... .......... .......... .......... .......... 81% 98,9M 2s - 34000K .......... .......... .......... .......... .......... 81% 79,3M 2s - 34050K .......... .......... .......... .......... .......... 81% 93,2M 2s - 34100K .......... .......... .......... .......... .......... 82% 96,5M 2s - 34150K .......... .......... .......... .......... .......... 82% 95,0M 2s - 34200K .......... .......... .......... .......... .......... 82% 52,0M 2s - 34250K .......... .......... .......... .......... .......... 82% 104M 2s - 34300K .......... .......... .......... .......... .......... 82% 93,2M 2s - 34350K .......... .......... .......... .......... .......... 82% 25,0M 1s - 34400K .......... .......... .......... .......... .......... 82% 7,35M 1s - 34450K .......... .......... .......... .......... .......... 82% 5,23M 1s - 34500K .......... .......... .......... .......... .......... 82% 6,79M 1s - 34550K .......... .......... .......... .......... .......... 83% 99,1M 1s - 34600K .......... .......... .......... .......... .......... 83% 3,23M 1s - 34650K .......... .......... .......... .......... .......... 83% 3,34M 1s - 34700K .......... .......... .......... .......... .......... 83% 6,32M 1s - 34750K .......... .......... .......... .......... .......... 83% 18,3M 1s - 34800K .......... .......... .......... .......... .......... 83% 12,6M 1s - 34850K .......... .......... .......... .......... .......... 83% 40,4M 1s - 34900K .......... .......... .......... .......... .......... 83% 68,0M 1s - 34950K .......... .......... .......... .......... .......... 84% 58,3M 1s - 35000K .......... .......... .......... .......... .......... 84% 45,2M 1s - 35050K .......... .......... .......... .......... .......... 84% 63,1M 1s - 35100K .......... .......... .......... .......... .......... 84% 54,5M 1s - 35150K .......... .......... .......... .......... .......... 84% 64,2M 1s - 35200K .......... .......... .......... .......... .......... 84% 74,6M 1s - 35250K .......... .......... .......... .......... .......... 84% 120M 1s - 35300K .......... .......... .......... .......... .......... 84% 95,9M 1s - 35350K .......... .......... .......... .......... .......... 85% 102M 1s - 35400K .......... .......... .......... .......... .......... 85% 117M 1s - 35450K .......... .......... .......... .......... .......... 85% 124M 1s - 35500K .......... .......... .......... .......... .......... 85% 139M 1s - 35550K .......... .......... .......... .......... .......... 85% 18,0M 1s - 35600K .......... .......... .......... .......... .......... 85% 98,5M 1s - 35650K .......... .......... .......... .......... .......... 85% 91,6M 1s - 35700K .......... .......... .......... .......... .......... 85% 120M 1s - 35750K .......... .......... .......... .......... .......... 85% 120M 1s - 35800K .......... .......... .......... .......... .......... 86% 107M 1s - 35850K .......... .......... .......... .......... .......... 86% 118M 1s - 35900K .......... .......... .......... .......... .......... 86% 83,0M 1s - 35950K .......... .......... .......... .......... .......... 86% 94,1M 1s - 36000K .......... .......... .......... .......... .......... 86% 69,9M 1s - 36050K .......... .......... .......... .......... .......... 86% 81,4M 1s - 36100K .......... .......... .......... .......... .......... 86% 117M 1s - 36150K .......... .......... .......... .......... .......... 86% 89,9M 1s - 36200K .......... .......... .......... .......... .......... 87% 83,4M 1s - 36250K .......... .......... .......... .......... .......... 87% 14,0M 1s - 36300K .......... .......... .......... .......... .......... 87% 84,0M 1s - 36350K .......... .......... .......... .......... .......... 87% 27,5M 1s - 36400K .......... .......... .......... .......... .......... 87% 94,0M 1s - 36450K .......... .......... .......... .......... .......... 87% 91,9M 1s - 36500K .......... .......... .......... .......... .......... 87% 47,3M 1s - 36550K .......... .......... .......... .......... .......... 87% 98,3M 1s - 36600K .......... .......... .......... .......... .......... 88% 88,5M 1s - 36650K .......... .......... .......... .......... .......... 88% 102M 1s - 36700K .......... .......... .......... .......... .......... 88% 97,9M 1s - 36750K .......... .......... .......... .......... .......... 88% 127M 1s - 36800K .......... .......... .......... .......... .......... 88% 57,2M 1s - 36850K .......... .......... .......... .......... .......... 88% 95,7M 1s - 36900K .......... .......... .......... .......... .......... 88% 88,0M 1s - 36950K .......... .......... .......... .......... .......... 88% 84,0M 1s - 37000K .......... .......... .......... .......... .......... 88% 38,4M 1s - 37050K .......... .......... .......... .......... .......... 89% 96,2M 1s - 37100K .......... .......... .......... .......... .......... 89% 10,9M 1s - 37150K .......... .......... .......... .......... .......... 89% 19,7M 1s - 37200K .......... .......... .......... .......... .......... 89% 5,09M 1s - 37250K .......... .......... .......... .......... .......... 89% 7,41M 1s - 37300K .......... .......... .......... .......... .......... 89% 3,85M 1s - 37350K .......... .......... .......... .......... .......... 89% 4,88M 1s - 37400K .......... .......... .......... .......... .......... 89% 133M 1s - 37450K .......... .......... .......... .......... .......... 90% 3,40M 1s - 37500K .......... .......... .......... .......... .......... 90% 17,3M 1s - 37550K .......... .......... .......... .......... .......... 90% 11,2M 1s - 37600K .......... .......... .......... .......... .......... 90% 123M 1s - 37650K .......... .......... .......... .......... .......... 90% 92,4M 1s - 37700K .......... .......... .......... .......... .......... 90% 68,4M 1s - 37750K .......... .......... .......... .......... .......... 90% 62,4M 1s - 37800K .......... .......... .......... .......... .......... 90% 59,1M 1s - 37850K .......... .......... .......... .......... .......... 91% 65,5M 1s - 37900K .......... .......... .......... .......... .......... 91% 55,8M 1s - 37950K .......... .......... .......... .......... .......... 91% 66,4M 1s - 38000K .......... .......... .......... .......... .......... 91% 56,0M 1s - 38050K .......... .......... .......... .......... .......... 91% 61,3M 1s - 38100K .......... .......... .......... .......... .......... 91% 60,9M 1s - 38150K .......... .......... .......... .......... .......... 91% 65,8M 1s - 38200K .......... .......... .......... .......... .......... 91% 57,1M 1s - 38250K .......... .......... .......... .......... .......... 91% 67,8M 1s - 38300K .......... .......... .......... .......... .......... 92% 74,7M 1s - 38350K .......... .......... .......... .......... .......... 92% 26,4M 1s - 38400K .......... .......... .......... .......... .......... 92% 70,8M 1s - 38450K .......... .......... .......... .......... .......... 92% 177M 1s - 38500K .......... .......... .......... .......... .......... 92% 103M 1s - 38550K .......... .......... .......... .......... .......... 92% 96,5M 1s - 38600K .......... .......... .......... .......... .......... 92% 92,9M 1s - 38650K .......... .......... .......... .......... .......... 92% 179M 1s - 38700K .......... .......... .......... .......... .......... 93% 64,0M 1s - 38750K .......... .......... .......... .......... .......... 93% 95,7M 1s - 38800K .......... .......... .......... .......... .......... 93% 69,1M 1s - 38850K .......... .......... .......... .......... .......... 93% 92,3M 1s - 38900K .......... .......... .......... .......... .......... 93% 97,2M 1s - 38950K .......... .......... .......... .......... .......... 93% 80,6M 0s - 39000K .......... .......... .......... .......... .......... 93% 89,0M 0s - 39050K .......... .......... .......... .......... .......... 93% 118M 0s - 39100K .......... .......... .......... .......... .......... 94% 21,5M 0s - 39150K .......... .......... .......... .......... .......... 94% 98,3M 0s - 39200K .......... .......... .......... .......... .......... 94% 25,7M 0s - 39250K .......... .......... .......... .......... .......... 94% 111M 0s - 39300K .......... .......... .......... .......... .......... 94% 64,2M 0s - 39350K .......... .......... .......... .......... .......... 94% 75,8M 0s - 39400K .......... .......... .......... .......... .......... 94% 64,2M 0s - 39450K .......... .......... .......... .......... .......... 94% 72,3M 0s - 39500K .......... .......... .......... .......... .......... 94% 72,0M 0s - 39550K .......... .......... .......... .......... .......... 95% 69,6M 0s - 39600K .......... .......... .......... .......... .......... 95% 75,7M 0s - 39650K .......... .......... .......... .......... .......... 95% 72,5M 0s - 39700K .......... .......... .......... .......... .......... 95% 74,1M 0s - 39750K .......... .......... .......... .......... .......... 95% 69,4M 0s - 39800K .......... .......... .......... .......... .......... 95% 61,5M 0s - 39850K .......... .......... .......... .......... .......... 95% 70,3M 0s - 39900K .......... .......... .......... .......... .......... 95% 76,4M 0s - 39950K .......... .......... .......... .......... .......... 96% 93,7M 0s - 40000K .......... .......... .......... .......... .......... 96% 73,8M 0s - 40050K .......... .......... .......... .......... .......... 96% 11,3M 0s - 40100K .......... .......... .......... .......... .......... 96% 5,42M 0s - 40150K .......... .......... .......... .......... .......... 96% 6,38M 0s - 40200K .......... .......... .......... .......... .......... 96% 37,9M 0s - 40250K .......... .......... .......... .......... .......... 96% 4,09M 0s - 40300K .......... .......... .......... .......... .......... 96% 4,75M 0s - 40350K .......... .......... .......... .......... .......... 97% 3,60M 0s - 40400K .......... .......... .......... .......... .......... 97% 16,7M 0s - 40450K .......... .......... .......... .......... .......... 97% 78,3M 0s - 40500K .......... .......... .......... .......... .......... 97% 10,4M 0s - 40550K .......... .......... .......... .......... .......... 97% 50,6M 0s - 40600K .......... .......... .......... .......... .......... 97% 96,0M 0s - 40650K .......... .......... .......... .......... .......... 97% 101M 0s - 40700K .......... .......... .......... .......... .......... 97% 114M 0s - 40750K .......... .......... .......... .......... .......... 97% 125M 0s - 40800K .......... .......... .......... .......... .......... 98% 81,4M 0s - 40850K .......... .......... .......... .......... .......... 98% 107M 0s - 40900K .......... .......... .......... .......... .......... 98% 107M 0s - 40950K .......... .......... .......... .......... .......... 98% 75,1M 0s - 41000K .......... .......... .......... .......... .......... 98% 108M 0s - 41050K .......... .......... .......... .......... .......... 98% 62,9M 0s - 41100K .......... .......... .......... .......... .......... 98% 51,6M 0s - 41150K .......... .......... .......... .......... .......... 98% 73,4M 0s - 41200K .......... .......... .......... .......... .......... 99% 47,4M 0s - 41250K .......... .......... .......... .......... .......... 99% 87,9M 0s - 41300K .......... .......... .......... .......... .......... 99% 18,0M 0s - 41350K .......... .......... .......... .......... .......... 99% 78,5M 0s - 41400K .......... .......... .......... .......... .......... 99% 78,3M 0s - 41450K .......... .......... .......... .......... .......... 99% 107M 0s - 41500K .......... .......... .......... .......... .......... 99% 73,6M 0s - 41550K .......... .......... .......... .......... .......... 99% 50,9M 0s - 41600K .......... .......... .......... .......... ...... 100% 122M=7,4s - -2014-06-18 13:38:29 (5,52 MB/s) - ‘/home/jwiklund/Documents/.git/annex/tmp/SHA256E-s42645638--4ae41fb29bd26339ea10f53ea2b7cf3132e53d5e8fbfde7b43b912aa52b3d319.tar.gz’ saved [42645638/42645638] - -[2014-06-18 13:38:29 CEST] main: Downloaded git-annex.. upgrade) -(checksum...) -[2014-06-18 13:38:29 CEST] Pusher: Syncing with born -(Recording state in git...) -To ssh://jwiklund@born/store/backup/Documents.annex.1/ - 38006f5..fdae080 git-annex -> synced/git-annex -git-annex version: 5.20140610-g5ec8bcf -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -[2014-06-18 13:38:31 CEST] main: Upgrading git-annex -[2014-06-18 13:38:31 CEST] UpgradeWatcher: A new version of git-annex has been installed. - -Already up-to-date. - -Already up-to-date. - -Already up-to-date. - -Already up-to-date. -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data -channel 4: bad ext data - -# End of transcript or log. -"""]] - -> [[fixed|done]]; the merge race has been fixed. The upgrade loop has also -> been dealt with. --[[Joey]] diff --git a/doc/bugs/files_lost_during_upgrade/comment_1_3f779c4d0c9fb27532b2981bd3ad4eee._comment b/doc/bugs/files_lost_during_upgrade/comment_1_3f779c4d0c9fb27532b2981bd3ad4eee._comment deleted file mode 100644 index b510d92c1..000000000 --- a/doc/bugs/files_lost_during_upgrade/comment_1_3f779c4d0c9fb27532b2981bd3ad4eee._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.203" - subject="comment 1" - date="2014-06-18T18:12:47Z" - content=""" -So [[bugs/git-annex_auto_upgrade_is_redundant]] strikes again. I have fixed up the versions to avoid this upgrade loop again. I would rather discuss any problems with where the automatic upgrade code puts git-annex in a separate bug report than this one.. (If you're running git-annex as a user that is not allowed to write to the directory where you installed it in the first place then yes, it cannot write there and will instead unpack itself into the home directory.) - -There are many strange things in the log, but this is probably the strangest: - -> fatal: Could not switch to '/home/jwiklund/Documents/.git/annex/merge/': No such file or directory - -This is the gitAnnexMergeDir used for direct mode merges. Since git-annex always creates that directory before starting a merge, I don't know how it could fail to exist. - -Other strange things: - -* The assistant fixes stale index.lock files on startup. But the log shows the assistant starting up and shortly thereafter there's a stale index.lock file. All I can think is that perhaps two git processes are trying to commit at the same time. - -* \"fatal: pathspec 'music.txt' did not match any files\", apparently output by git-add. - -* \"error: duplicate parent 294b61a3dce1e87a62e4d675deac2a9130b819e6 ignored\", which would happen if git-commit-tree were passed duplicate parent refs. AFAICS, the only place in git-annex that might do that is when it commits the git-annex branch. (While this says it's an error, it really is ignored, and git-commit-tree continues and makes a valid commit.) -"""]] diff --git a/doc/bugs/files_lost_during_upgrade/comment_2_80ba8c217e83c9d44a9dc52f4028719d._comment b/doc/bugs/files_lost_during_upgrade/comment_2_80ba8c217e83c9d44a9dc52f4028719d._comment deleted file mode 100644 index b09df4eeb..000000000 --- a/doc/bugs/files_lost_during_upgrade/comment_2_80ba8c217e83c9d44a9dc52f4028719d._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 2" - date="2014-07-10T19:10:15Z" - content=""" -Looking back at this bug, it's clearly the same race that I later -debugged and fixed in [[bad_merge_commit_deleting_all_files]]. There are instructions in that bug for recovering it. - -In particular, the \"fatal: Could not switch to '/home/jwiklund/Documents/.git/annex/merge/': No such file or directory\" is because of the race; the merge directory is being created and deleted by two contending threads. -"""]] diff --git a/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn b/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn deleted file mode 100644 index 0d513d459..000000000 --- a/doc/bugs/flooding_me_with_ssh_password_prompts.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -### Please describe the problem. - -When I login to my session, git-annex starts a few daemons, which is fine, but then it prompts me for tons of passwords, which is really annoying. - -It is strange because one of the things I do when I start my session is to input my keys in the SSH agent. But then git-annex still prompts me: - -~~~~ -21503 ? Sl 3:04 git-annex assistant --startdelay=5s -21517 ? S 0:03 \_ git --git-dir=/srv/musique/anarcat/books/.git --work-tree=/srv/musique/anarcat/books cat-file --batch -21612 ? SNl 0:00 \_ git-annex remotedaemon -21706 ? S 0:00 \_ git --git-dir=/srv/musique/anarcat/books/.git --work-tree=/srv/musique/anarcat/books check-ignore -z --stdin --verbose --non-matching -21898 ? SN 0:00 \_ git --git-dir=/srv/musique/anarcat/books/.git --work-tree=/srv/musique/anarcat/books check-attr -z --stdin annex.backend annex.numcopies -- - 6712 ? SNl 0:00 \_ git-annex transferkeys - 6719 ? SN 0:00 \_ git --git-dir=/srv/musique/anarcat/books/.git --work-tree=/srv/musique/anarcat/books cat-file --batch - 6720 ? SN 0:00 \_ rsync --progress --inplace --perms -e 'ssh' '-S' '.git/annex/ssh/anarc.at' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-T' 'anarc.at' 'git-annex-shell ''sendkey'' ''/srv/books'' ''SHA256E-s17781587--f204e6ef1f14b624e222d6ad73ed41edf65c29c93afad9a1e4e1954ad68d1753.pdf'' --uuid a75cbbf7-e055-423e-b375-443e0552c9e2 ''--'' ''remoteuuid=aa500f29-42d9-4777-ae02-4a2c3d47db44'' ''direct='' ''associatedfile=Garde cotiere canadienne/Navigation dans les glaces en eaux Canadiennes (1112)/Navigation dans les glaces en eaux Canadie - Garde cotiere canadienne.pdf'' ''--''' -- dummy: /srv/musique/anarcat/books/.git/annex/tmp/SHA256E-s17781587--f204e6ef1f14b624e222d6ad73ed41edf65c29c93afad9a1e4e1954ad68d1753.pdf - 6721 ? SN 0:00 \_ ssh -S .git/annex/ssh/anarc.at -o ControlMaster=auto -o ControlPersist=yes -T anarc.at git-annex-shell 'sendkey' '/srv/books' 'SHA256E-s17781587--f204e6ef1f14b624e222d6ad73ed41edf65c29c93afad9a1e4e1954ad68d1753.pdf' --uuid a75cbbf7-e055-423e-b375-443e0552c9e2 '--' 'remoteuuid=aa500f29-42d9-4777-ae02-4a2c3d47db44' 'direct=' 'associatedfile=Garde cotiere canadienne/Navigation dans les glaces en eaux Canadiennes (1112)/Navigation dans les glaces en eaux Canadie - Garde cotiere canadienne.pdf' '--' dummy rsync --server --sender -vpe.Lsf --inplace . - 6722 ? SN 0:00 \_ /usr/bin/ssh-askpass anarcat@anarc.at's password: -~~~~ - -Yet I can login to `shell.anarc.at` without a passphrase without problems. - -Interestingly enough, my main session and git-annex do not seem to share the same `SSH_AGENT` environment variable. It's unclear to me why. git-annex's SSH_AGENT environment variable seems to refer to a process that disappeared, actually. So it could be there's something wrong with my session. - -Still, when a situation like this occurs, it seems to me that it should generate in this noisy concert of ssh prompts that basically blocks all work until i hit "escape" often enough. In fact, that it is rather problematic to have random password prompts show up like this without an explanation: git-annex should tell me it's the source of this password prompt or not prompt at all, because there's no way i'll start entering random passphrases into random pinentry dialogs that show up... - -Doesn't git-annex deploy its own ssh keys once it has established a connexion with an SSH remote? - -> After more investigation, it turns out this peculiar git-annex daemon was some left-overs from a previous session i had logged out of. It is unclear why git-annex was still running, but there were also pulseaudio and redshift programs lying around so I suspect it wasn't git-annex specific. -> -> However, this problem remains on login. When I start a new session, there's a race condition between git-annex asking passwords and ssh-add asking me to unlock my private key. It's a nice festival of password prompts as I struggle to type in my ssh key faster than git-annex asks me for the remote host's password. -> -> In general, I think git-annex should set `PasswordAuthentication=no` (or allow me to configure it as such), especially if it knows it was able to login without a password at some point. It should especially do that if there's no UI attached informing the user it will be prompting for a password. `NumberOfPasswordPrompts=1` would also be a welcome improvement, but I really don't think I should be seeing those password prompts, especially since I *can* login to the server with my existing SSH key. -> -> Also note that I use Monkeysphere to input my private key into the SSH agent so it could explain why this doesn't usually happen to other people: Monkeysphere doesn't automatically get started from `ssh` if the key is missing, and instead `ssh` will revert to a regular password-based authentication which competes with the Monkeysphere password prompt. - -### What steps will reproduce the problem? - -It's unclear - i guess you need to setup git-annex to autostart and sync with remote ssh annexes. You may also need to have to use XFCE with Awesome to reproduce the problem. I can provide more details on my session setup on request. --[[anarcat]] - -### What version of git-annex are you using? On what operating system? - -5.20140927~bpo70+3 on debian wheezy. - -> The git-annex daemon being a "leftover" from a previous session seems -> like the root cause. We have a new bug for this, -> [[bugs/kill_git-annex_assistant_on_logout]], so I am going to close this -> one as a dup. [[done]] --[[Joey]] diff --git a/doc/bugs/flooding_me_with_ssh_password_prompts/comment_1_dba769cf0fca540f50f5e4b732a7e353._comment b/doc/bugs/flooding_me_with_ssh_password_prompts/comment_1_dba769cf0fca540f50f5e4b732a7e353._comment deleted file mode 100644 index 1cfa8763c..000000000 --- a/doc/bugs/flooding_me_with_ssh_password_prompts/comment_1_dba769cf0fca540f50f5e4b732a7e353._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo" - nickname="Justin" - subject="comment 1" - date="2014-10-30T18:07:28Z" - content=""" -I've ran into this as well using wheezy+awesome. It definitely looks like a race condition, I ended up doing a - - killall git-annex - ssh-add - git-annex webapp - -to get things going again. -"""]] diff --git a/doc/bugs/flooding_me_with_ssh_password_prompts/comment_2_4a283ef50351e8c604a1f87aaaee1bb0._comment b/doc/bugs/flooding_me_with_ssh_password_prompts/comment_2_4a283ef50351e8c604a1f87aaaee1bb0._comment deleted file mode 100644 index 2f9fe10ae..000000000 --- a/doc/bugs/flooding_me_with_ssh_password_prompts/comment_2_4a283ef50351e8c604a1f87aaaee1bb0._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="still an issue" - date="2015-01-26T17:27:25Z" - content=""" -this is still a major annoyance here. so much so that i disabled the assistant completely here. i ended up blacklisting myself from my own server... repeatedly. -"""]] diff --git a/doc/bugs/follows_symlinks_to_outside_annex.mdwn b/doc/bugs/follows_symlinks_to_outside_annex.mdwn deleted file mode 100644 index a58d755a7..000000000 --- a/doc/bugs/follows_symlinks_to_outside_annex.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -I've had a bug report that the assistant follows directory symlinks to elsewhere. I thought it didn't. This needs to be avoided. - -[[fixed|done]] diff --git a/doc/bugs/follows_symlinks_to_outside_annex/comment_1_f7a01bb627a6780d6940886401cde454._comment b/doc/bugs/follows_symlinks_to_outside_annex/comment_1_f7a01bb627a6780d6940886401cde454._comment deleted file mode 100644 index e532e1b09..000000000 --- a/doc/bugs/follows_symlinks_to_outside_annex/comment_1_f7a01bb627a6780d6940886401cde454._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 1" - date="2013-12-18T18:22:49Z" - content=""" -Tried to reproduce this, and so far no luck. I tried several symlinks to outside ~/annex, in both direct and indirect mode, and neither the assistant's startup scan nor its inotify handling followed the links and added the content of the directory symlinked to. - -I wonder if [[bugs/Symlinks_from_git-annex_repository_to_outside_git_repository_not_supported]] is the same problem. That seems to suggest this happens when merging the symlink into another repository. I am not clear on the details of how to reproduce it yet. -"""]] diff --git a/doc/bugs/follows_symlinks_to_outside_annex/comment_2_fcbeffab5a0146062a9c945dfff48507._comment b/doc/bugs/follows_symlinks_to_outside_annex/comment_2_fcbeffab5a0146062a9c945dfff48507._comment deleted file mode 100644 index 1e6d81107..000000000 --- a/doc/bugs/follows_symlinks_to_outside_annex/comment_2_fcbeffab5a0146062a9c945dfff48507._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 2" - date="2013-12-18T19:32:06Z" - content=""" -This was the same as the other bug, and only happened on OSX, in the startup scan. -"""]] diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn deleted file mode 100644 index 7f9ca28f6..000000000 --- a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -### Please describe the problem. - -Current layout is DIRHASH (of two levels) /KEY/KEY, so I would need to hardcode having that KEY directory. It might be nice to either make DIRHASH to return full hash directory (but it might break existing special remotes), or supplement with e.g. DIRHASHFULL which would return all the levels necessary to reach the KEY file - -> [[done]] --[[Joey]] diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment deleted file mode 100644 index dcedee1e6..000000000 --- a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_1_7454fe8e5a33335b89168de161d6a739._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-27T17:55:13Z" - content=""" -The intent in providing DIRHASH is to let external special remotes that -would like to do some hashing in their own backend storage get a value -that's suitable for that. - -I guess you're instead trying to use it to let the external special remote -access data stored in .git/annex/objects in the local repositpry. -And DIRHASH won't work for that; it's not even the right hash method. -(Not to mention, in direct mode, the data may not be stored in -.git/annex/objects at all.) - -If that's what you're looking for, I think that a new plumbing command -would be best. Something like `git annex contentlocation $KEY` outputting -a path to the content. -"""]] diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment deleted file mode 100644 index dd8cad081..000000000 --- a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="you read my mind correctly" - date="2015-03-27T19:43:01Z" - content=""" -Indeed I was just trying to get to the key's content (i.e. original archive from which to extract the load). Indeed, new command would be lovely to have - -I started to wonder what would be faster though -- calling another git annex instance with that command or asking through the PIPE/interface? - -P.S. I am scared to try any real tarball usecase and see how well it scales or not with all the ping-pong between external remote and annex ;) I guess I will discover soon -"""]] diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_3_6430c915dd2969bda4070fa4ba01a935._comment b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_3_6430c915dd2969bda4070fa4ba01a935._comment deleted file mode 100644 index b6d24563a..000000000 --- a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_3_6430c915dd2969bda4070fa4ba01a935._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-04-09T19:08:40Z" - content=""" -I've added a contentlocation command - -I'd expect an external command to not be much slower than using the pipe -for this. It does not need to spin up any git commands etc to get the -content location. Also, you can pass it multiple keys to query at one time -if necessary. - -I guess we'll see if this is too slow and can revisit it if so.. -"""]] diff --git a/doc/bugs/forget_corrupts_non-ascii_chars.mdwn b/doc/bugs/forget_corrupts_non-ascii_chars.mdwn deleted file mode 100644 index f4506c228..000000000 --- a/doc/bugs/forget_corrupts_non-ascii_chars.mdwn +++ /dev/null @@ -1,78 +0,0 @@ -### Please describe the problem. - -it seems that `git annex forget --drop-dead --force` will double-encode UTF-8 characters. - -### What steps will reproduce the problem? - -Have a remote with an accent in the description. - -### What version of git-annex are you using? On what operating system? - -5.20140412 on debian jessie amd64. - -### Please provide any additional information below. - -[[!format sh """ -anarcat@marcos:video$ git annex info -repository mode: indirect -trusted repositories: 1 - 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- here (backup (anarcat@marcos:/srv/video)) -semitrusted repositories: 5 - 00000000-0000-0000-0000-000000000001 -- web - 2d594c02-9164-4ebd-ac47-f8cdc9c16e2f -- rachel@topcrapn:~/Vidéos/anarcat - 2f90b958-95e4-44e3-8d3b-e780b63936d1 -- portable (300GB drive labeled VHS) - 96365189-a0b9-4c33-865f-b573d98572dc -- trouneslo@ifuckinglovecumputers:~/video-anarcat - ae3d62e6-49be-4340-ba25-c8736a1637c4 -- anarcat@angela:~/video -untrusted repositories: 1 - f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 -- External hard drive labeled VHS -transfers in progress: none -available local disk space: 14.29 gigabytes (+10 gigabytes reserved) -local annex keys: 4110 -local annex size: 991.85 gigabytes (+ 2 unknown size) -annexed files in working tree: 4108 -size of annexed files in working tree: 1.01 terabytes (+ 2 unknown size) -bloom filter size: 16 mebibytes (0.8% full) -backend usage: - SHA256E: 8214 - URL: 4 -anarcat@marcos:video$ git annex dead f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 -dead f6a70cfe-0ee4-4762-9f1d-b7b545fbd856 ok -(Recording state in git...) -anarcat@marcos:video$ git annex unused -unused . (checking for unused data...) (checking HEAD...) (checking synced/master...) (checking backup/master...) (checking portable/annex/direct/master...) (checking portable/master...) (checking portable/synced/master...) (checking steph/master...) (checking steph/synced/master...) (checking video/synced/master...) ok -anarcat@marcos:video$ git annex forget --drop-dead --force -forget git-annex (Recording state in git...) -ok -(Recording state in git...) -anarcat@marcos:video$ git annex info -repository mode: indirect -trusted repositories: (merging synced/git-annex backup/git-annex backup/synced/git-annex portable/git-annex portable/synced/git-annex steph/git-annex video/synced/git-annex into git-annex...) -(Recording state in git...) -(Recording state in git...) -1 - 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- here (backup (anarcat@marcos:/srv/video)) -semitrusted repositories: 5 - 00000000-0000-0000-0000-000000000001 -- web - 2d594c02-9164-4ebd-ac47-f8cdc9c16e2f -- rachel@topcrapn:~/Vidéos/anarcat - 2f90b958-95e4-44e3-8d3b-e780b63936d1 -- portable (300GB drive labeled VHS) - 96365189-a0b9-4c33-865f-b573d98572dc -- trouneslo@ifuckinglovecumputers:~/video-anarcat - ae3d62e6-49be-4340-ba25-c8736a1637c4 -- anarcat@angela:~/video -untrusted repositories: 0 -transfers in progress: none -available local disk space: 14.25 gigabytes (+10 gigabytes reserved) -local annex keys: 4110 -local annex size: 991.85 gigabytes (+ 2 unknown size) -annexed files in working tree: 4108 -size of annexed files in working tree: 1.01 terabytes (+ 2 unknown size) -bloom filter size: 16 mebibytes (0.8% full) -backend usage: - SHA256E: 8214 - URL: 4 -# End of transcript or log. -"""]] - -well that's interesting - the above paste is broken by ikiwiki as well... in the text area where i paste it, "rachel@topcrapn:~/Vidéos/anarcat" shows up as "rachel@topcrapn:~/Vidéos/anarcat" but when i preview, the character gets corrupted. and obviously, the second instance then gets *double* corrupted - wheepee. the original paste has "rachel@topcrapn:~/Vidéos/anarcat". --[[anarcat]] - -> [[fixed|done]]; writes to git-annex branch now preserve the original -> encoding, and I've tested that lots of interesting unicode is preserved -> across a forget run. --[[Joey]] diff --git a/doc/bugs/forget_corrupts_non-ascii_chars/comment_1_fc8a4a93be2c234567836a4acee90957._comment b/doc/bugs/forget_corrupts_non-ascii_chars/comment_1_fc8a4a93be2c234567836a4acee90957._comment deleted file mode 100644 index 1431f85bb..000000000 --- a/doc/bugs/forget_corrupts_non-ascii_chars/comment_1_fc8a4a93be2c234567836a4acee90957._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="comment 1" - date="2014-05-16T14:36:09Z" - content=""" -this eventually completely breaks with: - -[[!format txt \"\"\" -anarcat@marcos:video$ git annex info --fast -repository mode: indirect -trusted repositories: 2 - 31912b57-62a5-475c-87a7-582b5492a216 -- WD green 1.5TB backup drive - 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- here (main (anarcat@marcos:/srv/video)) -semitrusted repositories: 5 - 00000000-0000-0000-0000-000000000001 -- web - 2d594c02-9164-4ebd-ac47-f8cdc9c16e2f -- rachel@topcrapn:~/Vid -git-annex: <stdout>: commitBuffer: invalid argument (invalid character) -failed -git-annex: info: 1 failed -\"\"\"]] -"""]] diff --git a/doc/bugs/forget_corrupts_non-ascii_chars/comment_2_31f9362619dee0b8ebae80694ae1b2d0._comment b/doc/bugs/forget_corrupts_non-ascii_chars/comment_2_31f9362619dee0b8ebae80694ae1b2d0._comment deleted file mode 100644 index 6c62a91cb..000000000 --- a/doc/bugs/forget_corrupts_non-ascii_chars/comment_2_31f9362619dee0b8ebae80694ae1b2d0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 2" - date="2014-05-27T17:58:35Z" - content=""" -Notice that the filename is corrupted from the beginning; all writes to the git-annex branch truncated characters to 8 bits. The rest just followed from that. -"""]] diff --git a/doc/bugs/forget_corrupts_non-ascii_chars/comment_3_6310ae21036582688881f1890a5c4643._comment b/doc/bugs/forget_corrupts_non-ascii_chars/comment_3_6310ae21036582688881f1890a5c4643._comment deleted file mode 100644 index de949dc30..000000000 --- a/doc/bugs/forget_corrupts_non-ascii_chars/comment_3_6310ae21036582688881f1890a5c4643._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="comment 3" - date="2014-05-29T16:09:38Z" - content=""" -awesome, thanks! -"""]] diff --git a/doc/bugs/fsck_--from___36__remote__44___copies_symlinks_instead_of_content.mdwn b/doc/bugs/fsck_--from___36__remote__44___copies_symlinks_instead_of_content.mdwn deleted file mode 100644 index 732af2990..000000000 --- a/doc/bugs/fsck_--from___36__remote__44___copies_symlinks_instead_of_content.mdwn +++ /dev/null @@ -1,80 +0,0 @@ -### Please describe the problem. - - git annex fsck --from $remote - -copies the symlinks from the remote into *.git/annex/tmp*, which then fail to fsck as they don't point to content. - -In the transcript below, the 'a' file should fail fsck, but the rest pass. - -### What steps will reproduce the problem? - -See transcript - -### What version of git-annex are you using? On what operating system? - -* git-annex version: 5.20150409-g3575ee5 -* Arch Linux (git-annex-bin) - -### Please provide any additional information below. - - ## git init origin - ## cd corrupt/ - ## git annex init corrupt - ## echo a > a.txt - ## echo b > b.txt - ## echo c > c.txt - - ## git annex add . - add a.txt ok - add b.txt ok - add c.txt ok - (recording state in git...) - - ## git commit -m "add files" - [master (root-commit) 1d670a5] add files - 3 files changed, 3 insertions(+) - create mode 120000 a.txt - create mode 120000 b.txt - create mode 120000 c.txt - -("corrupting" a file not needed but here for completeness) - - ## chmod +w .git/annex/objects/41/pJ/SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt/ - ## echo 'd' > .git/annex/objects/41/pJ/SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt/SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt - - ## cd .. - - ## git clone corrupt/ recovery/ - Cloning into 'recovery'... - done. - - ## cd recovery/ - - ## git annex init recovery - init recovery (merging origin/git-annex into git-annex...) - (recording state in git...) - ok - (recording state in git...) - - ## git annex fsck --from origin - fsck a.txt - git-annex: .git/annex/tmp/fsck24477.SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt: getFileStatus: does not exist (No such file or directory) - failed - fsck b.txt - git-annex: .git/annex/tmp/fsck24477.SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f.txt: getFileStatus: does not exist (No such file or directory) - failed - fsck c.txt - git-annex: .git/annex/tmp/fsck24477.SHA256E-s2--a3a5e715f0cc574a73c3f9bebb6bc24f32ffd5b67b387244c2c909da779a1478.txt: getFileStatus: does not exist (No such file or directory) - failed - (recording state in git...) - git-annex: fsck: 3 failed - - ## ls -lah .git/annex/tmp/ - total 20K - drwxr-xr-x 2 gemma users 4.0K Apr 18 17:27 .. - drwxr-xr-x 5 gemma users 4.0K Apr 18 17:27 .. - lrwxrwxrwx 1 gemma users 197 Apr 18 17:27 fsck24477.SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f.txt -> ../corrupt/.git/annex/objects/x7/01/SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f.txt/SHA256E-s2--0263829989b6fd954f72baaf2fc64bc2e2f01d692d4de72986ea808f6e99813f.txt - lrwxrwxrwx 1 gemma users 197 Apr 18 17:27 fsck24477.SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt -> ../corrupt/.git/annex/objects/41/pJ/SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt/SHA256E-s2--87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7.txt - lrwxrwxrwx 1 gemma users 197 Apr 18 17:27 fsck24477.SHA256E-s2--a3a5e715f0cc574a73c3f9bebb6bc24f32ffd5b67b387244c2c909da779a1478.txt -> ../corrupt/.git/annex/objects/Vw/zz/SHA256E-s2--a3a5e715f0cc574a73c3f9bebb6bc24f32ffd5b67b387244c2c909da779a1478.txt/SHA256E-s2--a3a5e715f0cc574a73c3f9bebb6bc24f32ffd5b67b387244c2c909da779a1478.txt - -> reproduced, test cased, fixed, [[done]] --[[Joey]] diff --git a/doc/bugs/fsck_giving_false_checking_information.mdwn b/doc/bugs/fsck_giving_false_checking_information.mdwn deleted file mode 100644 index b22ac1c66..000000000 --- a/doc/bugs/fsck_giving_false_checking_information.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -### Please describe the problem. -When a repository has no object of a given file and git annex fsck is run it still shows "fsck file ok", which is missleading in the sense, that it gives the impression that it checked the file is alright/checksummed. - -As a result of this it seems that incremental fscks are not incremental with non checkable objects. On each run (after the first one) with "git annex fsck --incremental --more --schedule-limit 1d" all files without objects are checked even so it should wait another day till it checks again. - -Probably best to say checksum couldn't be checked on x files (only give that as quiet output, not every check) - -Another thing, which came up as a problem was, that checksum fsck would not be wanted to run as often as numcopie checks. -When the incremental fsck is used to check for bad files "git annex fsck --incremental --more --limit 1m" after a fast numcopies check "git annex fsck --incremental --more --limit 1m fast" it messes up the actual bad files check. -As both are currently using the same incremental "lock"-file they are colliding. - -### What steps will reproduce the problem? -- - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140210-gd99db49 -Linux (Ubuntu 13.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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/fsck_giving_false_checking_information/comment_1_1000603ea6b8a19eb09e6754789ad528._comment b/doc/bugs/fsck_giving_false_checking_information/comment_1_1000603ea6b8a19eb09e6754789ad528._comment deleted file mode 100644 index af198c722..000000000 --- a/doc/bugs/fsck_giving_false_checking_information/comment_1_1000603ea6b8a19eb09e6754789ad528._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="188.193.207.34" - subject="Earlier version syntax was removed" - date="2014-02-17T16:05:34Z" - content=""" -In earlier versions I noticed that when checksumming it would give back \"fsck file (checksum...) ok\" instead of \"fsck file ok\", which is at least better than not differentiating. This should definitely be improved. Perhaps even clearer than the (checksum...) notice. - -But still the incremental run not being incremental and not taking into account the schedule-limit seems strange. -"""]] diff --git a/doc/bugs/fsck_giving_false_checking_information/comment_2_3ce7c8f7098f0bf86ed409a3a095c152._comment b/doc/bugs/fsck_giving_false_checking_information/comment_2_3ce7c8f7098f0bf86ed409a3a095c152._comment deleted file mode 100644 index 838471598..000000000 --- a/doc/bugs/fsck_giving_false_checking_information/comment_2_3ce7c8f7098f0bf86ed409a3a095c152._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 2" - date="2014-02-20T20:11:36Z" - content=""" -You're only meant to use one of --incremental, or --more, or --incremental-schedule at a time. I have made fsck refuse to accept combinations of those options. - -What was happening is that, since you didn't understand the documentation (which is possibly not as clear as it could be; I have tried to improve it now), the --incremental option you passed dominated all the other options, and made it start a *new* incremental fsck each time. Which means it started from the beginning and fscked every file until you stopped it. - -I agree that it would be better if fsck --fast --incremental did not collide with fsck --incremental. There is already a bug about that: [[incremental fsck should not use sticky bit]]. - -Finally, I agree that losing the \"(checksum)\" made fsck output less informative. Although I don't think it is needed in the `git annex add` output. I have made it be shown in only the fsck output. -"""]] diff --git a/doc/bugs/fsck_giving_false_checking_information/comment_3_be4d0fec56c29cf978ef7d1715eaa516._comment b/doc/bugs/fsck_giving_false_checking_information/comment_3_be4d0fec56c29cf978ef7d1715eaa516._comment deleted file mode 100644 index 27de72358..000000000 --- a/doc/bugs/fsck_giving_false_checking_information/comment_3_be4d0fec56c29cf978ef7d1715eaa516._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="84.56.21.11" - subject="Great improvements" - date="2014-02-20T21:20:15Z" - content=""" -Thanks for clearing it up. It is still a bit confusing that you have to differentiate on the second run. (using --more) I probably view it as inconvenient as it make me have to remember the first and second time of running a command. I think it would be cleaner to have \"--incremental\" always skipping files and \"--incremental restart\" start from the beginning. - -Ah great yeah they are different functions and should therefore not interfere. (fsck --fast --incremental) - -Great that the checksum is back in and yeah I agree that it isn't really needed in the add command. - - -"""]] diff --git a/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok.mdwn b/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok.mdwn deleted file mode 100644 index fb0f84150..000000000 --- a/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -I am trying to verify that my files are where they should after having updated my remotes to use chunking. I do get the following two error messages, but then git-annex reports that everything is Ok. I find it slightly scary and thus wonder if the fsck command in all cases do a conservative enough check. All other files (except two other ones where it noticed that they where in fact not on the remote do not report any errors.) - -When running the fsck command for all files I got the following slightly worring message for one file. - - fsck Ekonomi/2014-06-02_Elavräkning.pdf (checking box.com5...) (checking box.com5...) (checking box.com5...) - 79% 23.2KB/s 26s - Error_Packet "partial packet: expecting 16448 bytes, got: 891" - ok - -Reading the message it seems that the file was not correctly downloaded, but still deemed Ok enough by git-annex. - -Further while writing this report I get the following message from a remote using the external protocol: - - fsck Deklaration/archive/2012/DE/Steuerklärung Formular.pdf - 93% 221.9KB/s 12s - /Users/carlmod/Annex/.git/annex/tmp/GPGHMACSHA1--0e7e4951e2650ac636bc3fc17c673f1f2dfb3071: openBinaryFile: does not exist (No such file or directory) - ok - -Source code for this remote is not yet published online, as i would want to build it slightly more reliable before releasing it. It however passes the remote test suite without any problem. -### What steps will reproduce the problem? - -Not really sure, but rerunning the commands show that the openBinaryFile happens here for this particular file. - -### What version of git-annex are you using? On what operating system? - - $ git annex version - git-annex version: 5.20141125 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - -built using Homebrew (i.e. in a cabal sandbox) on OS X Yosemite 10.10.1 - -> [[fixed|done]] as described in comment --[[Joey]] diff --git a/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok/comment_1_b76598aebcaccf1e1065dc6372a333ab._comment b/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok/comment_1_b76598aebcaccf1e1065dc6372a333ab._comment deleted file mode 100644 index 52f42ba89..000000000 --- a/doc/bugs/fsck_of_special_remotes_incorrectly_reports_ok/comment_1_b76598aebcaccf1e1065dc6372a333ab._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-10T17:04:10Z" - content=""" -So, what's going on here is: - -* fsck first calls hasKey to check if the remote has the key -* It does, so it proceeds to try to download the file -* This fails for whatever reason (probably a transient network error - in the first example, and a bug in your code in the second) -* So, fsck bypasses checking the checksum, and just assumes that - hasKey was right, the key is present in the remote. - -Question is, should it instead assume hasKey is innaccurate, -and mark the remote as no longer containing the file jut because -it failed to download it once? - -I don't think so. This would mean that fsck --from networkremote -and then dropping network connection in the middle of the file -download would mark the file as not present on the remote any longer. - -I think though, that it would make sense for fsck to propigate an -error in this case. It can leave the location log as-is, but not -assume "ok". -"""]] diff --git a/doc/bugs/fsck_reports_unsolvable_problem.mdwn b/doc/bugs/fsck_reports_unsolvable_problem.mdwn deleted file mode 100644 index 56c794422..000000000 --- a/doc/bugs/fsck_reports_unsolvable_problem.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -On my bare git-annex repo, `git annex fsck -q` reports: - - ** No known copies exist of SHA256E-s1212237--d2edd369f6a9005e23f022c7d797b166c66b90defc561329dbafab9a0fc0c7fc.jpg - -`git log -SSA256E...` returns nothing. `git annex repair` and `git annex forget` do not fix the problem. - -This means that running `fsck` from cron or a script will now always fail. There should be a way to recover from this situation. - -### What steps will reproduce the problem? - -According to IRC this "can happen if you annexed a file and then deleted it without ever committing to git". - - -### What version of git-annex are you using? On what operating system? - -5.20140717 from Ubuntu utopic - -[[!tag confirmed]] - -> [[done]] -- fsck --all or in a bare repo will skip over keys that have -> been marked dead, which can be done with `git annex dead --key`. -> -> Might go further later, and make `git annex drop --force`, when removing -> the last copy of a key, mark it as dead. But maybe that is too DWIM. -> --[[Joey]] diff --git a/doc/bugs/fsck_reports_unsolvable_problem/comment_1_2beb21b685cea7402ffbf84d247c30b2._comment b/doc/bugs/fsck_reports_unsolvable_problem/comment_1_2beb21b685cea7402ffbf84d247c30b2._comment deleted file mode 100644 index e43ed96f5..000000000 --- a/doc/bugs/fsck_reports_unsolvable_problem/comment_1_2beb21b685cea7402ffbf84d247c30b2._comment +++ /dev/null @@ -1,51 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-14T16:57:15Z" - content=""" -case 1 - -1. git annex add file -2. git annex drop --force file -3. git rm file -4. git commit -m nochange - -case 2 - -1. git annex add file -2. git commit -m added -3. git annex drop --force file -4. git rm file -5. git commit -m removed - -fsck --all, or fsck in a bare repo, will repport the same problem in either -case; the only difference being that in the latter case you can see that -the master branch's history (or some user branch) did once include the lost -file. In the former case, only the git-annex branch ever had a commit made -about the lost file. - -The only way to remove this message would be either remove the log file -from the git-annex branch, or teach fsck to ignore it. - -Due to union merge it's not as simple as deleting the log file. A `git -annex forget` type transition is needed to avoid merging the log file back in -from elsewhere. It's certianly doable using the transition infrastructure. - -Or, fsck could have its own blacklist of known problems to not warn about. -in some ways that's more complex; in others it's perhaps simpler since it -avoids the complexity needed to handle transitions. (forced pushing, branch -rewriting on merge, etc) - -Either way, I think the question is what UI to use to identify these keys. -Seems like the user would have to examine their repos's history and -understand whether they've hit case 1, or case 2, vs when a file they -really wanted to have available in the history has actually been lost. -Fsck could give some guidance, but not a whole lot. Note that if the user -goofs up, they coud end up in a situation that's rather more a mess than -this one! - -(I've seen maybe half a dozen people reporting this problem before. I think -most or all of them were using fsck in a bare repository. It might be that, -if fsck in a bare repository didn't behave as fsck --all, nobody would -care.) -"""]] diff --git a/doc/bugs/fsck_reports_unsolvable_problem/comment_2_d32d4cd471632f63db681f3495039b00._comment b/doc/bugs/fsck_reports_unsolvable_problem/comment_2_d32d4cd471632f63db681f3495039b00._comment deleted file mode 100644 index 1fa08f39c..000000000 --- a/doc/bugs/fsck_reports_unsolvable_problem/comment_2_d32d4cd471632f63db681f3495039b00._comment +++ /dev/null @@ -1,52 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-06-09T16:59:22Z" - content=""" -Had a closer look at using a transition for this. It would mean that, when -merging with any repo that has not made the transition yet, that repo would -need to be modified to remove log files for keys that are no longer present -anywhere. Without a list of exactly which keys, the transition could take -out files, as it spreads, that were not the ones originally desired to be -ignored. - -So, I think that and the branch rewriting overhead of transitions both make -a transition not a desirable way to handle this. - -Seems like the best way, then, is a log file where keys can be listed that -are known gone and that fsck should shut up about. Although there could be -scalability problems to listing them all in a single file, which would all -need to be loaded into memory by fack. - -Or, could have separate files per key, but that adds another query to every -key fsck processes. - -Or, the location log format could be extended, to add a flag to indicate -when fsck should ignore a given key. This adds some complexity to file -formats, but it seems like the best choice. - -Could extend the 1/0 in the log to add a third value for "ignore this". -Turns out that putting eg 'X' there doesn't break any old versions of -git-annex; they ignore the unparsable line, and the result is the same as a -'0' line; the key is not present in the specified location. - -So, if there's an 'X', it means the key is thought to be dead at that -location; it's not present in that location, and fsck should avoid warning -when a key is dead in all locations. (A key that somehow had no locations -listed at all but still had a location log would also meet that crieria, -but that currently can't happen.) - -If a key is dead in one location and alive in another location, it's still -alive. A key that was thought to be dead everywhere can come back alive, -eg, when a previously unknown remote that has the content is merged in. - -As to the UI for this, it could be added to `git annex forget` or a new -command. It would also be possible for `drop --force` to automatically set -the dead flag when it removed the last copy of a key. Seems like, if the -user has requested a forced drop of the last copy, they don't need fsck -telling them about it later. - -I think that only fsck --all (or in a bare repo) should ignore dead keys -though. If a git work tree has files that point to dead keys, fsck should -still complain. -"""]] diff --git a/doc/bugs/getEffectiveUserID_not_supported_on_Windows.mdwn b/doc/bugs/getEffectiveUserID_not_supported_on_Windows.mdwn deleted file mode 100644 index e8271ff94..000000000 --- a/doc/bugs/getEffectiveUserID_not_supported_on_Windows.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. -After a clean install of the latest git-annex for Windows (https://downloads.kitenet.net/git-annex/windows/current/), most git-annex commands fail with the following error message: - - git-annex: System.PosixCompat.User.getEffectiveUserID: not supported: illegal operation - -### What steps will reproduce the problem? - - git init - git annex init - -Running for example `git annex version` or `git annex info` gives the same error message. - - -### What version of git-annex are you using? On what operating system? - -git-annex version should be 5.20141024, but the installer does not specify version and `git annex info` does not work, so it is hard to tell for sure. -Running Windows 7, x64. Also tried running as administrator and in a cmd.exe shell as well as Powershell. - - -### Please provide any additional information below. - -The `git annex test` command does work, and all 84 tests passes. - -> [[fixed|done]]; I was able to reproduce this bug, and it was crashing -> trying to look up the geckos username. I don't understand why this worked -> before; some change exposed this code path on Windows. In any case, I've -> fixed the crash, and I will be updating the windows builds with this bug -> fix. --[[Joey]] diff --git a/doc/bugs/get_from_glacier_fails_too_early.mdwn b/doc/bugs/get_from_glacier_fails_too_early.mdwn deleted file mode 100644 index 489240330..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early.mdwn +++ /dev/null @@ -1,72 +0,0 @@ -### Please describe the problem. - -In order to test the integrity of my file backup on glacier, -I initiated get of a single file from glacier via: - - $ git annex get --from=glacier localdir/myfile.jpg - -A check with - - $ glacier job list - -confirmed, that a job was in progress. - -Then after a couple hours wait the job is complete -[[!format sh """ -[ben@voyagerS9 annex]$ glacier job list -i/d 2014-10-16T20:25:23.068Z glacier-bbbbbbbb-bbbb-bbbb-bbbb-MYVAULTbbbbb -a/d 2014-10-16T20:30:13.086Z glacier-bbbbbbbb-bbbb-bbbb-bbbb-MYVAULTbbbbb GPGHMACSHA1--cccccccccccc -"""]] - -So, again I enter the get command: -[[!format sh """ -[ben@voyagerS9 annex]$ git annex get --from=glacier localdir/myfile.jpg -get localdir/myfile.jpg (from glacier...) (gpg) -failed -git-annex: get: 1 failed -[ben@voyagerS9 annex]$ -"""]] - -The command immediately fails after entering the gpg passphrase, releasing the shell. -But in the background the glacier-cli is still running, downloads the file from Amazon -and then dumps the gpg encrypted file content into the terminal. -(4 MB of binary character garbage on the screen) - -git annex should not fail so early and wait until the data is coming in order to pipe it into gpg. - -### What version of git-annex are you using? On what operating system? -Arch Linux git-annex-bin package. -[[!format sh """ -[ben@voyagerS9 annex]$ git annex version -git-annex version: 5.20140920-gb0c4300 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -[ben@voyagerS9 annex]$ gpg --version -gpg (GnuPG) 2.0.26 -libgcrypt 1.6.2 -"""]] - -### Possibly related information about the annexed repo and its history -The file was uploaded sometime earlier this year with a different version of git annex: Older source package for Arch Linux with Haskell packages from the Arch haskell repos. - -The special glacier remote was initially set up with an old gpg key (hybrid encryption), which is still in my keychain but has expired. I exchanged the key with a new one by - - $ git annex enableremote glacier keyid+=NEWKEY keyid-=OLDKEY - -I don't know why, but my AWS credentials seem no longer be embedded into the git repo. glacier upload (copy --to=) only succeeds with explicitly set AWS credential environment variables - -I tried - - $ git annex enableremote embedcreds=yes - -with no noticeable change. -I had changed the AWS credentials a while ago. - -Tomorrow I will try to download a just recently uploaded file with the current credentials and keys. - -> [[done]]; I am not confident that I understand this failure on retrival, -> and that I've fixed it. --[[Joey]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_1_5a4e37fef629e07dce6b83ae311d1b03._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_1_5a4e37fef629e07dce6b83ae311d1b03._comment deleted file mode 100644 index 736457f2a..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_1_5a4e37fef629e07dce6b83ae311d1b03._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-10-20T18:54:43Z" - content=""" -Wow, the code seems to neglect to actually set up a pipe from glacier-cli's -stdout. It seems this broke quite a while ago, in -[[!commit fb19d56476bb6eb5aa4d794a10199adb267d5870]] and nobody noticed. - -I have committed what should be a fix, but it's pretty hard for me to test -this. Can you please either test the current daily autobuild for linux -amd64 (should be ready about 15 minutes after I post this comment), or -build git-annex from master and test? -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_2_da065d367d0a3c91e4957f588f36dc67._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_2_da065d367d0a3c91e4957f588f36dc67._comment deleted file mode 100644 index 2afe60195..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_2_da065d367d0a3c91e4957f588f36dc67._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""creds""" - date="2014-10-20T19:09:28Z" - content=""" -Since you are using gpg encryption, your repository may have -[[upgrades/insecure_embedded_creds]]. Strongly suggest you check if it -does. -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_3_1b49cd66a612bb46da5b73c83ab14688._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_3_1b49cd66a612bb46da5b73c83ab14688._comment deleted file mode 100644 index ccdd94848..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_3_1b49cd66a612bb46da5b73c83ab14688._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkck-Tokgfh_1Fwh6pkl69xPA_dYUgA4Tg" - nickname="Benjamin" - subject="autobuild" - date="2014-10-20T22:39:25Z" - content=""" -Okay, where do I get the newest build? I cannot find a link to a packaged file at http://downloads.kitenet.net/git-annex/autobuild/amd64/ - -I'd rather not build it from master myself, as all the Haskell dependencies are not well supported on Arch linux. Thats why I switched from the git-annex package to the git-annex-bin package in AUR in the first place. - -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_4_a20b46a5e9c1c72a484962f3539d3b3e._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_4_a20b46a5e9c1c72a484962f3539d3b3e._comment deleted file mode 100644 index c46042d4e..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_4_a20b46a5e9c1c72a484962f3539d3b3e._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2014-10-21T16:31:33Z" - content=""" -http://git-annex.branchable.com/install/Linux_standalone/ -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_5_488bb44796e6a4e16f7bfc1f229233e7._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_5_488bb44796e6a4e16f7bfc1f229233e7._comment deleted file mode 100644 index c67f60288..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_5_488bb44796e6a4e16f7bfc1f229233e7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.96" - subject="comment 5" - date="2014-10-21T19:59:06Z" - content=""" -Recent autobuilds will also print out some useful info when you run `git annex info glacier`, including where it's getting the AWS credentials from. -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_6_9c8f262b3d8b37f2e68108337acbd303._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_6_9c8f262b3d8b37f2e68108337acbd303._comment deleted file mode 100644 index 48e9f5335..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_6_9c8f262b3d8b37f2e68108337acbd303._comment +++ /dev/null @@ -1,48 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkck-Tokgfh_1Fwh6pkl69xPA_dYUgA4Tg" - nickname="Benjamin" - subject="autobuild test" - date="2014-10-21T22:09:47Z" - content=""" -Okay I managed to package the autobuild for my Arch system and installed. Here is what I get, retrieving finished glacier retrieval jobs which was started yesterday: - -Without AWS credentials as environment variables, the call fails: -[[!format sh \"\"\" -[ben@voyagerS9 annextest]$ git annex get --from=glacier mydir/myfile1 -get mydir/myfile (from glacier...) (gpg) -['/usr/local/bin/glacier', '--region=us-east-1', 'archive', 'retrieve', '-o-', 'glacier-myvault', 'GPGHMACSHA1--4286b1a121892c9e64de436725478b0bc5038e67'] -glacier: archive 'GPGHMACSHA1--4286b1a121892c9e64de436725478b0bc5038e67' not found -failed -git-annex: get: 1 failed -\"\"\"]] - -I patched the glacier-cli Python source so that it prints out the command arguments argv. -The archive _does_ exist. Executing the glacier-cli command manually is successful. So is calling -git-annex with AWS credentials exported into env: - -[[!format sh \"\"\" -[ben@voyagerS9 annextest]$ git annex get --from=glacier mydir/myfile2 -get mydir/myfile2 (from glacier...) (gpg) -['/usr/local/bin/glacier', '--region=us-east-1', 'archive', 'retrieve', '-o-', 'glacier-myvault', 'GPGHMACSHA1--c3827c03d48b4829c7cc584778652c66e2784b0f'] -ok -(Recording state in git...) -\"\"\"]] - -So I guess one bug is fixed, although I think there is a wrong error message. - -Regarding AWS credentials, I have no success in updating credentials or finding out which if any are embedded: -[[!format sh \"\"\" -[ben@voyagerS9 annextest]$ git annex info glacier -remote: glacier -description: [glacier] -uuid: b4dcf525-40c7-4f04-86cc-3850d1260680 -cost: 1050.0 -type: glacier -glacier vault: glacier-myvault -encryption: encrypted (to gpg keys: MYKEY) -chunking: none -\"\"\"]] - -When I checkout the git-annex branch and look into the remote.log I see fields for cipher, cipherkeys, datacenter, embedcreds=yes, name, s3creds, type, vault, timestamp. -The s3creds field does not look like my current AWS credentials, at least not in plaintext. -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_7_c96b71759fe0d2af450e321ca57edb46._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_7_c96b71759fe0d2af450e321ca57edb46._comment deleted file mode 100644 index 0cdef26b5..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_7_c96b71759fe0d2af450e321ca57edb46._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.96" - subject="comment 7" - date="2014-10-22T18:30:29Z" - content=""" -I forgot to include the creds in `git annex info` for glacier; fixed that now. - -It seems that changing the creds with `enableremote` did embed them into your git repository, but it neglected to update the .git/annex/creds/$remoteuuid file that caches the creds locally. So I think that your old creds are still cached there, and still being used, and this explains why the file is not found in glacier; the wrong creds are being used to access it! You can work around this by deleting the .git/annex/creds/$remoteuuid file correspnding to the uuid of the glacier remote. (You can also look at that file and compare it with what the creds are supposed to be.) I have fixed git-annex enableremote to update that creds file. - -Also, it looks like you did not fall afoul of the [[upgrades/insecure_embedded_creds]] problem! If you had, this new version of git-annex would be complaining that it had detected that problem. If you want to double-check that, the s3creds= value is base64 encoded, and when run through `base64 -d`, it should yield a gpg encrypted file. If your repo did have that problem, it would instead decode to the creds in clear text. -"""]] diff --git a/doc/bugs/get_from_glacier_fails_too_early/comment_8_1267236ae339d1affd46edb5cf5f4ac5._comment b/doc/bugs/get_from_glacier_fails_too_early/comment_8_1267236ae339d1affd46edb5cf5f4ac5._comment deleted file mode 100644 index 5265d7cfb..000000000 --- a/doc/bugs/get_from_glacier_fails_too_early/comment_8_1267236ae339d1affd46edb5cf5f4ac5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkck-Tokgfh_1Fwh6pkl69xPA_dYUgA4Tg" - nickname="Benjamin" - subject="comment 8" - date="2014-10-22T19:56:23Z" - content=""" -Thanks, deleting the cached file fixed it. -"""]] diff --git a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected.mdwn b/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected.mdwn deleted file mode 100644 index 85aec12fb..000000000 --- a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected.mdwn +++ /dev/null @@ -1,121 +0,0 @@ -### Please describe the problem. - -[[git-annex-shell]] seems to be designed to be put as some users' shells so that git-annex can be safely used from `sshd`. - -### What steps will reproduce the problem? - -<pre> -root@cs:/srv/gitannex-test# grep gitannex /etc/passwd -gitannex:x:999:999:Git annex sandbox:/var/lib/gitannex:/usr/local/bin/git-annex-shell -</pre> - -`/usr/local/bin/git-annex-shell` is a symlink to the standalone git-annex installed in `/opt`. - -<pre> -anarcat@desktop008:isuma-annex-test$ git remote -v -origin gitannex@example.com:/srv/gitannex-test (fetch) -anarcat@desktop008:isuma-annex-test$ git annex sync -muxserver_listen: link mux listener .git/annex/ssh/gitannex@example.com.bFOddoa2pVKZGHQ2 => .git/annex/ssh/gitannex@example.com: Operation not permitted - - Remote origin does not have git-annex installed; setting annex-ignore - - This could be a problem with the git-annex installation on the remote. Please make sure that git-annex-shell is available in PATH when you ssh into the remote. Once you have fixed the git-annex installation, run: git config remote.origin.annex-ignore false -commit ok -pull origin -git-annex: unknown command gitannex@cs.isuma.tv - -Usage: git-annex command [option ...] - -Commonly used commands: - -add [PATH ...] add files to annex -[...] - -Testing commands: - -fuzztest generates fuzz test files -test run built-in test suite -testremote REMOTE test transfers to/from a remote - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -failed -push origin -git-annex: unknown command gitannex@cs.isuma.tv - -Usage: git-annex command [option ...] - -Commonly used commands: - -add [PATH ...] add files to annex -[...] -Testing commands: - -fuzztest generates fuzz test files -test run built-in test suite -testremote REMOTE test transfers to/from a remote - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config) -failed -git-annex: sync: 2 failed -</pre> - -Note that moving the repository out of NFS doesn't fix the problem, i still get `git-annex: unknown command gitannex@cs.isuma.tv`. - -How am i supposed to use `git-annex-shell`? -- [[anarcat]] - -### What version of git-annex are you using? On what operating system? - -client side: 5.20141125 - -server side: 5.20150406-g2a9fbec - -### 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. -"""]] - -Update: well that's confusing. it turns out the `unknown command` bit still happens when i use `/bin/sh` as a shell for the gitannex user. i really don't understand what's going on here... :/ - -After running with `--debug`, i noticed this was happening on the client with any git-annex remote, including one running the same version (`5.20141125`), and it happens after `git-annex` calls `git push` or `git fetch`: - -<pre> -anarcat@desktop008:isuma-annex-test$ git annex --debug sync test3 -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","show-ref","git-annex"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","show-ref","--hash","refs/heads/git-annex"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/git-annex..41069ddc0e22abc7ef0dca2aa31b20af9cee6116","-n1","--pretty=%H"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/git-annex..0ad850f59bdbe2448fa75e415ebfa5cf19cbebcd","-n1","--pretty=%H"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/git-annex..3476b0db2960fa9c9b00350e692e23dd30cd18c7","-n1","--pretty=%H"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/git-annex..d5cd95f472e00c51a2d35dedabf85f47cf3ce7fa","-n1","--pretty=%H"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/git-annex..778ba43445db7deb1bc6543e07145c13d3c3e5e2","-n1","--pretty=%H"] -[2015-04-06 16:52:36 EDT] chat: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","cat-file","--batch"] -[2015-04-06 16:52:36 EDT] read: git ["config","--null","--list"] -commit [2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","commit","-a","-m","git-annex automatic sync"] -ok -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","symbolic-ref","HEAD"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","show-ref","refs/heads/master"] -[2015-04-06 16:52:36 EDT] call: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","show-ref","--verify","-q","refs/heads/synced/master"] -[2015-04-06 16:52:36 EDT] read: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","log","refs/heads/master..refs/heads/synced/master","-n1","--pretty=%H"] -pull test3 -[2015-04-06 16:52:36 EDT] read: ssh ["-O","stop","-S","anarc.at","-o","ControlMaster=auto","-o","ControlPersist=yes","localhost"] -[2015-04-06 16:52:36 EDT] call: git ["--git-dir=/srv/scratch/anarcat/isuma-annex-test/.git","--work-tree=/srv/scratch/anarcat/isuma-annex-test","fetch","test3"] -git-annex: unknown command anarc.at -</pre> - -Turning off `sshcaching` seems to work around the issue. Note that this happens even if the git repo is moved to a non-NFS filesystem, so I have the feeling it's not directly related to [this bugfix](http://source.git-annex.branchable.com/?p=source.git;a=commit;h=bd110516c09d318b298804efc4ee888270f3d601). - -> [[done]] diff --git a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_1_a9854c59ff288c503788d6fff6cf37b5._comment b/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_1_a9854c59ff288c503788d6fff6cf37b5._comment deleted file mode 100644 index b2909a9ce..000000000 --- a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_1_a9854c59ff288c503788d6fff6cf37b5._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-06T21:15:46Z" - content=""" -This has nothing to do with git-annex-shell or anything server-side. We can -see this in the error messages; the error comes from client-side git-annex -and not from git-annex-shell at all. - -For annex.sshcaching to work, git-annex has to set GIT_SSH=git-annex, and -then git calls it with the name of the hostname to ssh to. - -So, your client-side git-annex is new enough to do sshcaching on sync, but -then when git runs $GIT_SSH, the git-annex program it then runs seems -to be an older version of git-annex. Which does not appreciate being called -as if it is ssh. - -Fix this version confusion and your problem will be solved. Maybe -have an older version of git-annex somewhere in PATH where git finds it. -Or, maybe you have a ~/.config/git-annex/program file that points to some -older installation of git-annex. - -(It might also help to upgrade to a current version, ideally before filing -a bug report; it's quite possible some change has been made that will -make whatever your setup is work.) -"""]] diff --git a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_2_258c158e90e1b159e0f89b82f3585b4d._comment b/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_2_258c158e90e1b159e0f89b82f3585b4d._comment deleted file mode 100644 index a0a3133a3..000000000 --- a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_2_258c158e90e1b159e0f89b82f3585b4d._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 2" - date="2015-04-06T22:16:57Z" - content=""" -thanks for the quick feedback. it can certainly be the case that i have two installs of git-annex out there... i'll take a look when i'm back in the office. - -it wasn't obvious to me that the error was from the client-side of things, how could I tell? - -wouldn't it be better if GIT_SSH would be set to the full path of the binary? - -thanks! -"""]] diff --git a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_3_b4b8f2c595a1add70c176cf51d27b72a._comment b/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_3_b4b8f2c595a1add70c176cf51d27b72a._comment deleted file mode 100644 index 9e35f3412..000000000 --- a/doc/bugs/git-annex-shell_doesn__39__t_work_as_expected/comment_3_b4b8f2c595a1add70c176cf51d27b72a._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="confirmed" - date="2015-05-14T15:50:32Z" - content=""" -so this is confirmed: i had git-annex installed from packages, and git-annex in /opt/bin/, installed using the standalone binary. `~/.config/git-annex/program` points to the latter, `$PATH` to the former. - -really confusing bug... removing the package works around the issue. -"""]] diff --git a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git.mdwn b/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git.mdwn deleted file mode 100644 index 47ee6ed81..000000000 --- a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git.mdwn +++ /dev/null @@ -1,50 +0,0 @@ -### Please describe the problem. - -When trying to create a repository—i.e., running it for the first time—I get this error message: - -> user error (git ["--git-dir=(path)/.git","--work-tree=(path)","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904","--no-gpg-sign"] exited 128) - -It _seems_ that it's because the bundled `git` executable isn't used, and instead `/usr/bin/git` is; and it's too old to support the `--no-gpg-sign` flag. - - -### What steps will reproduce the problem? - -Run `git-annex.app` for the first time and give it a path. - - -### What version of git-annex are you using? On what operating system? - - $ /Applications/Git-Annex.app/Contents/MacOS/git-annex version - git-annex version: 5.20140707-gf0c48e8 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - - -### Please provide any additional information below. - -`…/.git/annex/daemon.log` doesn't exist - - $ tree -a - . - ├── .DS_Store - └── .git - ├── HEAD - ├── annex - │ ├── index - │ ├── misctmp - │ ├── sentinal - │ └── sentinal.cache - ├── config - ├── hooks - │ └── pre-commit - ├── objects - │ ├── 4b - │ │ └── 825dc642cb6eb9a060e54bf8d69288fbee4904 - │ ├── info - │ └── pack - └── refs - ├── heads - └── tags - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_1_73924adc1c3c0dca5adce9a5e1740e48._comment b/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_1_73924adc1c3c0dca5adce9a5e1740e48._comment deleted file mode 100644 index 888ef1e4a..000000000 --- a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_1_73924adc1c3c0dca5adce9a5e1740e48._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-08T16:44:32Z" - content=""" -No, it's using it, it seems the version of git in the OSX build does not support that option. - -I am going to fix the version problem, and update yesterday's OSX release with the fix. -"""]] diff --git a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_2_81c2896c9dfe5d96ad5a8f40cb312790._comment b/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_2_81c2896c9dfe5d96ad5a8f40cb312790._comment deleted file mode 100644 index fef971218..000000000 --- a/doc/bugs/git-annex.app_doesn__39__t_seem_to_use_the_bundled_git/comment_2_81c2896c9dfe5d96ad5a8f40cb312790._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawn0aWOz5xMj5VuexPl55h7IasQnsh7sVwE" - nickname="Andy" - subject="It works now" - date="2014-07-08T22:47:07Z" - content=""" -You were right, it was an old git. I could have sworn it worked, but I must've got the versions mixed up because it didn't earlier. - -Anyway, after updating, everything works fine. Thankyou! -"""]] diff --git a/doc/bugs/git-annex_annex_repo_not_found.mdwn b/doc/bugs/git-annex_annex_repo_not_found.mdwn deleted file mode 100644 index 1a2998f05..000000000 --- a/doc/bugs/git-annex_annex_repo_not_found.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -### Please describe the problem. - -The git-annex annex repo at <https://downloads.kitenet.net/.git/> is not available. This is the address mentioned at <http://git-annex.branchable.com/publicrepos/>. - -### What steps will reproduce the problem? - - $ git clone https://downloads.kitenet.net/.git/ - Cloning into 'downloads.kitenet.net'... - fatal: repository 'https://downloads.kitenet.net/.git/' not found - -### Please provide any additional information below. - -Have tried various combinations of the URL, but nothing works. It was like this a week ago too, but I didn't report it because I thought it was a temporary error due to some server reconfiguration or something. - -[[!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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn b/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn deleted file mode 100644 index af9a4a1e5..000000000 --- a/doc/bugs/git-annex_assistant_not_working_with_nested_git_repos.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. -When using git-annex in indirect mode (or even in direct mode I think, although this is not to be very reliable in this context), git repos inside a git-annex are ignored. This is due to the fact that git is ignoring nested .git folders, and then, we can safely work with git-annex and nested git repos without conflicts. - -Using a tool such as my-repos, one can then sync its entire home directory, containing folders and git repos, syncing the normal folders thanks to git-annex, and storing the git repos metadata for easy cloning using my-repos. - -However, when using the git-annex assistant (or the daemon to have automatic background sync), this is no longer the case. - -After discussion on IRC, we thought this could be due to the fact that files are copied sequentially and that the .git folder is not yet present when it starts copying. However, disabling the daemon, copying the files and reenabling it then leads to the same behaviour. - -Thanks! - - -### What version of git-annex are you using? On what operating system? - -git-annex-bin on AUR. - -> Many people have reported this as a bug, see -> <http://git-annex.branchable.com/bugs/Can__39__t_add_a_git_repo_to_git_annex:___34__Invalid_path_repo__47__.git__47__X__34___for_many_X/> -> -> But git simply does not allow -> storing .git in .git. With good reason IMHO. So this is a duplicate -> bug report, and I can't fix it. [[done]]. --[[Joey]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant.mdwn b/doc/bugs/git-annex_auto_upgrade_is_redundant.mdwn deleted file mode 100644 index 582a8edee..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. - -Hi, - -On OSX the web-app keeps notifying me of an upgrade, I choose to run it but nothing seems to happen. - -The debug logs show that the upgrade is skipped as it's redundant. - -### What steps will reproduce the problem? - -Have upgrades set to notify. - -### What version of git-annex are you using? On what operating system? - -Current. - -### 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 -[2014-04-25 08:26:30 BST] Upgrader: An upgrade of git-annex is available. (version 5.20140421) -[2014-04-25 08:27:02 BST] main: Skipping redundant upgrade - -# End of transcript or log. -"""]] - -[[!meta title="upgrade loop when info file contains newer version than distributed version of git-annex"]] - -[[!tag confirmed]] - -> [[fixed|done]]; the release process now uses versions from build-version -> files that are created by the autobuilders, so should always be accurate. -> --[[Joey]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_1_67cdbedc70695d1e4be81e59ab9b87bd._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_1_67cdbedc70695d1e4be81e59ab9b87bd._comment deleted file mode 100644 index be27aa0d9..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_1_67cdbedc70695d1e4be81e59ab9b87bd._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 1" - date="2014-04-25T07:36:09Z" - content=""" -The upgrade notifications seem to appear when switching between repositories in the web-app - are repositories treated separately? Or perhaps notifications sent per repo? - -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_2_3a8041ce622b9288261fab57ecb87c28._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_2_3a8041ce622b9288261fab57ecb87c28._comment deleted file mode 100644 index 1b4c0505d..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_2_3a8041ce622b9288261fab57ecb87c28._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="comment 2" - date="2014-04-25T13:25:43Z" - content=""" -i think this problem was quickly mentionned in [[devblog/day_157__upgrade_checking]], can you provide a full debug log? -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_3_2597b2008557b80f4b71630c5c4a4241._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_3_2597b2008557b80f4b71630c5c4a4241._comment deleted file mode 100644 index 22c8986b7..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_3_2597b2008557b80f4b71630c5c4a4241._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 3" - date="2014-04-26T20:26:35Z" - content=""" -I'm pretty sure that was the sum total of the log (even with debug on). Only the brevity of it makes me doubt myself. -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_4_5dc46103994f064f5b9e120a16317dbd._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_4_5dc46103994f064f5b9e120a16317dbd._comment deleted file mode 100644 index 7bd1ec883..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_4_5dc46103994f064f5b9e120a16317dbd._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.114" - subject="comment 4" - date="2014-04-27T00:02:41Z" - content=""" -What version of git-annex do you have running? - -I suspect that if you look around, you will find you have a git-annex-5.20140421 directory in either your home directory or next to where you installed the DMG. -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_5_e26cf6fa6358c8d53c0b16206d0d0ca6._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_5_e26cf6fa6358c8d53c0b16206d0d0ca6._comment deleted file mode 100644 index 65c6b05c6..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_5_e26cf6fa6358c8d53c0b16206d0d0ca6._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 5" - date="2014-04-27T11:10:49Z" - content=""" -Hi, - -Yes there is a git-annex.app.5.20140421 directory in $HOME. And it looks as though I'm running git-annex.app.5.20140420 - even though I manually tried to upgrade by downloading - -https://downloads.kitenet.net/git-annex/OSX/current/10.9_Mavericks/git-annex.dmg - -Running `$HOME/git-annex.app.5.20140421/.../git-annex` gives me `5.20140420-ga25b8bb`. So the downloaded version even though labeled 5.20140421 contains 5.20140420. -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_6_c2c7c071fc5b1d3a55254d01a287c9f8._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_6_c2c7c071fc5b1d3a55254d01a287c9f8._comment deleted file mode 100644 index 3092626e6..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_6_c2c7c071fc5b1d3a55254d01a287c9f8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 6" - date="2014-04-27T11:14:40Z" - content=""" -And I still think there is a slight bug in there somewhere. If due to packaging errors an upgrade doesn't apply and the logs are smart enough to notice it's redundant then there shouldn't be continued notifications of an available upgrade... -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_7_85e8a286d6b1ec5212614c36bf54addb._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_7_85e8a286d6b1ec5212614c36bf54addb._comment deleted file mode 100644 index 3586aca7f..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_7_85e8a286d6b1ec5212614c36bf54addb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 7" - date="2014-05-16T17:54:38Z" - content=""" -I've temporarily worked around this by updating the .info file for OSX to have the right version number. - -I think that my release process generally manages to avoid version skew, but not always. And it's most likely to happen for OSX since that autobuilder only runs once per day. -"""]] diff --git a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_8_2b2152844612d83f295a5de02f6ed3e7._comment b/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_8_2b2152844612d83f295a5de02f6ed3e7._comment deleted file mode 100644 index 9dc7257fa..000000000 --- a/doc/bugs/git-annex_auto_upgrade_is_redundant/comment_8_2b2152844612d83f295a5de02f6ed3e7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4" - nickname="Ovidiu" - subject="comment 8" - date="2014-05-16T18:00:18Z" - content=""" -So what do we as end-users do to get the latest version now? Re-download? -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3.mdwn b/doc/bugs/git-annex_broken_on_Android_4.3.mdwn deleted file mode 100644 index 4c1b356fb..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -As per [[install/Android/#comment-e218073735d67691a2c3f66cc53ca6ac]] and [[install/Android/#comment-29bd13ab9cb830ffcd7850b84fb111c8]] : - -git-annex is broken on Android 4.3; both on Nexus 4 and Nexus 7. - -> [[Fixed|done]]. A 4.3 build of the apk is now available. -> (Unfortunately the fix breaks support for older versions of Android, -> so two versions of the apk have to be built now.) --[[Joey]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_10_e47c073f1614f7b57f86acedeeb1cadc._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_10_e47c073f1614f7b57f86acedeeb1cadc._comment deleted file mode 100644 index 5d56dc84c..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_10_e47c073f1614f7b57f86acedeeb1cadc._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm7qEQF8yzbY0_PHq3QERHxUGuXmW6qw8o" - nickname="Anton" - subject="comment 10" - date="2013-11-10T22:10:49Z" - content=""" -I can confirm that the Hello World program works with the Nexus 7 2013, running Android 4.3. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_11_ce34578c45060b7c8b759efd1c1d8df8._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_11_ce34578c45060b7c8b759efd1c1d8df8._comment deleted file mode 100644 index d84a59b76..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_11_ce34578c45060b7c8b759efd1c1d8df8._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Hooray!" - date="2013-11-10T22:21:46Z" - content=""" -I have a Nexus 7 (2013) with 4.3 that I'll test it on---I expect that my test will be successful. - -I'll also run the test on my Nexus 5, running 4.4. - -Getting git-annex working on 4.3 was the last thing keeping me from being able to ditch Dropbox entirely. I'm so glad to hear there's some potential progress. - -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_12_75965395dc33046ce34ac5ba972b7d64._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_12_75965395dc33046ce34ac5ba972b7d64._comment deleted file mode 100644 index 3f520d7e4..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_12_75965395dc33046ce34ac5ba972b7d64._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 12" - date="2013-11-10T22:23:49Z" - content=""" -Full rebuild in progress (takes about 6 hours +- manual fixing). -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_13_f07bc76dd3c5580fc0855a33ae835c8d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_13_f07bc76dd3c5580fc0855a33ae835c8d._comment deleted file mode 100644 index f2a57f731..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_13_f07bc76dd3c5580fc0855a33ae835c8d._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Oh, and if a 4.3 device would be helpful..." - date="2013-11-10T22:28:48Z" - content=""" -I have Samsung Epic 4G (epic_mtd) that I'm no longer using and would be quite happy to send you---it's older, and slow, but it is at least currently supported by CyanogenMod, so it should be possible to install 10.2 milestone builds on it and at least do basic testing. - -Hell, if it would really facilitate Android support, I'd happily pick up something like a B&N Nook HD+ and send it to you---that should be similarly amenable to CM installs and testing. - -Though I will also understand if you don't necessarily want to have a bunch of superfluous hardware laying around. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_14_637c59becc68a1e4f60069d8873489ff._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_14_637c59becc68a1e4f60069d8873489ff._comment deleted file mode 100644 index 6336a3bd4..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_14_637c59becc68a1e4f60069d8873489ff._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Works on KitKat" - date="2013-11-10T23:15:28Z" - content=""" -I skipped testing on my Nexus 7, figuring that would be duplicative, and instead ran it on my Nexus 5, and it worked great. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_15_d80b87055f72873f5678a01d2630bea4._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_15_d80b87055f72873f5678a01d2630bea4._comment deleted file mode 100644 index 6bca41b3a..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_15_d80b87055f72873f5678a01d2630bea4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 15" - date="2013-11-11T04:34:21Z" - content=""" -6 hours later, and: <http://downloads.kitenet.net/git-annex/autobuild/android/git-annex.apk> - -testing appreciated! -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_16_57ac84868b223b30f005704eefa01b8d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_16_57ac84868b223b30f005704eefa01b8d._comment deleted file mode 100644 index 204845eb5..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_16_57ac84868b223b30f005704eefa01b8d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~subito" - nickname="subito" - subject="Nexus 5 Android 4.4" - date="2013-11-11T10:07:07Z" - content=""" -Does not work for me. Same error as in the original Bug report. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_17_a41f4d8a72c07ad770e6479e9b8c7f1d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_17_a41f4d8a72c07ad770e6479e9b8c7f1d._comment deleted file mode 100644 index 9712f5944..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_17_a41f4d8a72c07ad770e6479e9b8c7f1d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Same error as before, Nexus 5 and 7" - date="2013-11-11T13:06:17Z" - content=""" -Unfortunately, my experience mirrors subito's---same error as before on both 4.3 and 4.4. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_18_7d36637f11cda51de395303d5c1c6a3f._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_18_7d36637f11cda51de395303d5c1c6a3f._comment deleted file mode 100644 index 2dc32cf15..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_18_7d36637f11cda51de395303d5c1c6a3f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 18" - date="2013-11-11T13:27:49Z" - content=""" -Hmm, maybe the problem is caused by stripping the program? If so, this should fail the same way: <http://tmp.kitenet.net/hello.stripped> -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_19_c8609c3f7f62ae5427fd8c60bc9546ed._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_19_c8609c3f7f62ae5427fd8c60bc9546ed._comment deleted file mode 100644 index 2f22ad21c..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_19_c8609c3f7f62ae5427fd8c60bc9546ed._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Unfortunately, it would not appear that easy..." - date="2013-11-11T14:33:05Z" - content=""" -The stripped binary for hello worked fine. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_1_0ffb3833ce2c2e0320468dc9a09866d7._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_1_0ffb3833ce2c2e0320468dc9a09866d7._comment deleted file mode 100644 index 9b3b35c4b..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_1_0ffb3833ce2c2e0320468dc9a09866d7._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.21" - subject="comment 1" - date="2013-07-30T17:31:53Z" - content=""" -Given that the issue is it can't link against libc, it may need to be rebuilt with a newer version of the Android SDK and/or NDK. - -OTOH, for it to get as far as it does, the start.c has successfully run, using the system's libc. So perhaps this only affects Haskell binaries somehow? -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_20_0886bca6d0c6a9415a7794d256be2e9d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_20_0886bca6d0c6a9415a7794d256be2e9d._comment deleted file mode 100644 index 2b547d9a7..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_20_0886bca6d0c6a9415a7794d256be2e9d._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 20" - date="2013-11-11T16:23:11Z" - content=""" -To bisect the problem space further, in case the apk build machinery is at fault, here's a git-annex binary not included in an apk. (Run same as the hello world.) - -<http://tmp.kitenet.net/git-annex.bin> - -And here's a more minimal git-annex binary (trying to look identical to hello world from the linker's perspective, just a bit larger..). - -<http://tmp.kitenet.net/git-annex-min.bin> -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_21_2b39729f95c9c4bba620ecdd3d1558ed._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_21_2b39729f95c9c4bba620ecdd3d1558ed._comment deleted file mode 100644 index 551334819..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_21_2b39729f95c9c4bba620ecdd3d1558ed._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmqz6wCn-Q1vzrsHGvEJHOt_T5ZESilxhc" - nickname="Sören" - subject="Galaxy S4 Android 4.3" - date="2013-11-11T18:47:23Z" - content=""" -hello and hello.stripped both work here but the git-annex binaries don't (still the same error as in the bug report). -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_22_8d90d92951919aa70638b31e9248bec5._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_22_8d90d92951919aa70638b31e9248bec5._comment deleted file mode 100644 index e4937e0f8..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_22_8d90d92951919aa70638b31e9248bec5._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Both fail..." - date="2013-11-11T18:53:34Z" - content=""" -Same linking issue for both. - -I don't *think* it should make any difference at all, but to spare myself a little bit of typing on this soft keyboard, I'm using a small variation on your script; I'm sharing it so other testers can use it, too, and so someone can point out if I'm doing something wrong: - - D=/data/data/ga/androidterm/tmp/gatest - cp <file> $D - chmod +x $D - $D - -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_23_6398271f5cd9e94996202ef3bce6f6ed._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_23_6398271f5cd9e94996202ef3bce6f6ed._comment deleted file mode 100644 index 05cb634e6..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_23_6398271f5cd9e94996202ef3bce6f6ed._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 23" - date="2013-11-11T19:14:59Z" - content=""" -Script variation is ok. - -So, it's looking like perhaps a problem with the way cabal links the executable, which I notice is a two stage process, vs the way ghc links it with --make. - -To narrow down, here is hello built using cabal: - -<http://tmp.kitenet.net/hello-cabal> - -Here is git-annex built not using cabal: - -<http://tmp.kitenet.net/git-annex-byhand> - -(For my own reference, it's also built without WITH_CLIBS.) -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_24_c9e399833cc6235077161f490dfa866f._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_24_c9e399833cc6235077161f490dfa866f._comment deleted file mode 100644 index c8fea212b..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_24_c9e399833cc6235077161f490dfa866f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmqz6wCn-Q1vzrsHGvEJHOt_T5ZESilxhc" - nickname="Sören" - subject="comment 24" - date="2013-11-11T19:56:04Z" - content=""" -hello-cabal working, git-annex-byhand not. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_25_cf093737eefb2b99f6f0eac9bf3e74b3._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_25_cf093737eefb2b99f6f0eac9bf3e74b3._comment deleted file mode 100644 index e28a9508b..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_25_cf093737eefb2b99f6f0eac9bf3e74b3._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="I got the same results as Sören." - date="2013-11-11T20:37:08Z" - content=""" -cabal doesn't seem to be the culprit. - -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_26_c122ce53175fc9e0e114a8acd2385c0d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_26_c122ce53175fc9e0e114a8acd2385c0d._comment deleted file mode 100644 index 1c72cd27b..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_26_c122ce53175fc9e0e114a8acd2385c0d._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="finally getting debugger spun up" - date="2013-11-12T01:08:24Z" - content=""" -<https://code.google.com/p/android/issues/detail?id=28598> seems relevant (and the patches to fix it seem likely to have led to the linker rejecting this). - -So I can probably stop torturing your soft keyboards. I need a binary where `arm-linux-androideabi-4.8/bin/arm-linux-androideabi-readelf -r` does not contain `R_ARM_COPY`. Checking against the binaries so far, this consistently matches the test results, all the git-annex binaries have: - -<pre> - Offset Info Type Sym.Value Sym. Name -011d05f0 00004e14 R_ARM_COPY 011d05f0 environ -</pre> - -(Which is itself interesting; I've had to work around some problems with the haskell port not supporting getting the environment (Annex.Branch.withIndex). Possibly because it was copied and the linker screwed that up? <https://github.com/neurocyte/ghc-android/issues/7>) - -Ok, here's a binary that meets those criteria. Obtained by passing -z nocopyreloc to the gold linker (ghc options -optl-z -optlnocopyreloc) - -<http://tmp.kitenet.net/git-annex-nocopy> - -Also, here's a hello world binary that *should* fail. It attempts to read and print the environment, and has the same `R_ARM_COPY` relocation. - -<http://tmp.kitenet.net/hello-env-copy> - -And, here's a hello world binary that *might* successfully print out the full environment (like `set` does). If it does, I can also remove the ugly hack in Annex.Branch.withIndex. Which would be an unexpected reward. - -<http://tmp.kitenet.net/hello-env-nocopy> -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_27_237e41e61781bb058f5fd39362a904e4._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_27_237e41e61781bb058f5fd39362a904e4._comment deleted file mode 100644 index dd911955a..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_27_237e41e61781bb058f5fd39362a904e4._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="nocopy variants work!" - date="2013-11-12T03:17:09Z" - content=""" -I tested both the hello-env-nocopy and the git-annex-nocopy binaries successfully. hello-env-copy failed as you predicted. - -Yay! -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_28_97f423a41ee9d2d74291594fae20dd4e._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_28_97f423a41ee9d2d74291594fae20dd4e._comment deleted file mode 100644 index 6341aae80..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_28_97f423a41ee9d2d74291594fae20dd4e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 28" - date="2013-11-12T03:58:56Z" - content=""" -This fix is now in place in the android autobuilds. - -Just to be sure, hello-env-nocopy managed to print out multiple environment variables? -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_29_7b3fbe7e38f637fcea511441ac243d93._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_29_7b3fbe7e38f637fcea511441ac243d93._comment deleted file mode 100644 index 1cd4c356f..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_29_7b3fbe7e38f637fcea511441ac243d93._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmqz6wCn-Q1vzrsHGvEJHOt_T5ZESilxhc" - nickname="Sören" - subject="APK now works too" - date="2013-11-12T09:10:49Z" - content=""" -I got the same results as Michael. The output of hello-nocopy is a longer list of environment variables. -Even better, the apk from the autobuilder now seems to work fine as well, including the webapp. -Great work! Thanks for digging into this. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_2_53e2d095b2501844cadec910de286814._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_2_53e2d095b2501844cadec910de286814._comment deleted file mode 100644 index 3d5003504..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_2_53e2d095b2501844cadec910de286814._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="173.162.44.162" - subject="comment 2" - date="2013-08-28T13:54:00Z" - content=""" -On a stock Nexus 7 running the latest OS (4.3), this is still the case as of release 4.20130827. - - Falling back to hardcoded app location; cannot find expected files in /data/app-lib - git annex webapp - u0_a18@grouper:/sdcard/git-annex.home $ git annex webapp - CANNOT LINK EXECUTABLE: git-annex invalid R_ARM_COPY relocation against DT_SYMBOLIC shared library libc.so (built with -Bsymbolic?) - 1|u0_a18@grouper:/sdcard/git-annex.home $ -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_30_26c04584c3c6dacf59e1b6c82042c97c._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_30_26c04584c3c6dacf59e1b6c82042c97c._comment deleted file mode 100644 index 3409b9c4a..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_30_26c04584c3c6dacf59e1b6c82042c97c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnegApaT6kTI0Gxy9SNmI9Og-k_fC_aS7Y" - nickname="Michael Alan" - subject="Yep, the env was printed" - date="2013-11-12T10:18:56Z" - content=""" -I would recognize the output of a Show instance anywhere. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_3_ddc9cbae1a721400a9acf2153e18f4f0._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_3_ddc9cbae1a721400a9acf2153e18f4f0._comment deleted file mode 100644 index 14eed81c9..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_3_ddc9cbae1a721400a9acf2153e18f4f0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkgedYqmQb4dJU7UdVuRLwsQE-KlKVrFto" - nickname="Chungy" - subject="comment 3" - date="2013-09-01T00:25:15Z" - content=""" -Just confirming the bug on my Verizon Galaxy S 3 with CyanogenMod 10.2 (Android 4.3), it's not Nexus-specific. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_4_593235735e32238094121b1f79355bbd._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_4_593235735e32238094121b1f79355bbd._comment deleted file mode 100644 index ab721064a..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_4_593235735e32238094121b1f79355bbd._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawntVnR-Z5ghYInvsElbDeADPSuCsF18iTY" - nickname="Thomas" - subject="comment 4" - date="2013-09-01T20:02:59Z" - content=""" -Yet another confirmation of the bug on a Samsung Galaxy Note running 4.3 via Cyanogenmod as well. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_5_f806fd5930e90920db24456297465bae._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_5_f806fd5930e90920db24456297465bae._comment deleted file mode 100644 index cfb75bdd8..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_5_f806fd5930e90920db24456297465bae._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://edheil.wordpress.com/" - ip="173.162.44.162" - subject="comment 5" - date="2013-09-03T14:38:51Z" - content=""" -If there's anything we can do to help debug this, please let us know. Have just started using git-annex on android recently & would love to have it on all my devices. - -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_6_5741b6a5997328fdcd5cc99f841b18d3._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_6_5741b6a5997328fdcd5cc99f841b18d3._comment deleted file mode 100644 index 438e00454..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_6_5741b6a5997328fdcd5cc99f841b18d3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnRai_qFYPVvEgC6i1nlM1bh-C__jbhqS0" - nickname="Matthew" - subject="Definitely broken Galaxy Nexus GSM 4.3" - date="2013-09-12T11:11:34Z" - content=""" -Definitely broken in 4.3, stock Galaxy Nexus GSM \"maguro\" release `2013-09-09 12:46` -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_7_3e0d9949dd810069af0b8076807e5924._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_7_3e0d9949dd810069af0b8076807e5924._comment deleted file mode 100644 index 4a3819472..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_7_3e0d9949dd810069af0b8076807e5924._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawknwkXgi8SnK4QT32ANl3GMKvFLyQGeHqo" - nickname="Florian" - subject="comment 7" - date="2013-10-08T16:18:07Z" - content=""" -Any comment from on this from one of the maintainers would be great. Apparently this was not fixed in the latest (2013-10-02 18:46) build. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_8_f58897eff6b4693f0c73474ccfe6e733._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_8_f58897eff6b4693f0c73474ccfe6e733._comment deleted file mode 100644 index 52326b8e2..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_8_f58897eff6b4693f0c73474ccfe6e733._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA" - nickname="Joe" - subject="Samsung Galaxy S4 also affected" - date="2013-11-09T02:47:54Z" - content=""" -Verizon just pushed out 4.3 to Samsung Galaxy S4 devices. This issue is affecting me now too. -"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3/comment_9_ddba87b2f20d8a63f7b8ebdb9bd13515._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_9_ddba87b2f20d8a63f7b8ebdb9bd13515._comment deleted file mode 100644 index 015efd7ce..000000000 --- a/doc/bugs/git-annex_broken_on_Android_4.3/comment_9_ddba87b2f20d8a63f7b8ebdb9bd13515._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 9" - date="2013-11-10T20:12:47Z" - content=""" -I have finally managed to get ghc to build with the newest version of the NDK. I hope this means it will make binaries that work with 4.3, but I don't have a device to test. - -Here is a hello world program built with it: -<http://tmp.kitenet.net/hello> - -After downloading it to an Android device, you can test it by opening the -git-annex terminal, and running: `D=/data/data/ga.androidterm/tmp; cp hello $D; chmod +x $D/hello; $D/hello` - -Tested working on android 4.0.4 - -Also, I have filed a bug upstream about this at <https://github.com/neurocyte/ghc-android/issues/23> -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn deleted file mode 100644 index 2e86f488d..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -### Please describe the problem. - -umask is 022 on both hosts -If one does ls -lL on source repo, the files are shown 644. - -Now, "git annex get" from a clone done over ssh generally preserves 644 ... except if the transfer (rsync) is interrupted, and then resumed. -In fact, looks like the temp files in .git/annex/tmp have the og+r bits cleared during the resumed transfer. - -So this is inconsistent: I don't see why permissions should be different, depending whether or not there was an interruption in the transfer. -Plus, og+r permissions can actually be important for setups like serving contents using Samba. - -### What steps will reproduce the problem? - - cd dir1 - git init - git annex init - touch a - truncate -s 10G b - git annex add . - git commit -m 'new' - - git clone localhost:/path/to/dir1 dir2 - cd dir2 - git annex get - ctrl^c - git annex get - ls -lL - ... see different perms - - - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140411-gda795e0 -Linux - -### 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. -"""]] - -> [[fixed|done]]; brought back -p on non-crippled file systems --[[Joey]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_1_0fc5c7251ead7a0fbbcd357a8bc53f05._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_1_0fc5c7251ead7a0fbbcd357a8bc53f05._comment deleted file mode 100644 index 48069eebd..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_1_0fc5c7251ead7a0fbbcd357a8bc53f05._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 1" - date="2014-04-17T18:32:40Z" - content=""" -(I think you forgot to mention you were using direct mode.) - -Like git, git-annex does not preserve file permissions. If you want to ensure that a group or everyone can read file in a git repository, you have to use the core.sharedRepository git configuration. git-annex will also honor that. - -git-annex will try to preserve the execute bit, since git does support that single permission bit. But even this cannot be guaranteed. (Eg, when using special remotes which have no concept of file permissions.) - -Interrupting rsync and resuming it does cause rsync to not transfer through permissions. This is rsync's normal behavior when not using -p. git-annex used to use rsync -p to preserve whatever file permissions there were. However, <http://bugs.debian.org/700282>, and then [[!commit f92eaf631509d02491c1b0ebfbb15145f80df797]]. - -It looks like I could preserve the execute bit across interrupt and resume by using rsync's --executability option. - -Or, I could use the -p when git-annex is running in a non-crippled filesystem. -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment deleted file mode 100644 index f32a4a70f..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_2_992c1a51d0300bd676cb431688efa524._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 2" - date="2014-04-17T21:19:10Z" - content=""" -Hi Joey, - -In fact, this is indirect mode on Linux, ext4. -I'm less worried about preserving +x mode (though I can see why it would be useful). Here I'm referring to plain \"group\" and \"other\" read permissions being cleared. - -And I just did a test with a standalone rsync, using rsync -P localhost:file file2 and interrupting it, the partial (and final after resume) file2 still is 644 (and not 600 like in git-annex case). -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_3_3001a11839eff6a4c3a9f12096b29704._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_3_3001a11839eff6a4c3a9f12096b29704._comment deleted file mode 100644 index b365baa75..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_3_3001a11839eff6a4c3a9f12096b29704._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 3" - date="2014-04-17T21:19:59Z" - content=""" -I think -p on non-crippled does make sense, and -E does too for crippled. -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_4_a13abb45b9a94d275177641db0538765._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_4_a13abb45b9a94d275177641db0538765._comment deleted file mode 100644 index 919adc2e7..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_4_a13abb45b9a94d275177641db0538765._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 4" - date="2014-04-17T21:22:16Z" - content=""" -s/and not 600/and not 400/ - -In my ideal case I'd like to see indirect git-annex to set files to 444 (if umask in destination doesn't prevent that otherwise). -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_5_faac2d48950307ce245f0da501ace730._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_5_faac2d48950307ce245f0da501ace730._comment deleted file mode 100644 index 57db29c8a..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_5_faac2d48950307ce245f0da501ace730._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 5" - date="2014-04-17T21:32:35Z" - content=""" -core.sharedRepository does fix things here. Thanks Joey! -I'm all set for my use case. -"""]] diff --git a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_6_7df03eee7d5dc5a7ed0c9abef5053788._comment b/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_6_7df03eee7d5dc5a7ed0c9abef5053788._comment deleted file mode 100644 index bfed27fb4..000000000 --- a/doc/bugs/git-annex_clears_files__39___og+r_permissions_when_rsync_transfer_is_interrupted_and_resumed/comment_6_7df03eee7d5dc5a7ed0c9abef5053788._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 6" - date="2014-04-18T18:32:22Z" - content=""" -One issue (bug) still remains: git annex does respect - -sharedRepository = world - -but not - -sharedRepository = 0644 - -In the later case, with indirect mode, files end up with 400 permissions. - -"""]] diff --git a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__.mdwn b/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__.mdwn deleted file mode 100644 index 1081b7acf..000000000 --- a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__.mdwn +++ /dev/null @@ -1,112 +0,0 @@ -### Please describe the problem. - -When using "`git annex addurl --file`" with an ftp url, the committed -file is deleted after dropping the contents with --force (because -git-annex can't determine if the ftp server contains a valid copy) and -executing "`git annex get`". It's the "`git annex get`" command that -deletes the file. - -This does not happen when using an http url. - -### What steps will reproduce the problem? - -`git clone https://gist.github.com/sunny256/24f6c29645efd0aab4d9` - -and execute the bash script `runme`. There's more info in a long comment -there, plus various flags you can enable/disable to test under different -conditions. - -### What version of git-annex are you using? On what operating system? - -Using the newest git-annex from <https://downloads.kitenet.net/.git/> in -directory git-annex/linux/current/, 5.20150420-gb0ebb23. - -Have tested with versions way back to v5.20131221, they all behave the -same. - -Using Debian GNU/Linux 7.8 (wheezy) on x86_64 with brand new git 2.4.0. - -### 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 - -$ ./runme - -================== git init ================== -Initialized empty Git repository in /home/sunny/src/git/ga-bug/tmpdirawedsfkn/.git/ - -================== git annex init ================== -init ok -(recording state in git...) - -================== git commit, empty start commit ================== -[master (root-commit) 6d5d623] Empty startcommit - -================== git annex addurl ================== -addurl README (downloading ftp://ftp.funet.fi/pub/Linux/mirrors/debian/README ...) ---2015-05-02 03:28:59-- ftp://ftp.funet.fi/pub/Linux/mirrors/debian/README - => '.git/annex/tmp/URL--ftp&c%%ftp.funet.fi%pub%Linux%mirrors%debian%README' -Resolving ftp.funet.fi (ftp.funet.fi)... 193.166.3.2, 2001:708:10:9::20:2 -Connecting to ftp.funet.fi (ftp.funet.fi)|193.166.3.2|:21... connected. -Logging in as anonymous ... Logged in! -==> SYST ... done. ==> PWD ... done. -==> TYPE I ... done. ==> CWD (1) /pub/Linux/mirrors/debian ... done. -==> SIZE README ... 1495 -==> PASV ... done. ==> RETR README ... done. -Length: 1495 (1.5K) (unauthoritative) - -100%[================================================>] 1,495 --.-K/s in 0.01s - -2015-05-02 03:29:00 (125 KB/s) - '.git/annex/tmp/URL--ftp&c%%ftp.funet.fi%pub%Linux%mirrors%debian%README' saved [1495] - -ok -(recording state in git...) - -================== git commit, add README ================== -[master 264d597] Add README - 1 file changed, 1 insertion(+) - create mode 120000 README - -================== git annex drop --force ================== -drop README ok -(recording state in git...) - -================== git annex get ================== -get README (from web...) ---2015-05-02 03:29:00-- ftp://ftp.funet.fi/pub/Linux/mirrors/debian/README - => '.git/annex/tmp/SHA256-s1495--8822780b87a880ca9956ac108812557044618859cecb07df488df57e8134e34f' -Resolving ftp.funet.fi (ftp.funet.fi)... 193.166.3.2, 2001:708:10:9::20:2 -Connecting to ftp.funet.fi (ftp.funet.fi)|193.166.3.2|:21... connected. -Logging in as anonymous ... Logged in! -==> SYST ... done. ==> PWD ... done. -==> TYPE I ... done. ==> CWD (1) /pub/Linux/mirrors/debian ... done. -==> SIZE README ... 1495 -==> PASV ... done. ==> RETR README ... done. -Length: 1495 (1.5K) (unauthoritative) - -100%[================================================>] 1,495 --.-K/s in 0s - -2015-05-02 03:29:02 (73.1 MB/s) - '.git/annex/tmp/SHA256-s1495--8822780b87a880ca9956ac108812557044618859cecb07df488df57e8134e34f' saved [1495] - -ok -(recording state in git...) - -================== ls -l ================== -total 0 - -README is gone, should not happen - -Reached the end -$ - -# End of transcript or log. -"""]] - -> workaround in place; [[done]] --[[Joey]] - -> Also, fixed it to allow dropping the file if the ftp server seems -> to reply with a successful result (it's replying with 350, which is not -> unambiguously good, but since curl is able to get the right file length, -> the file is presumably still on the ftp server. --[[Joey]] diff --git a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_1_dca81d5db9a966fc992ed28bb3c2a242._comment b/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_1_dca81d5db9a966fc992ed28bb3c2a242._comment deleted file mode 100644 index 65ebab1f2..000000000 --- a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_1_dca81d5db9a966fc992ed28bb3c2a242._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-05-05T17:11:38Z" - content=""" -Thanks for a great bug report! - -Unfortunately, this turns out to be a bug in wget, as shown by this transcript: - - joey@darkstar:~/tmp/y>ls - README@ - joey@darkstar:~/tmp/y>wget -q --show-progress --clobber -c -O .git/annex/tmp/SHA256E-s1495--8822780b87a880ca9956ac108812557044618859cecb07df488df57e8134e34f ftp://ftp.funet.fi/pub/Linux/mirrors/debian/README --user-agent git-annex/5.20150505-gcdb212f - joey@darkstar:~/tmp/y>ls - joey@darkstar:~/tmp/y> - -I have filed a bug report on wget <http://bugs.debian.org/784348>, -and I guess I'll try to work around it in git-annex by running wget -inside an empty temp directory. -"""]] diff --git a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment b/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment deleted file mode 100644 index 8c757b8a3..000000000 --- a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://sunny256.wordpress.com/" - nickname="sunny256" - subject="Thanks" - date="2015-05-07T14:20:49Z" - content=""" -Thank you for looking into this and coming up with a fix. Awesome. :) -"""]] diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin.mdwn b/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin.mdwn deleted file mode 100644 index 8e205e1e9..000000000 --- a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. - - -### What steps will reproduce the problem? - -$ git init -Initialized empty Git repository in /cygdrive/c/Temp/.git/ - -$ git-annex init -init - Detected a filesystem without fifo support. - - Disabling ssh connection caching. - - Detected a crippled filesystem. - - Disabling core.symlinks. - - Enabling direct mode. -fatal: You are on a branch yet to be born -git-annex.exe: git [Param "checkout",Param "-q",Param "-B",Param "annex/direct/master"] failed - -$ git checkout -B annex/direct/master -fatal: You are on a branch yet to be born - -### What version of git-annex are you using? On what operating system? - -Running under cygwin bash - -$ git --version -git version 1.7.9 - -$ git-annex version -git-annex version: 5.20140421-g78d6aa1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -> [[fixed|done]]; documented the needed version of git on the windows -> install page. --[[Joey]] diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_1_24d626923403b097f57bc3d3a8c5befa._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_1_24d626923403b097f57bc3d3a8c5befa._comment deleted file mode 100644 index 8610061d5..000000000 --- a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_1_24d626923403b097f57bc3d3a8c5befa._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.114" - subject="comment 1" - date="2014-04-27T00:13:49Z" - content=""" -This looks similar to [[bugs/git-annex_fails_to_initialize_under_Windows]], which was solved by upgrading to a newer version of msysgit. - -git 1.7.9 is extremely old (years). Probably the empty commit that is done when switching to direct mode, precisely to avoid this problem, fails, because the pre-built git-annex for windows is targeting a modern version of git, from msysgit. -"""]] diff --git a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_2_32a74f078f45ee069a7d386734e379e2._comment b/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_2_32a74f078f45ee069a7d386734e379e2._comment deleted file mode 100644 index bafaaa3fd..000000000 --- a/doc/bugs/git-annex_fails_to_initialize_under_Windows_with_cygwin/comment_2_32a74f078f45ee069a7d386734e379e2._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkYmMFDdf3GJ9Oba6NCVkzGc4JyB9WavMs" - nickname="Xinruo" - subject="comment 2" - date="2014-04-27T11:58:13Z" - content=""" -OK installing git 1.9.2 from msysgit solves the problem. I thought I have read somewhere that you used cygwin for Windows development and didn't know that git from cygwin is too old. Thanks for the help! -"""]] diff --git a/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response.mdwn b/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response.mdwn deleted file mode 100644 index f18d7a522..000000000 --- a/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -### Please describe the problem. - -During a git annex fsck --fast --from <someexternalremote>, any CHECKPRESENT-SUCCESS responses are considered failures: - - fsck file - failed to download file from remote - failed - (recording state in git...) - git-annex: fsck: 1 failed - -It doesn't appear that the external protocol is being violated in any way; it occurs both with my special external (https://git.encryptio.com/slime/blob/refs/heads/master:/misc/git-annex-remote-slime/main.go) and with the example external remote. Making these dump their IO to stderr shows they're behaving correctly, as far as I can tell. - -`git annex testremote` passes on these remotes too, so it's not catching the issue (though it probably should.) - -These implementations used to work fine (~6mo ago? not sure); I haven't been able to get git-annex to build (cabal woes), so I can't bisect it myself. - -### What steps will reproduce the problem? - -With https://git-annex.branchable.com/special_remotes/external/example.sh/ installed as "git-annex-remote-externaltest", this script shows the issue: - -[[!format sh """ -#!/bin/sh -set -e - -[ -e "annex-test-dirs/repo/.git/annex/objects" ] && ( - find "annex-test-dirs/repo/.git/annex/objects" -type f -exec chmod 0644 {} \; - find "annex-test-dirs/repo/.git/annex/objects" -type d -exec chmod 0755 {} \; -) - -rm -rf annex-test-dirs -mkdir -p annex-test-dirs/{repo,data} - -cd annex-test-dirs/repo -git init -git annex init -MYPASSWORD=a MYLOGIN=b git annex initremote ext type=external encryption=none externaltype=externaltest directory="$(pwd)/../data" - -echo "data" > file -git annex add file -git commit -m message - -git annex copy --to ext - -# this works: -git annex fsck --from ext - -# but this incorrectly fails and marks the file "not present": -git annex fsck --fast --from ext -"""]] - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20150420-gb0ebb23, from the linux standalone tarball, on linux. - -> Upgrade, this was fixed earlier this week, in [[!commit -> cfbeb1e7b74aa9759bd62b342e80869de582f10d]]; [[done]] afaik --[[Joey]] diff --git a/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response/comment_1_25f456784172f591f8a587f8106d9793._comment b/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response/comment_1_25f456784172f591f8a587f8106d9793._comment deleted file mode 100644 index bc5a787e8..000000000 --- a/doc/bugs/git-annex_fails_to_parse_external_remotes__39_____34__CHECKPRESENT-SUCCESS__34___response/comment_1_25f456784172f591f8a587f8106d9793._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="encryptio" - subject="comment 1" - date="2015-05-31T13:54:30Z" - content=""" -Confirmed fixed at least as of 5.20150528-gedaacae. -"""]] diff --git a/doc/bugs/git-annex_fails_to_start_when_nautilus_script_directory_is_missing.mdwn b/doc/bugs/git-annex_fails_to_start_when_nautilus_script_directory_is_missing.mdwn deleted file mode 100644 index e3441489d..000000000 --- a/doc/bugs/git-annex_fails_to_start_when_nautilus_script_directory_is_missing.mdwn +++ /dev/null @@ -1,49 +0,0 @@ -### Please describe the problem. -Starting the webapp fails if the Nautilus scripts directory doesn't exist. - -### What steps will reproduce the problem? - -[[!format sh """ -$ mv ~/.local/share/nautilus ~/.local/share/nautilus.bak -$ git-annex webapp - -git-annex: /home/brunksn/.local/share/nautilus/scripts/git-annex get: openFile: does not exist (No such file or directory) -failed -git-annex: webapp: 1 failed -"""]] - -### What version of git-annex are you using? On what operating system? -5.20140402, Debian testing - -### Please provide any additional information below. - -Workaround for users without Gnome/Nautilus: -[[!format sh """ -$ mkdir -p ~/.local/share/nautilus -"""]] - -It seems git-annex tries to create the scripts without checking if the actually directory exists. One solution would be to just create it if it doesn't exist or to only write the scripts if it exists already. Patch for the latter below. Works for me but my haskell knowledge is still very limited. - -By the way, what is the preferred way to contribute patches for git-annex? I couldn't find any information about that on the website. - -[[!format diff """ -diff --git a/Assistant/Install.hs b/Assistant/Install.hs -index 4d02c0e..883ca48 100644 ---- a/Assistant/Install.hs -+++ b/Assistant/Install.hs -@@ -87,8 +87,9 @@ installNautilus :: FilePath -> IO () - #ifdef linux_HOST_OS - installNautilus program = do - scriptdir <- (\d -> d </> "nautilus" </> "scripts") <$> userDataDir -- genscript scriptdir "get" -- genscript scriptdir "drop" -+ whenM (doesDirectoryExist scriptdir) $ do -+ genscript scriptdir "get" -+ genscript scriptdir "drop" - where - genscript scriptdir action = - installscript (scriptdir </> scriptname action) $ unlines -"""]] - -> [[applied|done]]. thanks! That's a fine way to send a small patch, or -> make a git branch somewhere for a larger one. --[[Joey]] diff --git a/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups.mdwn b/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups.mdwn deleted file mode 100644 index 5d8f863ec..000000000 --- a/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -Running `git annex group here manual` and `git annex group here client` results in the nonsensical group of "manual client". Should there be checking for the reserved "standard" group words? - -The intention from the webapp and docs reads as though these groups should be mutually exclusive. - -Also it would be nice if `git annex group here` returned the list of groups (I put this as a wishlist item but think it perhaps warrants a bug mention). - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[done]] per my comment. (Please comment if you disagree!) --[[Joey]] diff --git a/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment b/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment deleted file mode 100644 index 154bcd12e..000000000 --- a/doc/bugs/git-annex_group_remote_allows_bad_settings_with_standard_groups/comment_1_b3090201e90a78e049cf299fc322d60e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-05-16T18:34:49Z" - content=""" -You can get the same effect by running `git annex vicfg` in 2 repositories at the same time, and adding different groups. When the repositories sync and merge, things end up in 2 groups. - -So, this is something that git-annex has to deal with being done, even if the configuration does not make sense. It deals with it by treating such a configuration the same as if the repository was in no groups, as far as preferred content is concerned. - -So, I don't see much point in adding configuration time checks, since they'd not catch all ways this can happen. -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory.mdwn b/doc/bugs/git-annex_on_NAS_eats_all_memory.mdwn deleted file mode 100644 index c1777223f..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. - -"Git annex sync" stopped working when syncing my NAS to my Laptop, it just eats up all the memory on the NAS without any result. When running the debug mode I found out that it stops working when it tries to run "git-annex-shell 'configlist' 'mygitannexfolder'". -That's the first command to be run on the NAS over ssh. - -I traced the problem down and the following command also won't work without any output just eating up all memory: -ssh myuser@mynas "git-annex-shell 'configlist' 'mygitannexfolder'" - -But when I log in to the NAS and run the git-annex-shell script inside the .ssh folder with exactly the same command, it works perfectly and returns the uuid and so on. - -### What steps will reproduce the problem? -Execute on PC (doesn't work, just uses all memory and crashes): ssh myuser@mynas "git-annex-shell 'configlist' 'mygitannexfolder'" -Execute on NAS (should work): ./.ssh/git-annex-shell "git-annex-shell 'configlist' 'mygitannexfolder'" - - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140412ubuntu1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -and the current bundle on the NAS - -### 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. -"""]] - -> Went ahead with setting LOCPATH=/dev/null in runshell, so it won't -> run into whatever problem with the locales is causing it to hit this GHC -> bug. [[done]] (I hope) --[[Joey]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_10_10bbc2181876875d5e0c824c3eb3d164._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_10_10bbc2181876875d5e0c824c3eb3d164._comment deleted file mode 100644 index dc3f12cd3..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_10_10bbc2181876875d5e0c824c3eb3d164._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=c - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 10" - date="2015-02-21T20:46:22Z" - content=""" -Could install gconv and adjust the paths so that gconv-modules is found when running sync per ssh. -new Strace at the point of interest: -open(\"/usr/lib/arm-linux-gnueabi/gconv/gconv-modules.cache\", O_RDONLY) = -1 ENOENT (No such file or directory) -open(\"/usr/lib/arm-linux-gnueabi/gconv/gconv-modules\", O_RDONLY|0x80000) = 8 -fcntl64(8, F_GETFD) = 0x1 (flags FD_CLOEXEC) -fstat64(8, {st_mode=S_IFREG|0644, st_size=56368, ...}) = 0 -mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2ab6b000 -read(8, \"# GNU libc iconv configuration.\n\"..., 4096) = 4096 -read(8, \"B1.002//\nalias\tJS//\t\t\tJUS_I.B1.0\"..., 4096) = 4096 -read(8, \"59-3\t1\nmodule\tINTERNAL\t\tISO-8859\"..., 4096) = 4096 -read(8, \"859-14//\nalias\tISO-IR-199//\t\tISO\"..., 4096) = 4096 -read(8, \"CDIC-DK-NO-A//\tEBCDIC-DK-NO-A\t1\n\"..., 4096) = 4096 -read(8, \"\t\tIBM281//\t\tIBM281\t\t1\n\n#\tfrom\t\t\t\"..., 4096) = 4096 -read(8, \"\tIBM863\t\t1\n\n#\tfrom\t\t\tto\t\t\tmodule\"..., 4096) = 4096 -read(8, \"\tmodule\t\tcost\nalias\tIBM-939//\t\tI\"..., 4096) = 4096 -read(8, \"\t\t\tmodule\t\tcost\nalias\tEUCCN//\t\t\t\"..., 4096) = 4096 -read(8, \"CN//\t\tISO-2022-CN\t1\n\n#\tfrom\t\t\tto\"..., 4096) = 4096 -read(8, \"INTERNAL\t\tISO_5427-EXT//\t\tISO_54\"..., 4096) = 4096 -read(8, \"e\t\tcost\nmodule\tARMSCII-8//\t\tINTE\"..., 4096) = 4096 -read(8, \"2//\nmodule\tIBM1112//\t\tINTERNAL\t\t\"..., 4096) = 4096 -read(8, \"\tIBM9448//\nalias\tCP9448//\t\tIBM94\"..., 4096) = 3120 -read(8, \"\", 4096) = 0 -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_11_2756bfd050bec6a47818e7fb0df05d56._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_11_2756bfd050bec6a47818e7fb0df05d56._comment deleted file mode 100644 index 60d49264a..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_11_2756bfd050bec6a47818e7fb0df05d56._comment +++ /dev/null @@ -1,42 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 11" - date="2015-02-22T01:26:28Z" - content=""" -it seems gconv-modules is parsed and afterwards UTF-32.so is selected for encoding translation. But why? -My locale settings: -LANG=en_US.UTF-8 -LANGUAGE=en_US -LC_CTYPE=\"en_US.UTF-8\" -LC_NUMERIC=\"en_US.UTF-8\" -LC_TIME=\"en_US.UTF-8\" -LC_COLLATE=\"en_US.UTF-8\" -LC_MONETARY=\"en_US.UTF-8\" -LC_MESSAGES=\"en_US.UTF-8\" -LC_PAPER=\"en_US.UTF-8\" -LC_NAME=\"en_US.UTF-8\" -LC_ADDRESS=\"en_US.UTF-8\" -LC_TELEPHONE=\"en_US.UTF-8\" -LC_MEASUREMENT=\"en_US.UTF-8\" -LC_IDENTIFICATION=\"en_US.UTF-8\" -LC_ALL= - - -and on my nas: -LANG=en_US.utf8 -LC_CTYPE=\"en_US.utf8\" -LC_NUMERIC=\"en_US.utf8\" -LC_TIME=\"en_US.utf8\" -LC_COLLATE=\"en_US.utf8\" -LC_MONETARY=\"en_US.utf8\" -LC_MESSAGES=\"en_US.utf8\" -LC_PAPER=\"en_US.utf8\" -LC_NAME=\"en_US.utf8\" -LC_ADDRESS=\"en_US.utf8\" -LC_TELEPHONE=\"en_US.utf8\" -LC_MEASUREMENT=\"en_US.utf8\" -LC_IDENTIFICATION=\"en_US.utf8\" -LC_ALL=en_US.utf8 - -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_12_0e1cea9050c4f84d0fb4398fc8342fb4._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_12_0e1cea9050c4f84d0fb4398fc8342fb4._comment deleted file mode 100644 index 399a0bb87..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_12_0e1cea9050c4f84d0fb4398fc8342fb4._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 12" - date="2015-02-22T01:47:36Z" - content=""" -Approaching...: - -added exec locale inside runshell and now I get this error when running per ssh (but not when running on nas!!!) - -+ exec locale -fatal: protocol error: bad line length character: LANG -failed - -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_4165ed1d7381c6311740d57a1ef74086._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_4165ed1d7381c6311740d57a1ef74086._comment deleted file mode 100644 index b2dc79df4..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_4165ed1d7381c6311740d57a1ef74086._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 14""" - date="2015-02-25T17:02:44Z" - content=""" -Nice job debugging. - -runshell sets `GCONV_PATH` to a copy of the gconv directory that is -included in the standalone bundle. The bundle does not include a copy -of /usr/lib/locale/locale-archive, and looking at the glibc source, -even if I included one, it's hard-coded to use that path for the file. - -Hmm, it looks like setting LOCPATH to anything will prevent glibc from -trying to use the locale-archive file. (Normally it is /usr/lib/locale/) - -Or, it could force LANG=C, or unset LANG, which in my tests, both -prevent any locale files being opened at all. - -Your NAS seems to have a default locale, in the interactive shell, -of "en_US.utf8", which I guess is not being propigated via ssh's -SendEnv from the host you ssh in from, since that host has a -different "en_US.UTF-8". I wonder what the locale is set to when sshing -into the NAS noninteractively? Ie, output of "ssh $nas locale" -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_7f5ead46834296a9d72860ee677bdf88._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_7f5ead46834296a9d72860ee677bdf88._comment deleted file mode 100644 index 4a0318e60..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_14_7f5ead46834296a9d72860ee677bdf88._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 14" - date="2015-02-22T02:03:59Z" - content=""" -Added \"export LANG=en_US.utf8\" to runshell and now it works - fuck yeah! -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_1_0201600e27f38c5d8ee3774a827cc7a9._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_1_0201600e27f38c5d8ee3774a827cc7a9._comment deleted file mode 100644 index 7ef80df74..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_1_0201600e27f38c5d8ee3774a827cc7a9._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-10T16:04:09Z" - content=""" -What kind of NAS is it, and how did you install git-annex? In particular, -how did you arrange for git-annex-shell to be in PATH when sshing into the -NAS? - -My guess is that you have done something that is causing git-annex-shell to -not be run with the versions of libraries it needs. Normally its wrapper -script sets this up. -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_3_70ae89522c001bbe2aa10531e66423be._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_3_70ae89522c001bbe2aa10531e66423be._comment deleted file mode 100644 index b1d810d58..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_3_70ae89522c001bbe2aa10531e66423be._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 3" - date="2015-02-11T16:22:58Z" - content=""" -git-annex-shell-cgit-annex-shell doesn't even exist in git-annex-shell - -when I run runshell directly being logged in per ssh, it's the same command but sh/sh is run instead of git-annex-shell/git-annex-shell-cgit-annex-shell but I don't know how the shell to be run is selected -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment deleted file mode 100644 index dc9c1ce1b..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_3b226c7ce28f1caee2d5e568d91c96bc._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-02-11T16:48:58Z" - content=""" -You seem to have catted /proc/pid/cmdline, so the parameters are all -mashed together without the separating `\0` being visible. Not the best way -to examine a process. Use `ps`. - -It may be that the --library-path parameter is too long and is being -truncated. That's what appears to be the case when it ends at -"/shimmed/git-annex-shell/git-annex-shell-c". - -However, Linux's command-line length limits are much much longer than this -command line, so it shouldn't be truncated. And, I don't know why it would -only be truncated when the script is called by ssh. - -I suggest that you edit `git-annex.linux/git-annex-shell` and -`git-annex.linux/runshell` and `git-annex.linux/bin/git-annex-shell` ; make -the first line of each shell script be "#!/bin/sh -x". - -Then you can try running it again via ssh and on the NAS, and paste the -debug output. -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_46d66ab3216594fbe808c95baddba02f._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_46d66ab3216594fbe808c95baddba02f._comment deleted file mode 100644 index 3189c3f51..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_4_46d66ab3216594fbe808c95baddba02f._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="cmdline of neverending process" - date="2015-02-11T11:17:03Z" - content=""" -It's a DS414 Synology NAS. I followed this tutorial: -http://git-annex.branchable.com/tips/Synology_NAS_and_git_annex/ and I've run runshell to create those two scripts inside the .ssh folder. - -I'm using the pubkey authentication with separate keys (just as described). Thus git-annex-shell in the .ssh script is run, when git-annex on my laptop tries to connect by ssh. - -This is the cmdline argument of the process that eats up all memory without finishing: -/volume1/homes/admin/git-annex.linux//lib/ld-linux.so.3--library-path/volume1/homes/admin/git-annex.linux//etc/ld.so.conf.d:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi/audit:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi/gconv:/volume1/homes/admin/git-annex.linux//usr/lib:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi:/volume1/homes/admin/git-annex.linux//lib:/volume1/homes/admin/git-annex.linux//lib/arm-linux-gnueabi:/volume1/homes/admin/git-annex.linux/shimmed/git-annex-shell/git-annex-shell-cgit-annex-shell 'configlist' '/volume1/homes/admin/GitAnnex' -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_5_cc24b3cc44e66c8dce7448daa2fa7682._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_5_cc24b3cc44e66c8dce7448daa2fa7682._comment deleted file mode 100644 index 61082cfee..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_5_cc24b3cc44e66c8dce7448daa2fa7682._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 5" - date="2015-02-12T17:19:40Z" - content=""" -Running git annex sync on my Laptop: -+ cmd=git-annex-shell -+ shift 1 -+ exec git-annex-shell -c \"git-annex-shell 'configlist' '/volume1/homes/admin/GitAnnex'\" -+ exec /volume1/homes/admin/git-annex.linux//lib/ld-linux.so.3 --library-path /volume1/homes/admin/git-annex.linux//etc/ld.so.conf.d:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi/audit:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi/gconv:/volume1/homes/admin/git-annex.linux//usr/lib:/volume1/homes/admin/git-annex.linux//usr/lib/arm-linux-gnueabi:/volume1/homes/admin/git-annex.linux//lib:/volume1/homes/admin/git-annex.linux//lib/arm-linux-gnueabi: /volume1/homes/admin/git-annex.linux/shimmed/git-annex-shell/git-annex-shell -c \"git-annex-shell 'configlist' '/volume1/homes/admin/GitAnnex'\" - -If I copy the last command and run it directly on the NAS it works like a charm. That's so ridiculous. -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment deleted file mode 100644 index 01900e69f..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_6_2ad3d0960929533fef8f827bbf06f085._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-02-12T18:20:39Z" - content=""" -Does it work if ssh allocates a pseudo-tty? - -ssh -t myuser@mynas "git-annex-shell 'configlist' 'mygitannexfolder'" - -There must be some fundamental difference in the environment between the -same command being run over ssh and at the console that is making it behave -differently one way than the other. It could be the pseudo-tty, or an -environment variable, or a different user account, or whatever. - -I think that the only way to get to the bottom of this problem is going to be -finding out what the difference is. (Or perhaps stracing it to see what -it's doing when it uses so much memory.) -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_7_a8b34dfe0daad646f8c1def2b7a4d999._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_7_a8b34dfe0daad646f8c1def2b7a4d999._comment deleted file mode 100644 index eec2352ed..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_7_a8b34dfe0daad646f8c1def2b7a4d999._comment +++ /dev/null @@ -1,88 +0,0 @@ -[[!comment format=c - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 7" - date="2015-02-17T14:43:02Z" - content=""" -ssh -t makes no difference, the strace output: -it's completely repetitive, only the futex and mmap calls are at random positions (mmap probably leads to the enormous memory consumption) - -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {31, 737743240}) = 0 -clock_gettime(CLOCK_MONOTONIC, {365100, 810332327}) = 0 -clock_gettime(0x3 /* CLOCK_??? */, {31, 737155560}) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -futex(0x2b32fb1c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x2b32fb18, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 -futex(0x2b32fb48, FUTEX_WAKE_PRIVATE, 1) = 1 -futex(0x41981d0, FUTEX_WAKE_PRIVATE, 1) = 1 ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {31, 851239760}) = 0 -clock_gettime(CLOCK_MONOTONIC, {365100, 933314386}) = 0 -clock_gettime(0x3 /* CLOCK_??? */, {31, 850549960}) = 0 -mmap2(0x30b00000, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x30b00000 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [HUP ILL TRAP KILL USR1 USR2 CHLD TSTP TTIN URG XFSZ VTALRM IO PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {56, 575838240}) = 0 -clock_gettime(CLOCK_MONOTONIC, {365125, 751101804}) = 0 -clock_gettime(0x3 /* CLOCK_??? */, {56, 574935120}) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now []) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [ILL FPE KILL SEGV USR2 PIPE TERM STOP TSTP URG XCPU XFSZ VTALRM]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [QUIT ABRT BUS PIPE TERM CONT STOP URG IO PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [QUIT ABRT BUS PIPE TERM CONT STOP URG IO PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [QUIT ABRT BUS PIPE TERM CONT STOP URG IO PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [QUIT ABRT BUS PIPE TERM CONT STOP URG IO PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_8_5cabffc139a8db7680346ccf0f4dc429._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_8_5cabffc139a8db7680346ccf0f4dc429._comment deleted file mode 100644 index b0cb8674f..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_8_5cabffc139a8db7680346ccf0f4dc429._comment +++ /dev/null @@ -1,254 +0,0 @@ -[[!comment format=c - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 8" - date="2015-02-18T12:39:17Z" - content=""" -Diff between the straces (the first ~490 lines have been identical and are removed for simplicity) - -Running per ssh: -mprotect(0x2b1e2000, 8192, PROT_READ) = 0 -mprotect(0x2aafb000, 4096, PROT_READ) = 0 -mprotect(0x2b24e000, 4096, PROT_READ) = 0 -mprotect(0x2aca5000, 4096, PROT_READ) = 0 -mprotect(0x2ad6d000, 4096, PROT_READ) = 0 -mprotect(0x2b21f000, 4096, PROT_READ) = 0 -mprotect(0x2acdd000, 4096, PROT_READ) = 0 -mprotect(0x2ac24000, 4096, PROT_READ) = 0 -mprotect(0x2aae5000, 4096, PROT_READ) = 0 -mprotect(0x2ad27000, 20480, PROT_READ) = 0 -mprotect(0x2acbd000, 4096, PROT_READ) = 0 -mprotect(0x2b0a0000, 4096, PROT_READ) = 0 -mprotect(0x2ab55000, 4096, PROT_READ) = 0 -mprotect(0x2aacd000, 4096, PROT_READ) = 0 -mprotect(0x2ab32000, 4096, PROT_READ) = 0 -mprotect(0x2afeb000, 16384, PROT_READ) = 0 -mprotect(0x2aeaf000, 20480, PROT_READ) = 0 -mprotect(0x2abfd000, 4096, PROT_READ) = 0 -mprotect(0x2ada4000, 4096, PROT_READ) = 0 -mprotect(0x2abbc000, 4096, PROT_READ) = 0 -set_tid_address(0x2ac28068) = 18015 -set_robust_list(0x2ac28070, 0xc) = 0 -rt_sigaction(SIGRTMIN, {0x2ac04550, [], SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigaction(SIGRT_1, {0x2ac043e4, [], SA_RESTART|SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 -getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 -futex(0x2ad2cc44, FUTEX_WAKE_PRIVATE, 2147483647) = 0 -brk(0) = 0x2bf15000 -brk(0x2bf36000) = 0x2bf36000 -open(\"/dev/urandom\", O_RDONLY|O_LARGEFILE) = 3 -fcntl64(3, F_GETFD) = 0 -fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 -fstat64(3, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9), ...}) = 0 -clock_gettime(CLOCK_REALTIME, {1424257023, 820788195}) = 0 -getrusage(0x1 /* RUSAGE_??? */, {ru_utime={0, 20000}, ru_stime={0, 10000}, ...}) = 0 -read(3, \"yx$\17\207\4\364\233\366\361\210[,\334(\214\\"\343\226\2'd\303\24\306\254\323\363\2523\36\2\", 32) = 32 -read(3, \"\243e\370\36n\320@l\345\27\6/\323<U\240xM\221\2507m\24\31\200mI\355\0043*\375\", 32) = 32 -read(3, \">%5`2\355\355B\", 8) = 8 -clock_getres(0x2 /* CLOCK_??? */, {0, 1}) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {0, 44157400}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438775, 660164522}) = 0 -brk(0x2bf57000) = 0x2bf57000 -mmap2(NULL, 2097152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b250000 -munmap(0x2b250000, 720896) = 0 -munmap(0x2b400000, 327680) = 0 -timer_create(CLOCK_MONOTONIC, {0, SIGVTALRM, SIGEV_SIGNAL, {...}}, {0x1}) = 0 -rt_sigaction(SIGVTALRM, {0x3cc4e08, [], SA_RESTART|0x4000000}, NULL, 8) = 0 -timer_settime(0x1, 0, {it_interval={0, 10000000}, it_value={0, 10000000}}, NULL) = 0 -rt_sigaction(SIGINT, {0x3cce17c, [], 0x4000000 /* SA_??? */}, {SIG_DFL, [], 0}, 8) = 0 -rt_sigaction(SIGINT, NULL, {0x3cce17c, [], 0x4000000 /* SA_??? */}, 8) = 0 -rt_sigaction(SIGINT, {0x3cce17c, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -rt_sigaction(SIGPIPE, {0x3cce0b4, [], 0x4000000 /* SA_??? */}, {SIG_DFL, [], 0}, 8) = 0 -rt_sigaction(SIGTSTP, {0x3cce1c0, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -epoll_create(0x100) = 4 -fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 -pipe([5, 6]) = 0 -fcntl64(6, F_GETFL) = 0x1 (flags O_WRONLY) -fcntl64(6, F_SETFL, O_WRONLY|O_NONBLOCK) = 0 -fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 -fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 -mmap2(NULL, 8388608, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|0x20000, -1, 0) = 0x2b400000 -mprotect(0x2b400000, 4096, PROT_NONE) = 0 -clone(child_stack=0x2bbfef98, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x2bbff4c8, tls=0x2bbff920, child_tidptr=0x2bbff4c8) = 18039 -futex(0x2bf3aa6c, FUTEX_WAIT_PRIVATE, 1, NULL) = 0 -futex(0x2bf3aa98, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 -futex(0x2bf3aa98, FUTEX_WAKE_PRIVATE, 1) = 0 -futex(0x41981d0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 -futex(0x41981d0, FUTEX_WAKE_PRIVATE, 1) = 0 -eventfd2(0, 0) = 7 -fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR) -fcntl64(7, F_SETFL, O_RDWR|O_NONBLOCK) = 0 -fcntl64(7, F_SETFD, FD_CLOEXEC) = 0 -epoll_ctl(0x4, 0x1, 0x5, 0x2b304430) = 0 -epoll_ctl(0x4, 0x1, 0x7, 0x2b304448) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {0, 46001320}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438775, 665190920}) = 0 -futex(0x2bf3aa6c, FUTEX_WAIT_PRIVATE, 3, NULL) = 0 -futex(0x2bf3aa98, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 -futex(0x2bf3aa98, FUTEX_WAKE_PRIVATE, 1) = 0 -futex(0x41981d0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 -futex(0x41981d0, FUTEX_WAKE_PRIVATE, 1) = 0 -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -rt_sigaction(SIGINT, {0x3cce0b8, [], SA_RESETHAND|SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -open(\"/usr/lib/arm-linux-gnueabi/gconv/gconv-modules.cache\", O_RDONLY) = -1 ENOENT (No such file or directory) -open(\"/usr/lib/arm-linux-gnueabi/gconv/gconv-modules\", O_RDONLY|0x80000) = -1 ENOENT (No such file or directory) -futex(0x2b1e4ef4, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [TRAP FPE KILL SEGV USR2 TERM STKFLT CHLD CONT TSTP TTIN TTOU XCPU VTALRM WINCH PWR]) ---- SIGVTALRM (Virtual timer expired) @ 0 (0) --- -sigreturn() = ? (mask now [TRAP FPE KILL SEGV USR2 TERM STKFLT CHLD CONT TSTP TTIN TTOU XCPU VTALRM WINCH PWR]) - -Running local on NAS: -mprotect(0x2b0dc000, 8192, PROT_READ) = 0 -mprotect(0x2ae4a000, 4096, PROT_READ) = 0 -mprotect(0x2b241000, 4096, PROT_READ) = 0 -mprotect(0x2aee9000, 4096, PROT_READ) = 0 -mprotect(0x2b19e000, 4096, PROT_READ) = 0 -mprotect(0x2b1d7000, 4096, PROT_READ) = 0 -mprotect(0x2b15c000, 4096, PROT_READ) = 0 -mprotect(0x2ae71000, 4096, PROT_READ) = 0 -mprotect(0x2ab70000, 4096, PROT_READ) = 0 -mprotect(0x2b138000, 20480, PROT_READ) = 0 -mprotect(0x2b0f8000, 4096, PROT_READ) = 0 -mprotect(0x2af9a000, 4096, PROT_READ) = 0 -mprotect(0x2ab57000, 4096, PROT_READ) = 0 -mprotect(0x2ab3a000, 4096, PROT_READ) = 0 -mprotect(0x2ab1b000, 4096, PROT_READ) = 0 -mprotect(0x2ae33000, 16384, PROT_READ) = 0 -mprotect(0x2acf7000, 20480, PROT_READ) = 0 -mprotect(0x2abec000, 4096, PROT_READ) = 0 -mprotect(0x2abab000, 4096, PROT_READ) = 0 -mprotect(0x2aaf3000, 4096, PROT_READ) = 0 -set_tid_address(0x2b2a8068) = 18072 -set_robust_list(0x2b2a8070, 0xc) = 0 -rt_sigaction(SIGRTMIN, {0x2ae51550, [], SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigaction(SIGRT_1, {0x2ae513e4, [], SA_RESTART|SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 -getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 -futex(0x2b13dc44, FUTEX_WAKE_PRIVATE, 2147483647) = 0 -brk(0) = 0x2ca10000 -brk(0x2ca31000) = 0x2ca31000 -open(\"/dev/urandom\", O_RDONLY|O_LARGEFILE) = 3 -fcntl64(3, F_GETFD) = 0 -fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 -fstat64(3, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9), ...}) = 0 -clock_gettime(CLOCK_REALTIME, {1424257086, 456931329}) = 0 -getrusage(0x1 /* RUSAGE_??? */, {ru_utime={0, 20000}, ru_stime={0, 0}, ...}) = 0 -read(3, \"l\36K\322\231Ud\302.\335\301dhC)A\260\374~\350\254\341-\267\215\300\313\334\215XqI\", 32) = 32 -read(3, \"\25017J\372\361^\374\254\347$\f=Ag)\10r\25\317r]\216\337G\371M\27\321\326\0(\", 32) = 32 -read(3, \"\245\271\251\373\270\350S1\", 8) = 8 -open(\"/usr/lib/locale/locale-archive\", O_RDONLY|O_LARGEFILE|0x80000) = 4 -fstat64(4, {st_mode=S_IFREG|0644, st_size=14362288, ...}) = 0 -mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 4, 0) = 0x2b36b000 -close(4) = 0 -clock_getres(0x2 /* CLOCK_??? */, {0, 1}) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {0, 29204680}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438838, 301653485}) = 0 -brk(0x2ca52000) = 0x2ca52000 -mmap2(NULL, 2097152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b579000 -munmap(0x2b579000, 552960) = 0 -munmap(0x2b700000, 495616) = 0 -timer_create(CLOCK_MONOTONIC, {0, SIGVTALRM, SIGEV_SIGNAL, {...}}, {0x2}) = 0 -rt_sigaction(SIGVTALRM, {0x3cc4e08, [], SA_RESTART|0x4000000}, NULL, 8) = 0 -timer_settime(0x2, 0, {it_interval={0, 10000000}, it_value={0, 10000000}}, NULL) = 0 -rt_sigaction(SIGINT, {0x3cce17c, [], 0x4000000 /* SA_??? */}, {SIG_DFL, [], 0}, 8) = 0 -rt_sigaction(SIGINT, NULL, {0x3cce17c, [], 0x4000000 /* SA_??? */}, 8) = 0 -rt_sigaction(SIGINT, {0x3cce17c, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -rt_sigaction(SIGPIPE, {0x3cce0b4, [], 0x4000000 /* SA_??? */}, {SIG_DFL, [], 0}, 8) = 0 -rt_sigaction(SIGTSTP, {0x3cce1c0, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -epoll_create(0x100) = 4 -fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 -pipe([5, 6]) = 0 -fcntl64(6, F_GETFL) = 0x1 (flags O_WRONLY) -fcntl64(6, F_SETFL, O_WRONLY|O_NONBLOCK) = 0 -fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 -fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 -mmap2(NULL, 8388608, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS|0x20000, -1, 0) = 0x2b700000 -mprotect(0x2b700000, 4096, PROT_NONE) = 0 -clone(child_stack=0x2befef98, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x2beff4c8, tls=0x2beff920, child_tidptr=0x2beff4c8) = 18073 -futex(0x2ca36264, FUTEX_WAIT_PRIVATE, 1, NULL) = 0 -futex(0x2ca36290, FUTEX_WAKE_PRIVATE, 1) = 0 -eventfd2(0, 0) = 7 -fcntl64(7, F_GETFL) = 0x2 (flags O_RDWR) -fcntl64(7, F_SETFL, O_RDWR|O_NONBLOCK) = 0 -fcntl64(7, F_SETFD, FD_CLOEXEC) = 0 -epoll_ctl(0x4, 0x1, 0x5, 0x2b604430) = 0 -epoll_ctl(0x4, 0x1, 0x7, 0x2b604448) = 0 -futex(0x2ca36314, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x2ca36310, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 -clock_gettime(0x2 /* CLOCK_??? */, {0, 31248840}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438838, 311493486}) = 0 -futex(0x2ca36264, FUTEX_WAIT_PRIVATE, 3, NULL) = 0 -futex(0x2ca36290, FUTEX_WAKE_PRIVATE, 1) = 0 -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -rt_sigaction(SIGINT, {0x3cce0b8, [], SA_RESETHAND|SA_SIGINFO|0x4000000}, NULL, 8) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 -stat64(\"/volume1/homes/admin/GitAnnex.git\", 0x2b604890) = -1 ENOENT (No such file or directory) -getcwd(\"/volume1/homes/admin\", 4096) = 21 -getcwd(\"/volume1/homes/admin\", 4096) = 21 -getcwd(\"/volume1/homes/admin\", 4096) = 21 -pipe([8, 9]) = 0 -pipe([10, 11]) = 0 -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -timer_settime(0x2, 0, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0 -vfork() = 18074 -close(9) = 0 -fcntl64(8, F_SETFD, FD_CLOEXEC) = 0 -close(11) = 0 -fcntl64(10, F_SETFD, FD_CLOEXEC) = 0 -read(10, \"\", 4) = 0 -close(10) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -timer_settime(0x2, 0, {it_interval={0, 10000000}, it_value={0, 10000000}}, NULL) = 0 -fcntl64(8, F_GETFL) = 0 (flags O_RDONLY) -fcntl64(8, F_SETFL, O_RDONLY|O_NONBLOCK) = 0 -ioctl(8, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7ea3e7ac) = -1 EINVAL (Invalid argument) -read(8, 0x2b6f1010, 8096) = -1 EAGAIN (Resource temporarily unavailable) -epoll_ctl(0x4, 0x1, 0x8, 0x2b604d0c) = 0 -write(7, \"\1\0\0\0\0\0\0\0\", 8) = 8 -futex(0x2ca36314, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x2ca36310, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 -futex(0x2ca36340, FUTEX_WAKE_PRIVATE, 1) = 1 -futex(0x41981d0, FUTEX_WAKE_PRIVATE, 1) = 1 -futex(0x2ca36264, FUTEX_WAIT_PRIVATE, 5, NULL) = ? ERESTARTSYS (To be restarted) ---- SIGCHLD (Child exited) @ 0 (0) --- -futex(0x2ca36264, FUTEX_WAIT_PRIVATE, 5, NULL) = -1 EAGAIN (Resource temporarily unavailable) -futex(0x2ca36290, FUTEX_WAKE_PRIVATE, 1) = 0 -read(8, \"user.email\nbraun_markus@gmx.de\0u\"..., 8096) = 211 -read(8, \"\", 8096) = 0 -close(8) = 0 -wait4(18074, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 18074 -rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0 -rt_sigaction(SIGINT, {SIG_DFL, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -select(2, [], [1], NULL, {0, 0}) = 1 (out [1], left {0, 0}) -write(1, \"annex.uuid=8d7304a1-6ea5-46cc-83\"..., 48) = 48 -select(2, [], [1], NULL, {0, 0}) = 1 (out [1], left {0, 0}) -write(1, \"core.gcrypt-id=\n\", 16) = 16 -wait4(-1, 0x2b604f10, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child processes) -clock_gettime(0x2 /* CLOCK_??? */, {0, 36727080}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438838, 341180247}) = 0 -write(6, \"\376\", 1) = 1 -rt_sigprocmask(SIG_BLOCK, [], [], 8) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {0, 36947040}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438838, 341757433}) = 0 -clock_getres(0x3 /* CLOCK_??? */, {0, 1}) = 0 -clock_gettime(0x3 /* CLOCK_??? */, {0, 36313200}) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -futex(0x2ca36314, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x2ca36310, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 -futex(0x2ca36340, FUTEX_WAKE_PRIVATE, 1) = 1 -futex(0x41981d0, FUTEX_WAKE_PRIVATE, 1) = 1 -timer_settime(0x2, 0, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0 -rt_sigaction(SIGVTALRM, {SIG_IGN, [], SA_INTERRUPT|SA_NODEFER|SA_RESETHAND|0x4000000}, {0x3cc4e08, [], SA_RESTART|0x4000000}, 8) = 0 -timer_delete(0x2) = 0 -rt_sigprocmask(SIG_BLOCK, [TTOU], [], 8) = 0 -rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 -rt_sigaction(SIGINT, {SIG_DFL, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -rt_sigaction(SIGPIPE, {SIG_DFL, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -rt_sigaction(SIGTSTP, {SIG_DFL, [], 0x4000000 /* SA_??? */}, NULL, 8) = 0 -clock_gettime(0x2 /* CLOCK_??? */, {0, 38184040}) = 0 -clock_gettime(CLOCK_MONOTONIC, {438838, 344573245}) = 0 -close(3) = 0 -exit_group(0) = ? - -"""]] diff --git a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_9_40f1f7c3f272af5ec44d1d84ad145e36._comment b/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_9_40f1f7c3f272af5ec44d1d84ad145e36._comment deleted file mode 100644 index 62cf76aa8..000000000 --- a/doc/bugs/git-annex_on_NAS_eats_all_memory/comment_9_40f1f7c3f272af5ec44d1d84ad145e36._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmLuHhscJsoAqb9q0N3LdtHum6LjY1LK4" - nickname="Markus" - subject="comment 9" - date="2015-02-21T20:21:32Z" - content=""" -Approaching the solution after hours and hours of debugging: - -https://ghc.haskell.org/trac/ghc/ticket/7695 -This explains why so much ram is used when trying to open gconv-modules in the ssh strace! - -the local strace is using \"/usr/lib/locale/locale-archive\" instead of gconv-modules -both libs are stated in the ghc.haskell bug report - -Just have to figure out, why the ghc created haskell binary tries to access gconv-modules instead of locale/locale-archive when run per ssh -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files.mdwn b/doc/bugs/git-annex_opens_too_many_files.mdwn deleted file mode 100644 index f439b383f..000000000 --- a/doc/bugs/git-annex_opens_too_many_files.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -[[!meta title="network-muticast FD leak fix not deployed to Linux autobuilds yet"]] - -### Please describe the problem. -After running git-annex some minutes, the websites is not responsible any more and it even crashes eventually. - -### What steps will reproduce the problem? -Start the assistant. - -### What version of git-annex are you using? On what operating system? -it-annex version: 4.20130802-g1452ac3 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP - -### 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 -[2013-08-06 13:32:51 CEST] main: starting assistant version 4.20130802-g1452ac3 - -Already up-to-date. -(scanning...) [2013-08-06 13:32:51 CEST] Watcher: Performing startup scan - -Already up-to-date. -(started...) -git-annex: accept: resource exhausted (Too many open files) -[2013-08-06 19:50:37 CEST] read: git ["--git-dir=/home/christian/git-annex/.git","--work-tree=/home/+christian/git-annex","symbolic-ref","HEAD"] -git-annex: runInteractiveProcess: pipe: Too many open files -[2013-08-06 19ND:ea5te1Wm:ao1tn1cS htCeaErtSFuTas]l lcNbreaatcsWkha etcdcr:ha es/rhh:eo dmd:ee /tgc+eihctrt:ie sdct rineaeantt/wegoPirrtko- cacenosnnsen:xe /cr.tegisiootnu/ -racnen[ e2ex0x/1h:3a -uo0sp8te-en0dT6 e (m1Tp9oF:oi5 l1me:a:1n 1yr eCosEpoSeuTnr] c feri eleaexdsh:+)a -ugsitte d[ "(-T-ogoi tm-adniyr =o/pheonm ef/iclhersi)s -tian/git-annex/.git","--work-tree=/home/christian/git-annex","symbolic-ref","HEAD"] -git-annex: runInteractiveProcess: pipe: Too many open files -git-annex: git: createProcess: resource exhausted (Too many open files) -[2013-08-06 19:51:11 CEST] NetWatcherFallback: warning NetWatcherFallback crashed: git: createProces+s: resource exhausted (Too many open files) -[2013-08-06 19:51:11 CEST] DaemonStatus: warning DaemonStatus crashed: /home/christian/git-annex/.gi+t/annex/: openTempFile: resource exhausted (Too many open files) - -(system was asleep from 14:00 until 19:50) - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_1_37f6f5838c41c533df4be1f927b9b03d._comment b/doc/bugs/git-annex_opens_too_many_files/comment_1_37f6f5838c41c533df4be1f927b9b03d._comment deleted file mode 100644 index de5dde9b5..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_1_37f6f5838c41c533df4be1f927b9b03d._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="chrisbra" - ip="80.149.220.45" - subject="sorry, added some wrapping signs from vim." - date="2013-08-06T18:01:40Z" - content=""" -[2013-08-06 13:32:51 CEST] main: starting assistant version 4.20130802-g1452ac3 - -Already up-to-date. -(scanning...) [2013-08-06 13:32:51 CEST] Watcher: Performing startup scan - -Already up-to-date. -(started...) -git-annex: accept: resource exhausted (Too many open files) -[2013-08-06 19:50:37 CEST] read: git [\"--git-dir=/home/christian/git-annex/.git\",\"--work-tree=/home/christian/git-annex\",\"symbolic-ref\",\"HEAD\"] -git-annex: runInteractiveProcess: pipe: Too many open files -[2013-08-06 19ND:ea5te1Wm:ao1tn1cS htCeaErtSFuTas]l lcNbreaatcsWkha etcdcr:ha es/rhh:eo dmd:ee /tgceihctrt:ie sdct rineaeantt/wegoPirrtko- cacenosnnsen:xe /cr.tegisiootnu/ -racnen[ e2ex0x/1h:3a -uo0sp8te-en0dT6 e (m1Tp9oF:oi5 l1me:a:1n 1yr eCosEpoSeuTnr] c feri eleaexdsh:)a -ugsitte d[ \"(-T-ogoi tm-adniyr =o/pheonm ef/iclhersi)s -tian/git-annex/.git\",\"--work-tree=/home/christian/git-annex\",\"symbolic-ref\",\"HEAD\"] -git-annex: runInteractiveProcess: pipe: Too many open files -git-annex: git: createProcess: resource exhausted (Too many open files) -[2013-08-06 19:51:11 CEST] NetWatcherFallback: warning NetWatcherFallback crashed: git: createProcess: resource exhausted (Too many open files) -[2013-08-06 19:51:11 CEST] DaemonStatus: warning DaemonStatus crashed: /home/christian/git-annex/.git/annex/: openTempFile: resource exhausted (Too many open files) - -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_2_347ef233b9845b84d7c4d49ed166e797._comment b/doc/bugs/git-annex_opens_too_many_files/comment_2_347ef233b9845b84d7c4d49ed166e797._comment deleted file mode 100644 index 381d425fc..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_2_347ef233b9845b84d7c4d49ed166e797._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="2001:4978:f:21a::2" - subject="comment 2" - date="2013-08-07T15:59:59Z" - content=""" -What operating system is this? - -Can you see which files the git-annex process has open? -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_3_d5f644d97cd2db471deb5dcd728cae60._comment b/doc/bugs/git-annex_opens_too_many_files/comment_3_d5f644d97cd2db471deb5dcd728cae60._comment deleted file mode 100644 index fbd3bce8f..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_3_d5f644d97cd2db471deb5dcd728cae60._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="chrisbra" - ip="212.121.153.12" - subject="This is ubuntu 12.10" - date="2013-08-12T13:30:00Z" - content=""" -This is ubuntu 12.10 and seems to be the same problem which has been mentioned before (resource exhausted or similar) -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_4_c03bde64be8fdd962826bc7afa07d2a9._comment b/doc/bugs/git-annex_opens_too_many_files/comment_4_c03bde64be8fdd962826bc7afa07d2a9._comment deleted file mode 100644 index b4c458706..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_4_c03bde64be8fdd962826bc7afa07d2a9._comment +++ /dev/null @@ -1,137 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlmRpGORNKWimtzqItvwm4I6cn16vx8OvU" - nickname="hayden" - subject="Many network sockets with associated fds hanging around" - date="2013-08-15T18:00:42Z" - content=""" -I see something similar in logs and after roughly 10 mins the web-apps dies. -So I think I hit the same as the above user. -Sometimes I get thread deaths and restart requests but the root cause appears to match the scenario mentioned over. -Often the webapp just hangs. But always when it hits the fd ulimit... 1024 on this system. - -git-annex version is 4.20130802-g1452ac3 and I used the static-linked linux tar.gz linux-binary download. - -Test setup is a from scratch assistant startup on Ubuntu 12.04. -Not exactly a clean ubuntu though, so maybe difficult to duplicate troubles at your end. - -I fired up the web-app with a cleaned out config. No signs of leaks until an annex is created. -On creation of an empty annex I get fd leaks a about 1 per second after a repository is created. -Strace'ing the main process only shows 8-bytes writes (see below) at the same rate as the leak. -Sometimes the fd-leak stops before the resource limit, sometimes not. -Creating a new annex on top of an existing directory tree with many files is pretty reliable trigger though. -Startup scan finishes and fds leak away until the ulimit is hit. - - hayden@orca:~/gamma$ ls /proc/26319/fd - 0 10 12 14 16 18 2 21 23 25 27 29 30 32 34 36 38 4 41 43 45 6 8 - 1 11 13 15 17 19 20 22 24 26 28 3 31 33 35 37 39 40 42 44 5 7 9 - hayden@orca:~/gamma$ ls /proc/26319/fd - 0 10 12 14 16 18 2 21 23 25 27 29 30 32 34 36 38 4 41 43 45 6 8 - 1 11 13 15 17 19 20 22 24 26 28 3 31 33 35 37 39 40 42 44 5 7 9 - hayden@orca:~/gamma$ ls /proc/26319/fd - 0 10 12 14 16 18 2 21 23 25 27 29 30 32 34 36 38 4 41 43 45 5 7 9 - 1 11 13 15 17 19 20 22 24 26 28 3 31 33 35 37 39 40 42 44 46 6 8 - - hayden@orca:~/gamma$ ls /proc/26319/fd/43 - /proc/26319/fd/43 - - hayden@orca:~/gamma$ ls -l /proc/26319/fd/43 - ls -l /proc/26319/fd/43 - lrwx------ 1 hayden hayden 64 Aug 14 21:10 /proc/26319/fd/43 -> socket:[568994] - - hayden@orca:~/gamma$ lsof | grep 568994 - git-annex 26319 hayden 43u IPv4 568994 0t0 UDP 224.0.0.251:55556 - - hayden@orca:~/gamma$ uname -a - Linux orca 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux - - hayden@orca:~/gamma$ cat /etc/issue - Ubuntu 12.04 LTS \n \l - - hayden@orca:~/gamma$ fuser 55556/udp -a - 55556/udp: 4415 26319 27080 27083 - - hayden@orca:~/gamma$ ps aux | grep 4415 - hayden 4415 0.0 0.0 66716 3036 ? S Aug12 0:03 curl -s --head -L http://127.0.0.1:38464/?auth=da9c4aba4cc2db9cf78574753f6e94d8031c6a7bdf8bfe100bde868f57b81fd751965cc9d68a9afac79f826d257a256a04ce62615a7f23cd7c925969dda1c7b8 -w %{http_code} - hayden 27458 0.0 0.0 10612 924 pts/0 S+ 21:50 0:00 grep --color=auto 4415 - - hayden@orca:~/gamma$ ps aux | grep 26319 - hayden 26319 0.1 0.7 497188 28560 pts/5 Sl 21:09 0:04 git-annex webapp - hayden 26338 3.4 3.4 1035572 137864 pts/5 Sl 21:09 1:25 /usr/lib/firefox/firefox /tmp/webapp26319.html - hayden 27460 0.0 0.0 10612 920 pts/0 S+ 21:50 0:00 grep --color=auto 26319 - - hayden@orca:~/gamma$ ps aux | grep 27080 - hayden 27080 0.0 0.0 16476 1288 pts/5 S 21:33 0:00 git --git-dir=/home/hayden/boo/.git --work-tree=/home/hayden/boo cat-file --batch - hayden 27462 0.0 0.0 10612 924 pts/0 S+ 21:50 0:00 grep --color=auto 27080 - - hayden@orca:~/gamma$ ps aux | grep 27083 - hayden 27083 0.0 0.0 16476 1060 pts/5 S 21:33 0:00 git --git-dir=/home/hayden/boo/.git --work-tree=/home/hayden/boo check-attr -z --stdin annex.backend annex.numcopies -- - hayden 27464 0.0 0.0 10612 920 pts/0 S+ 21:51 0:00 grep --color=auto 27083 - -----> has 579 open fds at this point but this number holds stable over 10 min -(copy in new tree to provoke) -(no change) -----> restart daemon in gui to provoke -(new process has open fds slowly climbing after startup scan) - -straces look like this repeating every second. (clipped down) - - futex(0x34f001c, FUTEX_WAIT_PRIVATE, 51, NULL) = ? ERESTARTSYS (To be restarted) - --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- - rt_sigreturn(0x1a) = 202 - futex(0x34f001c, FUTEX_WAIT_PRIVATE, 51, NULL) = ? ERESTARTSYS (To be restarted) - --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- - rt_sigreturn(0x1a) = 202 - futex(0x34f001c, FUTEX_WAIT_PRIVATE, 51, NULL) = ? ERESTARTSYS (To be restarted) - --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- - rt_sigreturn(0x1a) = 202 - futex(0x34f001c, FUTEX_WAIT_PRIVATE, 51, NULL) = ? ERESTARTSYS (To be restarted) - --- SIGVTALRM (Virtual timer expired) @ 0 (0) --- - write(6, \"\377\0\0\0\0\0\0\0\", 8) = 8 - rt_sigreturn(0x2) = 202 - futex(0x34f001c, FUTEX_WAIT_PRIVATE, 51, NULL^C <unfinished ...> - Process 29803 detached - -Until after roughly 10 mins... - - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1017 - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1023 - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1024 - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1024 - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1024 - hayden@orca:~/boo$ ls /proc/29803/fd | wc -l - 1024 - - hayden@orca:~/boo$ ulimit -a - core file size (blocks, -c) 0 - data seg size (kbytes, -d) unlimited - scheduling priority (-e) 0 - file size (blocks, -f) unlimited - pending signals (-i) 31164 - max locked memory (kbytes, -l) 64 - max memory size (kbytes, -m) unlimited - open files (-n) 1024 - pipe size (512 bytes, -p) 8 - POSIX message queues (bytes, -q) 819200 - real-time priority (-r) 0 - stack size (kbytes, -s) 8192 - cpu time (seconds, -t) unlimited - max user processes (-u) 31164 - virtual memory (kbytes, -v) unlimited - file locks (-x) unlimited - hayden@orca:~/boo$ - -At this point the webapp hangs but a number of interesting crashes may occur. I've also seen the particular error in the previous users log (on a big tree). - - [2013-08-14 21:56:12 CEST] main: starting assistant version 4.20130802-g1452ac3 - (scanning...) [2013-08-14 21:56:12 CEST] Watcher: Performing startup scan - (started...) DaemonStatus crashed: /home/hayden/boo/.git/annex/: openTempFile: resource exhausted (Too many open files) - [2013-08-14 22:06:12 CEST] DaemonStatus: warning DaemonStatus crashed: /home/hayden/boo/.git/annex/: openTempFile: resource exhausted (Too many open files) - -Is any of the above helpful? Anything else useful to kick for testing that you'd like done? -I'd guess this is something weird with my ubuntu setup that provokes this as more users would see it otherwise. -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_5_33a2e783e5355e981497b9861997570b._comment b/doc/bugs/git-annex_opens_too_many_files/comment_5_33a2e783e5355e981497b9861997570b._comment deleted file mode 100644 index 786672eb2..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_5_33a2e783e5355e981497b9861997570b._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.63" - subject="comment 5" - date="2013-08-24T17:09:43Z" - content=""" -Thanks for an excellent amount of debug information. - -I can see what's leaking is UDP connections to 224.0.0.251. That address is used for the \"local pairing\" option in the webapp. - -I was able to reproduce the problem by disabling all network interfaces except `lo`. The PairListener then failed to open a multicast listening socket. When it fails that way, it retried every second, as you noticed. And there is a socket leak in that failure mode. - -I wonder if you're seeing this even when on the network? If so, perhaps your Ubuntu system has something going on that prevents opening a multicast listening socket on even `eth0` or `wlan0` or whatever. - -Unfortunately, the actual socket leak bug is in the [network-multicast](http://hackage.haskell.org/package/network-multicast) library, and not in git-annex. I have filed an upstream bug report: <https://github.com/audreyt/network-multicast/issues/4> - -Hopefully that will be dealt with soon. There is a workaround I could do in git-annex: If it fails (leaking one socket), it could wait until the NetworkListener indicated a new network interface was opened, before trying again (possibly leaking one socket again). This would change it from a 1 per second leak to a 1 per change of network leak at worst, which is probably much less likely to cause problems. -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_6_b3a5a4e4ca29c5cd2840bfeb4c63ea68._comment b/doc/bugs/git-annex_opens_too_many_files/comment_6_b3a5a4e4ca29c5cd2840bfeb4c63ea68._comment deleted file mode 100644 index 60c268fc0..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_6_b3a5a4e4ca29c5cd2840bfeb4c63ea68._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.63" - subject="comment 6" - date="2013-08-24T18:38:56Z" - content=""" -My NetListener workaround turned out to not be portable enough. - -However, I have sent a patch to fix the FD leak: <https://github.com/audreyt/network-multicast/pull/6> -Hopefully it gets applied soon. - -I have also made the PairListener only retry every 60 seconds. Which makes the leak 1/60th as bad, for whatever that's worth. - -Once a fix for this gets into Debian, I need to remember to backport it to stable, and update the autobuilders to use it. Also need to remember to update the Android autobuilder. Leaving this bug report open until that happens. -"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files/comment_7_d73454c9ab3729989e4bc3f2223ccde9._comment b/doc/bugs/git-annex_opens_too_many_files/comment_7_d73454c9ab3729989e4bc3f2223ccde9._comment deleted file mode 100644 index 8e1a18fda..000000000 --- a/doc/bugs/git-annex_opens_too_many_files/comment_7_d73454c9ab3729989e4bc3f2223ccde9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 7" - date="2014-01-01T17:29:03Z" - content=""" -OSX, Android, Windows all updated. Debian backport and linux autobuilds updated. -"""]] diff --git a/doc/bugs/git-annex_remotedeamon.mdwn b/doc/bugs/git-annex_remotedeamon.mdwn deleted file mode 100644 index 15f728362..000000000 --- a/doc/bugs/git-annex_remotedeamon.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -git-annex is back on the radar now that the jabber requirement has been dropped! :-) - -But, it seems as though when I create a remote repo via the webapp it always makes it a bare git repo. Even when I specify the "client usage grouping". - -If I manually create two repos on ssh enabled servers, manually link them, and fire up the assistant they are awesomely kept in sync (with no bare repo in sight). - -### What steps will reproduce the problem? - -Use the webapp to try to create a client usage remote repo. - -### What version of git-annex are you using? On what operating system? - -Latest as of post. - -### 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. -"""]] - -> [[notabug|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_remotedeamon/comment_1_bf8aa639ddc7f51ed7b2b83e31694e85._comment b/doc/bugs/git-annex_remotedeamon/comment_1_bf8aa639ddc7f51ed7b2b83e31694e85._comment deleted file mode 100644 index 47d85fc67..000000000 --- a/doc/bugs/git-annex_remotedeamon/comment_1_bf8aa639ddc7f51ed7b2b83e31694e85._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.114" - subject="comment 1" - date="2014-04-24T18:00:52Z" - content=""" -Please use descriptive bug titles. - -The webapp configures some common use cases, not every possible use case. Running git-annex assistant on a remote server to keep a directory there updated is not a relatively common use case. You can do it if you want; and if someone provided a very complelling UI markup that made sense to regular users it might be added to the webap (but this seems unlikely. - -As it is, the webapp set up bare git repositories on remotes, because that is by far the most common useful way to use git on a remote server. And if the webapp's local pairing interface is used, two existing non-bare client repositories will be paired, and the new remotedaemon will help keep the in sync. -"""]] diff --git a/doc/bugs/git-annex_remotedeamon/comment_2_82f71852df61d12333d08ba25af9d7be._comment b/doc/bugs/git-annex_remotedeamon/comment_2_82f71852df61d12333d08ba25af9d7be._comment deleted file mode 100644 index 0228e2fbb..000000000 --- a/doc/bugs/git-annex_remotedeamon/comment_2_82f71852df61d12333d08ba25af9d7be._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 2" - date="2014-04-24T18:43:50Z" - content=""" -hmmm - I think that it's arguable that if in the repository group drop down I select \"client\" then the remote repo should *not* be bare. - -I would predict that this new functionality will supercede the existing use-cases in terms of popularity. It's very cool that all my machines can be kept in sync with just ssh - a walkthrough showing desktop, laptop, and phone all just syncing (i.e., without the cloud transfer repo and jabber complications) makes a much simpler and compelling advert for this cool code! But it won't happen unless the GUI supports it... -"""]] diff --git a/doc/bugs/git-annex_sync_does_not_push.mdwn b/doc/bugs/git-annex_sync_does_not_push.mdwn deleted file mode 100644 index a5fbc1742..000000000 --- a/doc/bugs/git-annex_sync_does_not_push.mdwn +++ /dev/null @@ -1,52 +0,0 @@ -### Please describe the problem. - -From the description of `sync` in the man page I assume it should be able to push all the branches it needs: - -> The sync process involves first committing all local changes, then fetching and merging the `synced/master` and the `git-annex` branch from the remote repositories, and finally pushing the changes back to those branches on the remote repositories. You can use standard git commands to do each of those steps by hand, or if you don't want to worry about the details, you can use sync. - -However this does not seem to be the case if one starts from an empty repository. - -### What steps will reproduce the problem? - -The following script (from <https://gist.github.com/gioele/d4e0905a3570f097fb0b>) will reproduce this problem: - - #!/bin/sh -x - - set -e ; set -u - export LC_ALL=C - - d=$(pwd) - - # cleanup - chmod a+rwx -R REPO pc1 || true - rm -Rf REPO pc1 - - # create central git repo - mkdir -p REPO/Docs.git - cd REPO/Docs.git - git init --bare - cd $d - - # populate repo in PC1 - mkdir -p pc1/Docs - cd pc1/Docs - echo AAA > fileA - echo BBB > fileB - - git init - git remote add origin $d/REPO/Docs.git - git fetch --all - - git annex init "pc1" - git annex add . - git annex sync - - find $d/REPO/Docs.git/refs - - # there should be some branches inside refs - -### What version of git-annex are you using? On what operating system? - -5.20140412ubuntu1 from Ubuntu 14.04. - -> Documentation fixed, so provisionally [[done]] --[[Joey]] diff --git a/doc/bugs/git-annex_sync_does_not_push/comment_1_8b9b53163b012563b3e80f8eded76aaa._comment b/doc/bugs/git-annex_sync_does_not_push/comment_1_8b9b53163b012563b3e80f8eded76aaa._comment deleted file mode 100644 index 424d4db0d..000000000 --- a/doc/bugs/git-annex_sync_does_not_push/comment_1_8b9b53163b012563b3e80f8eded76aaa._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-11T18:09:51Z" - content=""" -git-annex sync only syncs with remotes that have an annex.uuid configured. So you can solve your problem by: `git annex sync origin`, which will sync to the remote and incidentially initialize it for git-annex use. - -I think this is merely a documentation problem, as the documentation says it syncs with all remotes. Although I don't have any strong feelings about whether sync should act on remotes that have not yet been initialized with git-annex. -"""]] diff --git a/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__.mdwn b/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__.mdwn deleted file mode 100644 index 25a60cb5d..000000000 --- a/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__.mdwn +++ /dev/null @@ -1,46 +0,0 @@ -### Please describe the problem. -git annex sync fails with "error while loading shared libraries: hostname: cannot open shared object file: No such file or directory" with hostname being the hostname of the remote git annex repo. - -### What steps will reproduce the problem? -Running "git annex sync" in a normal git annex repo. - -### What version of git-annex are you using? On what operating system? -Arch Linux with the git-annex-bin package from AUR - -git-annex version: 5.20150317-g237d5b0 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - -### Please provide any additional information below. -people describing the same problem here: <https://aur.archlinux.org/packages/git-annex-bin/> - -SSH and normal git operations work fine. - -The --verbose flag doesn't change the output. - -[[!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 -[dafo@simon-desktop dokumente_ga]$ git annex sync -commit ok -pull leno -dafo@leno: error while loading shared libraries: dafo@leno: cannot open shared object file: No such file or directory -fatal: Could not read from remote repository. -Please make sure you have the correct access rights -and the repository exists. -failed -push leno -dafo@leno: error while loading shared libraries: dafo@leno: cannot open shared object file: No such file or directory -fatal: Could not read from remote repository. -Please make sure you have the correct access rights -and the repository exists. - Pushing to leno failed. - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config) -failed -git-annex: sync: 2 failed - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__/comment_1_f9fbaa2232113803db5fe95b7466298f._comment b/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__/comment_1_f9fbaa2232113803db5fe95b7466298f._comment deleted file mode 100644 index 54d87f6b3..000000000 --- a/doc/bugs/git-annex_sync_fails_with___34__error_while_loading_shared_libraries__34__/comment_1_f9fbaa2232113803db5fe95b7466298f._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 1" - date="2015-03-27T12:13:44Z" - content=""" -This is something to do with sshcaching.. - - git annex sync -c annex.sshcaching=false - -works for me. - -For some reason, it is trying to load the hostnames as a shared library.. which seems like a potential security problem to me. -"""]] diff --git a/doc/bugs/git-annex_sync_may_fail_when_the_directory_I__39__m_in_disepeared.mdwn b/doc/bugs/git-annex_sync_may_fail_when_the_directory_I__39__m_in_disepeared.mdwn deleted file mode 100644 index 7a2690be2..000000000 --- a/doc/bugs/git-annex_sync_may_fail_when_the_directory_I__39__m_in_disepeared.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -### Please describe the problem. -While running git annex sync, it may failed if one did run it on some deep directory, and the sync remove this direcory. - -### What version of git-annex are you using? On what operating system? - -git-annex version: 4.20130815 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP -local repository version: 3 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 - -on Debian Gnu Linux sid - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command.mdwn b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command.mdwn deleted file mode 100644 index 0b219457e..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command.mdwn +++ /dev/null @@ -1,217 +0,0 @@ -### Please describe the problem. -I am cloning a remote annex repository to my Windows machine using git clone user@server:/home/user/data - -After I perform git annex init, git annex sync fails with an error complaining that user@server is an invalid command (complete log below). - -It appears that git-annex sync invokes the git-annex executable with parameters for the ssh command. - -git config.sshcaching is false. - - -Thanks, - -Johannes - -PS: - -I found that after reverting commit a6d54e49a0676e1c8e4b3202b29c7725f45fa784 the git fetch command will work, but git push origin will fail: - -push origin [2015-06-21 00:25:32 ric] call: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","core.bare=false","push","origin","+git-annex:synced/git-annex","annex/direct/master:synced/master"] -Bad port '' -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. - - -### What steps will reproduce the problem? - -I tried setting up the repository many different ways, using git bash, cmd.exe or cygwin bash and always get the same error after git annex sync. - - -### What version of git-annex are you using? On what operating system? -C:\data_organization\data>git annex version -git-annex version: 5.20150611-g256b86b -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feed -s Quvi TDFA TorrentParser -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD -5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glac -ier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 2 3 4 - -I am using Windows 8.1 - -### Please provide any additional information below. - -[[!format sh """ - -C:\data_organization\data>git annex sync -commit ok -pull origin -git-annex.exe: unknown command user@55.89.78.37 - -Usage: git-annex command [option ...] - -Commonly used commands: - -add [PATH ...] add files to annex -addurl URL ... add urls to annex -assistant automatically sync changes -copy [PATH ...] copy content of files to/from another reposit -ory -drop [PATH ...] indicate content of files not currently wante -d -edit [PATH ...] same as unlock -get [PATH ...] make content of annexed files available -help [COMMAND] display help -import [PATH ...] move and add files from outside git working c -opy -importfeed URL ... import files from podcast feeds -lock [PATH ...] undo unlock command -mirror [PATH ...] mirror content of files to/from another repos -itory -move [PATH ...] move content of files to/from another reposit -ory -rmurl FILE URL record file is not available at url -status [PATH ...] show the working tree status -sync [REMOTE ...] synchronize local repository with remotes -undo [PATH ...] undo last change to a file or directory -unlock [PATH ...] unlock files for modification -watch watch for changes and autocommit -webapp launch webapp - -Repository setup commands: - -dead REMOTE ... hide a lost repository or key -describe REMOTE DESC change description of a repository -direct switch repository to direct mode -enableremote NAME [K=V ...] enables use of an existing special remote -group REMOTE DESC add a repository to a group -groupwanted GROUP [EXPR] get or set groupwanted expression -indirect switch repository to indirect mode -init DESC initialize git-annex -initremote NAME [K=V ...] creates a special (non-git) remote -numcopies NUMBER configure desired number of copies -required REMOTE [EXPR] get or set required content expression -schedule REMOTE [EXPR] get or set scheduled jobs -semitrust REMOTE ... return repository to default trust level -trust REMOTE ... trust a repository -ungroup REMOTE DESC remove a repository from a group -untrust REMOTE ... do not trust a repository -vicfg edit git-annex's configuration -wanted REMOTE [EXPR] get or set preferred content expression - -Repository maintenance commands: - -addunused NUM|RANGE ... add back unused files -dropunused NUM|RANGE ... drop unused file content -expire [REMOTE]:TIME ... expire inactive repositories -fix [PATH ...] fix up symlinks to point to annexed content -forget prune git-annex branch history -fsck [PATH ...] check for problems -merge automatically merge changes from remotes -repair recover broken git repository -unused look for unused file content -upgrade upgrade repository layout - -Query commands: - -find [PATH ...] lists available files -info [ITEM ...] shows information about the specified item or - the repository as a whole -list [PATH ...] show which remotes contain files -log [PATH ...] shows location log -map generate map of repositories -version show version info -whereis [PATH ...] lists repositories that have file content - -Metadata commands: - -metadata [PATH ...] sets or gets metadata of a file -vadd FIELD=GLOB ... add subdirs to current view -vcycle switch view to next layout -vfilter FIELD=VALUE ... filter current view -view FIELD=VALUE ... enter a view branch -vpop [NUMBER] switch back to previous view - -Utility commands: - -migrate [PATH ...] switch data to different backend -reinit UUID|DESC initialize repository, reusing old UUID -reinject SRC DEST sets content of annexed file -unannex [PATH ...] undo accidential add command -uninit [PATH ...] de-initialize git-annex and clean out reposit -ory - -Plumbing commands: - -checkpresentkey KEY REMOTE check if key is present in remote -contentlocation KEY ... looks up content for a key -diffdriver [-- cmd --] external git diff driver shim -dropkey KEY ... drops annexed content for specified keys -examinekey KEY ... prints information from a key -findref REF lists files in a git ref -fromkey KEY PATH adds a file using a specific key -lookupkey FILE ... looks up key used for file -pre-commit [PATH ...] run by git pre-commit hook -proxy -- git command safely bypass direct mode guard -readpresentkey KEY UUID read records of where key is present -registerurl KEY URL registers an url for a key -rekey [PATH KEY ...] change keys used for files -remotedaemon detects when remotes have changed, and fetche -s from them -resolvemerge resolve merge conflicts -setpresentkey KEY UUID [1|0] change records of where key is present -transferkey KEY transfers a key from or to a remote -transferkeys transfers keys - -Testing commands: - -fuzztest generates fuzz test files -test run built-in test suite -testremote REMOTE test transfers to/from a remote - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -failed -push origin -git-annex.exe: unrecognized option `-p' - -Usage: git-annex add [PATH ...] [option ...] - --include-dotfiles don't skip dotfiles - -x GLOB --exclude=GLOB skip files matching the glob pattern - -I GLOB --include=GLOB limit to files matching the glob pattern - --largerthan=SIZE match files larger than a size - --smallerthan=SIZE match files smaller than a size - --not negate next option - --and both previous and next option must match - --or either previous or next option must match - -( open group of options - -) close group of options - -To see additional options common to all commands, run: git annex help options - - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforward -s to false in the remote's git config) -failed -git-annex: sync: 2 failed - -C:\data_organization\data> - - -"""]] - -> [[fixed|done]] I think. --[[Joey]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_58d7fdcc87c68337581490ab5b5d18b5._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_58d7fdcc87c68337581490ab5b5d18b5._comment deleted file mode 100644 index 1067e8383..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_58d7fdcc87c68337581490ab5b5d18b5._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="zedr0nre@e1b86776f21c5f6a6e064c6ab8da039b54915b7d" - nickname="zedr0nre" - subject="comment 10" - date="2015-08-04T00:00:23Z" - content=""" -A workaround for now is to use a newer GIT from [http://git-for-windows.github.io/](http://git-for-windows.github.io/) which has Git 2.5+ and use the new environment variable GIT_SSH_COMMAND which overrides GIT_SSH so setting - -`export GIT_SSH_COMMAND=ssh` - -allows git annex sync to work successfully for me -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_11_28bfd4d05068748fab2daf1baa2a83cc._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_11_28bfd4d05068748fab2daf1baa2a83cc._comment deleted file mode 100644 index 8772b7307..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_11_28bfd4d05068748fab2daf1baa2a83cc._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 11""" - date="2015-08-04T19:03:54Z" - content=""" -I took another look at this, and I have a suspicion that the difference is -window's behavior when an env var is set to the empty string. - -On Unix, that has a distinct meaning from an env var being set. I suspect -that it doesn't on Windows. Or perhaps on some versions of windows and/or -some versions of haskell libraries on some versions of windows... (Since I -still can't reproduce the problem on windows myself.) - -If `GIT_ANNEX_SSHOPTION=""` results in it not being set, then the rest -of this bug report follows. - -I've made a simple change. If the option is empty, it doesn't try to set -`GIT_SSH` at all. I am pretty sure this entirely fixes the problem. - -Please test the windows daily build, which has this fix applied to it, -and get back to me if not. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_862598cbf80693972b752277da269601._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_862598cbf80693972b752277da269601._comment deleted file mode 100644 index cb478ea09..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_862598cbf80693972b752277da269601._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 12""" - date="2015-08-04T20:03:51Z" - content=""" -Windows build didn't actually get updated until now. - -And only the autobuild is updated, not the last release build of course. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_e2e7b7a5abe6d636fec207c7778c35aa._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_e2e7b7a5abe6d636fec207c7778c35aa._comment deleted file mode 100644 index 3bb3b78ce..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_12_e2e7b7a5abe6d636fec207c7778c35aa._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="comment 12" - date="2015-08-04T19:56:06Z" - content=""" -I did a quick test just after seeing the last comment using the build from here: <a href=\"https://downloads.kitenet.net/git-annex/autobuild/windows/\">https://downloads.kitenet.net/git-annex/autobuild/windows/</a> and it seems it's not working. I'll try the new git version as stated somewhere above later to see if that works. I'm still getting this (followed by the big help text) -<pre>C:\Users\me\gatest>git annex sync -commit ok -pull origin -Invalid argument `me@192.168.78.140' -</pre> -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_14_5b227393b0f341c22bf10ca895aff430._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_14_5b227393b0f341c22bf10ca895aff430._comment deleted file mode 100644 index 40249c6ae..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_14_5b227393b0f341c22bf10ca895aff430._comment +++ /dev/null @@ -1,27 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="comment 14" - date="2015-08-04T20:49:34Z" - content=""" -Sorry, my bad.<br/> -Just installed this build: <a href=\"https://qa.nest-initiative.org/view/msysGit/job/msysgit-git-annex-assistant-test/4837/\">https://qa.nest-initiative.org/view/msysGit/job/msysgit-git-annex-assistant-test/4837/</a><br/> -Still getting the error. %GIT_SSH% is not set. -<pre> -C:\Users\me\q\ga>git annex sync -commit ok -pull origin -Invalid argument `me@192.168.78.140' -</pre> -<pre> -C:\Users\me\q\ga>git annex version -git-annex version: 5.20150804-g4b8b3c6 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA TorrentParser Database -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEI -N256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 2 3 4 -</pre> - -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_15_22189cbd190134d116551bd19f0a1109._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_15_22189cbd190134d116551bd19f0a1109._comment deleted file mode 100644 index 74c24111f..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_15_22189cbd190134d116551bd19f0a1109._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 15""" - date="2015-08-04T20:54:23Z" - content=""" -Thanks for testing. I see I had a problem with my fix; have improved it and -the windows build is updated. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_16_4ff2a87765b1584e55655b2a5451dd50._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_16_4ff2a87765b1584e55655b2a5451dd50._comment deleted file mode 100644 index 4d1ae78c1..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_16_4ff2a87765b1584e55655b2a5451dd50._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="comment 16" - date="2015-08-04T21:46:17Z" - content=""" -Installed build 4839 and everything seems to work. One quick question though, doing sync on an origin and clone repos, shouldn't it make the git annex list look the same on both? I'm getting on the remote -<pre> -me@mint64vm ~/ga $ git annex list -here -|web -|| -X_ me -X_ me_local -X_ me_origin -</pre> -And on the clone (after some copying, moving, dropping and sync) -<pre> -C:\Users\me\q\ga>git annex list -here -|origin -||web -|||bittorrent -|||| -_X__ me -_X__ me_local -_X__ me_origin -</pre> -And, of course, thanks for the fix. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_17_e31976c66cc30b09d26b5a19eb855b0b._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_17_e31976c66cc30b09d26b5a19eb855b0b._comment deleted file mode 100644 index 4993638f5..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_17_e31976c66cc30b09d26b5a19eb855b0b._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="comment 17" - date="2015-08-09T10:00:48Z" - content=""" -OK, sorry for the bad question. Got it figured out that i needed to add a specific remote in order for it to appear in the list. So all git annex repos need to know about all other git annex repos -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_1_b726337841cca318bf0a54f0e6240d86._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_1_b726337841cca318bf0a54f0e6240d86._comment deleted file mode 100644 index bfa2a0a18..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_1_b726337841cca318bf0a54f0e6240d86._comment +++ /dev/null @@ -1,36 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-02T15:50:12Z" - content=""" -Based on the usage output, it seems to be running a recent enough version -of git-annex, which should notice if it's being run as a proxy for ssh. - -Some kind of problem with the environment variables used to communicate -with the git-annex proxy seems like the most likely problem. -But, I am not able to reproduce this problem on Windows (XP) here. -The `GIT_SSH` env var is clearly being set, or git wouldn't try to run -git-annex as ssh. The `GIT_ANNEX_SSHOPTION` env var is set in the same way -as `GIT_SSH`. Maybe git-annex is failing to see it for some reason? - -Since you're comfortable with building git-annex from source, maybe you can -try some simple patches to debug this? - -Here's the first patch I'd suggest. it will make git-annex print out -what value, if any, it's seeing for `GIT_ANNEX_SSHOPTION`. Note that you'll -need to install the patched git-annex into the path. - - diff --git a/CmdLine/GitAnnex.hs b/CmdLine/GitAnnex.hs - index 326dd3b..b612dbb 100644 - --- a/CmdLine/GitAnnex.hs - +++ b/CmdLine/GitAnnex.hs - @@ -225,6 +225,8 @@ run args = do - #ifdef WITH_EKG - _ <- forkServer "localhost" 4242 - #endif - + v <- getEnv sshOptionsEnv - + print (sshOptionsEnv, v) - go envmodes - where - go [] = dispatch True args cmds gitAnnexOptions [] header Git.CurrentRepo.get -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_2_18b3ddff003bcdd78779b35c900964c2._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_2_18b3ddff003bcdd78779b35c900964c2._comment deleted file mode 100644 index 3493cb7a4..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_2_18b3ddff003bcdd78779b35c900964c2._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="johannes.elferich@796088e47b21d72547837ed62ae5c5cb187830b3" - nickname="johannes.elferich" - subject="Patched git-annex output" - date="2015-07-04T02:12:51Z" - content=""" -You are right something weird is going on with the GIT_ANNEX_SSHOPTION variable even though I have no idea what.... - -This is the output I get after patching: - -›git annex sync -(\"GIT_ANNEX_SSHOPTION\",Nothing) -commit (recording state in git...) -ok -pull origin fatal: protocol error: bad line length character: (\"GI -git-annex.exe: unknown command 35.89.33.17 - -Usage: git-annex command [option ...] - -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_3_3d6d64040604f913ddb929dff76e2898._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_3_3d6d64040604f913ddb929dff76e2898._comment deleted file mode 100644 index 05408e053..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_3_3d6d64040604f913ddb929dff76e2898._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-06T16:25:01Z" - content=""" -Could you adjust the patch to print out the `GIT_SSH` variable? -I'm pretty sure that variable is set so git can see it; let's see if -git-annex can see it. If it cannot, this would hint that it's having some -trouble seeing environment variables in general.. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_4_1922bb745ff4194902801714d2b45d4b._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_4_1922bb745ff4194902801714d2b45d4b._comment deleted file mode 100644 index 895cd82d8..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_4_1922bb745ff4194902801714d2b45d4b._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""ping""" - date="2015-07-20T18:00:19Z" - content=""" -Someone else mentioned seeing this same problem on Windows. - -Any chance you can respond to my last comment, Johannes? -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_5_f82ac380383f5116ca1c3b49cdec0648._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_5_f82ac380383f5116ca1c3b49cdec0648._comment deleted file mode 100644 index d0a023684..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_5_f82ac380383f5116ca1c3b49cdec0648._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="same problem" - date="2015-07-21T19:01:52Z" - content=""" -Hi, i have the same problem. I can't compile from source but ive looked at the process and it seems that GIT_SSH/GIT_ANNEX_SSHOPTION are set ok. Ive also looked through the source even though my haskell is quite limited and eventually managed to get something working by bypassing the -<pre><code>g' <- addGitEnv g sshOptionsEnv val -addGitEnv g' \"GIT_SSH\" command</code></pre> -lines but i can't remember right now how i did it, though i remember it was by setting something similar to GIT_SSH (probably just it to 'c:\program...\git\bin\git.exe' or ssh.exe with a combination of GIT_ANNEX_SSHOPTION=''). -It didn't show the 'git annex unknown command' stuff but it did mess up the repo (said it synced the annex/direct/master synced/* branches but the changed didn't appear on the remote/origin). -If there's anything i can try without actually compiling, im all up for it. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_6_0ff253a71e44566d2e8583b25158a07d._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_6_0ff253a71e44566d2e8583b25158a07d._comment deleted file mode 100644 index f0d54baa2..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_6_0ff253a71e44566d2e8583b25158a07d._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-07-30T18:15:58Z" - content=""" -I'm confused, @threadshuffle. You say you're not able to compile it from -source, but then you seem to talk about editing the source code. - -If you could describe more clearly what you did, I'm sure that would be a -lot of help. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_7_1542901463c022d4e47bf0329c5887b3._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_7_1542901463c022d4e47bf0329c5887b3._comment deleted file mode 100644 index e15ce3271..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_7_1542901463c022d4e47bf0329c5887b3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="threadshuffle" - subject="cont'd" - date="2015-07-31T22:05:14Z" - content=""" -Hi joey, I know my english is not quite correct. What i was trying to say was that i managed to avoid certain parts of the code, because they're governed by some conditions by setting some env variables (what i remember was GIT_SSH and something, but can't say for sure now). So i haven't compiled the code, just went on different code paths based on the conditions described by the code. -I will get back to this shortly (maybe next week), install the latest version of git-annex and if that still doesn't work, im gonna build a devenv for haskell and try to see what's happening. I'm gonna be able to provide more details at that point. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_8_f1d20e734052b0e16bb38a059e5890f7._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_8_f1d20e734052b0e16bb38a059e5890f7._comment deleted file mode 100644 index 4b1fed712..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_8_f1d20e734052b0e16bb38a059e5890f7._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="zedr0nre@e1b86776f21c5f6a6e064c6ab8da039b54915b7d" - nickname="zedr0nre" - subject="comment 8" - date="2015-08-02T10:02:09Z" - content=""" -Having the same problem with git annex from 31 july both on Windows 7 and Windows 8.1 - -Original git annex init pulls the data correctly so the changes can be propagated by recloning and reinitialising git annex so it seems like the problem is just for git annex sync. -"""]] diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_9_ea40e1a33188f3aa4a5b414b2420fd76._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_9_ea40e1a33188f3aa4a5b414b2420fd76._comment deleted file mode 100644 index fe2ad3711..000000000 --- a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_9_ea40e1a33188f3aa4a5b414b2420fd76._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="zedr0nre@e1b86776f21c5f6a6e064c6ab8da039b54915b7d" - nickname="zedr0nre" - subject="comment 9" - date="2015-08-03T22:46:30Z" - content=""" -By default on windows in direct mode sshcaching is disabled but it seems like in [5.2010617](https://git-annex.branchable.com/news/version_5.20150617/) there was this change: - -`sync, remotedaemon: Pass configured ssh-options even when annex.sshcaching is disabled.` - -which might explain why GIT_SSH is still set up and points to git-annex instead of ssh? -"""]] diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t.mdwn b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t.mdwn deleted file mode 100644 index 7e82fb013..000000000 --- a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -### Please describe the problem. - -The command `git annex unused --from mys3remote` shows no unused data, when I'm expecting at least one old version of a file in the current directory. - -### What steps will reproduce the problem? - -- Create a file, `git annex add` the file, sync with remotes and copy to an amazon S3 special remote -- Run `git annex unlock` on the file, modify it, `git annex add` the file, sync and copy to S3 -- Now if you run `git annex unused` you should see the old version of the file in the local repo -- But `git annex unused --from mys3remote` shows nothing -- And I know that the old version is on S3 (at least according to the logs) because `git annex whereis --unused` shows that the file is both [here] and [mys3remote] - -I also noticed that the `git annex whereis --unused` command would show nothing if it was run directly after `git annex unused --from mys3remote`, but it would correctly show the locations when run directly after `git annex unused`. - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20141105-g8b19598 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -arch linux x86_64 - -### Please provide any additional information below. - -The S3 remote is encrypted with the default "hybrid" method - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment deleted file mode 100644 index a949625ad..000000000 --- a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_1_f139f18762f3acf8bfb9ce8a245b79f5._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-09T18:06:34Z" - content=""" -I have tried to reproduce this, and I can't seem to. - -There's no network traffic involved in git-annex unused --from remote, -so I don't see how this can involve the S3 backend at all. If there's a bug -here, it should affect any kind of remote. - -Are you sure you didn't forget to `git annex sync` before `git annex unused --from remote`? -If you have an old synced/master branch, that'll count as a user of the -file and so unused won't show it. - -I think you'll need to provide a full transcript of how to make this problem -happen for me to get any further. -"""]] diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_2_b624d895c85f1595dcb0872c88fb4e30._comment b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_2_b624d895c85f1595dcb0872c88fb4e30._comment deleted file mode 100644 index f48429e6c..000000000 --- a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_2_b624d895c85f1595dcb0872c88fb4e30._comment +++ /dev/null @@ -1,110 +0,0 @@ -[[!comment format=mdwn - username="skew" - subject="transcript" - date="2015-05-14T04:37:33Z" - content=""" -Hey Joey, after playing around a bit more, I noticed that the behavior was happening when I'm in a subdirectory, but not when I'm in the root of the repo. I also managed to reproduce the issue with a new repo (and a different type of remote): - -[[!format txt \"\"\" -[john@laptop tmp]$ git init annextest3 -Initialized empty Git repository in /home/john/tmp/annextest3/.git/ -[john@laptop tmp]$ cd annextest3/ -[john@laptop annextest3]$ git annex init laptop -init laptop ok -(Recording state in git...) -[john@laptop annextest3]$ git annex initremote rsyncnet type=rsync rsyncurl=user@server.rsync.net:/path/to/annextest3 encryption=none -initremote rsyncnet ok -(Recording state in git...) -[john@laptop annextest3]$ mkdir docs -[john@laptop annextest3]$ echo \"first version\" > docs/test.txt -[john@laptop annextest3]$ git annex add docs/test.txt -add docs/test.txt ok -(Recording state in git...) -[john@laptop annextest3]$ git annex sync --content -commit ok -copy docs/test.txt copy docs/test.txt (checking rsyncnet...) (to rsyncnet...) -sending incremental file list -./ -1a5/ -1a5/235/ -1a5/235/SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt/ -1a5/235/SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt/SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt - 14 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/5) -ok -(Recording state in git...) -[john@laptop annextest3]$ git annex whereis -whereis docs/test.txt (2 copies) - 139b18e5-1fd0-4144-a551-4e997333b8ae -- [rsyncnet] - 7187a4c5-d9ae-471d-9b4b-843c37bfb3c3 -- laptop [here] -ok -[john@laptop annextest3]$ git annex unlock docs/test.txt -unlock docs/test.txt (copying...) ok -[john@laptop annextest3]$ echo \"second version\" > docs/test.txt -[john@laptop annextest3]$ git annex add docs/test.txt -add docs/test.txt ok -(Recording state in git...) -[john@laptop annextest3]$ git annex sync --content -commit ok -copy docs/test.txt copy docs/test.txt (checking rsyncnet...) (to rsyncnet...) -sending incremental file list -6ad/ -6ad/09f/ -6ad/09f/SHA256E-s15--66ed1142ab3b2f1cdb29e8b81c9471444a5d9e6fb657a54d089073ab8bd34e27.txt/ -6ad/09f/SHA256E-s15--66ed1142ab3b2f1cdb29e8b81c9471444a5d9e6fb657a54d089073ab8bd34e27.txt/SHA256E-s15--66ed1142ab3b2f1cdb29e8b81c9471444a5d9e6fb657a54d089073ab8bd34e27.txt - 15 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/5) -ok -(Recording state in git...) -[john@laptop annextest3]$ git annex unused -unused . (checking for unused data...) (checking master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -[john@laptop annextest3]$ git annex unused --from rsyncnet -unused rsyncnet (checking for unused data...) (checking master...) - Some annexed data on rsyncnet is not used by any files: - NUMBER KEY - 1 SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused --from rsyncnet NUMBER - -ok -[john@laptop annextest3]$ cd docs/ -[john@laptop docs]$ git annex unused -unused . (checking for unused data...) (checking master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -[john@laptop docs]$ git annex unused --from rsyncnet -unused rsyncnet (checking for unused data...) ok -[john@laptop docs]$ git annex whereis --unused -[john@laptop docs]$ cd .. -[john@laptop annextest3]$ git annex whereis --unused -[john@laptop annextest3]$ git annex unused -unused . (checking for unused data...) (checking master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt - (To see where data was previously used, try: git log --stat -S'KEY') - - To remove unwanted data: git-annex dropunused NUMBER - -ok -[john@laptop annextest3]$ git annex whereis --unused -whereis SHA256E-s14--0533c80dc85756cf8cd5181e68d6520f5ffc4585def452d26f59756a5c2548b1.txt (2 copies) - 139b18e5-1fd0-4144-a551-4e997333b8ae -- [rsyncnet] - 7187a4c5-d9ae-471d-9b4b-843c37bfb3c3 -- laptop [here] -ok -[john@laptop annextest3]$ -\"\"\"]] -"""]] diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_3_895217e62f90524620bf452cfd6332be._comment b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_3_895217e62f90524620bf452cfd6332be._comment deleted file mode 100644 index e2c77e86a..000000000 --- a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_3_895217e62f90524620bf452cfd6332be._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-06T17:51:15Z" - content=""" -Reproduced with this transcript. Fascinating. Thankyou! -"""]] diff --git a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_4_768cc5be3d9b53a45419d02f2cb25ec6._comment b/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_4_768cc5be3d9b53a45419d02f2cb25ec6._comment deleted file mode 100644 index 7a09095e0..000000000 --- a/doc/bugs/git-annex_unused_--from_s3_doesn__39__t/comment_4_768cc5be3d9b53a45419d02f2cb25ec6._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-07-06T18:00:53Z" - content=""" -Analysis: To find the keys, it's using git ls-tree git-annex. When this is -run in a subdirectory, it only lists files in the branch located under that -subdirectory. Which is no files. It should pass --full-tree to avoid that -problem. - -Pretty much everywhere git-annex uses ls-tree, it does pass --full-tree. -But not in this particular case. Anything using Annex.Branch.branchFiles or -Annex.Branch.files would be affected; that's limited to git-annex unused -and code that runs transitions. git-annex unused w/o --from could also be -affected, I think, perhaps it's harder to trigger that though. -"""]] diff --git a/doc/bugs/git-annex_webapp_command_not_found.mdwn b/doc/bugs/git-annex_webapp_command_not_found.mdwn deleted file mode 100644 index 6854d541c..000000000 --- a/doc/bugs/git-annex_webapp_command_not_found.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -###What steps will reproduce the problem? - - greg@x220:~/Music$ git-annex version - git-annex version: 3.20121017 - - greg@x220:~/Documents$ git-annex watch - greg@x220:~/Documents$ git-annex: Daemon is already running. - - greg@x220:~/Documents$ git-annex assistant - greg@x220:~/Documents$ git-annex: Daemon is already running. - - greg@x220:~/Documents$ git-annex webapp - git-annex: unknown command webapp - -This is on an Ubuntu (12.10) machine, using git-annex from ubuntu+1 (13.04), which is just an autosync from sid: - -https://launchpad.net/ubuntu/+source/git-annex/3.20121017 - -###What is the expected output? What do you see instead? -I expect my browser to open the webapp. - - -(Also, it is odd how the output of "Daemon is already running" appears after my prompt is given back to me) - -> [[closing|done]]; forwarded upstream --[[Joey]] diff --git a/doc/bugs/git-annex_webapp_command_not_found/comment_1_6fa63ae1a7affb2351eda57ab3b4eda1._comment b/doc/bugs/git-annex_webapp_command_not_found/comment_1_6fa63ae1a7affb2351eda57ab3b4eda1._comment deleted file mode 100644 index d60432a8d..000000000 --- a/doc/bugs/git-annex_webapp_command_not_found/comment_1_6fa63ae1a7affb2351eda57ab3b4eda1._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.6.49" - subject="comment 1" - date="2012-11-29T19:45:25Z" - content=""" -Ubuntu is apparently building git-annex without the webapp. - -(Message display fixed.) -"""]] diff --git a/doc/bugs/git-annex_webapp_command_not_found/comment_2_d25232bb5eaff725281869d7681e81ad._comment b/doc/bugs/git-annex_webapp_command_not_found/comment_2_d25232bb5eaff725281869d7681e81ad._comment deleted file mode 100644 index eaf95ceb1..000000000 --- a/doc/bugs/git-annex_webapp_command_not_found/comment_2_d25232bb5eaff725281869d7681e81ad._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 2" - date="2012-11-29T19:55:25Z" - content=""" -Thanks, Joey. I've reported it [downstream in LP](https://bugs.launchpad.net/ubuntu/+source/git-annex/+bug/1084693). -"""]] diff --git a/doc/bugs/git-annex_webapp_command_not_found/comment_3_f593752a0c5c60daaacca46ced5ac5d8._comment b/doc/bugs/git-annex_webapp_command_not_found/comment_3_f593752a0c5c60daaacca46ced5ac5d8._comment deleted file mode 100644 index 531714d5c..000000000 --- a/doc/bugs/git-annex_webapp_command_not_found/comment_3_f593752a0c5c60daaacca46ced5ac5d8._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk4_47QIHYfGlI9aL04LXxOczcYABmmIfA" - nickname="Mike" - subject="On Opensuse 13.1 - I was able to run git-annex-webapp once. " - date="2014-02-01T15:34:50Z" - content=""" -As soon as I removed my single repository it never loaded again. I have re-booted. re-installed. I have the package installed it tries to load but doesn't. I have the stand-alone installed it does nothing. Only if I try to execute webapp as superuser does it launch the browser but doesn't execute properly. comes up to some url file://??? when it was working properly i noticed it was opening to locahost url 127.0.0.1/something - -Still seems to be running on my desktop machine though. But i did not try to remove the repository from that machine because git-annex does not provide a way to remove repository without actually deleting the files. Evidently Disable and Delete do exactly the same thing. - -Any ideas? thanks. Mike -"""]] diff --git a/doc/bugs/git-annex_webapp_command_not_found/comment_4_e4ef964274e74cb4a39dc8ecac8ceade._comment b/doc/bugs/git-annex_webapp_command_not_found/comment_4_e4ef964274e74cb4a39dc8ecac8ceade._comment deleted file mode 100644 index bc804d98a..000000000 --- a/doc/bugs/git-annex_webapp_command_not_found/comment_4_e4ef964274e74cb4a39dc8ecac8ceade._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk4_47QIHYfGlI9aL04LXxOczcYABmmIfA" - nickname="Mike" - subject="On Opensuse 13.1 - I was able to run git-annex-webapp once. " - date="2014-02-01T15:35:10Z" - content=""" -As soon as I removed my single repository it never loaded again. I have re-booted. re-installed. I have the package installed it tries to load but doesn't. I have the stand-alone installed it does nothing. Only if I try to execute webapp as superuser does it launch the browser but doesn't execute properly. comes up to some url file://??? when it was working properly i noticed it was opening to locahost url 127.0.0.1/something - -Still seems to be running on my desktop machine though. But i did not try to remove the repository from that machine because git-annex does not provide a way to remove repository without actually deleting the files. Evidently Disable and Delete do exactly the same thing. - -Any ideas? thanks. Mike -"""]] diff --git a/doc/bugs/git.kitenet.net__47__downloads_has_wrong_git-annex_branch.mdwn b/doc/bugs/git.kitenet.net__47__downloads_has_wrong_git-annex_branch.mdwn deleted file mode 100644 index ee1875e7e..000000000 --- a/doc/bugs/git.kitenet.net__47__downloads_has_wrong_git-annex_branch.mdwn +++ /dev/null @@ -1,58 +0,0 @@ -### Please describe the problem. - -This is coming from [[main repo not available on downloads.kitenet.net]], probably was the original issue, but since I already create a duplicate there, I won't assume anything (sorry about that!). - -### What steps will reproduce the problem? - -I am not sure. I know that I had an external drive with a clone of *some* repo related to `downloads.kitenet.net`. Doing a `git annex get` wouldn't work: - -<pre> -anarcat@marcos:current$ cd /media/anarcat/VHS/downloads.kitenet.net/git-annex/linux/current/ -anarcat@marcos:current$ git annex get git-annex-standalone-amd64.tar.gz -get git-annex-standalone-amd64.tar.gz (not available) - Try making some of these repositories available: - 840760dc-08f0-11e2-8c61-576b7e66acfd -- main repo - d7fa24ad-d104-4064-ad10-1078a4436e72 -- joey@elephant:~/lib/downloads -failed -git-annex: get: 1 failed -anarcat@marcos:current$ git remote -v -origin git://git.kitenet.net/downloads.git (fetch) -origin git://git.kitenet.net/downloads.git (push) -</pre> - -it turns out i somehow managed to checkout from `git://git.kitenet.net/downloads.git`. I don't know where I got this URL from, may it was back when I created that other bug report and the git URL wasn't explicitely mentionned on http://downloads.kitenet.net/ It turns out that there's a `git-annex` branch there that diverged from the "real" one, and is lacking tracking information. changing the remote here fixed the problem: - -<pre> -anarcat@marcos:current$ git remote set-url origin http://downloads.kitenet.net/.git/ -anarcat@marcos:current$ git remote update -Récupération de origin -Depuis http://downloads.kitenet.net/ - + e9febdc...1a80292 git-annex -> origin/git-annex (mise à jour forcée) -anarcat@marcos:current$ git annex get git-annex-standalone-amd64.tar.gz -get git-annex-standalone-amd64.tar.gz (from origin...) --2015-02-26 18:40:47-- http://downloads.kitenet.net/.git//annex/objects/Pm/8Z/SHA256E-s45589010--f82e2f600763b0f25a45a96ddf7ed68f26c67122e22cf8833d4c2473475bbce2.tar.gz/SHA256E-s45589010--f82e2f600763b0f25a45a96ddf7ed68f26c67122e22cf8833d4c2473475bbce2.tar.gz -Résolution de downloads.kitenet.net (downloads.kitenet.net)… 66.228.36.95, 2600:3c03::f03c:91ff:fe73:b0d2 -Connexion à downloads.kitenet.net (downloads.kitenet.net)|66.228.36.95|:80… connecté. -requête HTTP transmise, en attente de la réponse… 200 OK -[...] -</pre> - -### What version of git-annex are you using? On what operating system? - -5.20141125 on debian jessie. - -Sorry for the noise in that other bug report! I really thought it was the same issue .... --[[anarcat]] - -> The repository has a synced/git-annex that is newer, so it will be -> available if using git-annex sync. -> -> It looks like git-annex sync has not pushed git-annex:git-annex since -> [[!commit 6cdac3a003b6850fd96a60d94320d084d8651096]]. I think that commit might -> have removed that accidentially; I can't tell for sure. -> -> Adding git-annex:git-annex -> to the direct push would avoid this problem. Long as that push is not -> forced, there's no risk of overwriting other changes to the git-annex -> branch. (Even if it does get overwritten, there's no data loss; things -> will get into sync eventually.) -> -> So, I've added back the git-annex:git-annex push. [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_add_adds_unlocked_files.mdwn b/doc/bugs/git_annex_add_adds_unlocked_files.mdwn deleted file mode 100644 index 4496f3469..000000000 --- a/doc/bugs/git_annex_add_adds_unlocked_files.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -### Please describe the problem. - -git annex add . should ignore unlocked files - -### What steps will reproduce the problem? -SEE NEXT COMMENT - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_4b46116eabe61946ae65b293d7bbacb7._comment b/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_4b46116eabe61946ae65b293d7bbacb7._comment deleted file mode 100644 index 5eb35789b..000000000 --- a/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_4b46116eabe61946ae65b293d7bbacb7._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="behaving as intended" - date="2014-10-09T20:30:26Z" - content=""" -git-annex add is supposed to add unlocked files. See the documentation for the unlock command on the man page. Typical workflow is to unlock a file, edit it, add the changes, and commit it. - -Your example has 2 files with content \"foo\" and 1 file with content \"foobar\", which require 2 objects to be stored by git-annex, so that's what it stores. - -I suggest you get a bit more familiar with git-annex before filing bugs on it. -"""]] diff --git a/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_d53d0710d6ad9f0fdc8a29a98647e94b._comment b/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_d53d0710d6ad9f0fdc8a29a98647e94b._comment deleted file mode 100644 index 904cc9ebb..000000000 --- a/doc/bugs/git_annex_add_adds_unlocked_files/comment_2_d53d0710d6ad9f0fdc8a29a98647e94b._comment +++ /dev/null @@ -1,55 +0,0 @@ -[[!comment format=sh - username="https://www.google.com/accounts/o8/id?id=AItOawn0hu_TPhLcUM1Ivvn7iIoZ_iD3g_5WDcs" - nickname="Greg" - subject="comment 2" - date="2014-10-06T19:20:26Z" - content=""" -ubuntu@hostname:~$ cd annex -ubuntu@hostname:~/annex$ git init -Initialized empty Git repository in /home/ubuntu/annex/.git/ -ubuntu@hostname:~/annex$ git annex init -init ok -ubuntu@hostname:~/annex$ echo foo > test.txt -ubuntu@hostname:~/annex$ git annex add . -add test.txt (checksum...) ok -(Recording state in git...) -ubuntu@hostname:~/annex$ git commit -a -m first -[master (root-commit) fe54856] first - 1 file changed, 1 insertion(+) - create mode 120000 test.txt -ubuntu@hostname:~/annex$ git annex unlock test.txt -unlock test.txt (copying...) ok -ubuntu@hostname:~/annex$ echo foobar > test.txt -ubuntu@hostname:~/annex$ echo foo > test2.txt -ubuntu@hostname:~/annex$ git annex add . -add test2.txt (checksum...) ok -add test.txt (checksum...) ok -(Recording state in git...) -ubuntu@hostname:~/annex$ git commit -a -m second -[master 1776b25] second - 2 files changed, 2 insertions(+), 1 deletion(-) - create mode 120000 test2.txt -ubuntu@hostname:~/annex$ tree -d ./git/annex -./git/annex [error opening dir] - -0 directories -ubuntu@hostname:~/annex$ tree -d .git/annex -.git/annex -├── journal -├── objects -│ ├── 8Z -│ │ └── 1J -│ │ └── SHA256-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c -│ └── q2 -│ └── Xj -│ └── SHA256-s7--aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f -└── tmp - -9 directories -ubuntu@hostname:~/annex$ ls -test2.txt test.txt -ubuntu@hostname:~/annex$ - - -I'm expecting 3 SHA's in .git/annex, but I only see two. -"""]] diff --git a/doc/bugs/git_annex_add_ignores_some_files__47__directories.mdwn b/doc/bugs/git_annex_add_ignores_some_files__47__directories.mdwn deleted file mode 100644 index 45af8d76a..000000000 --- a/doc/bugs/git_annex_add_ignores_some_files__47__directories.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -### Please describe the problem. -After I run "git annex add" some folders (not empty) in current directory remain unannexed and git shows them as untracked. Even git annex add "problemDirName" does nothing. git annex add --force doesn't help either. - -### What steps will reproduce the problem? -No idea :( sometimes it happens and sometimes not. - -### What version of git-annex are you using? On what operating system? -5.20141013 on Debian testing - -### Please provide any additional information below. - -git add works fine. It correctly stages the files. - -This is regular repository (not direct). - -EDIT: -It seems that all the problem directories have either .git directory in them (I understand that git cannot manage .git but what about all the other files in there?) or are full of symlinks (git annex cannot manage symlinks?) - -> You should `git add` symlinks. They are not large files, so -> are out of scope for git-annex. -> -> Git repositories cannot contain other git repositories. [[done]] -> --[[Joey]] diff --git a/doc/bugs/git_annex_addurl___40__+quvi__41___should_filter_out_the___124_____40__pipe__41___character.mdwn b/doc/bugs/git_annex_addurl___40__+quvi__41___should_filter_out_the___124_____40__pipe__41___character.mdwn deleted file mode 100644 index 89f101498..000000000 --- a/doc/bugs/git_annex_addurl___40__+quvi__41___should_filter_out_the___124_____40__pipe__41___character.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -git annex addurl will keep the »|« symbol in the filename generated from the video title when using quvi. This should be filtered out as the resulting file cannot copied to fat filesystems and may cause other problems. - -### What steps will reproduce the problem? - - kasimon@pc:~/annex/YouTube/Kids$ git annex addurl --fast https://www.youtube.com/watch?v=OmXd6l54O8M - addurl Reinhard_Mey_singt_Ernie_und_Bert__Über_den_Wolken__|_NDR.webm ok - (Recording state in git...) - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20131221 - build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - local repository version: 3 - default repository version: 3 - supported repository versions: 3 5 - upgrade supported from repository versions: 0 1 2 4 - - Ubuntu 13.10 - -### Please provide any additional information below. - -> Ah, I see, pipe is not considered to be punctuation, but a math symbol. -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository.mdwn b/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository.mdwn deleted file mode 100644 index 61a01d73f..000000000 --- a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -I set up a systemd unit to start the assistant, which works fine (it uses --autostart). When it comes time to stop the unit, however, it calls git annex assistant --stop, which fails because the current directory doesn't have a git annex repository in it. - - git-annex version: 5.20140717 - build flags: Assistant Inotify DBus Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt bup directory rsync web tahoe glacier ddar hook external - -Here's my unit file: -[[!format ini """ -[Service] -ExecStart=/usr/bin/git-annex assistant --autostart -ExecStop=/usr/bin/git-annex assistant --stop - -[Install] -WantedBy=default.target -"""]] - -> This seems to overlap with [[todo/server-level_daemon__63__/]] in some way... --[[anarcat]] - -> Added --autostop and improved the docuemntation for --stop. [[done]] -> --[[Joey]] diff --git a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_1_a4cb3f759a1b076851c92fa8f9cca1be._comment b/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_1_a4cb3f759a1b076851c92fa8f9cca1be._comment deleted file mode 100644 index 24f24455f..000000000 --- a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_1_a4cb3f759a1b076851c92fa8f9cca1be._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-29T15:22:57Z" - content=""" -Well, --stop is intended to stop the daemon in the current git repository, -not all of them. That would be --autostop or something not implemented. - -I don't see how this is a bug. Feature request at best. -"""]] diff --git a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_2_953e6d1262728da6d30f4d3f1dd8fc29._comment b/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_2_953e6d1262728da6d30f4d3f1dd8fc29._comment deleted file mode 100644 index a58c1094b..000000000 --- a/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository/comment_2_953e6d1262728da6d30f4d3f1dd8fc29._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="db48x" - subject="comment 2" - date="2015-04-29T22:56:47Z" - content=""" -Well, the usage just says - - --stop stop daemon - -so naturally I assumed that this is how you stop the daemon. It's cool though; systemd can just send it a SIGKILL or whatever. -"""]] diff --git a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88.mdwn b/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88.mdwn deleted file mode 100644 index c374c6d57..000000000 --- a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -lsof got updated to version 4.88 some days ago (in archlinux) and since then the assistant reports the Committer crashed while parsing lsof output. - -After reverting to the previous version (4.87), it's working fine. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_1_e159e00e2ec7c128fda2190dc7d4c5ea._comment b/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_1_e159e00e2ec7c128fda2190dc7d4c5ea._comment deleted file mode 100644 index 915180a0c..000000000 --- a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_1_e159e00e2ec7c128fda2190dc7d4c5ea._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-11-10T17:07:17Z" - content=""" -Could you get me a sample of lsof output from this version? -git-annex runs lsof with the options `-F0can` which is supposed to -produce a machine-parsable output. - -A full command line would be something like: `lsof -F0can +d ~` -"""]] diff --git a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_2_d4ff043ebca6028105d6e38ee4020e7c._comment b/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_2_d4ff043ebca6028105d6e38ee4020e7c._comment deleted file mode 100644 index 9636edd19..000000000 --- a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_2_d4ff043ebca6028105d6e38ee4020e7c._comment +++ /dev/null @@ -1,539 +0,0 @@ -[[!comment format=mdwn - username="https://renaud.casenave.fr/" - subject="comment 2" - date="2014-11-11T04:35:57Z" - content=""" -Hi, - -Here it is: - - % lsof -v - lsof version information: - revision: 4.88 - latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/ - latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ - latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man - constructed: Wed Oct 29 13:53:05 PDT 2014 - constructed by and on: builduser@anatol - compiler: cc - compiler version: 4.9.1 20140903 (prerelease) (GCC) - compiler flags: -DLINUXV=316002 -DGLIBCV=220 -DHASIPv6 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAS_STRFTIME -DLSOF_VSTR=\"3.16.2\" -O - loader flags: -L./lib -llsof - system info: Linux anatol 3.17.1-1-ARCH #1 SMP PREEMPT Wed Oct 15 15:04:35 CEST 2014 x86_64 GNU/Linux - Only root can list all files. - /dev warnings are disabled. - Kernel ID check is disabled. - - % lsof -F0can +d ~ - p476csh - fcwda n/home/raz - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - f255arn/home/raz/.xsession - p483cdbus-launch - f8arnpipe - p486cuim-xim - fcwda n/home/raz - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - f6arnpipe - f9awnpipe - f11arnpipe - f14awnpipe - p487cuim-toolbar-gtk - fcwda n/home/raz - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - p488cclfswm - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - p490cuim-helper-serv - fcwda n/home/raz - f2awn/home/raz/.xsession-errors - p491csbcl - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - f10awnpipe - f11arnpipe - f12awnpipe - f13arnpipe - f14awnpipe - f15arnpipe - f16awnpipe - f17arnpipe - f18awnpipe - f19arnpipe - f20awnpipe - f21arnpipe - p492cmozc_server - fcwda n/home/raz - f1awn/home/raz/.xsession-errors - f2awn/home/raz/.xsession-errors - f6arnpipe - f9awnpipe - p580cld-linux-x86-64 - f4arnpipe - f5awnpipe - f13awnpipe - f15arnpipe - f18awnpipe - f19arnpipe - f22awnpipe - f23arnpipe - f25awnpipe - f26arnpipe - p591cgit - f0arnpipe - f1awnpipe - p621cld-linux-x86-64 - f4arnpipe - f5awnpipe - f15awnpipe - f16arnpipe - f18awnpipe - f19arnpipe - f23awnpipe - f24arnpipe - f25awnpipe - f26arnpipe - p649cgit - f0arnpipe - f1awnpipe - p656cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f16awnpipe - f18arnpipe - f19awnpipe - f20arnpipe - f21arnpipe - p673cssh - f0arnpipe - f1awnpipe - f2awnpipe - p703cgit - f0arnpipe - f1awnpipe - p719cld-linux-x86-64 - f4arnpipe - f5awnpipe - f13awnpipe - f15arnpipe - f18awnpipe - f19arnpipe - f20awnpipe - f22arnpipe - f24awnpipe - f25arnpipe - p743cgit - f0arnpipe - f1awnpipe - p745cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f18awnpipe - f19arnpipe - f20awnpipe - f21arnpipe - f22arnpipe - p762cssh - f0arnpipe - f1awnpipe - f2awnpipe - p804cgit - f0arnpipe - f1awnpipe - p836cld-linux-x86-64 - f4arnpipe - f5awnpipe - f15awnpipe - f16arnpipe - f18awnpipe - f19arnpipe - f22awnpipe - f23arnpipe - f25awnpipe - f26arnpipe - p858cgit - f0arnpipe - f1awnpipe - p865cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p868cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p878cld-linux-x86-64 - f4arnpipe - f5awnpipe - f13awnpipe - f15arnpipe - f18awnpipe - f19arnpipe - f20awnpipe - f22arnpipe - f24awnpipe - f25arnpipe - p901cgit - f0arnpipe - f1awnpipe - p914cld-linux-x86-64 - f4arnpipe - f5awnpipe - f13awnpipe - f15arnpipe - f18awnpipe - f19arnpipe - f22awnpipe - f23arnpipe - f25awnpipe - f26arnpipe - p936cgit - f0arnpipe - f1awnpipe - p952cld-linux-x86-64 - f4arnpipe - f5awnpipe - f9awnpipe - f15arnpipe - f18awnpipe - f19arnpipe - f22awnpipe - f23arnpipe - f25awnpipe - f26arnpipe - p956cskype - fcwda n/home/raz - f1awnpipe - f2awnpipe - f4arnpipe - f5awnpipe - f13arnpipe - f14awnpipe - f23arnpipe - f24awnpipe - f30arnpipe - f31awnpipe - f82arnpipe - f87awnpipe - p957ctrayer - fcwda n/home/raz - f1awnpipe - f2awnpipe - f6arnpipe - f7awnpipe - p961cpulseaudio - f5arnpipe - f6awnpipe - f7arnpipe - f8awnpipe - f42arnpipe - p972cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p973cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p988cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f18awnpipe - f19arnpipe - f20awnpipe - f21arnpipe - f22arnpipe - p1008cgit - f0arnpipe - f1awnpipe - p1012cssh - f0arnpipe - f1awnpipe - f2awnpipe - p1041cgconf-helper - f1awnpipe - p1081cuim-candwin-gtk - fcwda n/home/raz - f0arnpipe - f1awnpipe - f2awn/home/raz/.xsession-errors - p1087cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p1088cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f18awnpipe - f19arnpipe - f21arnpipe - f23awnpipe - f25arnpipe - p1106cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p1114cssh - f0arnpipe - f1awnpipe - f2awnpipe - p1121cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p1125cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p1159cgit - f0arnpipe - f1awnpipe - p1204cgit - f0arnpipe - f1awnpipe - p1227cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f18awnpipe - f19arnpipe - f21arnpipe - f23awnpipe - f25arnpipe - p1244cssh - f0arnpipe - f1awnpipe - f2awnpipe - p1275cgit - f0arnpipe - f1awnpipe - p1407cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p1410cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p1474cld-linux-x86-64 - f4arnpipe - f5awnpipe - f9arnpipe - f11awnpipe - f17awnpipe - f18arnpipe - f19awnpipe - f20arnpipe - f21arnpipe - p1510cssh - f0arnpipe - f1awnpipe - f2awnpipe - p1515cgit - f0arnpipe - f1awnpipe - p1522cld-linux-x86-64 - f4arnpipe - f5awnpipe - f11arnpipe - f12awnpipe - f17awnpipe - f18arnpipe - f19awnpipe - f20arnpipe - f21arnpipe - p1541cssh - f0arnpipe - f1awnpipe - f2awnpipe - p1564cgit - f0arnpipe - f1awnpipe - p1580cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p1583cssh - f2awnpipe - f6arnpipe - f7awnpipe - f8awnpipe - p1609cgit - f0arnpipe - f1awnpipe - f11arnpipe - f12awnpipe - p1610cgit - f0arnpipe - f1awnpipe - f9arnpipe - f11awnpipe - p1642cgit - f0arnpipe - f1awnpipe - p1678cgit - f0arnpipe - f1awnpipe - p1683cgit - f0arnpipe - f1awnpipe - p1687cgit - f0arnpipe - f1awnpipe - p1693cgit - f0arnpipe - f1awnpipe - p1694cgit - f0arnpipe - f1awnpipe - p1697cgit - f0arnpipe - f1awnpipe - p1716cxulrunner - fcwda n/home/raz - f0arnpipe - f10arnpipe - f11awnpipe - f12arnpipe - f13awnpipe - f14arnpipe - f15awnpipe - f19arnpipe - f20awnpipe - f28arnpipe - f29awnpipe - f49arnpipe - f52awnpipe - p1719ckonsole - fcwda n/home/raz - f0arnpipe - f4arnpipe - f6awnpipe - f12awnpipe - f16awnpipe - f19arnpipe - f20awnpipe - f25arnpipe - f26awnpipe - p1724cemacs - fcwda n/home/raz - p1740czsh - fcwda n/home/raz - p1748cat-spi-bus-laun - f5arnpipe - f6awnpipe - p1980cgpg-agent - f3arnpipe - f4awnpipe - p1989cssh - fcwda n/home/raz - p1996czsh - fcwda n/home/raz - p2600clsof - fcwda n/home/raz - f4awnpipe - f5arnpipe - p2601clsof - fcwda n/home/raz - f3arnpipe - f6awnpipe - zsh: exit 1 lsof -F0can +d ~ - -Comparing with the same command using lsof-4.87, something doesn't seem quite right: - - % lsof -v - lsof version information: - revision: 4.87 - latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/ - latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ - latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man - constructed: Thu May 30 11:05:15 UTC 2013 - constructed by and on: nobody@-var-lib-archbuild-extra-x86_64-tomegun - compiler: cc - compiler version: 4.8.0 20130502 (prerelease) (GCC) - compiler flags: -DLINUXV=38004 -DGLIBCV=217 -DHASIPv6 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAS_STRFTIME -DLSOF_VSTR=\"3.8.4\" -O - loader flags: -L./lib -llsof - system info: Linux -var-lib-archbuild-extra-x86_64-tomegun 3.9.2-1-ARCH #1 SMP PREEMPT Sat May 11 20:31:08 CEST 2013 x86_64 GNU/Linux - Only root can list all files. - /dev warnings are disabled. - Kernel ID check is disabled. - % lsof -F0can +d ~ - p476csh - a n/home/raz - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - arn/home/raz/.xsession - p486cuim-xim - a n/home/raz - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - p487cuim-toolbar-gtk - a n/home/raz - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - p488cclfswm - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - p490cuim-helper-serv - a n/home/raz - awn/home/raz/.xsession-errors - p491csbcl - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - p492cmozc_server - a n/home/raz - awn/home/raz/.xsession-errors - awn/home/raz/.xsession-errors - p956cskype - a n/home/raz - p957ctrayer - a n/home/raz - p1081cuim-candwin-gtk - a n/home/raz - awn/home/raz/.xsession-errors - p1716cxulrunner - a n/home/raz - p1719ckonsole - a n/home/raz - p1724cemacs - a n/home/raz - p1740czsh - a n/home/raz - p1989cssh - a n/home/raz - p1996czsh - a n/home/raz - p2636cconkeror-spawn- - a n/home/raz - p2638cemacsclient - a n/home/raz - p2769clsof - a n/home/raz - p2770clsof - a n/home/raz - zsh: exit 1 lsof -F0can +d ~ - -"""]] diff --git a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_3_ae25d140e01d9e2a8f76b8f892ff71ec._comment b/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_3_ae25d140e01d9e2a8f76b8f892ff71ec._comment deleted file mode 100644 index b939c29bb..000000000 --- a/doc/bugs/git_annex_assistant_crashes_when_parsing_lsof_output_for_version_4.88/comment_3_ae25d140e01d9e2a8f76b8f892ff71ec._comment +++ /dev/null @@ -1,42 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2014-11-12T21:27:48Z" - content=""" - - cat > ~/tmp/dir/foo & - lsof -F0can +d ~/tmp/dir - -Old: - -<pre> -p15304^@ccat^@ -aw^@n/home/joey/tmp/dir/foo^@ -</pre> - -New: - -</pre> -p15304^@ccat^@ -f1^@aw^@n/home/joey/tmp/dir/foo^@ -p15399^@clsof^@ -f1^@aw^@npipe^@ -f4^@aw^@npipe^@ -f5^@ar^@npipe^@ -p15401^@cless^@ -f0^@ar^@npipe^@ -p15402^@clsof^@ -f3^@ar^@npipe^@ -f6^@aw^@npipe^@ -</pre> - -It looks like the new lsof has broken/changed -F; the file descriptor field -is being showed even though -F0can does not request it. - -IMHO this is a bug in lsof. - -Additionally, the new lsof shows processes that have open pipes, even -when it's been asked to show only files under a given directory. - -I've reported these problems upstream. Easy enough to work around in git-annex's parser. -"""]] diff --git a/doc/bugs/git_annex_copy_--fast_does_not_copy_files.mdwn b/doc/bugs/git_annex_copy_--fast_does_not_copy_files.mdwn deleted file mode 100644 index 9b84c21fd..000000000 --- a/doc/bugs/git_annex_copy_--fast_does_not_copy_files.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -Workflow: - - % git annex add - # list new files - % git commit -a -m "foo" - # commit summary - % git annex copy . --to remote --fast - # all files listed with "ok" - % git annex copy . --to remote - # again, lists all files, _but the new ones are actually copied, this time_. - -This happens no matter if I - - % git push - -before copy or not. - -PS: Arguably, a copy should push automagically. - -> Whups, not supposed to be that fast! [[Fixed|done]], and -> you should run `git annex fsck --fast` on the repo you ran the -> copy in. --[[Joey]] diff --git a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant.mdwn b/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant.mdwn deleted file mode 100644 index f3b124cf6..000000000 --- a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant.mdwn +++ /dev/null @@ -1,140 +0,0 @@ -### Please describe the problem. - -Hi, - -I have a number of repos that I created both by hand and via the web-app. Some manual, some client and one backup groupings. - -When creating by hand I manually set the annex-cost to 100 (but I notice the webapp sets local costs to 175 - not 100 as per the man page). - -(I'm assuming the creation by hand is still just to `git add remote` on both sides). - -When I run `git-annex sync --content` I do seem to get the local remote (the cheapest cost) that I want. - -When I use the assistant I get every odd behaviour. It will quite happily choose from any of the available repos with no descernible pattern. - -Even more strangely sometimes it queues all the transfers to use the local connection but then at the actual transfer it switches to use the public connection (I have two remotes for one repo: when on the local network and when on the internet). This is reflected in the webapps UI. - -For the snippet of logs below I see the files queued as the remote "Dancingfrog" (on the internnal network) then for the transfer the web page switches to "Home" (the public network). I think the data is actually transferred over the public network as it's much slower than compared to explicit repo transfers from the cli. - -<pre> -[2014-04-27 05:11:47 BST] TransferWatcher: transfer starting: Download UUID "c3cec307-367b-4373-8cb9-a3da67cee745" Dizzee Rascal/Tounge N' Cheek/03 Dance Wiv Me [Ft. Calvin Harris & Chrome].mp3 Nothing -[2014-04-27 05:11:47 BST] TransferWatcher: transfer starting: Download UUID "c3cec307-367b-4373-8cb9-a3da67cee745" Dizzee Rascal/Tounge N' Cheek/03 Dance Wiv Me [Ft. Calvin Harris & Chrome].mp3 Nothing - -SHA256E-s6759929--a822e83c3448716e793fb9d1d1b1523c2492c84ba07f5c093899810fbdfe5621.mp3 - - 0 0% 0.00kB/s 0:00:00 - 163,840 2% 159.20kB/s 0:00:41 - 360,448 5% 159.56kB/s 0:00:40 - 524,288 7% 155.01kB/s 0:00:40 - 688,128 10% 154.59kB/s 0:00:39 - 851,968 12% 153.18kB/s 0:00:38 [2014-04-27 05:11:54 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","ls-tree","--full-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","numcopies.log","schedule.log","preferred-content.log","required-content.log","group-preferred-content.log"] - - 1,015,808 15% 149.92kB/s 0:00:38 To gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mus - 617edaf..f016a03 git-annex -> synced/git-annex -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","git-annex"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","isilon","master"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..f016a03fc92aebba14b239cc3647478b1fb9f78f","--oneline","-n1"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..7339a1fdd007d7a528b7e2eb82c2aeedca511920","--oneline","-n1"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..00f5e110ca77b9b5103e1b568ea6aa9d9d9dbb81","--oneline","-n1"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..ab90c337053a61111060540d2f60ce20b44cc2d9","--oneline","-n1"] -[2014-04-27 05:11:56 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..88d99a7ef2d37d1a6180e5dd66a4559927a58eaf","--oneline","-n1"] - - 1,146,880 16% 98.64kB/s 0:00:56 - 1,507,328 22% 129.55kB/s 0:00:40 - 1,671,168 24% 126.84kB/s 0:00:40 [2014-04-27 05:12:00 BST] Pusher: Syncing with dancingfrog, rss, isilon -[2014-04-27 05:12:00 BST] chat: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","hash-object","-w","--stdin-paths","--no-filters"] -[2014-04-27 05:12:00 BST] feed: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","update-index","-z","--index-info"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -(Recording state in git...) -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","write-tree"] -[2014-04-27 05:12:00 BST] chat: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","commit-tree","86e5513adfc0d1f64cabd3ca3902738d45d809ad","-p","refs/heads/git-annex"] -[2014-04-27 05:12:00 BST] call: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","update-ref","refs/heads/git-annex","8808dc8effc3572ae1421461ff44574e900917bf"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","symbolic-ref","HEAD"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","refs/heads/master"] -[2014-04-27 05:12:00 BST] Pusher: pushing to [Remote { name ="dancingfrog" },Remote { name ="rss" },Remote { name ="isilon" }] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","git-annex"] -[2014-04-27 05:12:00 BST] call: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","branch","-f","synced/master"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -[2014-04-27 05:12:00 BST] call: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","dancingfrog","+git-annex:synced/git-annex","master:synced/master"] -[2014-04-27 05:12:00 BST] call: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","rss","+git-annex:synced/git-annex","master:synced/master"] -[2014-04-27 05:12:00 BST] call: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","isilon","+git-annex:synced/git-annex","master:synced/master"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..8808dc8effc3572ae1421461ff44574e900917bf","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..7339a1fdd007d7a528b7e2eb82c2aeedca511920","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..00f5e110gcrypt: Development version -- Repository format MAY CHANGE -ca77b9b5103e1b568ea6aa9d9d9dbb81","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..f016a03fc92aebba14b239cc3647478b1fb9f78f","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..ab90c337053a61111060540d2f60ce20b44cc2d9","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..88d99a7ef2d37d1a6180e5dd66a4559927a58eaf","--oneline","-n1"] -To ssh://10.23.33.19/Volumes/Media/iTunes Media/Music - f016a03..8808dc8 git-annex -> synced/git-annex -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","git-annex"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","dancingfrog","master"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..8808dc8effc3572ae1421461ff44574e900917bf","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..7339a1fdd007d7a528b7e2eb82c2aeedca511920","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..00f5e110ca77b9b5103e1b568ea6aa9d9d9dbb81","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..ab90c337053a61111060540d2f60ce20b44cc2d9","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..f016a03fc92aebba14b239cc3647478b1fb9f78f","--oneline","-n1"] -[2014-04-27 05:12:00 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..88d99a7ef2d37d1a6180e5dd66a4559927a58eaf","--oneline","-n1"] - - 1,835,008 27% 125.00kB/s 0:00:39 To rss:Music - f016a03..8808dc8 git-annex -> synced/git-annex -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","git-annex"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","rss","master"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..8808dc8effc3572ae1421461ff44574e900917bf","--oneline","-n1"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..7339a1fdd007d7a528b7e2eb82c2aeedca511920","--oneline","-n1"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..00f5e110ca77b9b5103e1b568ea6aa9d9d9dbb81","--oneline","-n1"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..ab90c337053a61111060540d2f60ce20b44cc2d9","--oneline","-n1"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..f016a03fc92aebba14b239cc3647478b1fb9f78f","--oneline","-n1"] -[2014-04-27 05:12:01 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..88d99a7ef2d37d1a6180e5dd66a4559927a58eaf","--oneline","-n1"] -gcrypt: Decrypting manifest -gpg: Signature made Sun 27 Apr 2014 05:11:41 BST using DSA key ID 29C42E01 -gpg: Good signature from "Matt Ford (Work) <matt.ford@manchester.ac.uk>" -gpg: aka "Matt Ford <matt@dancingfrog.co.uk>" -gcrypt: Encrypting to: -R 68D8501429C42E01 -gcrypt: Requesting manifest signature -gpg: 68D8501429C42E01: skipped: public key already present - - 1,998,848 29% 180.87kB/s 0:00:26 - 2,162,688 31% 135.56kB/s 0:00:33 To gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mus - f016a03..8808dc8 git-annex -> synced/git-annex -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","git-annex"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","show-ref","--hash","refs/heads/git-annex"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","push","isilon","master"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..8808dc8effc3572ae1421461ff44574e900917bf","--oneline","-n1"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..7339a1fdd007d7a528b7e2eb82c2aeedca511920","--oneline","-n1"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..00f5e110ca77b9b5103e1b568ea6aa9d9d9dbb81","--oneline","-n1"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..ab90c337053a61111060540d2f60ce20b44cc2d9","--oneline","-n1"] -[2014-04-27 05:12:03 BST] read: git ["--git-dir=/home/matt/Music/.git","--work-tree=/home/matt/Music","log","refs/heads/git-annex..88d99a7ef2d37d1a6180e5dd66a4559927a58eaf","--oneline","-n1"] - - 2,326,528 34% 139.74kB/s 0:00:31 - 3,637,248 53% 397.83kB/s 0:00:07 - 4,423,680 65% 556.91kB/s 0:00:04 - 5,079,040 75% 692.27kB/s 0:00:02 - 5,636,096 83% 781.05kB/s 0:00:01 - -× Synced with dancingfrog, rss, isilon -× Downloaded 11 Bad Be..viour.mp3 10 Holida..rome].mp3 09 Leisure.mp3 08 Money Money.mp3 07 Dirtee Cash.mp3 06 Chilli..n Dem.mp3 05 Can't .. More.mp3 04 Freaky..reaky.mp3 03 Dance ..rome].mp3 02 Road Rage.mp3 and 8 other files -× Synced with rss -× Performed startup scan -× Synced with dancingfrog, isilon -</pre> - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -[[!meta title="transferkeys protocol needs to include remote name to deal with multiple remotes with same UUID"]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_1_ab82b880bd75a206e0717146e1b79aba._comment b/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_1_ab82b880bd75a206e0717146e1b79aba._comment deleted file mode 100644 index 56d77a2d2..000000000 --- a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_1_ab82b880bd75a206e0717146e1b79aba._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 1" - date="2014-04-27T04:25:58Z" - content=""" -By the way these are indirect repos if that would make a difference. -"""]] diff --git a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_2_460e78ea8603bd87203d8014bcc3eb9a._comment b/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_2_460e78ea8603bd87203d8014bcc3eb9a._comment deleted file mode 100644 index ef70e0abd..000000000 --- a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_2_460e78ea8603bd87203d8014bcc3eb9a._comment +++ /dev/null @@ -1,55 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 2" - date="2014-04-27T11:48:18Z" - content=""" -Here's the `.git/config` - -<pre> -[core] - repositoryformatversion = 0 - filemode = true - bare = false - logallrefupdates = true -[branch \"master\"] - remote = home - merge = refs/heads/master -[annex] - uuid = 105776ba-bd78-4884-9126-aeb7c1e6da21 - version = 5 - diskreserve = 100 megabytes - autoupgrade = ask - debug = true - fscknudge = true -[remote \"dancingfrog\"] - url = ssh://10.23.33.19/Volumes/Media/iTunes Media/Music - fetch = +refs/heads/*:refs/remotes/dancingfrog/* - annex-uuid = c3cec307-367b-4373-8cb9-a3da67cee745 - annex-cost = 100 - annex-sync = true -[remote \"home\"] - url = home:/Volumes/Media/iTunes Media/Music - fetch = +refs/heads/*:refs/remotes/home/* - annex-uuid = c3cec307-367b-4373-8cb9-a3da67cee745 - annex-sync = true - annex-cost = 200 -[remote \"isilon\"] - url = gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mus - fetch = +refs/heads/*:refs/remotes/isilon/* - gcrypt-participants = 68D8501429C42E01 - gcrypt-signingkey = 68D8501429C42E01 - gcrypt-id = :id:92R1j7+L9r5LuWDi2ZlW - annex-gcrypt = true - annex-uuid = 949a8fc3-6334-5f5e-887d-b1e5725ea443 - annex-sync = true - annex-cost = 250 -[remote \"rss\"] - url = rss:Music - fetch = +refs/heads/*:refs/remotes/rss/* - annex-uuid = 79ff3c20-fab3-44dd-88f7-cc1a41eb73d6 - annex-sync = true - annex-cost = 200 - -</pre> -"""]] diff --git a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_3_17e9c2d29ddadcabc30ce884ffe0f853._comment b/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_3_17e9c2d29ddadcabc30ce884ffe0f853._comment deleted file mode 100644 index 1ff0f0b61..000000000 --- a/doc/bugs/git_annex_costs_not_working_as_expected_in_the_assistant/comment_3_17e9c2d29ddadcabc30ce884ffe0f853._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="216.145.95.162" - subject="comment 3" - date="2014-05-19T16:44:19Z" - content=""" -When the assistant wants to download a file, it queues a transfer from all remotes that are known to have the file, with the lowest cost remotes first. If it fails to get the file from the lowest cost remote, it automatically falls back to the next lowest cost, and so on. - -If there's a bug here, I'd suspect strongly it's due to having 2 remotes with the same UUID. - -Yes, I think I've found it. Assistant.TransferSlots.genTransfer calls performTransfer, which is passed only the Transfer, not the Remote. So it then looks up a remote with the UUID from the Transfer. To fix this, I will need to adjust the transferkeys command's protocol to include the name of the remote that should be used. -"""]] diff --git a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn deleted file mode 100644 index 72a0c9cc3..000000000 --- a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. - -Creating two repos with the same name causes git annex dead to randomly choose one. This is reasonable except that it can choose to mark an already dead remote dead (as long as it shares the name), causing it to actually do nothing. - -I think preferring to mark live repos dead and printing a warning when multiple repos could have been chosen (or if the repo is already marked dead) would be a good solution. - -### What steps will reproduce the problem? - -[[!format sh """ -# Create a new repo /somecopy -git clone /central /somecopy -cd /somecopy -git annex init somecopy -git annex sync -cd / - -# Now, git annex status shows somecopy as an existing repo. - -# Destroy the new repo -rm -rf /somecopy -cd /central -git annex dead somecopy - -# git annex status correctly hides somecopy, and it is properly dead. - -# create it again with the same name, but new UUID -git clone /central /somecopy -cd /somecopy -git annex init somecopy -git annex sync -cd / - -# Destroy the second repo -rm -rf /somecopy -cd /central -"""]] - -Now, git annex dead somecopy will randomly (based on the order of the UUIDs?) choose to mark dead the already dead old repo or the new repo, in both cases showing success to the user. - -### What version of git-annex are you using? On what operating system? - -git-annex 4.20131024 on linux. Also occurs on OSX. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_1_7ee08a60e4b2516c010d3c2163049681._comment b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_1_7ee08a60e4b2516c010d3c2163049681._comment deleted file mode 100644 index 3875affb7..000000000 --- a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_1_7ee08a60e4b2516c010d3c2163049681._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 1" - date="2013-10-29T21:10:53Z" - content=""" -I don't think it's a good idea to give multiple repos the same description. - -You can use the uuid to refer to a repo unambiguously in this situation. - -I think it would add unncessary complication to make git-annex guess which repository you mean based on context -(ie, choosing repositories that are not already dead). This would make commands that are currently idempotent not be. - -Perhaps git-annex should abort when multiple repositories match the given description? (Relevant code is Remote.nameToUUID's bydescription) -"""]] diff --git a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_2_c29525bfda08717f68aaac83014e6b08._comment b/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_2_c29525bfda08717f68aaac83014e6b08._comment deleted file mode 100644 index 17191be04..000000000 --- a/doc/bugs/git_annex_dead_does_not_work_as_expected_when_multiple_repos_exist_with_the_same_name___40__notably_including_dead_ones__41__/comment_2_c29525bfda08717f68aaac83014e6b08._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmGxww5ON3nilm7moGQCWJPnMEdRwNvb7U" - nickname="Chris" - subject="comment 2" - date="2013-10-29T22:01:04Z" - content=""" -I didn't think about idempotency. Erroring out seems like the best option now. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9.mdwn b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9.mdwn deleted file mode 100644 index 2169372a2..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9.mdwn +++ /dev/null @@ -1,220 +0,0 @@ -### Please describe the problem. -git-annex crashes on Max OS X 10.9 at startup - -### What steps will reproduce the problem? -- install Mac OS X 10.9 developer preview -- download and install the latest git-annex from here http://downloads.kitenet.net/git-annex/OSX/current/10.8.2_Mountain_Lion/ (I tried with the 10.8 version) -- attempt to start it, see it crashing - -### What version of git-annex are you using? On what operating system? -- latest version that is available for 10.8, on 10.9 DP 2 - -### Please provide any additional information below. - -I see the following in Console: - -15.07.2013 21:20:49,362 com.apple.launchd.peruser.501[259]: (com.branchable.git-annex.103872[67263]) Exited with code: 133 -15.07.2013 21:20:49,546 ReportCrash[67272]: Saved crash report for git-annex[67268] version ??? to /Users/stelianiancu/Library/Logs/DiagnosticReports/git-annex_2013-07-15-212049_poseidon-2.crash - -And the crash is as follows: - -Process: git-annex [67268] -Path: /Applications/git-annex.app/Contents/MacOS/bundle/git-annex -Identifier: git-annex -Version: ??? -Code Type: X86-64 (Native) -Parent Process: sh [67263] -Responsible: sh [67263] -User ID: 501 - -Date/Time: 2013-07-15 21:20:48.946 +0200 -OS Version: Mac OS X 10.9 (13A497d) -Report Version: 11 -Anonymous UUID: 634E8812-1F1A-11E0-61DA-7527061A194C - -Sleep/Wake UUID: AFC18477-57D2-4B69-8B0F-AE26BC3D9D0C - -Crashed Thread: 0 - -Exception Type: EXC_BREAKPOINT (SIGTRAP) -Exception Codes: 0x0000000000000002, 0x0000000000000000 - -Application Specific Information: -dyld: launch, loading dependent libraries - -Dyld Error Message: - Symbol not found: _objc_debug_taggedpointer_mask - Referenced from: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - Expected in: /Applications/git-annex.app/Contents/MacOS/bundle/I - in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - -Binary Images: - 0x104412000 - 0x10450fff7 +E (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /Applications/git-annex.app/Contents/MacOS/bundle/E - 0x104547000 - 0x10455bfff +F (0) <FA90B1B1-A866-3A6C-BB97-06955F4C8C0B> /Applications/git-annex.app/Contents/MacOS/bundle/F - 0x104567000 - 0x104594ff7 +G (0) <E276B5C2-6FAC-36A7-940B-7A75322F71AE> /Applications/git-annex.app/Contents/MacOS/bundle/G - 0x10459c000 - 0x104669fdf +H (0) <29C3AFF5-8EFB-3A16-81F6-0DA6CF2675A6> /Applications/git-annex.app/Contents/MacOS/bundle/H - 0x104699000 - 0x1046abff7 +B (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /Applications/git-annex.app/Contents/MacOS/bundle/B - 0x1046b1000 - 0x1047a6fff +D (34) <FEE8B996-EB44-37FA-B96E-D379664DEFE1> /Applications/git-annex.app/Contents/MacOS/bundle/D - 0x1047b7000 - 0x1048cf92f +I (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /Applications/git-annex.app/Contents/MacOS/bundle/I - 0x1048f6000 - 0x104af6fff +S (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /Applications/git-annex.app/Contents/MacOS/bundle/S - 0x104c06000 - 0x104c2bff7 +Z (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /Applications/git-annex.app/Contents/MacOS/bundle/Z - 0x104c5e000 - 0x104cc6ff7 +0A (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /Applications/git-annex.app/Contents/MacOS/bundle/0A - 0x104d21000 - 0x104d8afff +0B (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /Applications/git-annex.app/Contents/MacOS/bundle/0B - 0x104df3000 - 0x104e06fff +T (0) <DB28CA35-537D-3644-A6BE-179D1A1E9785> /Applications/git-annex.app/Contents/MacOS/bundle/T - 0x104e0e000 - 0x104e1bff7 +U (0) <DCFF385A-090B-3407-868C-91544A2EFEE1> /Applications/git-annex.app/Contents/MacOS/bundle/U - 0x104e1f000 - 0x104e41ff7 +V (0) <51B317C7-94CC-3C58-B515-924BB3AF0BCC> /Applications/git-annex.app/Contents/MacOS/bundle/V - 0x104e4e000 - 0x104e5bff7 +W (0) <91CF16BE-027F-3FE6-B1EE-6B8BFD51FC1B> /Applications/git-annex.app/Contents/MacOS/bundle/W - 0x104e68000 - 0x104ec4fd7 +X (0) <84D934AF-A321-36C0-BBCF-CD3FDAEB0B95> /Applications/git-annex.app/Contents/MacOS/bundle/X - 0x7fff6ca9d000 - 0x7fff6cad04a7 dyld (237) <BB7160C2-117E-3369-87F0-866ED454490E> /usr/lib/dyld - 0x7fff8ba5b000 - 0x7fff8ba5dfff libCVMSPluginSupport.dylib (9.0.74) <11FCA581-0FFD-37B1-966A-E47F4722D297> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib - 0x7fff8c053000 - 0x7fff8c05affb liblaunch.dylib (842.1.1) <7055DF9E-52CE-3746-96EB-3718DDBF0BD0> /usr/lib/system/liblaunch.dylib - 0x7fff8c11d000 - 0x7fff8c41cff7 com.apple.Foundation (6.9 - 1042) <CE00D0BB-1053-3EA0-A31F-C9F1E3FEFBF2> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation - 0x7fff8c41d000 - 0x7fff8c444ff7 libsystem_network.dylib (241.3) <D518703F-4C71-3CC5-99EF-A15C8F41A834> /usr/lib/system/libsystem_network.dylib - 0x7fff8c445000 - 0x7fff8c47eff7 com.apple.QD (3.49 - 297) <EE1DD6BE-5881-35C7-A9E8-30CCB26E6CF3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD - 0x7fff8c483000 - 0x7fff8c864ffe libLAPACK.dylib (1094.4) <19E25957-74BA-3770-AAB5-B6A05F19BDC2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib - 0x7fff8c8bc000 - 0x7fff8c8cbff8 com.apple.LangAnalysis (1.7.0 - 1.7.0) <ED300EBD-7AEF-34B4-B314-DFBD648214E1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis - 0x7fff8c8cc000 - 0x7fff8c8d9ff7 libxar.1.dylib (202) <E0BFCC9B-89D4-3F42-8460-4918573EFCA1> /usr/lib/libxar.1.dylib - 0x7fff8c8da000 - 0x7fff8cbaaff4 com.apple.CoreImage (9.0.33) <8BB17AEC-D09A-3173-8767-7DB5C982670E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage - 0x7fff8cbab000 - 0x7fff8cbabff7 libkeymgr.dylib (28) <AB6DE146-DDC4-397B-9182-ECE54FCDF5D7> /usr/lib/system/libkeymgr.dylib - 0x7fff8d095000 - 0x7fff8d09eff7 com.apple.speech.synthesis.framework (4.5.3 - 4.5.3) <B4B4F401-701F-3A6E-AB39-65BDBB9F3FA0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis - 0x7fff8d21a000 - 0x7fff8d274ff8 com.apple.AE (665.2 - 665.2) <DB39E7DF-E5EA-3D5C-81A5-1BA2159A2694> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE - 0x7fff8d2fb000 - 0x7fff8d342ff7 libcups.2.dylib (365) <49F3E642-D748-3A60-AF51-F9E90F65C543> /usr/lib/libcups.2.dylib - 0x7fff8d343000 - 0x7fff8d350ff0 libbz2.1.0.dylib (29) <C1100E81-9C9D-3E4E-B238-F4015BB35B15> /usr/lib/libbz2.1.0.dylib - 0x7fff8d489000 - 0x7fff8d489fff com.apple.Accelerate (1.9 - Accelerate 1.9) <94C28250-6BDB-30AD-B157-995D9C34A6FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate - 0x7fff8d75b000 - 0x7fff8d7a8fff com.apple.opencl (2.3.50 - 2.3.50) <33C1EC76-02A2-3474-BB9D-8F77B96E57CC> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL - 0x7fff8dd58000 - 0x7fff8dd5dff7 libunwind.dylib (35.3) <838CE69D-44F1-305C-8FA5-5E439D217F78> /usr/lib/system/libunwind.dylib - 0x7fff8dd5e000 - 0x7fff8dd61fff libCoreVMClient.dylib (58.1) <331C429A-3AE5-30B8-A4DE-1BF4EE4D8FA6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib - 0x7fff8de3e000 - 0x7fff8de3fff7 libDiagnosticMessagesClient.dylib (100) <B28C426E-E826-3EC3-80AD-E69F2EABE46B> /usr/lib/libDiagnosticMessagesClient.dylib - 0x7fff8de40000 - 0x7fff8de6ffff com.apple.DebugSymbols (106 - 106) <545E5A48-3516-3398-A33D-D6FB4FED4B7B> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols - 0x7fff8e4b2000 - 0x7fff8e500fff libcorecrypto.dylib (161) <56048D2C-3668-3E15-AF02-5C5A377320F6> /usr/lib/system/libcorecrypto.dylib - 0x7fff8e501000 - 0x7fff8e5c7ff7 com.apple.LaunchServices (572.3 - 572.3.1) <39618733-CC97-3991-BD3B-485BD7247115> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices - 0x7fff8e5ca000 - 0x7fff8e5caffd libOpenScriptingUtil.dylib (154) <9B8CECA0-360D-3C6D-A37D-95EE34AE2B16> /usr/lib/libOpenScriptingUtil.dylib - 0x7fff8e9ac000 - 0x7fff8e9b4ff7 com.apple.speech.recognition.framework (4.2.4 - 4.2.4) <1CE37DE8-BA4A-30CD-A802-18DAF42C328F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition - 0x7fff8ea01000 - 0x7fff8ea65ff6 com.apple.Heimdal (4.0 - 2.0) <463F41AC-39FF-30FC-B03A-4198E7A9321F> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal - 0x7fff8ea66000 - 0x7fff8ea6efff libsystem_dnssd.dylib (522.1.3) <29695A12-75FC-36EE-97AC-179F6E9DA419> /usr/lib/system/libsystem_dnssd.dylib - 0x7fff8eb28000 - 0x7fff8eb33fff libGL.dylib (9.0.74) <2DB19533-5983-3F59-93F3-2761DA6EEDA5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib - 0x7fff8eb37000 - 0x7fff8eb43ff3 com.apple.AppleFSCompression (56 - 1.0) <D80DF0B8-AC14-3686-9242-9750D6A8B8D3> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression - 0x7fff8eb44000 - 0x7fff8f44a043 com.apple.CoreGraphics (1.600.0 - 565) <81F84822-675E-3466-97A7-6FF69DF569E3> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics - 0x7fff8f44b000 - 0x7fff8f461fff com.apple.CFOpenDirectory (10.9 - 171) <A650D21D-D825-3C4E-AA2E-1218F8A5048E> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory - 0x7fff9003c000 - 0x7fff900c5fe7 libsystem_c.dylib (997) <5BAB0B09-A39E-39B9-9552-48B540B3ABD0> /usr/lib/system/libsystem_c.dylib - 0x7fff9088e000 - 0x7fff908b2fff libJPEG.dylib (1029) <D161F451-9A14-31DD-83D8-C475F8576ACF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib - 0x7fff908b3000 - 0x7fff908f7ffe com.apple.HIServices (1.22 - 454) <3625AF2C-1965-349D-B831-1FCC9084B675> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices - 0x7fff908f8000 - 0x7fff90bc7fdf com.apple.vImage (7.0 - 7.0) <C50F8737-E292-3D53-9AF7-F76797A1DDDD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage - 0x7fff90ce8000 - 0x7fff90d03ff7 libsystem_kernel.dylib (2422.1.26.0.1) <5F99677C-C760-3877-AFF7-F60B5ECE365E> /usr/lib/system/libsystem_kernel.dylib - 0x7fff90d04000 - 0x7fff90d77ffb com.apple.securityfoundation (6.0 - 55122) <A946CA5A-1396-3467-94B1-E6A8FA0347FC> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation - 0x7fff90e98000 - 0x7fff91034fff com.apple.QuartzCore (1.8 - 329.0) <08CE1885-71E8-3A38-AEB6-4BBB1A43785F> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore - 0x7fff91035000 - 0x7fff91050ff7 libPng.dylib (1029) <AB7D23B2-CB41-3108-A19E-9F7BA6F37178> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib - 0x7fff910c3000 - 0x7fff9113aff7 com.apple.CoreServices.OSServices (600 - 600) <73820122-62D4-359C-9312-CD49FCEDFE09> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices - 0x7fff9115a000 - 0x7fff911e5fff com.apple.Metadata (10.7.0 - 778.1) <93F05A4E-6581-3CD5-8697-84783CEBF764> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata - 0x7fff9139d000 - 0x7fff913a4ff3 libcopyfile.dylib (103) <54DD5730-3F05-3F18-B55C-24EA9546286F> /usr/lib/system/libcopyfile.dylib - 0x7fff9152c000 - 0x7fff91530ff7 libheimdal-asn1.dylib (323.3) <90100758-0CC6-3D00-90AB-D3C7DC8CCE45> /usr/lib/libheimdal-asn1.dylib - 0x7fff9193c000 - 0x7fff91947fff libkxld.dylib (2422.1.26.0.1) <CF43FD8E-E8FE-34F7-A3B1-286530AA9EFD> /usr/lib/system/libkxld.dylib - 0x7fff9194e000 - 0x7fff91950ff7 libquarantine.dylib (69) <1776AABC-F1D7-3CB0-B698-B0C70D4E535B> /usr/lib/system/libquarantine.dylib - 0x7fff91951000 - 0x7fff9195efff com.apple.Sharing (112 - 112) <24BA2112-4FFB-318A-B881-93FEB4648371> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing - 0x7fff919fb000 - 0x7fff91a02ff7 libsystem_pthread.dylib (53) <2160EC74-26FC-32CE-8161-B1A72D2B09B0> /usr/lib/system/libsystem_pthread.dylib - 0x7fff91a03000 - 0x7fff91a2cfff com.apple.DictionaryServices (1.2 - 197) <862F498E-3CB7-3087-BB07-AC185D5D08F8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices - 0x7fff91a3c000 - 0x7fff91b04ff7 libvDSP.dylib (423.29) <72A38066-D6F5-38EC-A8B9-0D025AFC6E2B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib - 0x7fff91b05000 - 0x7fff91b43ff7 libGLImage.dylib (9.0.74) <0DD99DA1-A8E7-3309-8DED-A2AB410E59C8> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib - 0x7fff92ade000 - 0x7fff92b00fff libxpc.dylib (300.1.4) <4F832032-9709-3E80-91C4-71914C67A32B> /usr/lib/system/libxpc.dylib - 0x7fff92b01000 - 0x7fff92b04ff7 libdyld.dylib (237) <EA2A0414-849F-3976-BA4E-A93D3206ECE5> /usr/lib/system/libdyld.dylib - 0x7fff92b05000 - 0x7fff92b05fff com.apple.ApplicationServices (48 - 48) <21188B7D-50E8-3C28-A15E-5345AE7BAFBB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices - 0x7fff92b08000 - 0x7fff92b6cff7 com.apple.datadetectorscore (5.0 - 343.0) <7FE14856-0C85-3382-AD6C-1B9E21C276CB> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore - 0x7fff92b6d000 - 0x7fff92b6fff3 libsystem_configuration.dylib (596.1) <1E0FDEA3-8822-3E80-AA0D-57D0F4E30E2E> /usr/lib/system/libsystem_configuration.dylib - 0x7fff92e00000 - 0x7fff92e53fff com.apple.ScalableUserInterface (1.0 - 1) <A82F7DD8-1C79-3872-96D1-875B4ED121D4> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface - 0x7fff92e72000 - 0x7fff92e73fff libunc.dylib (28) <53C7CED6-55F5-3121-B00E-4339C29297C8> /usr/lib/system/libunc.dylib - 0x7fff92e91000 - 0x7fff92f53ff9 com.apple.CoreText (352.0 - 367.6) <CAFF0767-3351-3FE3-843F-6EA65B8264C8> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText - 0x7fff934c7000 - 0x7fff934e2ff7 libCRFSuite.dylib (34) <E2353929-97B1-356A-84A0-CC650BC734D5> /usr/lib/libCRFSuite.dylib - 0x7fff934e3000 - 0x7fff93508ffb com.apple.CoreVideo (1.8 - 117.0) <50587BF1-D111-3D49-9DAB-8F86B5E95808> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo - 0x7fff93509000 - 0x7fff93522ff7 com.apple.Kerberos (3.0 - 1) <13DDC487-95C0-379F-BD7F-E0FC5F5922D3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos - 0x7fff93523000 - 0x7fff935a2fff com.apple.CoreSymbolication (3.0 - 137) <85C4F6E2-5039-3E53-9AB2-6D65CAC9AAC5> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication - 0x7fff935a3000 - 0x7fff935bdfff libsystem_malloc.dylib (23.1.1) <FBCF2C62-AA8D-322E-859E-B5D90C610A3F> /usr/lib/system/libsystem_malloc.dylib - 0x7fff935bf000 - 0x7fff93600ff7 com.apple.PerformanceAnalysis (1.45 - 45) <6C498B15-45DB-362F-983B-764ECC9B8E21> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis - 0x7fff9360f000 - 0x7fff93618ff3 libsystem_notify.dylib (121) <D34E9B17-297F-3C3F-BD16-69D1D9495B79> /usr/lib/system/libsystem_notify.dylib - 0x7fff93619000 - 0x7fff9362bff7 com.apple.MultitouchSupport.framework (245.12 - 245.12) <06CAA8FB-BEC6-3EF1-96FA-3D8A1EEB0959> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport - 0x7fff9367e000 - 0x7fff9368efff libbsm.0.dylib (33) <65C2FC5C-4B4B-3C1B-B935-D67A3BF96A79> /usr/lib/libbsm.0.dylib - 0x7fff937f6000 - 0x7fff937fafff libpam.2.dylib (20) <17E3DA0D-EE71-3398-BA30-BDD8514A6135> /usr/lib/libpam.2.dylib - 0x7fff93aea000 - 0x7fff93aedfff libsystem_stats.dylib (93.1.8.1.1) <CAC30E07-CE62-3536-8CD4-1A3CE44DD973> /usr/lib/system/libsystem_stats.dylib - 0x7fff93b96000 - 0x7fff93d79ff7 com.apple.CoreFoundation (6.9 - 842) <DC8875C4-DC2C-3ADC-B88B-D66722953255> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - 0x7fff93d7a000 - 0x7fff93db9fff libGLU.dylib (9.0.74) <294F4F86-E900-356C-9A47-0C47A929F2FB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib - 0x7fff93dba000 - 0x7fff93e9cff7 com.apple.backup.framework (1.5 - 1.5) <70E20485-EDB6-3225-8AF6-6D9494CB98B7> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup - 0x7fff93edb000 - 0x7fff93ee6ff7 com.apple.NetAuth (5.0 - 5.0) <64D42204-C075-3440-8C29-BBD68A99A771> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth - 0x7fff93ee7000 - 0x7fff93ef3fff com.apple.OpenDirectory (10.9 - 171) <FDE80473-0ADF-363A-8111-43CAB01A3F61> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory - 0x7fff93f3a000 - 0x7fff93f48ff7 com.apple.opengl (9.0.74 - 9.0.74) <9BD0013A-E503-3DA2-9F94-C42A11D2E734> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL - 0x7fff93f56000 - 0x7fff93f85ff5 com.apple.GSS (4.0 - 2.0) <6765C9D7-8AC9-3694-B5D4-5C26B119851D> /System/Library/Frameworks/GSS.framework/Versions/A/GSS - 0x7fff943f6000 - 0x7fff943fdfff libcompiler_rt.dylib (35) <A0A9D62C-E1A5-39A0-A38E-B0B38762002D> /usr/lib/system/libcompiler_rt.dylib - 0x7fff943fe000 - 0x7fff94404fef libsystem_platform.dylib (24) <5D8FE8C3-2A62-3705-AB7D-FBD7C284AFBD> /usr/lib/system/libsystem_platform.dylib - 0x7fff94405000 - 0x7fff9440fff7 com.apple.CrashReporterSupport (10.9 - 529) <F3BB7C5D-0775-3A05-944A-3A061E62B107> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport - 0x7fff94428000 - 0x7fff9442bffc com.apple.IOSurface (91 - 91) <1B7746FC-3599-3BDB-A0DA-65795C999435> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface - 0x7fff9442c000 - 0x7fff944dbff7 libvMisc.dylib (423.29) <83CBEBB6-B9C2-3D83-A32A-CED47CDB65D6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib - 0x7fff9451b000 - 0x7fff9451cffb libremovefile.dylib (33) <D7EF6E8B-95D8-3D8E-918C-2D3F51D00060> /usr/lib/system/libremovefile.dylib - 0x7fff9465b000 - 0x7fff94898fff com.apple.CoreData (107 - 468) <51F9B655-84D2-3E88-991B-914C9017BB08> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData - 0x7fff948ab000 - 0x7fff948acfff com.apple.TrustEvaluationAgent (2.0 - 25) <644D981B-A5A7-31F5-99A6-9F180B9A5DE3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent - 0x7fff948ad000 - 0x7fff948d0fff com.apple.IconServices (25 - 25.4) <525BAAE5-F45C-3A15-ACED-2AF4EFFED546> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices - 0x7fff948f6000 - 0x7fff94be0ff7 com.apple.CoreServices.CarbonCore (1077.6 - 1077.6) <C32B5E2A-3BD8-3D6C-A931-E05B47ECB3C9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore - 0x7fff94be1000 - 0x7fff94c09ffb libxslt.1.dylib (13) <33D39746-6FCD-3F32-AFAE-2E45232BF6FB> /usr/lib/libxslt.1.dylib - 0x7fff94c0a000 - 0x7fff94c14ff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <3E92DCA9-DA23-34E1-8C38-DA7488621FFB> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement - 0x7fff94c15000 - 0x7fff94c1ffff libcommonCrypto.dylib (60049) <FC0D70F5-E485-32E6-BFC2-1E072047282B> /usr/lib/system/libcommonCrypto.dylib - 0x7fff94c94000 - 0x7fff94d82fff libJP2.dylib (1029) <720403F5-7863-30D6-AC09-F5A04F069E1B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib - 0x7fff94daf000 - 0x7fff94dc8ff3 com.apple.Ubiquity (1.3 - 280) <581DAEFC-B314-3F92-93CF-7B70BF22AEEF> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity - 0x7fff95037000 - 0x7fff9513cfff com.apple.ImageIO.framework (3.2.0 - 1029) <FEF93B49-D136-3248-B46B-C026F7E906BD> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO - 0x7fff9513d000 - 0x7fff9526aff7 com.apple.desktopservices (1.8 - 1.8) <ACF9A2F5-6285-316E-958A-25C0AFDF3AEA> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv - 0x7fff9526b000 - 0x7fff95273ffc libGFXShared.dylib (9.0.74) <13A420C1-1B14-36F8-8F08-4698D423E52F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib - 0x7fff95274000 - 0x7fff9528cff7 com.apple.GenerationalStorage (2.0 - 158) <5BCFBEED-09D2-3BD3-8EE0-85E809C47380> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage - 0x7fff952b3000 - 0x7fff9533cff7 com.apple.ColorSync (4.9.0 - 4.9.0) <CBF9EA13-4FC4-34D8-812A-6A37189CD09E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync - 0x7fff95361000 - 0x7fff953baff7 libTIFF.dylib (1029) <12303E45-734B-3D6C-A5C8-1495ECBC0344> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib - 0x7fff9548c000 - 0x7fff954d9ff2 com.apple.print.framework.PrintCore (9.0 - 424) <B09BB55A-67C0-34F9-95DB-6F735842EAE5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore - 0x7fff954e4000 - 0x7fff95547ff3 com.apple.SystemConfiguration (1.13 - 1.13) <73B50935-DFE8-31B8-8583-27A28B5A9D1E> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration - 0x7fff955ac000 - 0x7fff955c6fff libdispatch.dylib (339.1.2) <A9C37B4E-B908-3212-BF59-CE336EC30E78> /usr/lib/system/libdispatch.dylib - 0x7fff95ca6000 - 0x7fff95ca7ff3 libSystem.B.dylib (1197) <7589D08E-9338-3E28-AA74-9734F0D51CE0> /usr/lib/libSystem.B.dylib - 0x7fff95cb3000 - 0x7fff95cfaff3 libFontRegistry.dylib (121.1) <C8BC9042-B3EA-35FB-B4D7-2B1A6E0E6AB5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib - 0x7fff95cfb000 - 0x7fff95deafff libFontParser.dylib (106) <16B9215D-3244-365F-910F-FA033495E3F5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib - 0x7fff95deb000 - 0x7fff95debfff com.apple.Cocoa (6.8 - 20) <B2519A80-93F8-3BEB-A6B2-780B0D291E89> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa - 0x7fff95e0f000 - 0x7fff95e10fff liblangid.dylib (117) <5146A22B-088F-3D8D-B245-F03DD3CDA2B0> /usr/lib/liblangid.dylib - 0x7fff95e11000 - 0x7fff9696ffff com.apple.AppKit (6.9 - 1240) <53CEC6E0-F928-32EC-919D-B34C0818C88C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit - 0x7fff96970000 - 0x7fff96977fff com.apple.NetFS (6.0 - 4.0) <553EA9F4-7B2C-371A-AF03-4B709A730582> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS - 0x7fff96978000 - 0x7fff969c8ffa com.apple.audio.CoreAudio (4.2.0 - 4.2.0) <548AC059-62DD-3CF6-B083-CABE454AFA38> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio - 0x7fff96a12000 - 0x7fff96a7cff7 com.apple.framework.IOKit (2.0.1 - 907.1.5) <BC9D0F47-DB6F-3AD0-B38F-267E891099D0> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit - 0x7fff96add000 - 0x7fff96ae0fff com.apple.TCC (1.0 - 1) <1DF1D216-1355-3E4F-B4BE-3E3BA5A696EB> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC - 0x7fff96ae1000 - 0x7fff96b06ff7 com.apple.ChunkingLibrary (2.0 - 154) <EBFF01E3-D26B-3031-9E4C-670303B1086A> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary - 0x7fff96b07000 - 0x7fff96b0bff7 libGIF.dylib (1029) <000B8500-FC82-3016-8E59-9FA0D6395F04> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib - 0x7fff96b58000 - 0x7fff96b59ff7 libsystem_blocks.dylib (63) <7836104E-39B9-31B6-A0C7-C02ACD401ADE> /usr/lib/system/libsystem_blocks.dylib - 0x7fff96db9000 - 0x7fff96db9ffd com.apple.audio.units.AudioUnit (1.9 - 1.9) <BBAD4575-CE0A-34EF-A5AF-36CD66FF260C> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit - 0x7fff96df6000 - 0x7fff96e07fff libsystem_asl.dylib (217) <F8795719-7E14-3FB2-8F4D-FF814AFFB7F7> /usr/lib/system/libsystem_asl.dylib - 0x7fff96e2d000 - 0x7fff96e5cfd2 libsystem_m.dylib (3047.15) <8A6B4EC2-BB25-342B-B3FE-9585175225B8> /usr/lib/system/libsystem_m.dylib - 0x7fff96e5d000 - 0x7fff96fb3ff3 com.apple.audio.toolbox.AudioToolbox (1.9 - 1.9) <D3F44C67-987D-3955-B15F-74A27C7E59E3> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox - 0x7fff96fb4000 - 0x7fff9709ffff libsqlite3.dylib (155) <F60CCD67-FA68-379E-9D9C-4085E06F5665> /usr/lib/libsqlite3.dylib - 0x7fff970a0000 - 0x7fff97348ff9 com.apple.HIToolbox (2.1 - 681) <F25DDDC9-D3BC-3E80-A57D-EC1FE747B40B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox - 0x7fff97349000 - 0x7fff97383ffb com.apple.bom (12.0 - 192) <FE625F33-643C-310A-B931-14CEBC007302> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom - 0x7fff97758000 - 0x7fff97759ff7 libsystem_sandbox.dylib (278.1) <F723F1D9-5561-344A-A6F0-B1373D355DBA> /usr/lib/system/libsystem_sandbox.dylib - 0x7fff977fb000 - 0x7fff977fbfff com.apple.Accelerate.vecLib (3.9 - vecLib 3.9) <349BA8B4-1C72-30BE-B2BB-1898F51B9B5E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib - 0x7fff97939000 - 0x7fff97aa2ff3 com.apple.CFNetwork (657 - 657) <59A9476F-19A2-3F8B-A9B0-8531EA36A4AE> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork - 0x7fff97ac9000 - 0x7fff97b20fff com.apple.Symbolication (1.4 - 125) <C3269812-583B-3349-A675-CCCFDF3140DB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication - 0x7fff97b24000 - 0x7fff97b93ff1 com.apple.ApplicationServices.ATS (360 - 360) <8A3AD47D-2777-3019-80BB-4B17AA055E13> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS - 0x7fff97c01000 - 0x7fff97c28ff3 libsystem_info.dylib (449) <B5F10962-3DA2-3557-A0B1-369BB80EA6A5> /usr/lib/system/libsystem_info.dylib - 0x7fff97d95000 - 0x7fff97e21ff7 com.apple.ink.framework (10.9 - 205) <A3B23363-D876-39CF-9290-F01520C484E3> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink - 0x7fff97e22000 - 0x7fff97f04fff com.apple.coreui (2.1 - 224) <9F8C1983-1795-34DA-A0C1-7F126ECA0D8E> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI - 0x7fff97f4d000 - 0x7fff97fbafff com.apple.SearchKit (1.4.0 - 1.4.0) <EACE2CF5-06EA-3899-9208-F9914C1922BD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit - 0x7fff98062000 - 0x7fff982b6ff0 com.apple.security (7.0 - 55377) <2F4EFC9E-DD86-32E5-A2CB-E83A5DF34F8F> /System/Library/Frameworks/Security.framework/Versions/A/Security - 0x7fff982b7000 - 0x7fff982bbff7 libcache.dylib (61) <E9CD6B70-0553-3808-87DA-D16A1A6AC3FB> /usr/lib/system/libcache.dylib - 0x7fff982bc000 - 0x7fff982c1fff com.apple.DiskArbitration (2.6 - 2.6) <4D7487BB-C4A7-32DB-BEE2-CE55EA7F40B2> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration - 0x7fff9838e000 - 0x7fff9838efff com.apple.CoreServices (59 - 59) <D84FB78F-0F3C-3383-AE76-4BD6E3173F7F> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices - 0x7fff983e0000 - 0x7fff98418ff7 com.apple.RemoteViewServices (2.0 - 94) <7E7B5F1F-9F0E-3DF7-B6B9-152DFD2DFFC7> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices - 0x7fff987c8000 - 0x7fff987e4fff libresolv.9.dylib (54) <78D891A1-6F8B-34D4-8F0D-59DB6DF53411> /usr/lib/libresolv.9.dylib - 0x7fff987e5000 - 0x7fff987eafff libmacho.dylib (845) <0038681B-CEC4-348A-A7B8-4236C701F2F8> /usr/lib/system/libmacho.dylib - 0x7fff98802000 - 0x7fff98844ff7 libauto.dylib (185.4) <379FBDA3-DB2A-35A3-A637-3893C0F0E52F> /usr/lib/libauto.dylib - 0x7fff9890a000 - 0x7fff98d3dff7 com.apple.vision.FaceCore (3.0.0 - 3.0.0) <14255DCC-80BD-3690-9269-057D175A9FC5> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore - 0x7fff98d66000 - 0x7fff98ed4ff7 libBLAS.dylib (1094.4) <80E99B02-BD2D-3D88-97B6-0BE2D8973633> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib - 0x7fff98f6b000 - 0x7fff98f6dfff libRadiance.dylib (1029) <4E13C7E9-9B17-33D3-9142-B645B5BBCCD6> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib - 0x7fff98f6e000 - 0x7fff98f77ffe com.apple.CommonAuth (4.0 - 2.0) <3918EBA0-A124-37DC-9BA6-4D1370AF03A8> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth - - - -[[!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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_10_141819a6b67de2602673698f6f148106._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_10_141819a6b67de2602673698f6f148106._comment deleted file mode 100644 index db4d3e269..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_10_141819a6b67de2602673698f6f148106._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="calmyournerves" - ip="85.3.250.239" - subject="comment 10" - date="2013-10-24T20:47:19Z" - content=""" -I was able to successfully build git-annex on Mac OS X 10.9. - -See https://gist.github.com/calmyournerves/7144127 for instructions. -I tried to document every step I made, but I'm not sure if I forgot to write down anything. - -Let me know if it works for you. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_11_8be96359fd2bd33ed2961e499dc2685e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_11_8be96359fd2bd33ed2961e499dc2685e._comment deleted file mode 100644 index d166e8c67..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_11_8be96359fd2bd33ed2961e499dc2685e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="warp" - ip="2001:4b98:dc0:45:216:3eff:fe83:3d9" - subject="comment 11" - date="2013-10-25T07:29:04Z" - content=""" -I was able to build git-annex on the work laptop with these steps: - -1. Make sure xcode is up-to-date. -2. Download and install \"Command Line Tools (OS X Mavericks) for Xcode - Late October 2013\" from https://developer.apple.com/downloads/ after logging in as a developer. -3. Follow the \"brew\" instructions at http://git-annex.branchable.com/install/OSX/ -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_12_26950a37e86d4dd83dd59fb2564d0a2e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_12_26950a37e86d4dd83dd59fb2564d0a2e._comment deleted file mode 100644 index b05d26c0b..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_12_26950a37e86d4dd83dd59fb2564d0a2e._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="imagejan" - ip="134.99.222.172" - subject="comment 12" - date="2013-10-25T13:37:13Z" - content=""" -I was able to build the git-annex.app OSX app using @calmyournerves instructions (see comment 10), but only after adding the 'async' dependency to the git-annex.cabal file. - -Command line works great now, but I wasn't able to run the git-annex-assistant :( - -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_13_cbf8150dbe0da64bde7f6af8e041eda8._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_13_cbf8150dbe0da64bde7f6af8e041eda8._comment deleted file mode 100644 index 94d962cd8..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_13_cbf8150dbe0da64bde7f6af8e041eda8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI" - nickname="Zellyn" - subject="Mac hardware" - date="2013-10-25T17:30:38Z" - content=""" -If someone had time to set up a campaign to buy you a Mac Mini, I'd chip in $20 :-) -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_14_0c203f90d911cf6869894dae89575a49._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_14_0c203f90d911cf6869894dae89575a49._comment deleted file mode 100644 index 591123175..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_14_0c203f90d911cf6869894dae89575a49._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="calmyournerves" - ip="85.3.250.239" - subject="comment 14" - date="2013-10-25T18:43:01Z" - content=""" -@imagejan: -What errors did you get before adding async to the cabal file? -What's the problem with the assistant? Running git-annex webapp as well as simply opening git-annex.app both worked for me. - -@Zellyn: -That's certainly a good idea and I would support it. But running multiple versions of OS X is tricky, Parallels allows this iirc (VM's). -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_15_68cbb7268bdad73357da2d11e05d73c4._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_15_68cbb7268bdad73357da2d11e05d73c4._comment deleted file mode 100644 index 07e76fcb8..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_15_68cbb7268bdad73357da2d11e05d73c4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="Remy" - ip="83.87.21.84" - subject="comment 15" - date="2013-10-25T18:51:32Z" - content=""" -I now got both the CLI and web app working but I had to switch to gcc-4.7 to work around a compiler preprocessing error and back to the default gcc to get fsevents to compile. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_16_816d552f871a1b06306f04d575adb2e5._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_16_816d552f871a1b06306f04d575adb2e5._comment deleted file mode 100644 index 96f379dcf..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_16_816d552f871a1b06306f04d575adb2e5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkQafKy7hNSEolLs6TvbgUnkklTctUY9LI" - nickname="Zellyn" - subject="Earmarked donations?" - date="2013-10-25T21:51:19Z" - content=""" -Joeyh, is it possible to earmark donations? We could set up a wiki page to track progress, and try to buy you a Mac Mini... -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_17_7905b097a9c582452fb04cdc88ed4285._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_17_7905b097a9c582452fb04cdc88ed4285._comment deleted file mode 100644 index c67cc7add..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_17_7905b097a9c582452fb04cdc88ed4285._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.47" - subject="comment 17" - date="2013-10-26T16:58:27Z" - content=""" -I'm glad that it's been gotten to build. - -Now all we need is for someone like @calmyournerves or @warp or @remy to put \"git pull; make osxapp\" in a cron job. I can provide a rsync account for publishing the DMG file, and help with setting up [gitbuilder](https://github.com/apenwarr/gitbuilder) which is one good way to automate it. - -Or, if someone else with a Mavericks desktop machine wants to install ssh and make me an account, I'm sure I can follow the instructions and set up an autobuilder on it. - -To be clear, I don't have time or interest in maintaining hardware to run the builds, even if I had the hardware. It's much better to let people who are passionate about it do it. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_18_bd5ac9bb2eaab66af6aa13b39172b49d._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_18_bd5ac9bb2eaab66af6aa13b39172b49d._comment deleted file mode 100644 index 903a41364..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_18_bd5ac9bb2eaab66af6aa13b39172b49d._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://jspk.clavid.com/" - nickname="flabbergast" - subject="comment 18" - date="2013-10-27T19:29:01Z" - content=""" -I've also just upgraded and had to compile git-annex (following @calmyournerves' instructions). I've made a dmg, so if anyone out there doesn't feel like compiling, you can get 4.20131027-g9230b07 for Mavericks temporarily [here (7z for saving bandwidth)](https://freeshell.de/~teatime/git-annex-4.20131027-g9230b07.dmg.7z). -(I've used my laptop, and I don't want to set it up for automatic building; I'll see if I can set up my work mac for that.) -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_19_9881db7bb6fef4e47c54cdc23e995f17._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_19_9881db7bb6fef4e47c54cdc23e995f17._comment deleted file mode 100644 index 96356e047..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_19_9881db7bb6fef4e47c54cdc23e995f17._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnt7phVzBQ0xO5rCO6sfmEmxQItmFMyqls" - nickname="Kevin" - subject="comment 19" - date="2013-11-02T00:58:31Z" - content=""" -I tried @flabbergast's dmg. It seems to work fine (including the web app) on my Air, but the web app fails on my iMac with - - $ git annex webapp - Launching web browser on file:///Users/kw/Desktop/annex/.git/annex/webapp.html - error: git-annex died of signal 4 - $ -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_1_4fb9d3de245dddab65fb1a53a67a095c._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_1_4fb9d3de245dddab65fb1a53a67a095c._comment deleted file mode 100644 index d73e8cb06..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_1_4fb9d3de245dddab65fb1a53a67a095c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://siancu.myopenid.com/" - nickname="siancu" - subject="I could help with this" - date="2013-07-15T19:29:26Z" - content=""" -I could help to track down this bug however I would need some assistance on where to start :) -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_20_41e2ea458669f59f96b5860825745910._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_20_41e2ea458669f59f96b5860825745910._comment deleted file mode 100644 index fca9ba58e..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_20_41e2ea458669f59f96b5860825745910._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnt7phVzBQ0xO5rCO6sfmEmxQItmFMyqls" - nickname="Kevin" - subject="comment 20" - date="2013-11-02T01:02:18Z" - content=""" -Also, to avoid hurt feelings etc., it might be best to make it clear on your home page and kickstarter that you do not intend to support OS X yourself. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_21_515039e321e0595f95430d8082bd54a5._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_21_515039e321e0595f95430d8082bd54a5._comment deleted file mode 100644 index a0a175d30..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_21_515039e321e0595f95430d8082bd54a5._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 21" - date="2013-11-08T19:22:17Z" - content=""" -Now that I can try running the 10.8 dmg on 10.9 myself, I get this failure: - -<pre> -oberon:~ joeyh$ /Volumes/git-annex/git-annex.app/Contents/MacOS/git-annex -dyld: Symbol not found: _objc_debug_taggedpointer_mask - Referenced from: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation - Expected in: /Volumes/git-annex/git-annex.app/Contents/MacOS/bundle/I - in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation -</pre> - -This makes me think that that adding back the OSX frameworks might possibly yield a dmg that can work on both versions. Although that's probably more likely to work if it's built on 10.8 and used on 10.9 than the other way around. Might be worth a try to revert commit 900351ab8585c171486cef853eff4a95ec151e6f and commit 9b663c7f8cf82cee523b75be1a8786fa7d34b428 to try that. - -Oh well, I should have a native 10.9 dmg autobuild set up before too long. 10.8 autobuilder has built its last image unfortunately, due to being upgraded to 10.9. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_22_9412236296871c570c66f5b4c7f9681e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_22_9412236296871c570c66f5b4c7f9681e._comment deleted file mode 100644 index e5942bfd4..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_22_9412236296871c570c66f5b4c7f9681e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 22" - date="2013-11-14T18:55:54Z" - content=""" -Native 10.9 autobuilder is now running. <https://downloads.kitenet.net/git-annex/autobuild/x86_64-apple-mavericks/git-annex.dmg.bz2> - -Lacks XMPP support until I get libxml2 linked on the autobuilder. Only tested on the build machine so far. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_23_e4e7d13be6c0bc63f426e535de6172f8._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_23_e4e7d13be6c0bc63f426e535de6172f8._comment deleted file mode 100644 index db8d835d2..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_23_e4e7d13be6c0bc63f426e535de6172f8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw" - nickname="Carl" - subject="comment 23" - date="2013-11-14T19:22:16Z" - content=""" -Seems to work on my Mavericks Macbook Air. Thank you! -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_24_c73e1277c5f284b1019362fb2bef94a8._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_24_c73e1277c5f284b1019362fb2bef94a8._comment deleted file mode 100644 index c3a0d3bec..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_24_c73e1277c5f284b1019362fb2bef94a8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmL8pteP2jbYJUn1M3CbeLDvz2SWAA1wtg" - nickname="Kristian" - subject="comment 24" - date="2013-11-17T17:01:14Z" - content=""" -Thanks Joey! It works great -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_2_f513259a2641e00b049203014ab940c8._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_2_f513259a2641e00b049203014ab940c8._comment deleted file mode 100644 index 6bf0a17f4..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_2_f513259a2641e00b049203014ab940c8._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.4.90" - subject="comment 2" - date="2013-07-15T20:12:04Z" - content=""" -AIUI, the git-annex dmg bundles several libraries and things that are not portable between OSX versions. So, the fix is probably to build git-annex from source on OS X 10.9. - -Following the [[install/cabal]] instructions would be a good first step to see if that gets a working git-annex. - -It seems likely that an autobuilder machine will need to be added for OS X 10.9 eventually. Maybe the guy who's providing the Mtn Lion build machine plans to upgrade it, and I can use that. Otherwise, it'll probably depend on someone with a 10.9 machine either setting up an autobuilder, or giving me a ssh account so I can run one. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_3_54ee7b90467fee8b0457e9c447747500._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_3_54ee7b90467fee8b0457e9c447747500._comment deleted file mode 100644 index cdff138ad..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_3_54ee7b90467fee8b0457e9c447747500._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://siancu.myopenid.com/" - nickname="siancu" - subject="comment 3" - date="2013-07-16T07:18:35Z" - content=""" -I got some problems building gpm on 10.9, will have to dig a bit more and see what's going on. It might be my environment. But for now I can't build gpm, thus no gnutls. I could try to build and install git-annex only without the assistant and webapp. - -BTW, how is the .app file generated? Is there an Xcode project or something like that? -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_4_7e6223c2dae3346e17276c7bbb01d53e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_4_7e6223c2dae3346e17276c7bbb01d53e._comment deleted file mode 100644 index f613f296e..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_4_7e6223c2dae3346e17276c7bbb01d53e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.4.90" - subject="comment 4" - date="2013-07-16T17:48:54Z" - content=""" -The dmg is built by running \"make osxapp\", once you've gotten git-annex to build. - -gnutls is only needed by the XMPP code. You can build without that, using `cabal configure -f-XMPP; cabal build` - -(If you're building from a git checkout, building w/o XMPP was broken the past couple days; make sure you update to current head.) -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment deleted file mode 100644 index 33c1319b3..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_5_13b6e595d595da7f036e81258a65541e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://siancu.myopenid.com/" - nickname="siancu" - subject="comment 5" - date="2013-07-16T19:52:28Z" - content=""" -Ok, I will try without XMPP. However I'm going to need it, because, if I understood correctly, it is needed to do remote pairings. But for now I can manage without as I can take the laptop with me to work and to syncing locally. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_6_94144c0cbdbccc72c13e12daf7657a29._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_6_94144c0cbdbccc72c13e12daf7657a29._comment deleted file mode 100644 index fbb519bdd..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_6_94144c0cbdbccc72c13e12daf7657a29._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlYsjf5dcZnzs0b9EPxnjVddx1rnrpZASs" - nickname="Duarte" - subject="Any news?" - date="2013-08-31T15:48:39Z" - content=""" -Has anyone made any progress on this? Just wondering... -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_7_9eb064ffdc3fdb70e85572185e151a3f._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_7_9eb064ffdc3fdb70e85572185e151a3f._comment deleted file mode 100644 index db8e707cd..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_7_9eb064ffdc3fdb70e85572185e151a3f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmBcKrChzs1mdF5pxnenPuMOaJBKfbeRVY" - nickname="Raffael" - subject="bump" - date="2013-10-24T07:03:56Z" - content=""" -As Mavericks is now the current version of Mac OS X, it would be cool to have a working DMG for it. Any news here? -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_8_cde756e8a9b18fe2ca9cda25967bc7fb._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_8_cde756e8a9b18fe2ca9cda25967bc7fb._comment deleted file mode 100644 index 708f21a79..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_8_cde756e8a9b18fe2ca9cda25967bc7fb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="67.223.1.203" - subject="comment 8" - date="2013-10-24T17:14:06Z" - content=""" -As I don't own any mac hardware, and don't plan to buy any, and I don't know of a way to just spin up a OSX VM in the cloud, I'm reliant on git-annex users for running builds for the various versions of OS X. - -I think there's a chance that one of the two people currently doing builds for older versions will upgrade their system. Although of course then we lose builds for that older version. Alternatively, I'm waiting for someone to either volenteer to set up a builder for 10.9, or give me ssh access to a machine were I can do it. -"""]] diff --git a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_9_1fd6a4374a334bc03914c3e0df95ef95._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_9_1fd6a4374a334bc03914c3e0df95ef95._comment deleted file mode 100644 index d70d0a872..000000000 --- a/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_9_1fd6a4374a334bc03914c3e0df95ef95._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="67.223.1.203" - subject="comment 9" - date="2013-10-24T17:27:04Z" - content=""" -Anyone trying to compile git-annex on OSX 10.9 will need to be aware of and work around this problem: -<http://justtesting.org/post/64947952690/the-glasgow-haskell-compiler-ghc-on-os-x-10-9> -<http://www.haskell.org/pipermail/haskell-cafe/2013-September/110320.html> -"""]] diff --git a/doc/bugs/git_annex_drop_direct_creates_symlinks_with_possibly_incorrect_path_separator.mdwn b/doc/bugs/git_annex_drop_direct_creates_symlinks_with_possibly_incorrect_path_separator.mdwn deleted file mode 100644 index e0c501c90..000000000 --- a/doc/bugs/git_annex_drop_direct_creates_symlinks_with_possibly_incorrect_path_separator.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. - -On windows, path separator of symlinks created by drop command is different than the one created by checkout/update, leading to incorrect git annex status reporting - -### What steps will reproduce the problem? - -Checkout a repo in direct mode on windows, you'll see symlinks as such (using the 'unix' path separator): - - ../../../.git/annex/objects/p1/GM/SHA256E-s921877--4801f74cb608bdcea1f7f7a50a874865c87d03bc6fff3d16e2b9d216b4c231 ..... etc. - -get the content, and then drop it, the symlink which is then recreated has different path separator: - - ..\..\..\.git\annex\objects\p1\GM\SHA256E-s921877--4801f74cb608bdcea1f7f7a50a874865c87d03bc6fff3d16e2b9d216b4c231 ----- etc. - -resulting in misreported git annex status: - - git annex statua - M dropped.file.name - -changing the path separator seemingly solves: - - sed -e 's/\\\/\\//g' dropped.file.name -i - git annex dropped.file.name - .... nothing reported .... - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20150128-g2df3a02 - running on Microsoft Windows [Version 6.1.7601] - - -### Please provide any additional information below. - -no additional info. - -> I see that I broke this some time ago. Fixed it now, and added a test -> case. [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_fsck_loops.mdwn b/doc/bugs/git_annex_fsck_loops.mdwn deleted file mode 100644 index ae3d6aec0..000000000 --- a/doc/bugs/git_annex_fsck_loops.mdwn +++ /dev/null @@ -1,91 +0,0 @@ -### Please describe the problem. - -It seems i have a somewhat corrupted git repository here, not sure how it happened. I was expecting the magic git annex fsck to recover from this, especially since this is a secondary repository and all objects should be available on the remotes... - -### What steps will reproduce the problem? - -I am really not sure, but i ended up with empty objects in my git repo. - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20141125 - -### 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 -anarcat@angela:films$ git annex addurl --fast https://www.youtube.com/watch?v=bS5P_LAqiVg -addurl KUNG_FURY_Official_Movie__HD_.mp4 error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -anarcat@angela:films$ git fsck -Vérification des répertoires d'objet: 100% (256/256), fait. -error: object file .git/objects/00/ef80c0eefb0ec6ad70c9270bd5780fa3b124b0 is empty -error: object file .git/objects/00/ef80c0eefb0ec6ad70c9270bd5780fa3b124b0 is empty -fatal: loose object 00ef80c0eefb0ec6ad70c9270bd5780fa3b124b0 (stored in .git/objects/00/ef80c0eefb0ec6ad70c9270bd5780fa3b124b0) is corrupt - -anarcat@angela:films$ git annex fsck -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt -error: object file /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b is empty -fatal: loose object bff9dc76b05081c33471b9a2bccdb8d86ab06c3b (stored in /home/anarcat/video/.git/objects/bf/f9dc76b05081c33471b9a2bccdb8d86ab06c3b) is corrupt - -git-annex: fd:13: hGetLine: end of file -failed - -git-annex: fd:12: hFlush: resource vanished (Broken pipe) -failed - -[...] - -git-annex: fd:12: hFlush: resource vanished (Broken pipe) -failed - -git-annex: fd:12: commitBuffer: resource vanished (Broken pipe) -failed - -git-annex: fd:12: commitBuffer: resource vanished (Broken pipe) -failed - -[...] - -git-annex: fd:12: commitBuffer: resource vanished (Broken pipe) -failed -^C -# End of transcript or log. -"""]] - ---[[anarcat]] - -Ah damnit, i confused [[git-annex-fsck]] and [[git-annex-repair]]... :/ Mabe one should run the other when it fails? :) sorry for the noise, [[done]]. diff --git a/doc/bugs/git_annex_fsck_on_btrfs_devices.mdwn b/doc/bugs/git_annex_fsck_on_btrfs_devices.mdwn deleted file mode 100644 index 7ed827b78..000000000 --- a/doc/bugs/git_annex_fsck_on_btrfs_devices.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -### Please describe the problem. -btrfs automatically validates checksums when data is read. If a checksum fails, instead of giving the corrupted file contents, the read will throw an I/O error. In result, it seems that git-annex fsck will not recognize the file as faulty, and will instead fail with a sha1sum parse error, without dropping the corresponding file as “bad”. - -[[!format sh """ -git annex fsck file -fsck file (checksum...) -sha1sum: .git/annex/objects/…: Input/output error -git-annex: sha1sum parse error -# End of transcript or log. -"""]] - -### What version of git-annex are you using? On what operating system? -git-annex 5.20150508 -linux 4.0.4 - -> [[fixed|done]]; IO errors are now detected and the file moved to bad/; -> the fsck also continues past that failure now, so if a disk has -> a lot of damanged files, it will find them all. --[[Joey]] diff --git a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment b/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment deleted file mode 100644 index d186370d3..000000000 --- a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_1_f33d4cb9689f89f07bb97460e4f30be8._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 1" - date="2015-05-24T15:07:34Z" - content=""" -I suppose since an I/O error can be intermittent, the file can’t be outright regarded as bad. Also I’m not sure whether the read system call returns a dedicated error code for checksum errors. -"""]] diff --git a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_2_fe050712ea067df80f8d8c52d90d24d9._comment b/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_2_fe050712ea067df80f8d8c52d90d24d9._comment deleted file mode 100644 index 8d2e95161..000000000 --- a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_2_fe050712ea067df80f8d8c52d90d24d9._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-05-27T19:10:48Z" - content=""" -Similar thing could happen on non-btrfs, if a disk sector -is bad, or the disk has gone walkabout, you might get back an -IO error reading it sometimes. And it could well be an intermittent error. - -`git annex fsck` already says "failed" and exits nonzero (immediately!) -when this happens. It just doesn't move the file to the `bad` directory. - -I've improved the "sha1sum parse error" to instead be -"sha1sum failed" in the case where the command exited nonzero. - -Moving everything to `bad` on what could be an -intermittent error risks overkill. OTOH, if the whole disk is gone, -it can make any changes it likes, it won't affect the actual disk. ;) - -On balance, I think fsck should assume that an IO error is something it -should fix, and so it should move such files to `bad/`. With care taken to -differentiate between a disk IO error and eg, a broken sha1sum command that -fails to run, or a permissions problem reading the file, or whatever. -"""]] diff --git a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_3_dfcef745c92ec629f82ec6acc14d1519._comment b/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_3_dfcef745c92ec629f82ec6acc14d1519._comment deleted file mode 100644 index ec277f9c2..000000000 --- a/doc/bugs/git_annex_fsck_on_btrfs_devices/comment_3_dfcef745c92ec629f82ec6acc14d1519._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 3" - date="2015-05-28T13:09:23Z" - content=""" -Thanks! If it’s just for one file, it’s probably okay to move it to bad. If the error was intermittent, one can try reinjecting the content. - -As for the risk of overkill, I don’t know enough about how the SATA/SCSI subsystem handles things. The cornercase would be one where (say due to EM interference) the SATA connection is reset and the device driver reports read errors for lots and lots of files, but the drive comes back in time so that these files are erroneously moved to bad. However, I guess you do the “move to bad” action file by file, and the whole fsck fails if moving to bad fails. In this case, we probably wouldn’t bite the cornercase, because when the drive comes back online, at most one file is moved to “bad“ erroneously. -"""]] diff --git a/doc/bugs/git_annex_ignores_GIT__95__SSH__63__.mdwn b/doc/bugs/git_annex_ignores_GIT__95__SSH__63__.mdwn deleted file mode 100644 index c0e634872..000000000 --- a/doc/bugs/git_annex_ignores_GIT__95__SSH__63__.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -### Please describe the problem. -I'm attempting to set up an ssh remote on windows. I've configured a key pair for it and set GIT_SSH to use plink. git fetch works correctly, but git annex info shows this: - -[[!format sh """ -C:\Users\db48x\annex>git annex info -repository mode: direct -trusted repositories: "ssh": argonath: no address associated with name - - Remote argonath does not have git-annex installed; setting annex-ignore -"""]] - -etc. Apparently it's trying to use the included ssh binary instead of my GIT_SSH setting. - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20140529-gb71f9bf - build flags: Assistant Pairing Testsuite S3 DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 2 3 4 - -> [[dup|done]] of [[todo/git-annex_ignores_GIT__95__SSH]] --[[Joey]] diff --git a/doc/bugs/git_annex_importfeed_not_working_on_youtube_playlists.mdwn b/doc/bugs/git_annex_importfeed_not_working_on_youtube_playlists.mdwn deleted file mode 100644 index 2306642fc..000000000 --- a/doc/bugs/git_annex_importfeed_not_working_on_youtube_playlists.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -### Please describe the problem. -The [podcasts page](https://git-annex.branchable.com/tips/downloading_podcasts/) mentions that you should be able to use `git annex importfeed` on youtube playlists, however, that doesn't seem to work (or I am using it incorrectly). - -For example: - - » git annex importfeed --fast "https://www.youtube.com/playlist?list=PLz8YL4HVC87X3tYVYOjOLzSasPwgUsMPT" - (checking known urls...) - importfeed https://www.youtube.com/playlist?list=PLz8YL4HVC87X3tYVYOjOLzSasPwgUsMPT - /var/folders/kb/fplmcbhs4z52p4x59cqgm4kw0000gn/T/f [ <=> ] 460.08K 1.87MB/s in 0.2s - - warning: bad feed content - ok - -### What steps will reproduce the problem? - -1. Enter a git annex repository -2. Attempt to import a youtube playlist feed (see command above) with `--fast` - -### What version of git-annex are you using? On what operating system? - - » git annex version - git-annex version: 5.20150205 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA TorrentParser - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL - remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -This is on Mac OSX 10.10.3, with git-annex installed via homebrew - -> You have to give it an url to a RSS feed containing the playlist. -> -> For example, `git annex importfeed -> 'http://gdata.youtube.com/feeds/api/playlists/PLz8ZG1e9MPlzefklz1Gv79icjywTXycR-'` -> still works despite there having been various news stories about youtube -> removing RSS functionality. -> -> I've added this example to the documentation. [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn deleted file mode 100644 index cf7ce7e5e..000000000 --- a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. - -I’m not sure whether this is a bug or a technical limitation, but here -you go: In direct mode, if a file is locally changed but unsynced, -«git annex whereis» and «git annex list» behave as if the file were -still unchanged. Any changes would only show after «git annex sync» or -«git annex add» (altough I’m not sure what the latter does if a file -is already annexed). - -Syncing prior to «whereis» is not viable since I might not want to -proliferate the changes to other remotes. Would it be reasonable making -sure that «whereis» considers uncommitted local changes? - -If doing so is too expensive to do implicitly, it would be useful -having an explicit means of seeing local changes in direct mode -repositories. Is «git annex add» the intended way of doing so? - -### What steps will reproduce the problem? - -1. Clone A to B. -2. Get file $f from A to B. -3. Switch B to direct mode. -4. Edit file $f. -5. «git annex list» reports that $f is on both A and B. - -### What version of git-annex are you using? On what operating system? -git-annex 5.20140421 -Linux 3.14.3 - -[[!tag confirmed]] - -> I think it's reasonable for whereis to show location tracking information -> which may be out of date for many reasons, and so, [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment deleted file mode 100644 index 83663316c..000000000 --- a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_1_99e8d2c1bbc23438f954d8ddc827078e._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 1" - date="2014-05-13T20:41:48Z" - content=""" -Crosslink to related wishlist item -http://git-annex.branchable.com/todo/wishlist:___96__git_annex_sync__96___without_auto-commit/ -"""]] diff --git a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_2_7c8d91d78608d717164cb3e825654654._comment b/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_2_7c8d91d78608d717164cb3e825654654._comment deleted file mode 100644 index a2cf16cb8..000000000 --- a/doc/bugs/git_annex_list__47__whereis_and_uncommited_local_changes/comment_2_7c8d91d78608d717164cb3e825654654._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="216.145.95.162" - subject="comment 2" - date="2014-05-19T17:04:16Z" - content=""" -Direct mode and indirect mode behave the same here -- in indirect mode, if you unlock and modify a file, whereis will show the location of the annexed file, not the un-added version. In general all git-annex commands except of course `add` and `status` operate on the files that are staged in the index or committed, not un-staged files in the work tree. This is consistent with git's own behavior. - -It is true that in direct mode, whereis will say that a file that has been modified is present locally, even though the modification has changed the only local copy of the file -- so it's not actually present locally. However, I don't think it makes sense to make whereis check if the file is actually still locally present before showing it is. whereis shows location tracking information, which can be out of date for many reasons. -"""]] diff --git a/doc/bugs/git_annex_map_has_problems_with_urls_containing___126__.mdwn b/doc/bugs/git_annex_map_has_problems_with_urls_containing___126__.mdwn deleted file mode 100644 index 24f04eeb5..000000000 --- a/doc/bugs/git_annex_map_has_problems_with_urls_containing___126__.mdwn +++ /dev/null @@ -1,46 +0,0 @@ -I discovered a problem with `git annex map` and relative urls containing `~`. -In this case i have a remote `noam` configured with the the following urls: - - zsh» git remote show noam | head -3 - * remote noam - Fetch URL: noam:bare-annex - Push URL: noam:bare-annex - -If i try to run `git annex map` i get the following error: - - zsh» git annex map - map /home/esc/annex ok - map noam (sshing...) - bash: line 0: cd: /~/bare-annex/: No such file or directory - Command ssh ["noam","cd '/~/bare-annex/' && git config --list"] failed; exit code 1 - (sshing...) - ok - - running: dot -Tx11 map.dot - - ok - -If i run the failing command manually, i get: - - zsh» ssh noam "cd ~/bare-annex && git config --list" - core.repositoryformatversion=0 - core.filemode=true - core.bare=true - annex.uuid=f267f55c-0732-11e1-a93b-93119f9aaf54 - annex.version=3 - -Also i can change the remote url to an absolute one, in which case `git annex -map` works too: - - zsh» git remote set-url noam noam:/home/esc/bare-annex - zsh» git annex map - map /home/esc/annex ok - map noam (sshing...) - ok - - running: dot -Tx11 map.dot - - ok - - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row.mdwn b/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row.mdwn deleted file mode 100644 index a3e4c3f67..000000000 --- a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row.mdwn +++ /dev/null @@ -1,77 +0,0 @@ -### Please describe the problem. - -git annex remotedaemon fails to reconnect after receiving several LOSTNET messages and RESUME. - -Initially I've encountered the issue by noticing that git annex assistant stops updating local working copy after suspend/resume of laptop. Later I've found out that the same issue happens when disconnecting from network via NetworkManager and connecting back. - -After some experiments with git annex remotedaemon I've found out that it incorrectly handles several LOSTNET messages in a row. After RESUME remotedaemon starts new SSH process and sends DISCONNECTED right away. Also it doesn't try to reconnect with backoff as it does with bad connection. - -I've checked sources and with some logging found that it sends DISCONNECTED because of some kind of queueing of LOSTNET and switching to stopped mode right after RESUME. Unfortunately I don't know haskell to fix it myself. - -### What steps will reproduce the problem? - -[[!format sh """ -% git annex remotedaemon --debug -[2014-12-19 11:07:13 NOVT] read: git ["config","--null","--list"] -[2014-12-19 11:07:13 NOVT] read: ssh ["-O","stop","-S","git@annex","-o","ControlMaster=auto","-o","ControlPersist=yes","localhost"] -[2014-12-19 11:07:13 NOVT] chat: ssh ["-S",".git/annex/ssh/git@annex","-o","ControlMaster=auto","-o","ControlPersist=yes","-T","git@annex","git-annex-shell 'notifychanges' '/~/annex' --uuid 858bc960-d379-4694-a6b8-98eba5fbeb82"] -CONNECTED ssh://git@annex/~/annex -[2014-12-19 11:07:13 NOVT] chat: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","cat-file","--batch"] -LOSTNET -[2014-12-19 11:07:21 NOVT] read: ssh ["-O","stop","-S","git@annex","-o","ControlMaster=auto","-o","ControlPersist=yes","localhost"] -DISCONNECTED ssh://git@annex/~/annex -LOSTNET -RESUME -[2014-12-19 11:07:27 NOVT] chat: ssh ["-S",".git/annex/ssh/git@annex","-o","ControlMaster=auto","-o","ControlPersist=yes","-T","git@annex","git-annex-shell 'notifychanges' '/~/annex' --uuid 858bc960-d379-4694-a6b8-98eba5fbeb82"] -DISCONNECTED ssh://git@annex/~/annex -"""]] - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20141203 on Gentoo Linux - -### Please provide any additional information below. - -Here is the original assistant log: - -[[!format sh """ - -[2014-12-19 11:14:47 NOVT] NetWatcher: detected network disconnection -[2014-12-19 11:14:47 NOVT] RemoteControl: LOSTNET -[2014-12-19 11:14:47 NOVT] RemoteControl: DISCONNECTED ssh://git@annex/~/annex -[2014-12-19 11:14:47 NOVT] RemoteControl: fromList [] -[2014-12-19 11:14:49 NOVT] NetWatcher: detected network disconnection -[2014-12-19 11:14:49 NOVT] RemoteControl: LOSTNET -[2014-12-19 11:14:52 NOVT] NetWatcher: detected network disconnection -[2014-12-19 11:14:52 NOVT] RemoteControl: LOSTNET -[2014-12-19 11:14:52 NOVT] NetWatcher: detected network disconnection -[2014-12-19 11:14:52 NOVT] RemoteControl: LOSTNET -[2014-12-19 11:14:53 NOVT] NetWatcher: detected network connection -[2014-12-19 11:14:53 NOVT] NetWatcher: Syncing with origin -[2014-12-19 11:14:53 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","symbolic-ref","HEAD"] -[2014-12-19 11:14:53 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","refs/heads/master"] -[2014-12-19 11:14:53 NOVT] call: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","fetch","origin"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","git-annex"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","--hash","refs/heads/git-annex"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","log","refs/heads/git-annex..b85cddc187d388ab12d18fddbdef266565e81e43","-n1","--pretty=%H"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","log","refs/heads/git-annex..12f83429b96850f81ff8edfc0a8651bfa65a066b","-n1","--pretty=%H"] -[2014-12-19 11:14:54 NOVT] call: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","--verify","-q","refs/remotes/origin/master"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","log","refs/heads/master..refs/remotes/origin/master","-n1","--pretty=%H"] -[2014-12-19 11:14:54 NOVT] call: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","--verify","-q","refs/remotes/origin/synced/master"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","log","refs/heads/synced/master..refs/remotes/origin/synced/master","-n1","--pretty=%H"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","symbolic-ref","HEAD"] -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","show-ref","refs/heads/master"] -[2014-12-19 11:14:54 NOVT] NetWatcher: pushing to [Remote { name ="origin" }] -[2014-12-19 11:14:54 NOVT] call: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","push","origin","+git-annex:synced/git-annex","master:synced/master"] -Everything up-to-date -[2014-12-19 11:14:54 NOVT] read: git ["--git-dir=/home/user/annex/.git","--work-tree=/home/user/annex","push","origin","master"] -[2014-12-19 11:14:54 NOVT] RemoteControl: RESUME -[2014-12-19 11:14:54 NOVT] RemoteControl: DISCONNECTED ssh://git@annex/~/annex -[2014-12-19 11:14:54 NOVT] RemoteControl: fromList [] - - -"""]] - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_1_7340e9cf5493e94cc6cb53adb6965f2c._comment b/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_1_7340e9cf5493e94cc6cb53adb6965f2c._comment deleted file mode 100644 index a1547f384..000000000 --- a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_1_7340e9cf5493e94cc6cb53adb6965f2c._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-01-15T19:09:08Z" - content=""" -Thanks for a great bug report. It took me a little while to remember how -this works; the LOSTNET and RESUME messages shown are ones you typed -in to communicate with remotedaemon. - -Looks like a probably straightforward bug in its state machine triggered by -the repeated LOSTNET messages. -"""]] diff --git a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_2_aa6f0371291eb27a55850d905cea381a._comment b/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_2_aa6f0371291eb27a55850d905cea381a._comment deleted file mode 100644 index e371a0592..000000000 --- a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_2_aa6f0371291eb27a55850d905cea381a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-01-15T19:17:20Z" - content=""" -Also, you were spot on about the cause being LOSTNET messages getting -queued up. Clearing that queue when restarting the transport -will fix this problem. - -Please bring your non-haskell code analysis skills to bear on git-annex -anytim! :) -"""]] diff --git a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_3_cafaa7f474fbd995d1c10ecd35d2efe5._comment b/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_3_cafaa7f474fbd995d1c10ecd35d2efe5._comment deleted file mode 100644 index 89fc145cf..000000000 --- a/doc/bugs/git_annex_remotedaemon_fails_to_connect_after_several_LOSTNET_messages_in_a_row/comment_3_cafaa7f474fbd995d1c10ecd35d2efe5._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="mkdf" - subject="comment 3" - date="2015-01-16T06:10:43Z" - content=""" -Thanks a lot Joey! git-annex works like a charm for me and this was the only issue I've encountered so far. I'm happy my guess was correct and it helped to improve git-annex a bit. Thanks for such great tool! -"""]] diff --git a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__.mdwn b/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__.mdwn deleted file mode 100644 index 2ac731909..000000000 --- a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__.mdwn +++ /dev/null @@ -1,78 +0,0 @@ -### Please describe the problem. - -I have a repo on a server running in direct mode. This repo is running Ubuntu 12.04 LTS. I run a windows laptop and the git-annex client to synchronise via SSH. - -### What steps will reproduce the problem? - -I set up the repo as normal on the server, clone it on the laptop, then when I issue the 'git annex get workspace' command to get the content for the workspace directory there are 10 random files with which I am getting the following error: - -get workspace/XXXXXXXX/Functional_Design/test3.docx (from origin...) -[2014-07-23 11:28:42 GMT Daylight Time] read: rsync ["--progress","--inplace","- -e","'ssh' '-T' 'adam@172.21.25.11' 'git-annex-shell ''sendkey'' ''/mnt/NAS1/repo -s/XXXXXXXXXXXXXXXXX'' ''SHA256E-s31601--6f4995ef93be1f640a8b229f84abc69bd44daf63 -6afeae9c1bcf91a6287cd92b.docx'' --uuid 51dce2ea-39c6-4498-a99d-8e189c154eef ''-- -'' ''remoteuuid=c5ec0b9a-b79e-4f3b-8f28-0e869b150f9c'' ''direct=1'' ''associated -file=workspace/XXXXXXXX/Functional_Design/test3.docx'' ''--'''","--","dummy:","/ -cygdrive/c/repos/XXXXXXXXXXXXXXXXX/.git/annex/tmp/SHA256E-s31601--6f4995ef93be1f -640a8b229f84abc69bd44daf636afeae9c1bcf91a6287cd92b.docx"] - requested key is not present -rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] -rsync error: error in rsync protocol data stream (code 12) at /home/lapo/package -/rsync-3.0.9-1/src/rsync-3.0.9/io.c(605) [Receiver=3.0.9] - - rsync failed -- run git annex again to resume file transfer - - Unable to access these remotes: origin - - Try making some of these repositories available: - 51dce2ea-39c6-4498-a99d-8e189c154eef -- root@vpndude:/mnt/NAS1/repos/XXXXXXXXXXXXXXXXXX [origin] -failed - -I have checked the files and the keys and they all seem to match. There are hundreds of other files which do work fine. - -I deleted the laptop repo and cloned again and had another attempt but the same thing occured again. - -I have checked permissions on these files and they are identical to other files which are working. - -I have run git annex sync on the server and the laptop, this has no impact. - -I have run git annex fsck on both server and laptop and this has no impact. - -I'm clueless as to why this is happening. - -### What version of git-annex are you using? On what operating system? - -Ubuntu 12.04 LTS: -git-annex version: 5.20140716-g8c14ba8 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -Windows 7: -git-annex version: 5.20140717-g3de6e4b -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feed -s Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SH -A256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar ho -ok external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 2 3 4 - -### 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. -"""]] - -> [[done]]; does not appear to be a git-annex bug. --[[Joey]] diff --git a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_1_410a591983ebb593e8ca978ceddf6a2c._comment b/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_1_410a591983ebb593e8ca978ceddf6a2c._comment deleted file mode 100644 index 8629e0556..000000000 --- a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_1_410a591983ebb593e8ca978ceddf6a2c._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkt8DjG40gowj_ETchFLDS_Z216tr7p1xw" - nickname="Adam" - subject="ok some progress" - date="2014-07-23T14:27:51Z" - content=""" -I tried to do the same from another local repository on the server and it worked fine. - -I created a Linux VM and that also struggled, but this time with 57 errors. - -It turns out that the way my files were being stored on the server was causing it. I had the files stored on a local NAS which was mounted via iSCSI. I moved the repository from the NAS to local storage and then did another clone and it is now working from the Linux VM and the Windows client via SSH. When using git annex get on the Linux VM it is much faster than the native Git bash which takes ages. -"""]] diff --git a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_2_c4c0dcc0074ff89866fb261c2d30148f._comment b/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_2_c4c0dcc0074ff89866fb261c2d30148f._comment deleted file mode 100644 index 3362fbab1..000000000 --- a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_2_c4c0dcc0074ff89866fb261c2d30148f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="24.159.78.125" - subject="comment 2" - date="2014-07-23T15:05:36Z" - content=""" -This looks very much like rsync on the server crashed, possibly because of an error reading the file. - -Accessing a git-annex repository over a network filesystem is almost never the best choice. Network filesystems are flakey at worst, and at best have locking problems and other limiations. - - -"""]] diff --git a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_3_c377b56d20b291877be3c7bce5e7bd0c._comment b/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_3_c377b56d20b291877be3c7bce5e7bd0c._comment deleted file mode 100644 index 6004fba5c..000000000 --- a/doc/bugs/git_annex_requested_key_is_not_present_on_random_files_even_though_they_exist___40__Direct_mode__41__/comment_3_c377b56d20b291877be3c7bce5e7bd0c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="24.159.78.125" - subject="comment 3" - date="2014-07-23T15:14:21Z" - content=""" -Actually no, rsync was never run on the server. git-annex-shell looked to see if the file was present, and did not see the file. -"""]] diff --git a/doc/bugs/git_annex_status_doesn__39__t_use_.gitignore_in_direct_mode.mdwn b/doc/bugs/git_annex_status_doesn__39__t_use_.gitignore_in_direct_mode.mdwn deleted file mode 100644 index 27bdc3241..000000000 --- a/doc/bugs/git_annex_status_doesn__39__t_use_.gitignore_in_direct_mode.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -Hello all! - -I'm doing tests with git annex to see how it works, and to start with it I'm trying to track my /home using some kind of a *white list* with .gitignore. - -So I have this .gitignore file: - - /* - !/web - - !/Desktop - /Desktop/* - !/Desktop/Work - -and when I do *git annex add .* it works as expected: It adds only ~/web and ~/Desktop/Work... but when I do *git annex status* it shows me the entire /home... it seems that *git annex status* doesn't use .gitignore... is this a bug or an intended behavior? - -Thanks for your time :) - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote.mdwn b/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote.mdwn deleted file mode 100644 index ff3a3b7e2..000000000 --- a/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. - -When using `git annex sync --content` with two archive with different cost, git annex will upload my file to the first archive, then to the second one, then it will drop it from the first one. - -### What steps will reproduce the problem? - -I've set both remote to "trusted", both in the "archive" group, both with "standard" preferred content, the remote named "hubic2" as an annex-cost of 200.0, and the remote named "hubic3" as an annex-cost of 175.0 - -### What version of git-annex are you using? On what operating system? -I'm using git-annex 5.20141125 on Debian Sid (upgraded today on November 7 2014). - -### 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 - -$ git annex list | head -here -|hubic2 -||hubic3 -||| -X__ Avatars/archer.jpg -$ git annex sync --content -commit ok -copy Avatars/archer.jpg copy Avatars/archer.jpg (to hubic3...) -ok -copy Avatars/archer.jpg copy Avatars/archer.jpg (to hubic2...) -ok -drop hubic3 Avatars/archer.jpg ok - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote/comment_1_56eaabb5988caa043ab2e9c1429f8595._comment b/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote/comment_1_56eaabb5988caa043ab2e9c1429f8595._comment deleted file mode 100644 index a6a7f7782..000000000 --- a/doc/bugs/git_annex_sync_--content_may_copy_then_drop_a_file_to_a_remote/comment_1_56eaabb5988caa043ab2e9c1429f8595._comment +++ /dev/null @@ -1,35 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-20T18:07:04Z" - content=""" -A good bug report that I didn't get to for far too long.. - -I reproduced this fairly easily; both remotes set to be -in the archive group and both set to use the "standard" preferred content -expression. - - joey@darkstar:~/tmp/bench/local>git annex sync --content - commit ok - copy file copy file (to hubic3...) - ok - copy file copy file (to hubic2...) - ok - drop hubic3 file ok - -It wants to drop the file from hubic3 once it's present on hubic2, -since archive remotes only want files not on other archive remotes. - -So, why does it send the file to hubic2, given that it's already in hubic3? - -If I manually copy the file to one of the remotes, sync --content won't -send it to the other. So, I suspect it's getting a list of remotes that -want the file first, and then copying the file to all of them. - -Aha, indeed: - - map put <$> filterM wantput lack - -Fixed by making it check if each remote wants the file inside the loop, -rather than checking when getting the list of remotes to loop over. -"""]] diff --git a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects.mdwn b/doc/bugs/git_annex_sync_--content_not_syncing_all_objects.mdwn deleted file mode 100644 index ad7a05d67..000000000 --- a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. -When "git annex sync --content" is used only objects currently in the working tree are synced. It doesn't honor full archives, which should get all objects. -So only objects similar to "git annex find --want-get" are synced and not every available object "git annex get --all" - - -### What steps will reproduce the problem? -# mein repo: -git annex add file -git annex sync -git annex rm file -git annex sync - -# other repo: -git annex wanted here "not copies=backup:3" -git annex find --want-get # will be empty -git annex sync --content # nothing is synced even so all files should be backed up -git annex get --all # will sync the object from file - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140210-gd99db49 -Linux (Ubuntu 13.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. -"""]] - -[[!tag confirmed]] - -> `git annex sync --content --all` was added in version 5.20150617. -> [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_1_36deea0f1277d6888c8bb79156c56efa._comment b/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_1_36deea0f1277d6888c8bb79156c56efa._comment deleted file mode 100644 index e395eac0e..000000000 --- a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_1_36deea0f1277d6888c8bb79156c56efa._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 1" - date="2014-02-20T19:34:29Z" - content=""" -Yep, sync --content only looks at the work tree. - -I suppose that the assistant does a better job in this situation, since if it cannot access an archive repo, it will remember that it tried to send a file to it, and retry that transfer later -- even if in the meantime the file has gotten deleted out of the work tree (and still has content present, due to using indirect mode). I'm actually not 100% sure .. the assistant may give up on transferring a file if it's gotten removed from the work tree. It's worth considering this because I basically want sync --content to do the same syncing that the assistant does. - -Anyway, sync --content could certianly look at all keys present in the annex. This would require a separate pass, and it might then try to upload a key twice, once from work tree, and once from annex, and fail twice. - -Maybe it would be better to have this as a separate --content --all. It might also make sense to keep sync --content only looking at the work tree by default to support cases where there are multiple branches and you only want to sync one. - -I think this needs more thought. -"""]] diff --git a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_2_70804d50b07630fadfc029a22173c5a0._comment b/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_2_70804d50b07630fadfc029a22173c5a0._comment deleted file mode 100644 index 4560e10d9..000000000 --- a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_2_70804d50b07630fadfc029a22173c5a0._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="84.56.21.11" - subject="Some ideas for content sync" - date="2014-02-20T21:18:30Z" - content=""" -I agree that it is a tricky situation. The main issue I have is that archive preferred content expressions indicates that all versions are transferred, but when you (worst case) migrate full archives to other disks and just use git annex sync --content, you would loose all objects. - -I like the idea of --content --all as this would be consistent with other commands such as fsck for example. -Still it seems with preferred content expressions only applying to working tree data that it would still miss \"copies=backup:2\" for example and only use working tree files. Which is misleading and could lead to dataloss in my opinion. - -So the best would probably be to let preferred content for number of copies at least work on all objects, either per default or when \"git annex sync --content --all\" is used. You wouldn't run that on usual repos, but definitely on backup, archive or similar repos. - -"""]] diff --git a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_3_d7349af488008e3ca6557e0c1fbfc5b6._comment b/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_3_d7349af488008e3ca6557e0c1fbfc5b6._comment deleted file mode 100644 index 34c2c4c16..000000000 --- a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_3_d7349af488008e3ca6557e0c1fbfc5b6._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="84.56.21.11" - subject="Ídea" - date="2014-02-23T14:25:22Z" - content=""" -I thought about the implementation need for git annex sync --content --all. If preferred content expressions would work it would be needed. Everything else. could be done via a split usage. -Run \"git annex sync --content\" to satisfy the preferred content expressions on the working tree and the numcopies on the working tree and then loop through all backup/archive repositories with \"git annex get --auto\" this should at least prevent archives from getting objects numcopies is already satisfying and sync the objects not yet satisfied right? -"""]] diff --git a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_6_4540c31acd63626fbad9bde487ec3005._comment b/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_6_4540c31acd63626fbad9bde487ec3005._comment deleted file mode 100644 index 54bce5df8..000000000 --- a/doc/bugs/git_annex_sync_--content_not_syncing_all_objects/comment_6_4540c31acd63626fbad9bde487ec3005._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="91.34.113.105" - subject="Any update" - date="2014-10-01T12:46:34Z" - content=""" -Any update? -"""]] diff --git a/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex.mdwn b/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex.mdwn deleted file mode 100644 index 76260cb5c..000000000 --- a/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -### Please describe the problem. - -If you `git annex edit FILE`, an already-committed file, then do `git annex sync`, FILE will be added to .git/objects, but can be cleaned up with `git prune`. An annoyance, but not a huge problem. - -> This is why you're recommended to use `git add` after you're done -> changing unlocked files. This avoids the git commit staging the file -> in the index, even though the pre-commit hook fixes that up. It does -> indeed leave the file contents in .git/objects, although with no refs -> pointing to it, `git prune` will delete it sooner or later. --[[Joey]] - -If, on the other hand, you do git annex add, then edit, then sync, it will actually be committed to the git repository. Fixing that is a lot less trivial than `git prune`. - -> This is indeed a problem.. - -### What steps will reproduce the problem? - - anthony@Watt:/tmp/test$ du -sh .git/objects/ - 24K .git/objects/ - anthony@Watt:/tmp/test$ dd if=/dev/urandom bs=$[1024*1024] count=100 of=100mb-3 - 100+0 records in - 100+0 records out - 104857600 bytes (105 MB) copied, 6.08718 s, 17.2 MB/s - anthony@Watt:/tmp/test$ git annex add 100mb-3 - add 100mb-3 ok - (Recording state in git...) - anthony@Watt:/tmp/test$ git annex edit 100mb-3 - unlock 100mb-3 (copying...) ok - anthony@Watt:/tmp/test$ git annex sync - commit ok - anthony@Watt:/tmp/test [$?=130]$ git prune - anthony@Watt:/tmp/test$ du -sh .git/objects/ - 101M .git/objects/ - anthony@Watt:/tmp/test$ ls -l 100mb-3 - -rw-r--r-- 1 anthony anthony 104857600 Jan 1 13:41 100mb-3 - - -### What version of git-annex are you using? On what operating system? - -5.20141125 on Debian testing/unstable - -> Analysis: This only happens when a file is added and then unlocked -> without first being committed. -> -> In this situation, the file has a typechange between the index and -> the working tree. However, by the time the pre-commit hook gets -> run, git commit has already staged the unlocked file content into the -> index. So, there is nolonger a typechange between the index and the work -> tree. And, since the file is new, there is no typechange between the -> index and last commit either. The latter is what the pre-commit hook -> looks for. -> -> Conclusion: The pre-commit hook cannot possibly detect this situation. -> Instead, it seems the only way to block the problem is to prevent -> unlocking a file that does not have any git history. -> -> And I've [[done]] that now. --[[Joey]] diff --git a/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex/comment_1_cf46f75c87a27cfc6883bcdb10fecf50._comment b/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex/comment_1_cf46f75c87a27cfc6883bcdb10fecf50._comment deleted file mode 100644 index cb71e7015..000000000 --- a/doc/bugs/git_annex_sync_can_commit_files_to_.git__47__objects_instead_of_.git__47__annex/comment_1_cf46f75c87a27cfc6883bcdb10fecf50._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd" - nickname="Anthony DeRobertis" - subject="comment 1" - date="2015-01-01T19:05:19Z" - content=""" -Wow, the `git filter-branch -f --index-filter 'git rm --cached --ignore-unmatch 100mb-3' HEAD` that you'd expect to remove the file doesn't work—`git annex sync` merges it right back in from one of its internal branches (filtering `synced/master` too seems to work). - -I'd hate to think of the mess had I actually had remotes. Good thing this is a test repository! - -(It *almost* happened on a real one, but I control-C'd it before it committed, after wondering 'why is it taking forever...') -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command.mdwn b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command.mdwn deleted file mode 100644 index e999b3330..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command.mdwn +++ /dev/null @@ -1,102 +0,0 @@ -### Please describe the problem. -git annex sync fails with "Unknown command 'i3'". i3 is the name of one annex. - - -### What steps will reproduce the problem? - -git annex clone i3:PATH annex - -git annex sync - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140920-gb0c4300 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - -on Linux Mint Qiana - -### 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 - - git annex sync -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -commit ok -pull origin -git-annex: Unknown command 'i3' - -Did you mean one of these? - fix - edit - init - find - add - get - vicfg - log - map - drop - move - copy - lock - sync - import - uninit - dead - fsck - direct - help - test - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -failed -push origin -git-annex: Unknown command 'i3' - -Did you mean one of these? - fix - edit - init - find - add - get - vicfg - log - map - drop - move - copy - lock - sync - import - uninit - dead - fsck - direct - help - test - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config) -failed -git-annex: sync: 2 failed - -# End of transcript or log. -"""]] - -> Chalking this one up as a local misconfiguration; I think it's ok for -> git-annex to run the version of itself ~/.config/git-annex/program -> points to. So, [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_1_dd9490e8c9488a78475ccee1ffef08f5._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_1_dd9490e8c9488a78475ccee1ffef08f5._comment deleted file mode 100644 index 8446926d8..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_1_dd9490e8c9488a78475ccee1ffef08f5._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-11-03T16:55:45Z" - content=""" -I cannot reproduce this. (I made the hostname i3 point to localhost to test -it.) - -Please paste the output of `git annex sync --debug` and -`git config --list`. If you have any executable hooks in .git/hooks, please -check that they don't try to run "git annex i3" for some reason. -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_2_4c0097f25c067c3146024ae39ccb10f1._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_2_4c0097f25c067c3146024ae39ccb10f1._comment deleted file mode 100644 index a77e04212..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_2_4c0097f25c067c3146024ae39ccb10f1._comment +++ /dev/null @@ -1,135 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="donkeyicydragon" - subject="git annex sync --debug and git config --list output " - date="2014-11-04T11:28:05Z" - content=""" -Hi Joey, - -I haven't installed any hooks there myself. These are all hooks in .git/hooks: - -* applypatch-msg.sample -* commit-msg.sample -* post-update.sample -* pre-applypatch.sample -* pre-commit -* pre-commit.sample -* prepare-commit-msg.sample -* pre-push.sample -* pre-rebase.sample -* update.sample - -[[!format sh \"\"\" -$ git annex sync --debug -[2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"git-annex\"] -[2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..989b2da3eedef22fffffa2d83d0f9d0012afaa7d\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..5681753eabba653efd94b6e87b2d117e559889e1\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..1632d8479f92ee30c9980c154669dfd5734bb8b0\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:31 CET] chat: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"cat-file\",\"--batch\"] -commit [2014-11-04 12:13:31 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"commit\",\"-a\",\"-m\",\"git-annex automatic sync\"] -ok -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"symbolic-ref\",\"HEAD\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"refs/heads/master\"] -[2014-11-04 12:13:34 CET] call: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"--verify\",\"-q\",\"refs/heads/synced/master\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/master..refs/heads/synced/master\",\"-n1\",\"--pretty=%H\"] -pull origin -[2014-11-04 12:13:34 CET] call: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"fetch\",\"origin\"] -git-annex: Unknown command 'i3' - -Did you mean one of these? - fix - edit - init - find - add - get - vicfg - log - map - drop - move - copy - lock - sync - import - uninit - dead - fsck - direct - help - test - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -failed -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"git-annex\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..989b2da3eedef22fffffa2d83d0f9d0012afaa7d\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..5681753eabba653efd94b6e87b2d117e559889e1\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/heads/git-annex..1632d8479f92ee30c9980c154669dfd5734bb8b0\",\"-n1\",\"--pretty=%H\"] -[2014-11-04 12:13:34 CET] call: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"branch\",\"-f\",\"synced/master\"] -[2014-11-04 12:13:34 CET] call: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/origin/synced/master\"] -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"log\",\"refs/remotes/origin/synced/master..refs/heads/synced/master\",\"-n1\",\"--pretty=%H\"] -push origin -[2014-11-04 12:13:34 CET] call: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"push\",\"origin\",\"+git-annex:synced/git-annex\",\"master:synced/master\"] -git-annex: Unknown command 'i3' - -Did you mean one of these? - fix - edit - init - find - add - get - vicfg - log - map - drop - move - copy - lock - sync - import - uninit - dead - fsck - direct - help - test - -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-11-04 12:13:34 CET] read: git [\"--git-dir=/home/marek/annex/.git\",\"--work-tree=/home/marek/annex\",\"push\",\"origin\",\"master\"] - - Pushing to origin failed. - - (non-fast-forward problems can be solved by setting receive.denyNonFastforwards to false in the remote's git config) -failed -git-annex: sync: 2 failed -\"\"\"]] -### git config --list ### -[[!format sh \"\"\" -user.name=Marek -user.email=marek@xxxx -push.default=simple -core.repositoryformatversion=0 -core.filemode=true -core.bare=false -core.logallrefupdates=true -remote.origin.url=i3:/bluepool/data/ -remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* -remote.origin.annex-uuid=90405788-bc2c-466f-96a7-c498ad9cc525 -branch.master.remote=origin -branch.master.merge=refs/heads/master -annex.uuid=6c5fe2d0-f6f3-4c4a-ad2d-ed140c111bb6 -annex.version=5 -\"\"\"]] - - - -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_3_c7f9b400336b29587b26a161041e7980._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_3_c7f9b400336b29587b26a161041e7980._comment deleted file mode 100644 index a42390df6..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_3_c7f9b400336b29587b26a161041e7980._comment +++ /dev/null @@ -1,34 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2014-11-04T21:21:16Z" - content=""" -From the debug output, it's apparently `git fetch origin` (and also the `git -push origin`) that is, somehow, resuting in the error message. - -But, I'll bet it doesn't happen if you run `git fetch origin` by hand, does -it? - -My best guess is that this is somehow related to the ssh connection -caching code. To make ssh connection caching work, git-annex sets -`GIT_SSH=git-annex`. This would result in `git fetch` running `git annex i3` -as we see here, but with some environment variables set that would make -git-annex know that it's supposed to be handling a ssh caching scenario. - -Perhaps you have a really old version of git-annex, that doesn't know about -that ssh caching environment, installed someplace, in addition to the more -recent version that's in you path. If the old version somehow gets run by -git, it would explain this behavior. - -To check this theory, first try disabling ssh caching temporarily, and see if -that avoids the problem: - - git config annex.sshcaching false - git annex sync - git config annex.sshcaching true - -If that did avoid the problem, take a look at -`~/.config/git-annex/program`. It probably points to the location of an old -version of git-annex. Likely one installed from the standalone tarball. -Removing that file would then solve your problem. -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_4_b5e3c925fcfa7d8a48d24eb677c6c2a0._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_4_b5e3c925fcfa7d8a48d24eb677c6c2a0._comment deleted file mode 100644 index 9c3f0e388..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_4_b5e3c925fcfa7d8a48d24eb677c6c2a0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="donkeyicydragon" - subject="This fixed it for me" - date="2014-11-04T23:41:58Z" - content=""" -Thank you very much for the quick response. -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_5_aed072d24e216b2ab0d22faa53b4de5b._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_5_aed072d24e216b2ab0d22faa53b4de5b._comment deleted file mode 100644 index cd8aa02b8..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_5_aed072d24e216b2ab0d22faa53b4de5b._comment +++ /dev/null @@ -1,48 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlXt6nnNs-3uw61EGYtxr_AVhJqXybwLR8" - nickname="Bruno" - subject="Problem with the SSH Caching feature ?" - date="2015-03-21T20:54:29Z" - content=""" -Hi, - -I have a similar problem, - - $ git annex sync --content - commit ok - pull origin - root@192.168.253.53: error while loading shared libraries: root@192.168.253.53: cannot open shared object file: No such file or directory - fatal: Could not read from remote repository. - - Please make sure you have the correct access rights - and the repository exists. - failed - -I have also verified the files paths, it seem ok, And effectively, it appear a SSH Caching feature that cause this error. - -For resolve it, i have used the **@joey** solution. - -I disabled the SSH Caching feature - - git config annex.sshcaching false - -Here the result after disable caching feature - - $ git annex sync --content - commit (recording state in git...) - ok - pull origin - ok - pull origin - ok - push origin - Counting objects: 5, done. - Delta compression using up to 4 threads. - Compressing objects: 100% (4/4), done. - Writing objects: 100% (5/5), 489 bytes | 0 bytes/s, done. - Total 5 (delta 1), reused 0 (delta 0) - To root@192.168.253.53:/data/samba/backup/newdocshare - 008ee7c..23e8372 git-annex -> synced/git-annex - ok - -"""]] diff --git a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_6_54eafe7c4beee93a92a80a544124ce86._comment b/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_6_54eafe7c4beee93a92a80a544124ce86._comment deleted file mode 100644 index 2af923cbe..000000000 --- a/doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_6_54eafe7c4beee93a92a80a544124ce86._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-03-27T20:56:16Z" - content=""" -"root@192.168.253.53: error while loading shared libraries: -root@192.168.253.53: cannot open shared object file: No such file or -directory" - -That is a different bug entirely. Sure, same codepath, but by posting your -problem report to a closed bug, you muddy the waters considerably. - -I fixed that problem today, once someone else brought it to my attention. -It's a pity that I didn't see your report earlier, due to where you posted -it.. -"""]] diff --git a/doc/bugs/git_annex_unlock_is_not_atomic.mdwn b/doc/bugs/git_annex_unlock_is_not_atomic.mdwn deleted file mode 100644 index 6d324ff50..000000000 --- a/doc/bugs/git_annex_unlock_is_not_atomic.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -Running a command like - -git annex unlock myfile - -is not atomic, that is if the execution is aborted you may end up with an incomplete version of myfile in the directory. If you don't notice this you may lock it again and then propagate this bad version of the file to your other repositories. A simple workaround is to simply name it something else while unlocking and then rename it to the correct filename once it's completely copied. I don't know Haskel yet so I can not fix this issue otherwise I would sure try. A part from this, I love git annex. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn b/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn deleted file mode 100644 index 05aa69572..000000000 --- a/doc/bugs/git_annex_unused_failes_on_empty_repository.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -[[!meta title="`git annex unused` fails on empty repository"]] - -The ``git annex unused`` command fails on a git-annex repository, if there are no objects yet: - - $ git annex unused - unused (checking for unused data...) - git-annex: /tmp/annextest/other_annex/.git/annex/objects: getDirectoryContents: does not exist (No such file or directory) - git-annex: 1 failed - $ - -This can give a user (especially one that wants to try out simple commands with his newly created repo) the impression that something is wrong, while it is not. I'd expect the program either to show the same message ``git annex unused`` shows when everything is ok (since it is, or should be). - -This can be a bug in the ``unused`` subcommand (that fails to accept the absence of an objects directory) or in the ``init`` subcommand (that fails to create it). - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_unused_fails_when_a_filename_contains_newline.mdwn b/doc/bugs/git_annex_unused_fails_when_a_filename_contains_newline.mdwn deleted file mode 100644 index 5aeff37d0..000000000 --- a/doc/bugs/git_annex_unused_fails_when_a_filename_contains_newline.mdwn +++ /dev/null @@ -1,69 +0,0 @@ -### Please describe the problem. - -After annexing files with newline (`\n`) characters in their name, then running `git annex unused` on the same git annex repository fails, instead of working correctly. The error is "git-annex: unknown response from git cat-file ". -This issue might happen with filenames with other special characters in the filename, too. - -### What steps will reproduce the problem? - -1. create git annex repository -2. create a file with a newline in its name -3. annex the file -4. run `git annex unused` - -Expected result: success - -Actual results: error: "git-annex: unknown response from git cat-file ". - - -### What version of git-annex are you using? On what operating system? - -git-annex package version 5.20140412ubuntu1, architecture i386. System is xubuntu 14.04. - -[[!format sh """ -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex$ git annex version -git-annex version: 5.20140412ubuntu1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -"""]] - - -### 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 - -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex$ git annex unused -unused . (checking for unused data...) [2014-07-13 16:42:04 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","ls-files","--cached","--others","-z","--","/media/zolee/Stuff/dell-zoli-git-annex"] -[2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","symbolic-ref","HEAD"] -[2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref","--hash","refs/heads/dell-zoli-master"] -[2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref"] -(checking dell-zoli-master...) [2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref","--head"] -[2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref","--head"] -[2014-07-13 16:42:31 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","diff-index","-z","--raw","--no-renames","-l0","refs/heads/dell-zoli-master"] -(checking store-zoli/laptop-zoli-master...) [2014-07-13 16:42:32 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref","--head"] -[2014-07-13 16:42:32 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","show-ref","--head"] -[2014-07-13 16:42:32 EEST] read: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","diff-index","-z","--raw","--no-renames","-l0","refs/remotes/store-zoli/laptop-zoli-master"] -[2014-07-13 16:42:33 EEST] chat: git ["--git-dir=/media/zolee/Stuff/dell-zoli-git-annex/.git","--work-tree=/media/zolee/Stuff/dell-zoli-git-annex","cat-file","--batch"] -git-annex: unknown response from git cat-file ("Code Composer Studio missing","refs/remotes/store-zoli/laptop-zoli-master:egyetem/2009-2010-sem2/diploma/tex/titlu-lucrare.tex~") -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex$ - - -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex/egyetem/2009-2010-sem2/media-processors$ ls -51325409-1.pdf course2010 Noterestanta.pdf Proiecte_6xxx.pdf rg_rand.c TMS320C6000?Code Composer Studio? Tutorial?- spru301c.pdf -ccs_workspace.tar.gz netrol Proc_Media project site -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex/egyetem/2009-2010-sem2/media-processors$ ls -b -51325409-1.pdf course2010 Noterestanta.pdf Proiecte_6xxx.pdf rg_rand.c \ \ \ TMS320C6000\nCode\ Composer\ Studio\n\ \ \ \ \ \ Tutorial\n-\ spru301c.pdf -ccs_workspace.tar.gz netrol Proc_Media project site -zolee@zolee-Latitude-E6440:/media/zolee/Stuff/dell-zoli-git-annex/egyetem/2009-2010-sem2/media-processors$ - -# End of transcript or log. -"""]] - -> dup of -> [[git_annex_import_fails_on_filenames_with_newlines_in_them]]; closing as -> such. [[done]] --[[Joey]] diff --git a/doc/bugs/git_clone_ignores_annex.mdwn b/doc/bugs/git_clone_ignores_annex.mdwn deleted file mode 100644 index 450a069ad..000000000 --- a/doc/bugs/git_clone_ignores_annex.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -More of a feature request than a bug. It would be nice if when creating a local clone with git clone this would run automatically: - -ln -s ../../annex/.git/annex .git/annex - -to hook up the annex. Just a minor thing, but I'd be nice. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[done]] --[[Joey]] diff --git a/doc/bugs/git_clone_ignores_annex/comment_1_18ba05c51f82ddadd2558f6cd789e394._comment b/doc/bugs/git_clone_ignores_annex/comment_1_18ba05c51f82ddadd2558f6cd789e394._comment deleted file mode 100644 index e0b69f81a..000000000 --- a/doc/bugs/git_clone_ignores_annex/comment_1_18ba05c51f82ddadd2558f6cd789e394._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 1" - date="2014-10-06T15:42:26Z" - content=""" -Making that symlink is extremely unsafe! git-annex will see two repositories. So if a file is present in the annex, with only one actual copy existing, and you try to drop it, git-annex will go check the other repository, find the file there, assume this means there's an extra copy and so proceed with the drop. Which deletes the only existing copy of your file. So if you do this, you will likely eventually lose data. - -However, recent versions of git-annex will detect if you clone a git repository with `--shared` and automatically hard link files into the annex when getting them into that repository. They also mark the shared clone as untrusted, to avoid the above problem. This is a much better solution. -"""]] diff --git a/doc/bugs/git_command_line_constructed_by_unannex_command_has_tons_of_redundant_-a_paramters.mdwn b/doc/bugs/git_command_line_constructed_by_unannex_command_has_tons_of_redundant_-a_paramters.mdwn deleted file mode 100644 index 181b02b5c..000000000 --- a/doc/bugs/git_command_line_constructed_by_unannex_command_has_tons_of_redundant_-a_paramters.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -This doesn't look right: - - simons 11148 0.0 0.0 15572 1268 pts/1 SN+ 04:00 0:00 | \_ git annex unannex stuff - simons 11150 0.5 0.0 130504 11212 pts/1 SN+ 04:00 3:40 | | \_ git-annex unannex stuff - simons 11152 0.0 0.1 39536 23932 pts/1 SN+ 04:00 0:00 | | \_ git --git-dir=/home/simons/annex/.git --work-tree=/home/simons/annex ls-files --cached -z -- stuff - simons 11288 0.0 0.0 0 0 pts/1 ZN+ 04:01 0:00 | | \_ [git] <defunct> - simons 11339 0.0 0.0 0 0 pts/1 ZN+ 04:02 0:00 | | \_ [git-annex] <defunct> - simons 11442 0.0 0.0 0 0 pts/1 ZN+ 04:06 0:00 | | \_ [git] <defunct> - simons 11443 0.0 0.0 0 0 pts/1 ZN+ 04:06 0:05 | | \_ [git] <defunct> - simons 16541 0.0 0.0 0 0 pts/1 ZN+ 04:14 0:00 | | \_ [git] <defunct> - simons 16543 0.3 0.0 15644 1744 pts/1 SN+ 04:14 2:13 | | \_ git --git-dir=/home/simons/annex/.git --work-tree=/home/simons/annex cat-file --batch - simons 14224 0.0 0.0 100744 796 pts/1 SN+ 14:10 0:00 | | \_ xargs -0 git --git-dir=/home/simons/annex/.git --work-tree=/home/simons/annex commit -a -m content removed from git annex - simons 14225 0.4 0.1 32684 18652 pts/1 DN+ 14:10 0:00 | | \_ git --git-dir=/home/simons/annex/.git --work-tree=/home/simons/annex commit -a -m content removed from git annex -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a -a - -> [[Fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn b/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn deleted file mode 100644 index 66a199e8c..000000000 --- a/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -When I `git mv` a file that I just `git annex add`-ed without having `git commit`-ed it first, then the symlink will break. - -### What steps will reproduce the problem? - - $ mkdir foo - $ echo hello > foo/bar - $ git annex add foo/bar - $ git mv foo/bar . - -### What version of git-annex are you using? On what operating system? - -5.20140529 on Debian testing - -> This is fundamentally something git-annex cannot deal with, -> because there is no way to hook into git to fix the symlink when -> `git mv` moves the file. -> -> Instead, git-annex has several "good enough" fixes for the problem: -> -> * As soon as you `git commit`, the pre-commit hook will run `git annex -> fix` and this will fix the symlink before it gets committed. -> * You can run `git annex fix` yourself after `git mv`. -> * Even `git annex add $file` will fix the symlink if the file is already -> annexed. -> -> So, [[done]] --[[Joey]] diff --git a/doc/bugs/git_pack-objects_eats_all_teh_ram.mdwn b/doc/bugs/git_pack-objects_eats_all_teh_ram.mdwn deleted file mode 100644 index 68c875f9c..000000000 --- a/doc/bugs/git_pack-objects_eats_all_teh_ram.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -### Please describe the problem. - -I'm running git annex sync <remote> sync'ing a local direct mode remote to a local indirect mode remote. - -As part of this process, git annex is running git pack-objects --keep-true-parents --honor-pack-keep --non-empty --all. - -This eats all of my raspberry pi's ram for lunch. I think it even starts swapping, which would explain why it never seems to complete. - -It's unclear why this is eating all my RAM, as I don't think I used to have this problem, and my repo didn't recently dramatically grow in size. (I added < 100 multi-gb files, but that shouldn't make a difference here, I think.) - -Anyway It would be nice if there were a way to get git-annex to pass a sensible -window-memory here. I'm trying to use a wimpy machine, but I'm sure this could be a problem on a bigger machine too. - -### What version of git-annex are you using? On what operating system? - -$ git-annex version -git-annex version: 5.20141024-g613f396 - -$ uname -a -Linux raspberrypi 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux - -> [[done]]; not a git-annex bug AFAICS. --[[Joey]] diff --git a/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_1_24df756bb2aac06c227fdc55d944e1d3._comment b/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_1_24df756bb2aac06c227fdc55d944e1d3._comment deleted file mode 100644 index e1a4adac7..000000000 --- a/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_1_24df756bb2aac06c227fdc55d944e1d3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmUJBh1lYmvfCCiGr3yrdx-QhuLCSRnU5c" - nickname="Justin" - subject="comment 1" - date="2015-03-24T15:30:30Z" - content=""" -One thing that's odd is that, if I disable swap, it still eats all my ram, and kswapd0 is still the primary user of CPU. The machine is even slower than it was before; iotop takes more than a minute to low. My best explanation is it must be swapping by kicking out cached pages. -"""]] diff --git a/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment b/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment deleted file mode 100644 index 07ff19070..000000000 --- a/doc/bugs/git_pack-objects_eats_all_teh_ram/comment_2_77cb32e7cee99d7325e7c6a595844e0c._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-03-26T15:50:49Z" - content=""" -git-annex never directly calls `git pack-object` or `git repack` -or anything like that. This is likely being done internally by git, -as controlled by `gc.auto` configuration. - -If this is eating a lot of ram, it seems to me that you have likely -checked some large files into you git repository, rather than using -git-annex to manange them. git using lots of ram when large -files have been added to it is one of the reasons git-annex exists, -after all.. -"""]] diff --git a/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files.mdwn b/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files.mdwn deleted file mode 100644 index 449a99753..000000000 --- a/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -### Please describe the problem. - -When git-annex assistant on Android setups up the DCIM repo a .gitignore file is dropped into place which ignores .thumbnails/* . Unfortunately this doesn't match .thumbnails/.thumbdata* - I have a 700MB file which matches this pattern. - -I suspect that making the pattern in .gitignore just .thumbnails should resolve this. - -### What steps will reproduce the problem? - -Create a repo - -### What version of git-annex are you using? On what operating system? - -Nightly build for Android from yesterday (2013-11-16) - -### Please provide any additional information below. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files/comment_1_f683ecf93e5a17c5c9c06225dbcce2a9._comment b/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files/comment_1_f683ecf93e5a17c5c9c06225dbcce2a9._comment deleted file mode 100644 index b90108bc4..000000000 --- a/doc/bugs/gitignore_for_DCIM_on_Android_misses_some_files/comment_1_f683ecf93e5a17c5c9c06225dbcce2a9._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 1" - date="2013-11-16T22:45:52Z" - content=""" -\".thumbnails/*\" in .gitignore makes git ignore dotfiles in the directory in my testing, and according to git's own documentation. - -However, it is the case that subdir/.thumbnails/* are not ignored by \".thumbnails/*\", but \".thumbnails\" will indeed ignore .thumbnails directories at any point in the tree. So, I've made the change you suggested. - -(I also tested on android, with 1.8.4.1.559 and the assistant was able to honor the .gitignore, and did not add any files from `.thumbnails/`.) -"""]] diff --git a/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn b/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn deleted file mode 100644 index 65cde407e..000000000 --- a/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -It's not possible to use gcrypt with gitlab repos, despite the webapp -currently offering this as an option. The resulting remote works as far as -pushes go, but fails with an error "Failed to connect to remote to set it -up." - -It seems that the gitlab repo is somehow in a state where git-annex-shell -configlist reports it's not yet a git-annex repo, but git-annex-shell -gcryptsetup fails with "gcryptsetup refusing to run; this repository already has a git-annex uuid!" - -This does not happen when I try the same setup on a self-hosted repo. -Unsure what is causing git-annex-shell to behave this way on gitlab. ---[[Joey]] - -> Here's a minimal way to reproduce this problem: -> -> 1. Make a new, empty repository on gitlab.com. -> 2. Run command: ssh git@gitlab.com git-annex-shell 'gcryptsetup' '/~/username/reponame.git' ':id:dummy' -> -> Leads to the failure as described above. But, the repo is new and empty -> and has not had any opportunity to get a git-annex uuid set.. -> -> I wonder what version of git-annex gitlab.com is running? --[[Joey]] - ->> gitlab tells me their version is 5.20140412ubuntu1. ->> I tried installing git-annex-shell from 5.20140412, but ->> was not able to reproduce the problem using it. This makes me think the ->> problem is somehow in gitlab's git-annex-shell integration code. ->> ->> Update: Root-caused and filed a bug: ->> <https://gitlab.com/gitlab-org/gitlab-shell/issues/24 ->> ->> This will need to be fixed on the gitlab side, so closing it here. ->> [[done]] --[[Joey]] diff --git a/doc/bugs/glacier_fails_to_copy.mdwn b/doc/bugs/glacier_fails_to_copy.mdwn deleted file mode 100644 index 3c6d95502..000000000 --- a/doc/bugs/glacier_fails_to_copy.mdwn +++ /dev/null @@ -1,85 +0,0 @@ -### Please describe the problem. -glacier copy shows the output of the glacier-cli help and a gpg error for each file and most of the files fail to copy. - -### What steps will reproduce the problem? -1. git annex init "Photos" -2. cp -R ../photodir/ . -3. git annex add . -4. git commit -a -m added -5. export AWS_ACCESS_KEY_ID="***" -6. export AWS_SECRET_ACCESS_KEY="***" -7. git annex initremote glacier type=glacier encryption=shared vault=photos -8. git annex copy --auto --to glacier - -### What version of git-annex are you using? On what operating system? -5.20150113-gcf247cf -Arch Linux (git-annex-bin package) - -### Please provide any additional information below. -I get the following messages over and over again: -[[!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 -copy 2003/10/14/085.jpg (checking glacier...) (to glacier...) -8% 0.0 B/s 0s -glacier <command> [args] - - Commands - vaults - Operations with vaults - jobs - Operations with jobs - upload - Upload files to a vault. If the vault doesn't exits, it is - created - - Common args: - --access_key - Your AWS Access Key ID. If not supplied, boto will - use the value of the environment variable - AWS_ACCESS_KEY_ID - --secret_key - Your AWS Secret Access Key. If not supplied, boto - will use the value of the environment variable - AWS_SECRET_ACCESS_KEY - --region - AWS region to use. Possible values: us-east-1, us-west-1, - us-west-2, ap-northeast-1, eu-west-1. - Default: us-east-1 - - Vaults operations: - - List vaults: - glacier vaults - - Jobs operations: - - List jobs: - glacier jobs <vault name> - - Uploading files: - - glacier upload <vault name> <files> - - Examples : - glacier upload pics *.jpg - glacier upload pics a.jpg b.jpg - -gpg: [stdout]: write error: Broken pipe -gpg: DBG: deflate: iobuf_write failed -gpg: build_packet failed: Broken pipe -gpg: [stdout]: write error: Broken pipe -gpg: iobuf_flush failed on close: Broken pipe -gpg: [stdout]: write error: Broken pipe -gpg: iobuf_flush failed on close: Broken pipe -gpg: symmetric encryption of '[stdin]' failed: Broken pipe - - user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--passphrase-fd","227","--symmetric","--force-mdc","--no-textmode"] exited 2) -failed -git-annex: fd:230: hPutBuf: resource vanished (Broken pipe) - -# lots more lines like this - -ok -(Recording state in git...) -git-annex: copy: 230 failed - -# End of transcript or log. -"""]] - -> git-annex will now detect this misconfiguration and refuse to use it, so -> [[done]] --[[Joey]] diff --git a/doc/bugs/glacier_fails_to_copy/comment_1_29ea384b6aa5a634ff75191eee14c7ef._comment b/doc/bugs/glacier_fails_to_copy/comment_1_29ea384b6aa5a634ff75191eee14c7ef._comment deleted file mode 100644 index c24f782a4..000000000 --- a/doc/bugs/glacier_fails_to_copy/comment_1_29ea384b6aa5a634ff75191eee14c7ef._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-05T17:55:25Z" - content=""" -From where did you install your glacier command? - -It does not seem to be the [glacier-cli](https://github.com/basak/glacier-cli) -that git-annex is built to use. - - glacier upload <vault name> <files> - -That is not the upload syntax that glacier-cli uses, which is instead -supposed to be: - - glacier archive upload example-vault example-content -"""]] diff --git a/doc/bugs/glacier_fails_to_copy/comment_2_329980c99dc244b227a967982cb9052c._comment b/doc/bugs/glacier_fails_to_copy/comment_2_329980c99dc244b227a967982cb9052c._comment deleted file mode 100644 index e6a6a72ae..000000000 --- a/doc/bugs/glacier_fails_to_copy/comment_2_329980c99dc244b227a967982cb9052c._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="Reed" - subject="glacier command" - date="2015-02-05T23:27:27Z" - content=""" -My `/usr/bin/glacier` is owned by `python2-boto-git` which is a requirement for `glacier-cmd-git`. I've now installed `glacier-cli` from the git repo and it seems to be working fine. Thanks for the help! -"""]] diff --git a/doc/bugs/glacier_fails_to_copy/comment_2_b0614f2e7417af733f54c9ff569b11b0._comment b/doc/bugs/glacier_fails_to_copy/comment_2_b0614f2e7417af733f54c9ff569b11b0._comment deleted file mode 100644 index 6813ff9fc..000000000 --- a/doc/bugs/glacier_fails_to_copy/comment_2_b0614f2e7417af733f54c9ff569b11b0._comment +++ /dev/null @@ -1,33 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-02-06T17:30:50Z" - content=""" -Since someone also mentioned this problem on IRC (I don't know if it was -you), I am wondering if this is an easy mistake to make. I guess so; you -installed boto from Arch's packages and it included a /usr/bin/glacier.. -Same could happen if using pip to install boto, I think. - -I don't want to support multiple different glacier interface programs. The -eventual plan is to move glacier support into git-annex, using a haskell -library. - -The other concerning thing is that git-annex seems to have reported that -some of the transfers succeeded. It seems, very unfortunately, that -the glacier command from boto exits 0 when given unsupported -parameters. So, git-annex will think a transfer succeeded, at least some of -the time (sometimes gpg notices that the encrypted output is not all -consumed). - -I think that the best fix will be to make glacier-cli install a -"glacier-cli" program. Then git-annex can run that instead of "glacier" and -will be much less likely to run into namespace pollution. - -I have filed 2 bug reports: - -* [boto's glacier should exit nonzero after displaying usage](https://github.com/boto/boto/issues/2942) -* [glacier-cli should provide a glacier-cli command](https://github.com/basak/glacier-cli/issues/30) - -I have also put a really ugly hack into git-annex to detect when the wrong -glacier is installed, and refuse to use it. -"""]] diff --git a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux.mdwn b/doc/bugs/gpg_does_not_ask_for_password_inside_tmux.mdwn deleted file mode 100644 index 7dbcf3048..000000000 --- a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -When commands that need gpg like `git annex copy` are run inside tmux, the GPG prompt does not show up and the user cannot give their password. - -Running the same command outside tmux causes GPG to properly show its prompt - -### What steps will reproduce the problem? - - $ tmux - TMUX$ GIT_ANNEX_ROOT/runshell - TMUX$ git annex copy --not -in remote --to remote - -git-annex will show the name of the first filename but will get stuck soon after that, waiting for GPG. - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20140708-g8c9cc55c from the precompiled binaries, run inside tmux 1.6. - -`tmux.conf` contains `set-option -g default-command $SHELL` (this means that a normal shell is spawned, not a login shell) - -Ubuntu 12.04.4 - -[[!tag moreinfo]] - -> [[done]]; apparently a local misconfiguration of some sort. --[[Joey]] diff --git a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_1_053b12e8b412723ff1d6b4e64e71af9e._comment b/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_1_053b12e8b412723ff1d6b4e64e71af9e._comment deleted file mode 100644 index 0359be528..000000000 --- a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_1_053b12e8b412723ff1d6b4e64e71af9e._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-10T18:24:17Z" - content=""" -I cannot reproduce this. I made sure to unset `GPG_AGENT_INFO` so gpg would need to prompt for a password on the terminal, and it did. - -<pre> -joey@darkstar:~/tmp/r>unset GPG_AGENT_INFO -joey@darkstar:~/tmp/r>git annex copy --to remote -copy n/xxx (gpg) -You need a passphrase to unlock the secret key for -user: \"Joey Hess <joeyh@debian.org>\" -4096-bit RSA key, ID 17065459, created 2009-06-17 (main key ID 2512E3C7) - -gpg: gpg-agent is not available in this session -Enter passphrase: -</pre> - -I cannot think of anything that would make gpg's password prompting behave differently inside tmux than outside, either. - -I think that to debug this, you are going to need to look at what the gpg process is trying to do. -"""]] diff --git a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_2_44830ba952cad3b153249bd405671507._comment b/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_2_44830ba952cad3b153249bd405671507._comment deleted file mode 100644 index 28756f654..000000000 --- a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_2_44830ba952cad3b153249bd405671507._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="GPG_AGENT_INFO was already set in the outside shell" - date="2014-07-11T07:19:45Z" - content=""" -I found what the problem is: GPG_AGENT_INFO was already set in the outside shell. - -Unsetting GPG_AGENT_INFO fixes the problem. -"""]] diff --git a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_3_a63db33a1dc70e64418de8b4bea6a9fa._comment b/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_3_a63db33a1dc70e64418de8b4bea6a9fa._comment deleted file mode 100644 index 4f5428b87..000000000 --- a/doc/bugs/gpg_does_not_ask_for_password_inside_tmux/comment_3_a63db33a1dc70e64418de8b4bea6a9fa._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 3" - date="2014-07-11T18:15:09Z" - content=""" -AFAICS there is no problem with GPG_AGENT_INFO being set while using tmux. The gpg agent works as usual and pops up a passphrase prompt window. - -Is there something broken in your gpg agent that prevents it from working inside tmux, or working at all? In any case, this seems like a local misconfiruation problem and out of git-annex's scope anyway so I suppose I will close the bug. - -"""]] diff --git a/doc/bugs/hS3_prevents_build.mdwn b/doc/bugs/hS3_prevents_build.mdwn deleted file mode 100644 index 1a064b90b..000000000 --- a/doc/bugs/hS3_prevents_build.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -The `hS3` dependency doesn't work with the `network` / `network-uri` split, which causes a build failure for `git-annex` in a fresh sandbox with its current version bounds. Either more gymnastics are needed to constrain `network` to accommodate `hS3`, or the `s3-aws` branch could be merged in if it's ready. Building `git-annex` with a `< 2.6` constraint on `network` does succeed. - -> not a bug in git-annex, but in a dependency it uses, so [[done]]. (I already told the hS3 author about this, which is a very easy fix there, and he promised to fix it soon.) --[[Joey]] diff --git a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__.mdwn b/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__.mdwn deleted file mode 100644 index afc95b6ce..000000000 --- a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. -shiny-2:MacOS ovi$ git annex sync -git: 'annex' is not a git command. See 'git --help'. -shiny-2:MacOS ovi$ - -### What steps will reproduce the problem? -INstall git-annex for MAC like this: http://git-annex.branchable.com/install/OSX/ via .dmg file then try above commands from your terminal - -### What version of git-annex are you using? On what operating system? -Version: 5.20140420-ga25b8bb Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -Mac OSX 10.9.2 - -### Please provide any additional information below. -I tried adding the path to my .bash_profile manually like this but it didn't help (actually, this was already in there, I just added the path to git-annex to the string): -export PATH=/opt/local/bin:/opt/local/sbin/Applications/git-annex.app/Contents/MacOS:$PATH - -[[!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. -"""]] - -> To the extent this is a bug report, it's a duplicate of -> [[standalone_tarball_symlink_to_PATH_broken]]. -> [[closing dup|done]]. --[[Joey]] diff --git a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_1_780fbb7b8dda331503064dfa6bcabaa3._comment b/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_1_780fbb7b8dda331503064dfa6bcabaa3._comment deleted file mode 100644 index 5d7dd9493..000000000 --- a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_1_780fbb7b8dda331503064dfa6bcabaa3._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-05-16T17:17:54Z" - content=""" -Here's how I do it: - -<pre> -$ oberon:tmp joeyh$ hdiutil attach git-annex.dmg -$ oberon:tmp joeyh$ /Volumes/git-annex/git-annex.app/Contents/MacOS/git-annex version -git-annex version: 5.20140516-g693a6a4 -oberon:tmp joeyh$ PATH=$PATH:/Volumes/git-annex/git-annex.app/Contents/MacOS/ -oberon:tmp joeyh$ git-annex version -git-annex version: 5.20140516-g693a6a4 -</pre> - -So, adding to PATH works fine. Perhaps you added the wrong directory to your PATH. - -Note that .bash_profile is only used for bash login shells. It may not be run when you open a terminal, or when git-annex ssh's in from elsewhere to run git-annex-shell (which you seem to be asking about, but only in the title of this page?). - -In particular, bash does not provide any way to set the PATH which works when you run \"ssh yourcomputer git-annex-shell\". So you will need to instead move the git-annex files into a directory that is in the default PATH. -"""]] diff --git a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_2_1785e99846998aa50e1c62a88b558196._comment b/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_2_1785e99846998aa50e1c62a88b558196._comment deleted file mode 100644 index e5d09ec64..000000000 --- a/doc/bugs/how_to_get_git-annex_shell_on_MAC__63__/comment_2_1785e99846998aa50e1c62a88b558196._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkAUMhKOSkh9JaBA6xst3XxQIIsDEq5Zd4" - nickname="Ovidiu" - subject="comment 2" - date="2014-05-16T17:23:32Z" - content=""" -Thanks for the additional info, for now its working fine: - -git-annex version -git-annex version: 5.20140420-ga25b8bb -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -"""]] diff --git a/doc/bugs/id__95__rsa_on_android.mdwn b/doc/bugs/id__95__rsa_on_android.mdwn deleted file mode 100644 index 2aadd6c40..000000000 --- a/doc/bugs/id__95__rsa_on_android.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -### Please describe the problem. - -I generated id_rsa and id_rsa.pub from the android shell. -After copying the id_rsa.pub file on my server, ssh on android complains because id_rsa permissions on the phone are too open (660). -Chmod 600 id_rsa on /sdcard/git-annex.home/.ssh/id_rsa has no effect, i.e. permissions remain 660. - -### What steps will reproduce the problem? -use ssh-keygen to generate keys, default location is /sdcard/git-annex.home/.ssh/ -copy id_rsa.pub on ssh server, try to connect from android to ssh server. - - -### What version of git-annex are you using? On what operating system? -latest git-annex.apk (2014-03-06) on android 4.4.2 - -### Please provide any additional information below. - - -root@android:/ # /data/data/ga.androidterm/runshell -Falling back to hardcoded app location; cannot find expected files in /data/app-lib - -root@android:/sdcard/git-annex.home # ssh MYSERVERIP -p PORT -l USERNAME - -@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ -@ WARNING: UNPROTECTED PRIVATE KEY FILE! @ -@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ -Permissions 0660 for '/sdcard/git-annex.home/.ssh/id_rsa' are too open. -It is required that your private key files are NOT accessible by others. -This private key will be ignored. -bad permissions: ignore key: /sdcard/git-annex.home/.ssh/id_rsa - - -> [[fixed|done]]; daily build is updated. --[[Joey]] diff --git a/doc/bugs/id__95__rsa_on_android/comment_1_58f4fd1c4ae29bc3d2f3ea0aa6f6c12b._comment b/doc/bugs/id__95__rsa_on_android/comment_1_58f4fd1c4ae29bc3d2f3ea0aa6f6c12b._comment deleted file mode 100644 index 0a5a9e230..000000000 --- a/doc/bugs/id__95__rsa_on_android/comment_1_58f4fd1c4ae29bc3d2f3ea0aa6f6c12b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-03-10T21:20:10Z" - content=""" -Hmm, I know that I and others have used git-annex on android with ssh, without encountering this problem. Odd. Oh well, was already patching out many other permissions checks in ssh, so added this one to the pile. -"""]] diff --git a/doc/bugs/id__95__rsa_on_android/comment_2_7039ed326c92211aa92e9276aba8c6b6._comment b/doc/bugs/id__95__rsa_on_android/comment_2_7039ed326c92211aa92e9276aba8c6b6._comment deleted file mode 100644 index 8500c41e5..000000000 --- a/doc/bugs/id__95__rsa_on_android/comment_2_7039ed326c92211aa92e9276aba8c6b6._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://smcv.pseudorandom.co.uk/" - nickname="smcv" - subject="comment 2" - date="2014-03-12T07:54:08Z" - content=""" -Would it be better to put the home directory under git-annex' directory -in `/data`, so it isn't available to every app (and every user, if more -than one) on the device? If other apps can write to its `.gitconfig` -then I think they can make git-annex run arbitrary code with its own -permissions. -"""]] diff --git a/doc/bugs/id__95__rsa_on_android/comment_3_cbe24ed08a7ef91c8c0c20ab9b7d25b7._comment b/doc/bugs/id__95__rsa_on_android/comment_3_cbe24ed08a7ef91c8c0c20ab9b7d25b7._comment deleted file mode 100644 index b972139a6..000000000 --- a/doc/bugs/id__95__rsa_on_android/comment_3_cbe24ed08a7ef91c8c0c20ab9b7d25b7._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 3" - date="2014-03-12T19:45:24Z" - content=""" -Well, that would simplify the ssh patching. - -Putting a git repository on /sdcard also allows other apps to do things with .git/config. I don't know if git-annex has permissions other apps might want to exploit.. Maybe the ability to use the network? -"""]] diff --git a/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6.mdwn b/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6.mdwn deleted file mode 100644 index 115b8a750..000000000 --- a/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -git-annex exists with "illegal hardware instruction" on OSX - -### What steps will reproduce the problem? - -git annex webapp - -### What version of git-annex are you using? On what operating system? - -git annex 5.20131230-g9a495e6 -OSX 10.9.1 - -### Please provide any additional information below. - -[[!format sh """ - -start git assistant with "git annex web app" -safari open tab, but shows connection refused -git annex crashed with "illegal hardware instruction" - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6/comment_1_515682c2338c861580105e869df648a1._comment b/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6/comment_1_515682c2338c861580105e869df648a1._comment deleted file mode 100644 index 2b9f629b1..000000000 --- a/doc/bugs/illegal_hardware_instruction_on_OSX_for_5.20131230-g9a495e6/comment_1_515682c2338c861580105e869df648a1._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.35" - subject="comment 1" - date="2014-01-07T15:37:18Z" - content=""" -This problem is fixed in the daily build. -"""]] diff --git a/doc/bugs/import_leaves_empty_directories_behind.mdwn b/doc/bugs/import_leaves_empty_directories_behind.mdwn deleted file mode 100644 index a2985dd75..000000000 --- a/doc/bugs/import_leaves_empty_directories_behind.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -### Please describe the problem. - -git annex import leaves empties directories behind. - -now maybe that's desired, but in this case, why are the *files* gone and not the directories? - -### What steps will reproduce the problem? - -<pre> -mkdir -p /tmp/foo/bar -touch /tmp/foo/bar/file -git annex import /tmp/foo -[ -d /tmp/foo/bar ] && echo 'fail: directory still there!' -</pre> - -### What version of git-annex are you using? On what operating system? - -5.20141125 - -> [[done]] per my earlier comment --[[Joey]] diff --git a/doc/bugs/import_leaves_empty_directories_behind/comment_1_8580ecc86a235323f88835cf8fbb7f47._comment b/doc/bugs/import_leaves_empty_directories_behind/comment_1_8580ecc86a235323f88835cf8fbb7f47._comment deleted file mode 100644 index 888cdd859..000000000 --- a/doc/bugs/import_leaves_empty_directories_behind/comment_1_8580ecc86a235323f88835cf8fbb7f47._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-06-15T18:22:49Z" - content=""" -I tend to see this as a feature, since I import from camera SD cards -which have their own directory structure and don't know how the camera -would react to the directories being deleted. - -Similarly, if I'm running some long-running process in a directory that's -dropping off files there, I don't want an import to delete the directory -out from under the process. -"""]] diff --git a/doc/bugs/import_leaves_stray___96__.tmp__96___files_if_interrupted.mdwn b/doc/bugs/import_leaves_stray___96__.tmp__96___files_if_interrupted.mdwn deleted file mode 100644 index 50037246d..000000000 --- a/doc/bugs/import_leaves_stray___96__.tmp__96___files_if_interrupted.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -### Please describe the problem. - -I have found various `.tmp` files in a directory in which I performed various `git annex import` that failed because the destination disk was full. - -These files should be removed when import detects that its has no more space to proceed and exists. - -### What version of git-annex are you using? On what operating system? - -git-annex 5.20140517.4 in Ubuntu 12.04. - -> The ".tmp" means this dropping is left by viaTmp, and I see why. -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/import_memleak_from_the_assistant.mdwn b/doc/bugs/import_memleak_from_the_assistant.mdwn deleted file mode 100644 index 5a0a0225b..000000000 --- a/doc/bugs/import_memleak_from_the_assistant.mdwn +++ /dev/null @@ -1,1608 +0,0 @@ -### Please describe the problem. -Git annex daemon are memleaking abundantly thus making it unusable for a long period of time. It is currently taking 38.8% of my available ram (8go) and has been launched arround 14h today. - -### What steps will reproduce the problem? -The assistant has been launched using "git annex assistant" on a repository -created by the Webapp (the Webapp wasn't running at that time). - -If I simply launch the Webapp, I've got the same result of memleaking. - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20131213 -build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - -On Ubuntu LTS using the ppa. - -### Please provide any additional information below. -This daemon.log come from a very fast moving repository but this also happen on other way slower moving repositories. - -[[!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 - -me@dolgoff ~/public/.git/annex ps avx | grep git -14647 pts/7 S+ 0:00 0 150 13493 948 0.0 grep -i --color=auto git -15910 ? Sl 273:24 0 39530 3879109 3207152 39.3 git-annex assistant -15925 ? R 134:10 1439 1283 544320 35660 0.4 git --git-dir=/home/me/public/.git --work-tree=/home/me/public -c core.bare=false cat-file --batch -15972 ? S 0:01 114 1283 530064 10576 0.1 git --git-dir=/home/me/public/.git --work-tree=/home/me/public -c core.bare=false cat-file --batch -16120 ? SN 0:00 0 1283 18196 1156 0.0 git --git-dir=/home/me/public/.git --work-tree=/home/me/public -c core.bare=false check-attr -z --stdin annex.backend annex.numcopies -- -25646 ? SNl 0:01 0 42547 222616 22132 0.2 git-annex transferkeys -25667 ? SN 0:00 0 1447 117648 1976 0.0 git --git-dir=/home/me/public/.git --work-tree=/home/me/public -c core.bare=false cat-file --batch -25677 ? SNs 0:00 0 410 42657 2620 0.0 ssh: .git/annex/ssh/griboiedov [mux] - -daemon.log -[2013-12-23 21:04:24 CET] NetWatcherFallback: Syncing with origin -From griboiedov:public - 331ab7e..763310f annex/direct/master -> origin/annex/direct/master - 4caf626..2171219 git-annex -> origin/git-annex - 73c5341..153ec5a synced/master -> origin/synced/master -Updating 73c5341..763310f -Fast-forward -Auto packing the repository for optimum performance. You may also -run "git gc" manually. See "git help gc" for more information. -warning: There are too many unreachable loose objects; run 'git prune' to remove them. - mails/.mhonarc.db | 2 +- - mails/{bin16MhWOPiG7.bin => binjMrfB7aM7s.bin} | 0 - mails/{binQBJzxA5RDD.bin => binuVoVGDloKB.bin} | 0 - mails/{jpgaShwRlHqXe.jpg => jpg9a_S8ignCJ.jpg} | 0 - mails/{jpgJuMwpbTZuo.jpg => jpgAU20k3zk5w.jpg} | 0 - mails/{jpgfkvs_VW3jY.jpg => jpgAsv158YPXC.jpg} | 0 - mails/{jpgLxB5GBQiyP.jpg => jpgCfz3HNRLYo.jpg} | 0 - mails/{jpg1QSm88B_oJ.jpg => jpgCw4FBEkcOV.jpg} | 0 - mails/{jpgy8l7kt7I0v.jpg => jpgJnSKE5skVx.jpg} | 0 - mails/{jpg8x0JSWWfmK.jpg => jpgK4Lmnj5kJU.jpg} | 0 - mails/{jpge0T37S_zYg.jpg => jpgKyEVJPJdPY.jpg} | 0 - mails/{jpg1jMp8X95a8.jpg => jpgMi7I6uLnaD.jpg} | 0 - mails/{jpg2JyFa9xlTU.jpg => jpgScmPPKPHFq.jpg} | 0 - mails/{jpgAnrbLOKtQO.jpg => jpgU2vrhPtw4a.jpg} | 0 - mails/{jpg9UIRRve9l7.jpg => jpgV1Ek5XTDpl.jpg} | 0 - mails/{jpg0du_rqAmnI.jpg => jpgVt3cWtM2fp.jpg} | 0 - mails/{jpgmyWk1QqZ0G.jpg => jpgVzzX55uqdu.jpg} | 0 - mails/{jpgNzn6pCkQ7B.jpg => jpgbS7_tLed4m.jpg} | 0 - mails/{jpgmChZ6KvYvR.jpg => jpgdQNUXemgWT.jpg} | 0 - mails/{jpgwu68ViO7tN.jpg => jpgh1EzKSHWvb.jpg} | 0 - mails/{jpgmUuI33SG9G.jpg => jpghvPaq3_Be0.jpg} | 0 - mails/{jpgvzPlOi4YH2.jpg => jpgim5vpaDawh.jpg} | 0 - mails/{jpgysNt2t743E.jpg => jpgjY_paWcDcr.jpg} | 0 - mails/{jpgFicFpbY5n4.jpg => jpgkU70wDyd7n.jpg} | 0 - mails/{jpgpjFS0Ztnqa.jpg => jpgmFXSd2Dp97.jpg} | 0 - mails/{jpgqOZX1xKVfl.jpg => jpgoHLfpoWcUO.jpg} | 0 - mails/{jpgTVf7RAQot8.jpg => jpgpIVZxq60Dk.jpg} | 0 - mails/{jpgkq63BbVlrP.jpg => jpgrzViZx_4aI.jpg} | 0 - mails/{jpgxpwzaJnSuX.jpg => jpgtvEG4unHFl.jpg} | 0 - mails/{jpgldUBRrRrcn.jpg => jpgwgZCUHCRLD.jpg} | 0 - mails/{jpgsKpQQEouso.jpg => jpgyDMQ3JRqJQ.jpg} | 0 - mails/msg00006.html | 2 +- - mails/msg00018.html | 2 +- - mails/msg00023.html | 2 +- - mails/msg00024.html | 2 +- - mails/msg00025.html | 2 +- - mails/msg00026.html | 2 +- - mails/msg00027.html | 2 +- - mails/msg00028.html | 2 +- - mails/msg00032.html | 2 +- - mails/msg00040.html | 2 +- - mails/msg00041.html | 2 +- - mails/msg00042.html | 2 +- - mails/msg00055.html | 2 +- - mails/{pdfyd4yHyuh7I.pdf => pdf82oysVxMKf.pdf} | 0 - mails/{pdfX5i1zjd35G.pdf => pdfDH4ZUAcsJE.pdf} | 0 - mails/{pdfDyhw6AitFo.pdf => pdfPePGLsDAym.pdf} | 0 - mails/{pdfkLRxiO4YS0.pdf => pdfU9I3NUvHOG.pdf} | 0 - mails/{pgpI_5jxFR7VZ.pgp => pgpBKaIcivKYa.pgp} | 0 - mails/{pngKStItI4meN.png => png9O3vtGcotx.png} | 0 - mails/{pngN5cn2FvoWV.png => pngBkJAx0zfhF.png} | 0 - 51 files changed, 14 insertions(+), 14 deletions(-) - rename mails/{bin16MhWOPiG7.bin => binjMrfB7aM7s.bin} (100%) - rename mails/{binQBJzxA5RDD.bin => binuVoVGDloKB.bin} (100%) - rename mails/{jpgaShwRlHqXe.jpg => jpg9a_S8ignCJ.jpg} (100%) - rename mails/{jpgJuMwpbTZuo.jpg => jpgAU20k3zk5w.jpg} (100%) - rename mails/{jpgfkvs_VW3jY.jpg => jpgAsv158YPXC.jpg} (100%) - rename mails/{jpgLxB5GBQiyP.jpg => jpgCfz3HNRLYo.jpg} (100%) - rename mails/{jpg1QSm88B_oJ.jpg => jpgCw4FBEkcOV.jpg} (100%) - rename mails/{jpgy8l7kt7I0v.jpg => jpgJnSKE5skVx.jpg} (100%) - rename mails/{jpg8x0JSWWfmK.jpg => jpgK4Lmnj5kJU.jpg} (100%) - rename mails/{jpge0T37S_zYg.jpg => jpgKyEVJPJdPY.jpg} (100%) - rename mails/{jpg1jMp8X95a8.jpg => jpgMi7I6uLnaD.jpg} (100%) - rename mails/{jpg2JyFa9xlTU.jpg => jpgScmPPKPHFq.jpg} (100%) - rename mails/{jpgAnrbLOKtQO.jpg => jpgU2vrhPtw4a.jpg} (100%) - rename mails/{jpg9UIRRve9l7.jpg => jpgV1Ek5XTDpl.jpg} (100%) - rename mails/{jpg0du_rqAmnI.jpg => jpgVt3cWtM2fp.jpg} (100%) - rename mails/{jpgmyWk1QqZ0G.jpg => jpgVzzX55uqdu.jpg} (100%) - rename mails/{jpgNzn6pCkQ7B.jpg => jpgbS7_tLed4m.jpg} (100%) - rename mails/{jpgmChZ6KvYvR.jpg => jpgdQNUXemgWT.jpg} (100%) - rename mails/{jpgwu68ViO7tN.jpg => jpgh1EzKSHWvb.jpg} (100%) - rename mails/{jpgmUuI33SG9G.jpg => jpghvPaq3_Be0.jpg} (100%) - rename mails/{jpgvzPlOi4YH2.jpg => jpgim5vpaDawh.jpg} (100%) - rename mails/{jpgysNt2t743E.jpg => jpgjY_paWcDcr.jpg} (100%) - rename mails/{jpgFicFpbY5n4.jpg => jpgkU70wDyd7n.jpg} (100%) - rename mails/{jpgpjFS0Ztnqa.jpg => jpgmFXSd2Dp97.jpg} (100%) - rename mails/{jpgqOZX1xKVfl.jpg => jpgoHLfpoWcUO.jpg} (100%) - rename mails/{jpgTVf7RAQot8.jpg => jpgpIVZxq60Dk.jpg} (100%) - rename mails/{jpgkq63BbVlrP.jpg => jpgrzViZx_4aI.jpg} (100%) - rename mails/{jpgxpwzaJnSuX.jpg => jpgtvEG4unHFl.jpg} (100%) - rename mails/{jpgldUBRrRrcn.jpg => jpgwgZCUHCRLD.jpg} (100%) - rename mails/{jpgsKpQQEouso.jpg => jpgyDMQ3JRqJQ.jpg} (100%) - rename mails/{pdfyd4yHyuh7I.pdf => pdf82oysVxMKf.pdf} (100%) - rename mails/{pdfX5i1zjd35G.pdf => pdfDH4ZUAcsJE.pdf} (100%) - rename mails/{pdfDyhw6AitFo.pdf => pdfPePGLsDAym.pdf} (100%) - rename mails/{pdfkLRxiO4YS0.pdf => pdfU9I3NUvHOG.pdf} (100%) - rename mails/{pgpI_5jxFR7VZ.pgp => pgpBKaIcivKYa.pgp} (100%) - rename mails/{pngKStItI4meN.png => png9O3vtGcotx.png} (100%) - rename mails/{pngN5cn2FvoWV.png => pngBkJAx0zfhF.png} (100%) -[2013-12-23 21:04:40 CET] Committer: Committing changes to git -[2013-12-23 21:04:40 CET] Pusher: Syncing with public, dolgoff, origin -error: Ref refs/heads/synced/git-annex is at 4f98427ba635b1548da21b5e6e1a84c49f708284 but expected 217121951ca4ede24d91fe92acee9061a527ba93 -remote: error: failed to lock refs/heads/synced/git-annex[K -Auto packing the repository for optimum performance. -Auto packing the repository for optimum performance. -fatal: Unable to create '/home/me/public/.git/packed-refs.lock': Le fichier existe. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -error: failed to run pack-refs -To /home/me/public - ! [remote rejected] git-annex -> synced/git-annex (failed to lock) -error: failed to push some refs to '/home/me/public' -[2013-12-23 21:04:42 CET] Committer: Adding pngBkJAx0zfhF.png png9O3vtGcotx.png pgpBKaIcivKYa.pgp pdfU9I3NUvHOG.pdf pdfPePGLsDAym.pdf pdfDH4ZUAcsJE.pdf pdf82oysVxMKf.pdf msg00040.html msg00032.html and 39 other files -ok -(Recording state in git...) -(Recording state in git...) -(merging synced/git-annex into git-annex...) -(Recording state in git...) - -(Recording state in git...) -(Recording state in git...) -add mails/pngBkJAx0zfhF.png ok -add mails/png9O3vtGcotx.png ok -add mails/pgpBKaIcivKYa.pgp ok -add mails/pdfU9I3NUvHOG.pdf ok -add mails/pdfPePGLsDAym.pdf ok -add mails/pdfDH4ZUAcsJE.pdf ok -add mails/pdf82oysVxMKf.pdf ok -add mails/msg00040.html ok -add mails/msg00032.html ok -add mails/msg00028.html ok -add mails/msg00027.html ok -add mails/msg00026.html ok -add mails/msg00025.html ok -add mails/msg00024.html ok -add mails/msg00023.html ok -add mails/msg00018.html ok -add mails/msg00006.html ok -add mails/jpgyDMQ3JRqJQ.jpg ok -add mails/jpgwgZCUHCRLD.jpg ok -add mails/jpgtvEG4unHFl.jpg ok -add mails/jpgrzViZx_4aI.jpg ok -add mails/jpgpIVZxq60Dk.jpg ok -add mails/jpgoHLfpoWcUO.jpg ok -add mails/jpgmFXSd2Dp97.jpg ok -add mails/jpgmFXSd2Dp97.jpg ok -add mails/jpgkU70wDyd7n.jpg ok -add mails/jpgjY_paWcDcr.jpg ok -add mails/jpgim5vpaDawh.jpg ok -add mails/jpghvPaq3_Be0.jpg ok -add mails/jpgh1EzKSHWvb.jpg ok -add mails/jpgdQNUXemgWT.jpg ok -add mails/jpgbS7_tLed4m.jpg ok -add mails/jpgbS7_tLed4m.jpg ok -add mails/jpgVzzX55uqdu.jpg ok -add mails/jpgVzzX55uqdu.jpg ok -add mails/jpgVt3cWtM2fp.jpg ok -add mails/jpgV1Ek5XTDpl.jpg ok -add mails/jpgV1Ek5XTDpl.jpg ok -add mails/jpgU2vrhPtw4a.jpg ok -add mails/jpgU2vrhPtw4a.jpg ok -add mails/jpgScmPPKPHFq.jpg ok -add mails/jpgScmPPKPHFq.jpg ok -add mails/jpgMi7I6uLnaD.jpg ok -add mails/jpgMi7I6uLnaD.jpg ok -add mails/jpgKyEVJPJdPY.jpg ok -add mails/jpgKyEVJPJdPY.jpg ok -add mails/jpgK4Lmnj5kJU.jpg ok -add mails/jpgK4Lmnj5kJU.jpg ok -add mails/jpgJnSKE5skVx.jpg ok -add mails/jpgCw4FBEkcOV.jpg ok -add mails/jpgCw4FBEkcOV.jpg ok -add mails/jpgCfz3HNRLYo.jpg ok -add mails/jpgCfz3HNRLYo.jpg ok -add mails/jpgAsv158YPXC.jpg ok -add mails/jpgAsv158YPXC.jpg ok -add mails/jpgAU20k3zk5w.jpg ok -add mails/jpgAU20k3zk5w.jpg ok -add mails/jpg9a_S8ignCJ.jpg ok -add mails/jpg9a_S8ignCJ.jpg ok -add mails/binuVoVGDloKB.bin ok -add mails/binjMrfB7aM7s.bin ok -add mails/binjMrfB7aM7s.bin ok -add mails/.mhonarc.db [2013-12-23 21:04:43 CET] Committer: Committing changes to git -[2013-12-23 21:04:43 CET] Transferrer: Uploaded msg00028.html -[2013-12-23 21:04:43 CET] Transferrer: Uploaded jpgyDMQ3JRqJQ.jpg -[2013-12-23 21:04:43 CET] Transferrer: Uploaded jpgkU70wDyd7n.jpg -[2013-12-23 21:04:43 CET] Transferrer: Uploaded jpgVt3cWtM2fp.jpg -[2013-12-23 21:04:43 CET] Transferrer: Uploaded jpgKyEVJPJdPY.jpg -[2013-12-23 21:04:43 CET] Transferrer: Uploaded jpgAsv158YPXC.jpg -[2013-12-23 21:04:43 CET] Transferrer: Uploaded .mhonarc.db -[2013-12-23 21:04:48 CET] Committer: Adding msg00041.html -ok -(Recording state in git...) -add mails/msg00041.html [2013-12-23 21:04:48 CET] Committer: Committing changes to git -warning: There are too many unreachable loose objects; run 'git prune' to remove them. -To /home/me/public - 2171219..4f98427 git-annex -> synced/git-annex -error: Ref refs/heads/synced/git-annex is at 90996528a22e94d52911e1abc8b90eb451d40dee but expected b0f556fff29e038eba46c95fecb4d1cc57d7dacd -remote: error: failed to lock refs/heads/synced/git-annex[K -To griboiedov:public - ! [remote rejected] git-annex -> synced/git-annex (failed to lock) -error: failed to push some refs to 'griboiedov:public' -To griboiedov:public - b0f556f..9099652 git-annex -> synced/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -From /home/me/public - 73c5341..763310f annex/direct/master -> dolgoff/annex/direct/master - e326ebb..c8c86fe git-annex -> dolgoff/git-annex - e326ebb..4f98427 synced/git-annex -> dolgoff/synced/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-12-23 21:04:59 CET] Committer: Adding msg00042.html -ok -(Recording state in git...) -add mails/msg00042.html [2013-12-23 21:04:59 CET] Committer: Committing changes to git -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -From griboiedov:public - 2171219..c7b4195 git-annex -> origin/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -Auto packing the repository for optimum performance. -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-12-23 21:05:07 CET] Committer: Adding msg00055.html -ok -(Recording state in git...) -(merging synced/git-annex into git-annex...) -(Recording state in git...) -add mails/msg00055.html [2013-12-23 21:05:07 CET] Committer: Committing changes to git -To griboiedov:public - 9099652..c8c86fe git-annex -> synced/git-annex -warning: There are too many unreachable loose objects; run 'git prune' to remove them. -To /home/me/public - c7b4195..c6278b9 git-annex -> synced/git-annex -[2013-12-23 21:05:13 CET] Pusher: Syncing with public, dolgoff, origin -fatal: Unable to create '/home/me/public/.git/refs/heads/synced/git-annex.lock': Le fichier existe. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: The remote end hung up unexpectedly -fatal: The remote end hung up unexpectedly -Auto packing the repository for optimum performance. -To griboiedov:public - c8c86fe..c6278b9 git-annex -> synced/git-annex -warning: There are too many unreachable loose objects; run 'git prune' to remove them. -To /home/me/public - c6278b9..fe337a3 git-annex -> synced/git-annex -From /home/me/public - c8c86fe..fe337a3 git-annex -> dolgoff/git-annex - c6278b9..fe337a3 synced/git-annex -> dolgoff/synced/git-annex -Everything up-to-date -[2013-12-23 22:04:54 CET] NetWatcherFallback: Syncing with origin -From griboiedov:public - 763310f..4a82c94 annex/direct/master -> origin/annex/direct/master - c7b4195..4051e5f git-annex -> origin/git-annex - 763310f..4a82c94 synced/master -> origin/synced/master -Updating 763310f..4a82c94 -Fast-forward -Auto packing the repository for optimum performance. You may also -run "git gc" manually. See "git help gc" for more information. -warning: There are too many unreachable loose objects; run 'git prune' to remove them. - code.html | 2 +- - libre.html | 2 +- - mails/.mhonarc.db | 2 +- - mails/{binuVoVGDloKB.bin => bin5AtY2Z6c7Y.bin} | 0 - mails/{binjMrfB7aM7s.bin => binrPJBAv0ZVt.bin} | 0 - mails/{jpghvPaq3_Be0.jpg => jpg1UMqWMrG7a.jpg} | 0 - mails/{jpgK4Lmnj5kJU.jpg => jpg3DFKEEjrkk.jpg} | 0 - mails/{jpgMi7I6uLnaD.jpg => jpg3krTrtBEkb.jpg} | 0 - mails/{jpgbS7_tLed4m.jpg => jpg7fboROgExn.jpg} | 0 - mails/{jpgVt3cWtM2fp.jpg => jpg924jbjXysn.jpg} | 0 - mails/{jpgCfz3HNRLYo.jpg => jpgE97mvEaO69.jpg} | 0 - mails/{jpgAU20k3zk5w.jpg => jpgFNaMv1VRz6.jpg} | 0 - mails/{jpgmFXSd2Dp97.jpg => jpgHsS_2rOL6Y.jpg} | 0 - mails/{jpgScmPPKPHFq.jpg => jpgKXplac49vA.jpg} | 0 - mails/{jpgJnSKE5skVx.jpg => jpgLRAgF_kk2y.jpg} | 0 - mails/{jpgKyEVJPJdPY.jpg => jpgLqoIemkRHW.jpg} | 0 - mails/{jpgVzzX55uqdu.jpg => jpgNehfnysPB_.jpg} | 0 - mails/{jpg9a_S8ignCJ.jpg => jpgOerFzfMUut.jpg} | 0 - mails/{jpgim5vpaDawh.jpg => jpgQJv5bJd7Z_.jpg} | 0 - mails/{jpgU2vrhPtw4a.jpg => jpgTmkvSP5OCN.jpg} | 0 - mails/{jpgAsv158YPXC.jpg => jpgWN0orLG26U.jpg} | 0 - mails/{jpgkU70wDyd7n.jpg => jpg_TlOpz5yEI.jpg} | 0 - mails/{jpgCw4FBEkcOV.jpg => jpgb6Amcdbt_p.jpg} | 0 - mails/{jpgrzViZx_4aI.jpg => jpgd4jRWMqhI3.jpg} | 0 - mails/{jpgyDMQ3JRqJQ.jpg => jpgdu9EKZP18V.jpg} | 0 - mails/{jpgoHLfpoWcUO.jpg => jpgfTUANHcfnz.jpg} | 0 - mails/{jpgjY_paWcDcr.jpg => jpggs4xMeCwqp.jpg} | 0 - mails/{jpgh1EzKSHWvb.jpg => jpgkoEH5SoLvR.jpg} | 0 - mails/{jpgwgZCUHCRLD.jpg => jpgmcn6CC58d1.jpg} | 0 - mails/{jpgV1Ek5XTDpl.jpg => jpgqYEKj5yxhL.jpg} | 0 - mails/{jpgtvEG4unHFl.jpg => jpgygiJgjjLdg.jpg} | 0 - mails/{jpgdQNUXemgWT.jpg => jpgzKwM4quoCJ.jpg} | 0 - mails/{jpgpIVZxq60Dk.jpg => jpgzTcmXOboBC.jpg} | 0 - mails/maillist.html | 2 +- - mails/msg00006.html | 2 +- - mails/msg00018.html | 2 +- - mails/msg00023.html | 2 +- - mails/msg00024.html | 2 +- - mails/msg00025.html | 2 +- - mails/msg00026.html | 2 +- - mails/msg00027.html | 2 +- - mails/msg00028.html | 2 +- - mails/msg00032.html | 2 +- - mails/msg00040.html | 2 +- - mails/msg00041.html | 2 +- - mails/msg00042.html | 2 +- - mails/msg00048.html | 2 +- - mails/msg00049.html | 2 +- - mails/msg00050.html | 2 +- - mails/msg00051.html | 2 +- - mails/msg00052.html | 1 - - mails/msg00053.html | 1 - - mails/msg00054.html | 1 - - mails/msg00055.html | 1 - - mails/{pdfDH4ZUAcsJE.pdf => pdf2EajO3nKRV.pdf} | 0 - mails/{pdfU9I3NUvHOG.pdf => pdf3vLwdvymu6.pdf} | 0 - mails/{pdfPePGLsDAym.pdf => pdfF0TCUFYgxV.pdf} | 0 - mails/{pdf82oysVxMKf.pdf => pdfmQ9u5fWUkK.pdf} | 0 - mails/{pgpBKaIcivKYa.pgp => pgpcO0uja6Z0Q.pgp} | 0 - mails/{png9O3vtGcotx.png => pngfmEm5tkUDn.png} | 0 - mails/{pngBkJAx0zfhF.png => pngphoxRepygs.png} | 0 - mails/threads.html | 2 +- - output.html | 2 +- - reflets.html | 2 +- - 64 files changed, 23 insertions(+), 27 deletions(-) - rename mails/{binuVoVGDloKB.bin => bin5AtY2Z6c7Y.bin} (100%) - rename mails/{binjMrfB7aM7s.bin => binrPJBAv0ZVt.bin} (100%) - rename mails/{jpghvPaq3_Be0.jpg => jpg1UMqWMrG7a.jpg} (100%) - rename mails/{jpgK4Lmnj5kJU.jpg => jpg3DFKEEjrkk.jpg} (100%) - rename mails/{jpgMi7I6uLnaD.jpg => jpg3krTrtBEkb.jpg} (100%) - rename mails/{jpgbS7_tLed4m.jpg => jpg7fboROgExn.jpg} (100%) - rename mails/{jpgVt3cWtM2fp.jpg => jpg924jbjXysn.jpg} (100%) - rename mails/{jpgCfz3HNRLYo.jpg => jpgE97mvEaO69.jpg} (100%) - rename mails/{jpgAU20k3zk5w.jpg => jpgFNaMv1VRz6.jpg} (100%) - rename mails/{jpgmFXSd2Dp97.jpg => jpgHsS_2rOL6Y.jpg} (100%) - rename mails/{jpgScmPPKPHFq.jpg => jpgKXplac49vA.jpg} (100%) - rename mails/{jpgJnSKE5skVx.jpg => jpgLRAgF_kk2y.jpg} (100%) - rename mails/{jpgKyEVJPJdPY.jpg => jpgLqoIemkRHW.jpg} (100%) - rename mails/{jpgVzzX55uqdu.jpg => jpgNehfnysPB_.jpg} (100%) - rename mails/{jpg9a_S8ignCJ.jpg => jpgOerFzfMUut.jpg} (100%) - rename mails/{jpgim5vpaDawh.jpg => jpgQJv5bJd7Z_.jpg} (100%) - rename mails/{jpgU2vrhPtw4a.jpg => jpgTmkvSP5OCN.jpg} (100%) - rename mails/{jpgAsv158YPXC.jpg => jpgWN0orLG26U.jpg} (100%) - rename mails/{jpgkU70wDyd7n.jpg => jpg_TlOpz5yEI.jpg} (100%) - rename mails/{jpgCw4FBEkcOV.jpg => jpgb6Amcdbt_p.jpg} (100%) - rename mails/{jpgrzViZx_4aI.jpg => jpgd4jRWMqhI3.jpg} (100%) - rename mails/{jpgyDMQ3JRqJQ.jpg => jpgdu9EKZP18V.jpg} (100%) - rename mails/{jpgoHLfpoWcUO.jpg => jpgfTUANHcfnz.jpg} (100%) - rename mails/{jpgjY_paWcDcr.jpg => jpggs4xMeCwqp.jpg} (100%) - rename mails/{jpgh1EzKSHWvb.jpg => jpgkoEH5SoLvR.jpg} (100%) - rename mails/{jpgwgZCUHCRLD.jpg => jpgmcn6CC58d1.jpg} (100%) - rename mails/{jpgV1Ek5XTDpl.jpg => jpgqYEKj5yxhL.jpg} (100%) - rename mails/{jpgtvEG4unHFl.jpg => jpgygiJgjjLdg.jpg} (100%) - rename mails/{jpgdQNUXemgWT.jpg => jpgzKwM4quoCJ.jpg} (100%) - rename mails/{jpgpIVZxq60Dk.jpg => jpgzTcmXOboBC.jpg} (100%) - delete mode 120000 mails/msg00052.html - delete mode 120000 mails/msg00053.html - delete mode 120000 mails/msg00054.html - delete mode 120000 mails/msg00055.html - rename mails/{pdfDH4ZUAcsJE.pdf => pdf2EajO3nKRV.pdf} (100%) - rename mails/{pdfU9I3NUvHOG.pdf => pdf3vLwdvymu6.pdf} (100%) - rename mails/{pdfPePGLsDAym.pdf => pdfF0TCUFYgxV.pdf} (100%) - rename mails/{pdf82oysVxMKf.pdf => pdfmQ9u5fWUkK.pdf} (100%) - rename mails/{pgpBKaIcivKYa.pgp => pgpcO0uja6Z0Q.pgp} (100%) - rename mails/{png9O3vtGcotx.png => pngfmEm5tkUDn.png} (100%) - rename mails/{pngBkJAx0zfhF.png => pngphoxRepygs.png} (100%) -[2013-12-23 22:05:12 CET] Committer: Committing changes to git -[2013-12-23 22:05:13 CET] Pusher: Syncing with public, dolgoff, origin -Auto packing the repository for optimum performance. -fatal: Unable to create '/home/me/public/.git/refs/heads/synced/git-annex.lock': Le fichier existe. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: The remote end hung up unexpectedly -fatal: The remote end hung up unexpectedly -[2013-12-23 22:05:16 CET] Committer: Adding reflets.html output.html threads.html pngphoxRepygs.png pngfmEm5tkUDn.png pgpcO0uja6Z0Q.pgp pdfmQ9u5fWUkK.pdf pdfF0TCUFYgxV.pdf pdf3vLwdvymu6.pdf and 51 other files -ok -(Recording state in git...) -(Recording state in git...) -(merging synced/git-annex into git-annex...) -(Recording state in git...) - -(Recording state in git...) -(Recording state in git...) -(Recording state in git...) -add reflets.html ok -add reflets.html ok -add output.html ok -add mails/threads.html ok -add mails/pngphoxRepygs.png ok -add mails/pngfmEm5tkUDn.png ok -add mails/pgpcO0uja6Z0Q.pgp ok -add mails/pdfmQ9u5fWUkK.pdf ok -add mails/pdfF0TCUFYgxV.pdf ok -add mails/pdf3vLwdvymu6.pdf ok -add mails/pdf2EajO3nKRV.pdf ok -add mails/msg00051.html ok -add mails/msg00050.html ok -add mails/msg00049.html ok -add mails/msg00048.html ok -add mails/msg00042.html ok -add mails/msg00041.html ok -add mails/msg00040.html ok -add mails/msg00032.html ok -add mails/msg00032.html ok -add mails/msg00028.html ok -add mails/msg00027.html ok -add mails/msg00026.html ok -add mails/msg00025.html ok -add mails/msg00024.html ok -add mails/msg00023.html ok -add mails/msg00018.html ok -add mails/msg00006.html ok -add mails/maillist.html ok -add mails/jpgzTcmXOboBC.jpg ok -add mails/jpgzTcmXOboBC.jpg ok -add mails/jpgzKwM4quoCJ.jpg ok -add mails/jpgygiJgjjLdg.jpg ok -add mails/jpgqYEKj5yxhL.jpg ok -add mails/jpgmcn6CC58d1.jpg ok -add mails/jpgkoEH5SoLvR.jpg ok -add mails/jpggs4xMeCwqp.jpg ok -add mails/jpggs4xMeCwqp.jpg ok -add mails/jpgfTUANHcfnz.jpg ok -add mails/jpgdu9EKZP18V.jpg ok -add mails/jpgd4jRWMqhI3.jpg ok -add mails/jpgb6Amcdbt_p.jpg ok -add mails/jpgb6Amcdbt_p.jpg ok -add mails/jpg_TlOpz5yEI.jpg ok -add mails/jpgWN0orLG26U.jpg ok -add mails/jpgWN0orLG26U.jpg ok -add mails/jpgTmkvSP5OCN.jpg ok -add mails/jpgTmkvSP5OCN.jpg ok -add mails/jpgQJv5bJd7Z_.jpg ok -add mails/jpgOerFzfMUut.jpg ok -add mails/jpgOerFzfMUut.jpg ok -add mails/jpgNehfnysPB_.jpg ok -add mails/jpgNehfnysPB_.jpg ok -add mails/jpgLqoIemkRHW.jpg ok -add mails/jpgLqoIemkRHW.jpg ok -add mails/jpgLRAgF_kk2y.jpg ok -add mails/jpgKXplac49vA.jpg ok -add mails/jpgKXplac49vA.jpg ok -add mails/jpgHsS_2rOL6Y.jpg ok -add mails/jpgHsS_2rOL6Y.jpg ok -add mails/jpgFNaMv1VRz6.jpg ok -add mails/jpgFNaMv1VRz6.jpg ok -add mails/jpgE97mvEaO69.jpg ok -add mails/jpgE97mvEaO69.jpg ok -add mails/jpg924jbjXysn.jpg ok -add mails/jpg7fboROgExn.jpg ok -add mails/jpg7fboROgExn.jpg ok -add mails/jpg3krTrtBEkb.jpg ok -add mails/jpg3krTrtBEkb.jpg ok -add mails/jpg3DFKEEjrkk.jpg ok -add mails/jpg3DFKEEjrkk.jpg ok -add mails/jpg1UMqWMrG7a.jpg ok -add mails/binrPJBAv0ZVt.bin ok -add mails/bin5AtY2Z6c7Y.bin ok -add mails/.mhonarc.db ok -add libre.html ok -add code.html [2013-12-23 22:05:17 CET] Committer: Committing changes to git -[2013-12-23 22:05:17 CET] Transferrer: Uploaded jpgb6Amcdbt_p.jpg -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -fatal: Unable to create '/home/me/public/.git/refs/heads/synced/git-annex.lock': File exists. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -git-annex-shell: fatal: The remote end hung up unexpectedly -fatal: The remote end hung up unexpectedly -key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -To griboiedov:public - c6278b9..d7c3c7d git-annex -> synced/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -warning: There are too many unreachable loose objects; run 'git prune' to remove them. -To /home/me/public - 4051e5f..8092c30 git-annex -> synced/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -From /home/me/public - 763310f..2ec4f5d annex/direct/master -> dolgoff/annex/direct/master - fe337a3..8092c30 git-annex -> dolgoff/git-annex - fe337a3..8092c30 synced/git-annex -> dolgoff/synced/git-annex - 763310f..6024c22 synced/master -> dolgoff/synced/master -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -Everything up-to-date -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -To griboiedov:public - d7c3c7d..8092c30 git-annex -> synced/git-annex - 4a82c94..2ec4f5d annex/direct/master -> synced/master -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-12-23 22:05:37 CET] Pusher: Syncing with public, dolgoff, origin -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -fatal: Unable to create '/home/me/public/.git/refs/heads/synced/git-annex.lock': Le fichier existe. - -If no other git process is currently running, this probably means a -git process crashed in this repository earlier. Make sure no other git -process is running and remove the file manually to continue. -fatal: The remote end hung up unexpectedly -fatal: The remote end hung up unexpectedly -Auto packing the repository for optimum performance. -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: To griboiedov:public - 8092c30..3f6f227 key is already present in annexgit-annex -> synced/git-annex - -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -warning: There are too many unreachable loose objects; run 'git prune' to remove them. -To /home/me/public - 8092c30..3f6f227 git-annex -> synced/git-annex -From /home/me/public - 8092c30..3f6f227 git-annex -> dolgoff/git-annex - 8092c30..3f6f227 synced/git-annex -> dolgoff/synced/git-annex -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -Everything up-to-date -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -git-annex-shell: key is already present in annex -rsync: connection unexpectedly closed (0 bytes received so far) [sender] -rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] -[2013-12-23 23:03:21 CET] SanityCheckerHourly: Rotated logs due to size: 1004794 - -# End of transcript or log. -"""]] - -> [[Fixed|done]]. This was several garden-variety haskell laziness leaks, -> all fixed by adding strictness annotations. -> -> Before: [[leakbefore.png]] -> After: [[leakafter.png]] -> -> Looks like I got them all, and it returns to running in constant space -> after adding and uploading the files (which can take memory porportional -> to the number of files that were added/changed at once). --[[Joey]] diff --git a/doc/bugs/import_memleak_from_the_assistant/comment_1_81c80ca3ea288c651ccf45c83477e058._comment b/doc/bugs/import_memleak_from_the_assistant/comment_1_81c80ca3ea288c651ccf45c83477e058._comment deleted file mode 100644 index e551c357f..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/comment_1_81c80ca3ea288c651ccf45c83477e058._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.227" - subject="comment 1" - date="2013-12-24T20:51:30Z" - content=""" -How many files are in this repository? - -There are various ways to profile git-annex's memory use, but they all require building it from source. For example, it can be built with [[EKG_support|ekg]]. -"""]] diff --git a/doc/bugs/import_memleak_from_the_assistant/comment_2_56089b7ad5d02c39ae0aacb442d789e9._comment b/doc/bugs/import_memleak_from_the_assistant/comment_2_56089b7ad5d02c39ae0aacb442d789e9._comment deleted file mode 100644 index dbc63d234..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/comment_2_56089b7ad5d02c39ae0aacb442d789e9._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~psycojoker" - nickname="psycojoker" - subject="comment 2" - date="2014-01-04T04:43:26Z" - content=""" -There are 139 files in this repo but this repos is updated very frequently (the files are generated every 10min). - -After a lot of fight with cabal and cabal-dev, I've managed to make EKG run, here is a screenshotof the result after hours of run and an actual consumption of 33.8% of 8gb of ram. - -http://pix.toile-libre.org/upload/original/1388810323.png - -But looking at it I don't know how it can be usefull. I don't know very well the haskell ecosystem, don't hesitate to point me to things that could help. - -On a more positive note: git annex compiled from cabal (and from source) seems to eat my available memory way slower than the one from the ubuntu ppa. -"""]] diff --git a/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment b/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment deleted file mode 100644 index 6d03b4cdb..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/comment_3_b193a4a0901c681b59a97b93b456765b._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.35" - subject="comment 3" - date="2014-01-05T20:41:35Z" - content=""" -Well, EKG either cannot see the leak, or perhaps haskell profiling generally cannot see it. Don't have a lot of experience with EKG, it's just a lot easier to ask for than full ghc profiling data.. - -It's certainly useful information that you are constantly changing the files. - -I have tried to replicate this setup, with a few hundred files, and writing random stuff to them repeatedly. The RSS did not grow at all despite repeatedly changing and committing the files. - -I then tried adding a remote for it to sync with, and see evidence of a small leak there -- around 8 bytes per file transferred. The leak appears to be in the transfer code, not the git sync code; it happens with both git remotes and with directory special remotes. - -"""]] diff --git a/doc/bugs/import_memleak_from_the_assistant/comment_4_d9464c7dc41773650ef7291391e1b414._comment b/doc/bugs/import_memleak_from_the_assistant/comment_4_d9464c7dc41773650ef7291391e1b414._comment deleted file mode 100644 index 11aeff31a..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/comment_4_d9464c7dc41773650ef7291391e1b414._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~psycojoker" - nickname="psycojoker" - subject="comment 4" - date="2014-01-06T01:31:14Z" - content=""" -Great, don't hesitate to ask me if you need more informations! - -Thanks :) -"""]] diff --git a/doc/bugs/import_memleak_from_the_assistant/leakafter.png b/doc/bugs/import_memleak_from_the_assistant/leakafter.png Binary files differdeleted file mode 100644 index 32c27f370..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/leakafter.png +++ /dev/null diff --git a/doc/bugs/import_memleak_from_the_assistant/leakbefore.png b/doc/bugs/import_memleak_from_the_assistant/leakbefore.png Binary files differdeleted file mode 100644 index 9a04bfb20..000000000 --- a/doc/bugs/import_memleak_from_the_assistant/leakbefore.png +++ /dev/null diff --git a/doc/bugs/importfeed_--relaxed_fails_with_HEAD-rejecting_servers.mdwn b/doc/bugs/importfeed_--relaxed_fails_with_HEAD-rejecting_servers.mdwn deleted file mode 100644 index f7b6199ff..000000000 --- a/doc/bugs/importfeed_--relaxed_fails_with_HEAD-rejecting_servers.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -### Please describe the problem. - -Calling "git annex importfeed --relaxed" on a url of a BBC podcast -fails just like a "git annex addurl --fast" (and not relaxed) on the -url of a show: - - addurl open.live.bbc.co.uk_mediaselector_5_redir_version_2.0_mediaset_audio_nondrm_download_proto_http_vpid_p02y8kfc.mp3 - unable to access url: http://open.live.bbc.co.uk/mediaselector/5/redir/version/2.0/mediaset/audio-nondrm-download/proto/http/vpid/p02y8kfc.mp3 - failed - git-annex: addurl: 1 failed - -I suppose that is because HEAD on that same URL returns 403 Forbidden -(addurl without fast works just fine). - -"git annex addurl --relaxed" works on the given url. - - -### What steps will reproduce the problem? - -I ran into this bug trying to importfeed various BBC podcasts. For instance: - - $ git annex importfeed --relaxed 'http://www.bbc.co.uk/programmes/p02pc9x6/episodes/downloads.rss' - (checking known urls...) - importfeed http://www.bbc.co.uk/programmes/p02pc9x6/episodes/downloads.rss - /tmp/feed3947 100%[=======================================================>] 8,39K --.-KB/s en 0,007s - addurl Comedy_of_the_Week/In_and_Out_of_the_Kitchen__Episode_1__The_Supplement.mp3 - unable to access url: http://open.live.bbc.co.uk/mediaselector/5/redir/version/2.0/mediaset/audio-nondrm-download/proto/http/vpid/p02yy1hn.mp3 - failed - - warning: problem downloading item - ok - - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20150731-1 on a quite up-to-date debian unstable. - -> Thanks for a nice test case. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds.mdwn b/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds.mdwn deleted file mode 100644 index bed954a9e..000000000 --- a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. - -[[git-annex-importfeed]] cannot reliably import feeds from <pyvideo.org/category/65/pycon-us-2015/rss> - -### What steps will reproduce the problem? - - git annex importfeed pyvideo.org/category/65/pycon-us-2015/rss - -### What version of git-annex are you using? On what operating system? - -5.20141125 - -### Please provide any additional information below. - -It seems related to the fact that the `enclosure` XML item links to the youtube page instead of the actual video, which sounds a little crazy... so maybe the feed is just wrong and this is invalid. - -In [this pull request to the conference proceedings repo](https://github.com/RichiH/conference_proceedings/pull/42), i hacked around that problem with a [simple loop](https://github.com/anarcat/conference_proceedings/blob/pycon/PyCon/README.md): - - curl -s http://pyvideo.org/category/65/pycon-us-2015/rss | xmllint --xpath '//enclosure/@url' - | sed 's/url=/\n/g' | xargs git annex addurl --fast - -xargs doesn't actually work so well because every once in a while, youtube will return a 403 and the whole pipeline crumbles to the ground. I found this to work better: - - curl -s http://pyvideo.org/category/65/pycon-us-2015/rss | xmllint --xpath '//enclosure/@url' - | sed 's/url="/\n/g;s/"//' | while read url ; do git annex addurl --fast $url ; done - -but it's pretty ugly! --[[anarcat]] - -> Per my comments, I don't think this is a bug in git-annex, but in the -> feeds. So [[done]] --[[Joey]] diff --git a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_1_92fe9fae13259e7f605a8762b093042f._comment b/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_1_92fe9fae13259e7f605a8762b093042f._comment deleted file mode 100644 index 0ec29fd68..000000000 --- a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_1_92fe9fae13259e7f605a8762b093042f._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-05-30T16:04:43Z" - content=""" -Afaik, the enclosure url is supposed to point to the actual file -to download. So this feed is broken. - -`git annex importfeed` has specific support for rss feeds -that link to youtube (or other quvi supported) pages. The way -such a feed should work, or at least the way that youtube's rss -feeds worked before they fell victim to the 5-year-old-feature-so-it-dies -google bitrot, is that an xml link element is used to point to the page. -"""]] diff --git a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_2_a76c59499546fc045a40a21a9ab6d4dc._comment b/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_2_a76c59499546fc045a40a21a9ab6d4dc._comment deleted file mode 100644 index 1022aa7a5..000000000 --- a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_2_a76c59499546fc045a40a21a9ab6d4dc._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 2" - date="2015-05-31T15:50:02Z" - content=""" -i agree the feed is broken. - -i guess what i was surprised about is that importfeed wasn't just doing a `addurl`, which would have detected the youtube site and shoved it into quvi for retrieval... -"""]] diff --git a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_3_b90cb5fa44d1d237843bc312fa036224._comment b/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_3_b90cb5fa44d1d237843bc312fa036224._comment deleted file mode 100644 index 05234eb9d..000000000 --- a/doc/bugs/importfeed_can__39__t_deal_with_pycon_rss_feeds/comment_3_b90cb5fa44d1d237843bc312fa036224._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-06T18:26:56Z" - content=""" -`importfeed` does use quvi to handle urls, but currently only if the url -is provided in a link tag, and there's no enclosure tag. - -This makes sense when you consider the standard; the enclosure tag is -supposed to be an url to content to download, with no additional smarts -needed to figure out a special way to download it. The link tag is a link -to the content, so if it's all we have, maybe quvi can figure out a way to -download from it. - -I don't feel that it makes sense to complicate behavior that's ok according -to the spec just because someone managed to ignore then spec when -generating this feed. -"""]] diff --git a/doc/bugs/importfeed_fails_with_local_file_urls.mdwn b/doc/bugs/importfeed_fails_with_local_file_urls.mdwn deleted file mode 100644 index 932848ddf..000000000 --- a/doc/bugs/importfeed_fails_with_local_file_urls.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -Hi, - -I've a script which generates .rss files which reference local files with the file:// scheme. I can import the file:// urls with git annex addurl, but it fails with git annex importfeed: - - -`$ git annex importfeed --fast file:///path/to/local/rss/file.rss` - -`(checking known urls...)` - -`importfeed file:///path/to/local/rss/file.rss` - -`git-annex: /tmp/feed6757: openFile: resource busy (file is locked)` - -If I try to import it with `$ git annex importfeed --fast /path/to/local/rss/file.rss` I get - -`importfeed /path/to/local/rss/file.rss` - -` warning: bad feed content` - -`ok` - -But the directory stays empty. - - -Is it possible to use local files in rss format with items which reference local files using the file:// scheme as input for importfeed? - -Cheers, -Marco - -> I've fixed it with file:// urls. -> -> Also made it error out on non-url feed inputs, which are not intended to be -> supported. -> -> [[done]] --[[Joey]] diff --git a/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn b/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn deleted file mode 100644 index df7fc5fb2..000000000 --- a/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn +++ /dev/null @@ -1,55 +0,0 @@ -### Please describe the problem. - -`git annex status` inconsistently uses mebi (SI) and giga (informal) prefixes. - -### What steps will reproduce the problem? - -Example: - -[[!format txt """ -anarcat@marcos:mp3$ git annex status -supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL -supported remote types: git S3 bup directory rsync web glacier hook -repository mode: direct -trusted repositories: 0 -semitrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - b7802161-c984-4c9f-8d05-787a29c41cfe -- here (anarcat@marcos:/srv/mp3) -untrusted repositories: 0 -transfers in progress: none -available local disk space: 31.93 gigabytes (+1 megabyte reserved) -local annex keys: 19913 -local annex size: 111.08 gigabytes -known annex keys: 20085 -known annex size: 111.38 gigabytes -bloom filter size: 16 mebibytes (3.1% full) -backend usage: - SHA256E: 39998 -"""]] - -Notice `mebibytes` and `gigabytes`. It is unclear whether those are gigabytes (1000^3) or gibibytes (1024^3). - -### What version of git-annex are you using? On what operating system? - -4.20130802~bpo70+2, Debian wheezy. - -### Please provide any additional information below. - -nil. --[[anarcat]] - -> git-annex consistently uses the powers of ten units -> for disk storage sizes. Its "gigabyte" is the SI gigabyte. -> -> It uses the absurdly named units for powers of 2 for memory sizes, -> in the few places it deals with memory (probably only the above bloom -> filter size number). -> -> AFAIK I am complying with all relevant standards and best practices. -> Even though I consider them rather dumb, as is clear if you -> [read the opionated source code I wrote to handle this](). -> -> If git-annex used "gibibyte", the numbers it reports for disk size -> would not match the numbers disk vendors and most tools use. -> -> [[bug_is_in_world_not_in_git-annex|done]] --[[Joey]] - diff --git a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_.mdwn b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_.mdwn deleted file mode 100644 index 8cc989a0b..000000000 --- a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. -Using the incremental fsck starts from the beginning over and over again. Currently, it's not possible to check a repo in smaller steps. - -### What steps will reproduce the problem? -Start an incremental fsck: `git-annex fsck -S` - -Abort the operation either by `Ctrl+C` or `--time-limit=1s` - -Continue the incremental fsck: `git-annex fsck -m` - -or try this test script: https://gist.github.com/parhuzamos/a72236e24a83bdee5830 - -The check starts with same file as the first time and takes the same files again. - -### What version of git-annex are you using? On what operating system? -git-annex: 5.20150727-g06082d8 -Linux: 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - -Also tried with `docker/ubuntu:latest` using a clean install from https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz - -git-annex: 5.20150522-gb199d65 -Linux: 3.16.0-43-generic #58-Ubuntu SMP Fri Jun 19 11:04:02 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - -> I've adjusted the timing of the fsck checkpoints used in resumes some. -> Now it makes one every 5 minutes, or every 1000 files, whichever comes -> first. I could make this tunable, but I don't think it's worth adding the -> complexity; this heuristic should work pretty well. -> -> Another approach would be to catch sigint and commit the fsck database -> then, as is now done when --time-limit interrupts a fsck run. -> But, I am leery of complicating git-annex with signal handling, -> so I've not done that currently. -> -> Also, documented this in fsck's man page. [[done]] --[[Joey]] diff --git a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment deleted file mode 100644 index 3b5bcb050..000000000 --- a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-30T16:59:40Z" - content=""" -What's actually going on is that incremental fsck has switched to using a -sqlite database to record what files it's fscked. Since making a new commit -to the database after every single file would tend to slow it down a lot, -it only commits after each 1000 files fscked. - -So, if you're fscking less than 1000 files, it won't resume; with more -files it will resume after some even thousand multiple of files. - -This could probably be improved by making it commit after some period of -time, like once per minute or so. -"""]] diff --git a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_2_5371a7493646ff47641816dfe53d2def._comment b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_2_5371a7493646ff47641816dfe53d2def._comment deleted file mode 100644 index 93f0d821b..000000000 --- a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_2_5371a7493646ff47641816dfe53d2def._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="parhuzamos" - subject="comment 2" - date="2015-07-31T08:38:11Z" - content=""" -Thanks for the clarification, so it's by design. - -I recommend commiting to the database when `--time-limit` is reached, if specified at all. What do you think? - -(And thank you for all the hard work on git-annex, it's my favorite tool/app.) - - -"""]] diff --git a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_3_4afd7d73952c7f9172c80f20a5047625._comment b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_3_4afd7d73952c7f9172c80f20a5047625._comment deleted file mode 100644 index 014b1a431..000000000 --- a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_3_4afd7d73952c7f9172c80f20a5047625._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-31T20:01:09Z" - content=""" -Yeah, very good point about --time-limit. I've gone ahead and made that -result in a fsck database save, so it will pick up right where it left off -when using --time-limit. -"""]] diff --git a/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository.mdwn b/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository.mdwn deleted file mode 100644 index 3b53866e3..000000000 --- a/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository.mdwn +++ /dev/null @@ -1,105 +0,0 @@ -### Please describe the problem. -Incremental fsck keeps information about which time a file was last fsck-ed by setting mtime of the file's parent directory in `.git/annex/objects/`. When we are doing incremental fsck from a remote, files that are not available locally are never marked as checked (since said directory does not exist), so they are checked at every invocation of `git annex fsck --more`. - -### What steps will reproduce the problem? -Create a git-annex repository with some random content. Then add any remote, copy files there, remove them locally and run an incremental fsck from the remote. Interrupt it and run again with `--more`. It will check again all the files, including those that have already been checked. - -### What version of git-annex are you using? On what operating system? -Debian official package, 5.20141125, on Debian sid (more or less up-to-date). - -### Please provide any additional information below. - -[[!format sh """ -# Create a test repository -giovanni@amalgama:~$ cd /tmp/ -giovanni@amalgama:/tmp$ mkdir test -giovanni@amalgama:/tmp$ cd test/ -giovanni@amalgama:/tmp/test$ git init -Inizializzato un repository Git in /tmp/test/.git/ -giovanni@amalgama:/tmp/test (master)$ git annex init -init ok -(Recording state in git...) -# Create random content -giovanni@amalgama:/tmp/test (master)$ dd if=/dev/urandom bs=1M count=20 of=test1 -20+0 record dentro -20+0 record fuori -20971520 byte (21 MB) copiati, 1,15928 s, 18,1 MB/s -giovanni@amalgama:/tmp/test (master)$ dd if=/dev/urandom bs=1M count=20 of=test2 -20+0 record dentro -20+0 record fuori -20971520 byte (21 MB) copiati, 1,12974 s, 18,6 MB/s -giovanni@amalgama:/tmp/test (master)$ dd if=/dev/urandom bs=1M count=20 of=test3 -20+0 record dentro -20+0 record fuori -20971520 byte (21 MB) copiati, 1,16881 s, 17,9 MB/s -giovanni@amalgama:/tmp/test (master)$ dd if=/dev/urandom bs=1M count=20 of=test4 -20+0 record dentro -20+0 record fuori -20971520 byte (21 MB) copiati, 1,14387 s, 18,3 MB/s -giovanni@amalgama:/tmp/test (master)$ git annex add . -add test1 ok -add test2 ok -add test3 ok -add test4 ok -(Recording state in git...) -# Create a remote of type directory and move content there -giovanni@amalgama:/tmp/test (master)$ mkdir /tmp/dir -giovanni@amalgama:/tmp/test (master)$ git annex initremote test type=directory encryption=none directory=/tmp/dir -initremote test ok -(Recording state in git...) -giovanni@amalgama:/tmp/test (master)$ git annex move --to test -move test1 (to test...) -ok -move test2 (to test...) -ok -move test3 (to test...) -ok -move test4 (to test...) -ok -(Recording state in git...) -# Launch a remote incremental fsck -giovanni@amalgama:/tmp/test (master)$ git annex fsck --from test --incremental -fsck test1 (checksum...) -ok -fsck test2 (checksum...) -ok -fsck test3 (checksum...) -ok -fsck test4 (checksum...) -ok -# Continue it; here I would expect nothing to happen, since all content has already been checked -giovanni@amalgama:/tmp/test (master)$ git annex fsck --from test --more -fsck test1 (checksum...) -ok -fsck test2 (checksum...) -ok -fsck test3 (checksum...) -ok -fsck test4 (checksum...) -ok -# Bring back content locally and launch again fsck -giovanni@amalgama:/tmp/test (master)$ git annex get -get test1 (from test...) -ok -get test2 (from test...) -ok -get test3 (from test...) -ok -get test4 (from test...) -ok -(Recording state in git...) -giovanni@amalgama:/tmp/test (master)$ git annex fsck --from test --incremental -fsck test1 (checksum...) -ok -fsck test2 (checksum...) -ok -fsck test3 (checksum...) -ok -fsck test4 (checksum...) -ok -# Now --more semantics is respected -giovanni@amalgama:/tmp/test (master)$ git annex fsck --from test --more -giovanni@amalgama:/tmp/test (master)$ -"""]] - -> [[done]] --[[Joey]] diff --git a/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository/comment_1_adbde1bbeb434f42f96cae7d3ad5b65f._comment b/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository/comment_1_adbde1bbeb434f42f96cae7d3ad5b65f._comment deleted file mode 100644 index 9fdc95a88..000000000 --- a/doc/bugs/incremental_fsck-ing_a_remote_does_not_work_for_files_that_are_not_present_in_current_repository/comment_1_adbde1bbeb434f42f96cae7d3ad5b65f._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-05-26T14:57:24Z" - content=""" -More recent versions of git-annex don't use the mtime hack, so avoid this -problem. I had not realized that was a benefit of ditching the mtime hack, -actually; it was done for other reasons like keeping separate incremental -fscks of different remotes. - -I have verified that the problem does not exist with current versions. -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit.mdwn b/doc/bugs/incremental_fsck_should_not_use_sticky_bit.mdwn deleted file mode 100644 index 65db54c55..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -### Please describe the problem. - -There are multiple problems that have the same cause: - - * When using a shared repository (core.sharedrepository = group), the directories that contain the actual objects may be owned by different users. In this case adding or removing the sticky bit is prohibited by the operating system. Thus shared repositories can only be incrementally fscked if all objects are owned by the same user. - - * It is not currently possible to run incremental fscks on the local repository and on a special remote at the same time, because both of them use the same flag space, the sticky bit. - -### What steps will reproduce the problem? - -Create a shared repository (core.sharedrepository = group), let a different user add an object and then try to fsck it. - -### What version of git-annex are you using? On what operating system? - -Debian's 4.20131106~bpo70+1 - -[[!tag confirmed]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_1_204f45a43cd10bcb45c4920a13d66e8d._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_1_204f45a43cd10bcb45c4920a13d66e8d._comment deleted file mode 100644 index b061224e9..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_1_204f45a43cd10bcb45c4920a13d66e8d._comment +++ /dev/null @@ -1,28 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 1" - date="2013-12-02T17:58:55Z" - content=""" -See [[todo/incremental_fsck]] for background. - -Options: - -* using per-object files -* using sqllite or another relational database -* using git as the database -* using a key/value store - -Per-object files have the problem that they clutter up the .git/annex/objects/ tree quite a lot with info only used by fsck. We have a similar clutter problem with direct mode mapping files, and for various reasons (including [[direct mode mappings scale badly with thousands of identical files|bugs/\"Adding_4923_files\"_is_really_slow]]) I have been hoping to move that data to a better storage, perhaps a database, eventually. Switching fsck to use a database first might be a good first step to using a database for the more important direct mode mapping storage. If the fsck database goes wrong, the worse that happens is some extra incremental fscking. - -Using git as the database is possible. Just store the info in a separate git ref, like the git-annex branch, but that is not synced. But it will use more disk over time. Probably not the best choice. - -There are plenty of sqllite interfaces for haskell. They all do have the problem that the C sqlite has to be installed. This will make `cabal install git-annex` harder. It is currently possible to do a `cabal install git-annex` with flags that avoid needing to install any C libraries. This is useful for my sanity, since otherwise people want hand-holding on installing libraries on OSX and stuff. - -Perhaps there's a pure haskell key/value store that would be a better choice than sqllite. I do not anticipate git-annex needing complex relational database storage, if we look at everything it needs to store so far, key/value is enough. (The more complicated stuff is stored in git anyway.) - -* <http://hackage.haskell.org/package/io-storage> is actually memory only, not suitable -* <http://hackage.haskell.org/package/acid-state> is I think the gold standard in its area. Strongly typed. Has some Template Haskell stuff but it's optional. Packaged in Debian already, but only on TH capable architectures so that would need to be fixed. Seems to have the disadvantage that it's not really a key/value store, so works by loading the *entire* data into ram. This is a problem since git-annex wants to run in constant memory. -* <http://hackage.haskell.org/package/keyvaluehash> has some caveats about not being able to remove old keys -* <http://hackage.haskell.org/package/HongoDB> looks possible, has only had one release in 2011 though and undocumented -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment deleted file mode 100644 index ec921ce8f..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_2_a8bb264cb2ceece72e0dd9191b2b566e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="helmut" - ip="89.0.78.89" - subject="git as a database" - date="2013-12-02T18:24:12Z" - content=""" -You said that \"[...] it will use more disk over time. Probably not the best choice.\" But this does not have to be true. Since this git ref is never synced, an update can be forced. The tricky part is in finding good truncation points. Now for fsck, the log can be truncated whenever an incremental fsck is started. -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment deleted file mode 100644 index 17d7a3aab..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 3" - date="2013-12-02T19:11:27Z" - content=""" -HongoDB doesn't build with current hackage. - -keyvaluehash passed some inital load etc tests. The inability to delete old keys/values might not be a significant problem. - -However I don't think it has any ACID guarantees; eg a crash at the wrong time could leave the database in some inconsistent state. <https://github.com/Peaker/keyvaluehash/issues/1> -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_4_5ac5a10bdddf23153e8ea0a8eb60323e._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_4_5ac5a10bdddf23153e8ea0a8eb60323e._comment deleted file mode 100644 index 3b55891c4..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_4_5ac5a10bdddf23153e8ea0a8eb60323e._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 4" - date="2013-12-02T20:35:45Z" - content=""" -@helmut Well, true, it could overwrite the old ref with a new one at the start of a new fsck pass. If there was a separate ref for each uuid, this would work even for mixed local/remote fscking. And git should eventually drop the objects associated with the old ref, probably in `gc --auto`, which has a default --prune of 2 weeks. - -The git overhead would probably be fine for fsck. I am less sure about it for the direct mode mapping files, which can be queried quite frequently. In particular inAnnex is used lots of places, often repeatedly on a lot of files, and it uses withObjectLoc, which uses associatedFiles. -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_5_ec29ed50c4321cf9e21c56c13c65156b._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_5_ec29ed50c4321cf9e21c56c13c65156b._comment deleted file mode 100644 index a627e1841..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_5_ec29ed50c4321cf9e21c56c13c65156b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="68.119.96.78" - subject="comment 5" - date="2013-12-21T16:26:51Z" - content=""" -<http://hackage.haskell.org/package/TCache> looks potentially good. It seems that it may allow storing stuff on disk and only loading it into cache when accessed, but I am not sure. Need to run some tests to try it out. -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_6_c7f1170b84f9ea4befe96cdfe3bdaa1f._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_6_c7f1170b84f9ea4befe96cdfe3bdaa1f._comment deleted file mode 100644 index 9d70c84ec..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_6_c7f1170b84f9ea4befe96cdfe3bdaa1f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 6" - date="2014-02-20T20:09:22Z" - content=""" -I also need some local fast database for metadata index storing. -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_7_f53d0542c9da38e0f6339df8c49c87db._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_7_f53d0542c9da38e0f6339df8c49c87db._comment deleted file mode 100644 index 6d6631bf0..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_7_f53d0542c9da38e0f6339df8c49c87db._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="stp" - ip="24.134.205.34" - subject="Any update" - date="2014-10-01T12:48:06Z" - content=""" -Any update? -"""]] diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_8_9f5acbc79b631a93d7cdf4ae37c07cab._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_8_9f5acbc79b631a93d7cdf4ae37c07cab._comment deleted file mode 100644 index a63381ed0..000000000 --- a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_8_9f5acbc79b631a93d7cdf4ae37c07cab._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""vache""" - date="2015-02-15T16:35:12Z" - content=""" -<https://github.com/dmbarbour/haskell-vcache> - -It uses LMDB, which is a C library, and its PVar is a variable named by a -bytestring, so it's essentially a key/value store where the values can be -arbitrary Haskell data types. Since git-annex already has Keys, and most -of the need for the database is to look up some cached value for a Key, -this seems like a pretty good fit! - -Unfortunately, "A VCache file may be opened by only one process at a time, -and only once within said process." - -But, git-annex needs multiple read-only access, as many git-annex processes -can run concurrently. -"""]] diff --git a/doc/bugs/index_file_smaller_than_expected.mdwn b/doc/bugs/index_file_smaller_than_expected.mdwn deleted file mode 100644 index 0eac3f20e..000000000 --- a/doc/bugs/index_file_smaller_than_expected.mdwn +++ /dev/null @@ -1,53 +0,0 @@ -### Please describe the problem. - -I get an error in one of my repositories. - -### What steps will reproduce the problem? - -I paired my macbook repository with an repository on my desktop. The repository on the desktop contains many smaller files, because it is my documents folder. - -Pairing this repository with smaller files never worked for me. I posted to the forum about it: -[[forum/ssh__95__exchange__95__identification:_read:_Connection_reset_by_peer/]] - -I am a little confused because I paired three other repositories between these computers sucessfully. They contain pictures, videos and music. - -### What version of git-annex are you using? On what operating system? - -Version: 5.20140106-gcb3351b -Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - -Mac OS X Mavericks - -### 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 - -Please make sure you have the correct access rights -and the repository exists. -fatal: index file smaller than expected -TransferScanner crashed: user error (git ["--git-dir=/Users/juh/Share/.git","--work-tree=/Users/juh/Share","-c","core.bare=false","update-index","-z","--index-info"] exited 128) -[2014-01-10 16:26:00 CET] TransferScanner: warning TransferScanner crashed: user error (git ["--git-dir=/Users/juh/Share/.git","--work-tree=/Users/juh/Share","-c","core.bare=false","update-index","-z","--index-info"] exited 128) -ssh_exchange_identification: read: Connection reset by peer -ssh_exchange_identification: read: Connection reset by peer -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -[2014-01-10 16:56:09 CET] NetWatcherFallback: Syncing with sokrates.local_Dokumente -ssh_exchange_identification: read: Connection reset by peer -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. -fatal: index file smaller than expected -NetWatcherFallback crashed: user error (git ["--git-dir=/Users/juh/Share/.git","--work-tree=/Users/juh/Share","-c","core.bare=false","update-index","-z","--index-info"] exited 128) -[2014-01-10 17:01:09 CET] NetWatcherFallback: warning NetWatcherFallback crashed: user error (git ["--git-dir=/Users/juh/Share/.git","--work-tree=/Users/juh/Share","-c","core.bare=false","update-index","-z","--index-info"] exited 128) - - -# End of transcript or log. -"""]] - -> Made assistant detect corrupted .git/annex/index on startup and correct -> it. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/index_file_smaller_than_expected/comment_1_d87ae8c4d384d2ce6d1286b51bfdeba1._comment b/doc/bugs/index_file_smaller_than_expected/comment_1_d87ae8c4d384d2ce6d1286b51bfdeba1._comment deleted file mode 100644 index 9cf0ce336..000000000 --- a/doc/bugs/index_file_smaller_than_expected/comment_1_d87ae8c4d384d2ce6d1286b51bfdeba1._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.43" - subject="comment 1" - date="2014-01-14T21:12:19Z" - content=""" -It's unusual for git's index file to get corrupted or short like this. git writes to .git/index by first writing the new content to .git/index.lock, and then once it's written, renaming it. So if git is interrupted in the middle of a write, it doesn't leave the index file truncated. Of course, it's somewhat up to the OS's filesystem and buffering, and so I suppose if the system loses power at just the right time, and the filesystem does not journal data, this could happen. - -Anyway, git-annex's assistant should be able to detect when the index file is corrupt, including too short, and fix it. When I try with a current version of git-annex, opening the webapp or starting the assistant results in the index file being automatically repaired, with this logged to .git/annex/daemon.log: - -<pre> -fatal: index file smaller than expected -[2014-01-14 16:58:11 JEST] SanityCheckerStartup: corrupt index file found at startup; removing and restaging -</pre> - -However, it looks like it needs to do the same check for .git/annex/index. I was able to reproduce this bug by corrupting that file. -"""]] diff --git a/doc/bugs/info_file_contains_wrong_version.mdwn b/doc/bugs/info_file_contains_wrong_version.mdwn deleted file mode 100644 index 629fd6399..000000000 --- a/doc/bugs/info_file_contains_wrong_version.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -### Please describe the problem. - -The script producing the .info file along with the binary tarball seems to generate the wrong version. - - -### What steps will reproduce the problem? - - % curl https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz.info - GitAnnexDistribution {distributionUrl = "https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz", - distributionKey = Key {keyName = "2a01f853b08dc0f47392b50cda41d5f589f46413073fdf4ffd5b817d6638a502.tar.gz", keyBackendName = "SHA256E", - keySize = Just 27578790, keyMtime = Nothing}, distributionVersion = "5.20131222", - distributionReleasedate = 2013-12-30 18:56:44.908259 UTC, distributionUrgentUpgrade = Nothing} - - -`distributionVersion` is 5.20131222, but `git annex version` returns 5.20131230-g4aa88d8. - -This may look anecdotical, but at least the `git-annex-bin` package of Arch Linux uses the .info data to retrieve the version information. - - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/interference_with_Dropbox_results_in_data_loss.mdwn b/doc/bugs/interference_with_Dropbox_results_in_data_loss.mdwn deleted file mode 100644 index baa59951c..000000000 --- a/doc/bugs/interference_with_Dropbox_results_in_data_loss.mdwn +++ /dev/null @@ -1,50 +0,0 @@ -### Please describe the problem. - -When working with git-annex in a folder managed by Dropbox, the folders names in .git/annex/objects/ are mangled by Dropbox. This leads to lost files. - -This is not a git-annex bug, but the problem is severe and it would be helpful when git-annex can deal with it somehow. Possibilities are: - -* include a warning in documentation (this will be probably found after someone encounters the problem actually) -* issue a warning when running in a Dropbox managed folder -* avoid using filenames that differs in case only (this would make git-annex also more robust against corruption i.e. when a repository is copied over filesystems/protocols without filename case support) - -Dropbox file name limitations: [[https://www.dropbox.com/help/145/en]] - -### What steps will reproduce the problem? - cd ~/Dropbox - mkdir test_annex - cd test_annex - git init - git annex init "test_annex" - cp ~/somefiles/* . - git annex add * - # wait for Dropbox to upload and mangle folder names in .git/annex/objects/ - find -L . -type l | wc -l # print number of broken symlinks - git annex fsck # prints all the missing files - - -### What version of git-annex are you using? On what operating system? - -* git-annex 3.20130207 -* Fedora 19 - -### Please provide any additional information below. - -[[!format sh """ -# folder names mangled by Dropbox - -$ ls .git/annex/objects/ -Ff/ M9 (Case Conflict (1))/ x8 (Case Conflict (1))/ -Ff (Case Conflict)/ pF/ x9/ -Ff (Case Conflict (1))/ pF (Case Conflict)/ x9 (Case Conflict)/ -Ff (Case Conflict (2))/ pF (Case Conflict (1))/ Zf/ -Ff (Case Conflict (3))/ pF (Case Conflict (2))/ Zf (Case Conflict)/ -Ff (Case Conflict (4))/ pF (Case Conflict (3))/ Zf (Case Conflict (1))/ -Ff (Case Conflict (5))/ pF (Case Conflict (4))/ Zf (Case Conflict (2))/ -Ff (Case Conflict (6))/ PG/ Zf (Case Conflict (3))/ -... - -# End of transcript or log. -"""]] - -> [[done]] --[[Joey]] diff --git a/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_1_837c7ab2d31531ac8a61509225926814._comment b/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_1_837c7ab2d31531ac8a61509225926814._comment deleted file mode 100644 index 256ae83b4..000000000 --- a/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_1_837c7ab2d31531ac8a61509225926814._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.35" - subject="comment 1" - date="2014-01-06T16:02:45Z" - content=""" -I'm not seeing data loss. It looks like the contents of your files are still there, you just need to rename them back to the right directory names. If you're using indirect mode, you should be able to do this: - - mv .git/annex/objects . - chmod -R u+w objects - git annex add objects - -That will re-inject all the file contents with the right names. You can then delete the objects directory, which should only contain symlinks at that point. - ----- - -Moving git-annex to using lower case hash directories is on the very long term todo list, due to various crappy filesystems (problems mostly worked around by direct mode). Since it requires changing every symlink in every existing git-annex repository, which will be extremely disruptive, I'd need a much better reason than dropbox to do it now. - -I have no interest, in general, in making git-annex use filenames that meet whatever limitations dropbox wants to impose on its users. -"""]] diff --git a/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment b/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment deleted file mode 100644 index a02a55f44..000000000 --- a/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkWQXo7MLYIDa-ep04UTbdz8KuvfjwLDCQ" - nickname="Matěj" - subject="comment 2" - date="2014-01-08T22:11:34Z" - content=""" -I understand, it's not git-annex fail. I added at least a tip with a warning here: [[forum/do not use git-annex inside your Dropbox]]. -"""]] diff --git a/doc/bugs/issues_with_non-posix_compatible_shells.mdwn b/doc/bugs/issues_with_non-posix_compatible_shells.mdwn deleted file mode 100644 index 34fb72a1c..000000000 --- a/doc/bugs/issues_with_non-posix_compatible_shells.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. -Some internals of git annex does not check if the shell it is running is Posix-compatible, ie. bash. - -I am using fish, and after setting up local pairing, and working, I switched back the login-shell to fish, and when syncing a file, I got this error, read from daemon.log: - -fish: Unknown command 'GIT_ANNEX_SHELL_DIRECTORY=/home/s/annex'. Did you mean to run ~/.ssh/git-annex-shell with a modified environment? Try 'env GIT_ANNEX_SHELL_DIRECTORY=/home/s/annex ~/.ssh/git-annex-shell...'. See the help section on the set command by typing 'help set'. -Standard input: GIT_ANNEX_SHELL_DIRECTORY='/home/s/annex' ~/.ssh/git-annex-shell - ^ -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights -and the repository exists. - -### What steps will reproduce the problem? -Set up local pairing ( I believe having sh/bash as login terminal is necessary for this). -Switch back to fish as login-shell with chsh -s /usr/bin/fish -Add a file to either repository. - -### What version of git-annex are you using? On what operating system? -[s@b ~]$ git annex version -git-annex version: 5.20140320-g63535e3 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -### 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. -"""]] - -> [[fixed|done]] so -> -> I have not tried to make the assistant go back and fix up existing -> `authorized_keys` lines. So if someone had been using a posix shell and -> switched to fish, they'll hit this and need to fix it themselves. I judge -> this is pretty small number of users. --[[Joey]] diff --git a/doc/bugs/issues_with_non-posix_compatible_shells/comment_1_076948499a9d581a50da52b7690e5d4e._comment b/doc/bugs/issues_with_non-posix_compatible_shells/comment_1_076948499a9d581a50da52b7690e5d4e._comment deleted file mode 100644 index 72b3e48e9..000000000 --- a/doc/bugs/issues_with_non-posix_compatible_shells/comment_1_076948499a9d581a50da52b7690e5d4e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://johan.kiviniemi.name/" - nickname="Johan" - subject="comment 1" - date="2014-04-02T08:40:17Z" - content=""" -FWIW, `env foo=bar cmd` would probably work on every system on which the `foo=bar cmd` invocation works now. -"""]] diff --git a/doc/bugs/kill_git-annex_assistant_on_logout.mdwn b/doc/bugs/kill_git-annex_assistant_on_logout.mdwn deleted file mode 100644 index 7c3a5affc..000000000 --- a/doc/bugs/kill_git-annex_assistant_on_logout.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -When you logout of any x session git-annex does not get killed. -This means that if you login again git-annex will still try to use the ssh-agent from the last session which doesn't run anymore. -This leads to countless password queries unless you use a passwordless key. - -> I've fixed this, though maybe not in an ideal way. -> -> There's no way to make a XDG desktop file run a command on logout, that I -> can see. That would have been my first choice. -> -> So, I thought I'd just have the assistant not run setsid, so it's part of -> the current login session and would get killed automatically on logout. -> I was surprised that this didn't seem to work, on a system using logind. -> Even when the desktop file ran git-annex with --foreground, it was not -> stopped on logout. This may be because logind defaults to -> KillUserProcesses=false, -> although I'm not sure why processes that are part of the login session -> are not killed at least. -> -> What I have settled on is to leave the daemon running after logout, -> but on a new login have the `git annex assistant --autostart` kill the -> old daemon and start a new one. -> -> Only possible problem with that is there will be a small window after -> login where the old daemon is running. It might slip in a password prompt -> there, using the new DISPLAY. At least it won't flood, and even a single -> password prompt is pretty unlikely. -> -> I am tenatively going to call this [[done]]. Seems to me that logind -> could be improved though. --[[Joey]] diff --git a/doc/bugs/kill_git-annex_assistant_on_logout/comment_1_35ad241515014f1c85668c6152538fb9._comment b/doc/bugs/kill_git-annex_assistant_on_logout/comment_1_35ad241515014f1c85668c6152538fb9._comment deleted file mode 100644 index 824fcbfaf..000000000 --- a/doc/bugs/kill_git-annex_assistant_on_logout/comment_1_35ad241515014f1c85668c6152538fb9._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-02T17:05:15Z" - content=""" -Thanks, some people have reported repeated ssh-agent prompts, and this is -the first one that fingered logout as contributing to the problem. -(Reading through the past reports, that all had hints about logout.) - -So, we need to get a desktop file to stop git-annex on logout. If that's -even possible. -"""]] diff --git a/doc/bugs/links_in_firefox_do_not_always_work.mdwn b/doc/bugs/links_in_firefox_do_not_always_work.mdwn deleted file mode 100644 index d0b735083..000000000 --- a/doc/bugs/links_in_firefox_do_not_always_work.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -### Please describe the problem. - -I noticed that you (@joey) wrote - -> webapp: Odd problem when using Firefox: Some links don't seem to load. Clicking on such a link repeatedly will eventually load the right page. Network console shows web browser is requesting page "/" despite a link to another page being clicked on. Workaround: Use Chrome instead; no such problem there. - -in [[todo/windows_support]], and thought I would get around to mentioning that I also see this problem on linux (so it's not windows specific), but I am using firefox. - - -### What steps will reproduce the problem? -Click on a link in the webapp; most of the time, even though the link target is correct, the current page is reloaded instead of loading the target. - -### What version of git-annex are you using? On what operating system? -5.20131205-gc448602 - -Ubuntu 13.04, firefox 25.0.1 - - - ---Walter - -> [[fixed|done]]; increased number of longpolling failures allowed before -> it enters the chromium back button bugfix workaround to 12. -> Should be more than enough for 3 or 4 long polling elements on a page. -> (Considered only running the chromium bugfix on chromium, but I don't -> want to get into browser detection hacks.) --[[Joey]] diff --git a/doc/bugs/links_in_firefox_do_not_always_work/comment_1_5e506674f157e8ed612eca1f9adfa068._comment b/doc/bugs/links_in_firefox_do_not_always_work/comment_1_5e506674f157e8ed612eca1f9adfa068._comment deleted file mode 100644 index 1249a6f81..000000000 --- a/doc/bugs/links_in_firefox_do_not_always_work/comment_1_5e506674f157e8ed612eca1f9adfa068._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 1" - date="2013-12-09T21:08:29Z" - content=""" -Thanks, that's very interesting indeed. - -When I was debugging this on Windows, I had the network console open, and could see clearly that Firefox was trying to load \"/\" when I clicked on a link to \"/config\". Both firefox and the git-annex webapp's debug log agreed that it asked for the wrong page. - -I have just reproduced it using iceweasel as well. I know that I have tested git-annex before under iceweasel and it seemed to work. - -Seems that clicking 3+ times on a link makes it finally follow it. - -I wonder if this has something to do with the long polling. Disabling javascript would avoid it if so. They've made disabling JS in firefox sufficiently hard that I cannot find how to do it. - -Also, the problem seems to open happen on the main page (/). Once I get to any other page, further links are followed without trouble. -"""]] diff --git a/doc/bugs/links_in_firefox_do_not_always_work/comment_2_dfde57b433301e971c2d5b9e4d3c824a._comment b/doc/bugs/links_in_firefox_do_not_always_work/comment_2_dfde57b433301e971c2d5b9e4d3c824a._comment deleted file mode 100644 index cda8995a4..000000000 --- a/doc/bugs/links_in_firefox_do_not_always_work/comment_2_dfde57b433301e971c2d5b9e4d3c824a._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 2" - date="2013-12-09T21:39:16Z" - content=""" -Tried renaming / to /dashboard , just in case firefox was having problems with the name of the page. Didn't help, so the problem must be something on the page. - -Tried removing the repolist and the transferlist from the dashboard, and this indeed avoided the problem. So it's certainly related to the long polling code. Although note that this left 1 long polling call still on the page, for the sidebar. In fact, only removing one of the repolist or transfer list seems to be enough to avoid the problem. 1 works, 2 works, 3 fails. - -Aha.. After 3 long polling failures, the JS runs a fail function. To work around a seeming bug in chromium when navigating back to a page, [[!commit b5678d74a29023cbeb3d65c0d7f57d20f47ebef9]] made this reload the page. -"""]] diff --git a/doc/bugs/links_in_firefox_do_not_always_work/comment_3_2d090d6e67ba53ff7e5c0275274f9b3d._comment b/doc/bugs/links_in_firefox_do_not_always_work/comment_3_2d090d6e67ba53ff7e5c0275274f9b3d._comment deleted file mode 100644 index f0e7cf244..000000000 --- a/doc/bugs/links_in_firefox_do_not_always_work/comment_3_2d090d6e67ba53ff7e5c0275274f9b3d._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 3" - date="2013-12-09T21:43:58Z" - content=""" -I just tried in the browser console, and see the same behaviour. - -I also see that links work when not on the dashboard. - -I disabled javasript (set javascript.enabled to false in about:config), and the links all work well (though dropdown menus don't work at all). - - -(I see after writing this you seem to have worked it out already) -"""]] diff --git a/doc/bugs/list-tests_runs_tests.mdwn b/doc/bugs/list-tests_runs_tests.mdwn deleted file mode 100644 index cea58db84..000000000 --- a/doc/bugs/list-tests_runs_tests.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -### Please describe the problem. -Running "git annex test --list-tests" seems to produce the same output as "git annex test" rather than list tests. - -### What steps will reproduce the problem? -git annex test --list-tests - -### What version of git-annex are you using? On what operating system? -5.20150317-g237d5b0 on Centos 6.6 and Ubuntu 12.04.5 - -5.20141125 on Mac OS X 10.10.2 - -### Please provide any additional information below. - -[[!format sh """ -# this is version 5.20150317-g237d5b0 on Ubuntu -$ ./git-annex test --list-tests -Tests - QuickCheck - prop_idempotent_deencode_git: OK (0.15s) - +++ OK, passed 1000 tests. - prop_idempotent_deencode: OK (0.12s) - +++ OK, passed 1000 tests. -[snip all the passing tests] -All 140 tests passed (305.69s) -"""]] - -> [[fixed|done]] although I don't understand why tasty needs the -> `listingTests` ingredient to come first for it to work. --[[Joey]] diff --git a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path.mdwn b/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path.mdwn deleted file mode 100644 index 92c3a525a..000000000 --- a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -### Please describe the problem. - -When the annex directory has a non-ascii character (like a tilde) on its path, local pairing fails and a couple of instances of the following message appear on the log - -"illegal control characters in pairing message; ignoring" - -### What steps will reproduce the problem? - -* make a new annex repo named on /home/someone/Vídeos/blah/ (notice the i with a tilde) on two computers -* try to pair them - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20141016-g26b38fd on Arch Linux - -git-annex version: 5.20140717 on Ubuntu 14.10 - -> [[done]]; see comment diff --git a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_1_cf4f286c55d319bd71c2fc573e313d4b._comment b/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_1_cf4f286c55d319bd71c2fc573e313d4b._comment deleted file mode 100644 index 1b9024745..000000000 --- a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_1_cf4f286c55d319bd71c2fc573e313d4b._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-09T20:02:56Z" - content=""" -I have not been able to reproduce this problem. - -I tried making the repository be in a directory named "dirĩ". -I'm guessing that might contain the character that you refer to, which you -unfortunately obfuscated right out of "/home/someone/Videos/blah/" - -But the code doing this sanity check was rather questionable -- it decoded -the input as a raw C-formatted string, and looked for unwanted chars in that. -That could be where the bug lay, since it decoded the same string twice, -possibly differently. I've improved the code to not do that, and instead -decode the message before sanity checking each field of it. - -I'm going to close this bug. If you can still reproduce it though, you need to - -1. tell me the actual filename -2. enable debug logging, and send .git/annex/daemon.log when this happens. -"""]] diff --git a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_2_89f25f787558c77201fa6226cc7af5f5._comment b/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_2_89f25f787558c77201fa6226cc7af5f5._comment deleted file mode 100644 index d922d1722..000000000 --- a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_2_89f25f787558c77201fa6226cc7af5f5._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://xgm.de/oid/" - nickname="Horus" - subject="comment 2" - date="2015-05-05T17:35:37Z" - content=""" -I have the same problem without any special characters in my path (besides ~ of $HOME) -Debug Log gives: - - illegal control characters in pairing message; ignoring - [2015-05-05 19:11:40 CEST] PairListener: received \"PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \\"asaru\\", remoteUserName = \\"florian\\", remoteDirectory = \\"~/Desktop/annex\\", remoteSshPubKey = \\"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDE8cd+cThzgRD+9RuiFhbL6UbPP+gvyNcUdrwVZoqfn2AE0niOe6XwsvqNrL4BZE50ySIo71XHyyAtRPiW3h0R8NjJo8+VFha2KL9vCXySNjq0Ib6HinfCDNUp5hI35F+LnUtUAVkhhhVqfJj4C6K3JTjXQ9J/hgiYRpNCY+2hV0+sF/e643SsyNlkUhiNxfCd4LQ5bedX6FeSCYBwteVgtZQzyByeawFpj1uajqBbDgDBLmclXDNrb4DwqavLRj+L+XxPtNqSKXSp8Q2/oypr/GQeTjmHEb8K/7qSjNHcBDAHH9fUI5lhDDhyxc4lMfap0lseSWtlwldhKjGqPnB9 florian@asaru\\n\\", pairUUID = UUID \\"0b1e8007-4a8d-4cc4-9ca1-320f4f700081\\"},IPv4Addr 347252928), verifiableDigest = \\"dff64a76c0333223cc3909f13bbdb3e1a70ddaa4\\"})\" - -I'll be very happy to provide any other help... -"""]] diff --git a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_3_74d65bd0edd92eb6acf6770d4b6e7826._comment b/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_3_74d65bd0edd92eb6acf6770d4b6e7826._comment deleted file mode 100644 index 604f1f5d6..000000000 --- a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_3_74d65bd0edd92eb6acf6770d4b6e7826._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/QeDOPmIryZqNyn0A84E.QmGJVazd_6_FpYa2nFtn#c7fa1" - nickname="Captain Kirk" - subject="I have the same issue, no special characters in path" - date="2015-06-23T20:24:30Z" - content=""" -I have the same issue like Horus described. Pairing fails in the LAN. - -\"illegal control characters in pairing message; ignoring\" appears in the log over and over - -distributionUrl = \"https://downloads.kitenet.net/git-annex/OSX/current/10.10_Yosemite/git-annex.dmg -distributionVersion = \"5.20150616\" -distributionReleasedate = 2015-06-17 18:18:52.552448 - -Would be great to get help or a fix! -"""]] diff --git a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_4_c6d6fa60e71895b7c0c68cc75cd7c5cc._comment b/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_4_c6d6fa60e71895b7c0c68cc75cd7c5cc._comment deleted file mode 100644 index 7ecbe91d0..000000000 --- a/doc/bugs/local_pair_fails_if_non-ascii_characters_present_on_annex_path/comment_4_c6d6fa60e71895b7c0c68cc75cd7c5cc._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-07-02T18:32:16Z" - content=""" -In comment 2, we see a message containing a ssh key with a newline at the -end. That is the control character it's objecting to, and it has good -security reasons to not allow newlines in there (multiline ssh keys could -result in a ~/.ssh/authorized_keys that runs arbitrary commands). - -I was able to reproduce that myself. The problem was that the assistant -didn't remove newlines when sending the ssh key. Fixed it. - -This bug report is **closed**, for the second time. -If you see this message using any newer version of git-annex, -please file a new bug report. -"""]] diff --git a/doc/bugs/log_fails_with_-raw_error.mdwn b/doc/bugs/log_fails_with_-raw_error.mdwn deleted file mode 100644 index 553c507a1..000000000 --- a/doc/bugs/log_fails_with_-raw_error.mdwn +++ /dev/null @@ -1,47 +0,0 @@ -### Please describe the problem. - -`git-annex log` fails to run if git is an older version. - -### What steps will reproduce the problem? - -`git-annex log` :) - -i somewhat thought that this would work even if i had an older version of git because the standalone release would use the bundled git release... - -### What version of git-annex are you using? On what operating system? - -5.20150610+gitg608172f-1~ndall+1 on Debian Wheezy. - -### 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 -$ git annex log video/mp4_sd/TV23_-_TV_Show_Excerpts_-Research.mov.mp4 -fatal: unrecognized argument: -raw - -$ git annex --debug log video/mp4_sd/TV23_-_TV_Show_Excerpts_-Research.mov.mp4 -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"] -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","log","refs/heads/git-annex..8bf42e9c6e5b301f487a2d2d596d7cef12a3283d","-n1","--pretty=%H"] -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","log","refs/heads/git-annex..9a7b6b197d5271c29034d47e908fec7de6ea7e5a","-n1","--pretty=%H"] -[2015-06-22 17:34:17 EDT] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"] -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","ls-files","--cached","-z","--","video/mp4_sd/TV23_-_TV_Show_Excerpts_-Research.mov.mp4"] -[2015-06-22 17:34:17 EDT] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","log","-z","--pretty=format:%ct","-raw","--abbrev=40","--remove-empty","refs/heads/git-annex","--","d65/b94/SHA256E-s493891859--5413dd9efe00cbc091e78a7ce6a7034be0e6e121b7faaa054ad2836f8a80aaad.mov.mp4.log"] -fatal: unrecognized argument: -raw -$ git --version -git version 1.7.10.4 -$ git annex version -git-annex version: 5.20150610+gitg608172f-1~ndall+1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -# End of transcript or log. -"""]] - ---[[anarcat]] - -> Fixed to use --raw, and added a test case. [[done]] --[[Joey]] diff --git a/doc/bugs/log_fails_with_-raw_error/comment_1_dcb3ff1a076c81472cd471254946a868._comment b/doc/bugs/log_fails_with_-raw_error/comment_1_dcb3ff1a076c81472cd471254946a868._comment deleted file mode 100644 index efdf0dccb..000000000 --- a/doc/bugs/log_fails_with_-raw_error/comment_1_dcb3ff1a076c81472cd471254946a868._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-02T16:18:09Z" - content=""" -I can reproduce this with debian unstable. It is a reversion introduced -in version 5.20150528 of git-annex. -"""]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net.mdwn b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net.mdwn deleted file mode 100644 index 94bac023d..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. - -The [downloads.kitenet.net](http://downloads.kitenet.net/) site is really a git annex repository, yet it is not possible to "git annex get" the files from there. - -I regularly have to do something like this to workaround that issue: - - git annex addurl --file git-annex-standalone-amd64.tar.gz https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz - -Shouldn't this be done automatically? - -### What steps will reproduce the problem? - - git clone https://downloads.kitenet.net/ - cd downloads.kitenet.net/ - git annex get git-annex/linux/ - -### What version of git-annex are you using? On what operating system? - -5.20141024 on Debian Jessie. - -### Please provide any additional information below. - -Thanks! -- [[anarcat]] - -> <del>done; apparently some pebak. --[[Joey]]</del> - -> > it's baaaack! :) -- [[anarcat]] - ->>> Please don't reuse old bug reports for unrelated issues. It muddies the ->>> waters. ->>> ->>> I've fixed git-update-server-info hook on the repository, fixing this ->>> second problem. ->>> [[done]] --[[Joey]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_1_fb324a4b1ec440275eca32dae15155b3._comment b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_1_fb324a4b1ec440275eca32dae15155b3._comment deleted file mode 100644 index e0575dfba..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_1_fb324a4b1ec440275eca32dae15155b3._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""works for me""" - date="2014-11-10T17:05:26Z" - content=""" -<pre> -joey@kite:~/tmp>git clone http://downloads.kitenet.net/.git/ dlCloning into 'dl'... -Checking connectivity... done. -joey@kite:~/tmp>cd dl -joey@kite:~/tmp/dl>git annex get git-annex/linux/ -get git-annex/linux/current/git-annex-standalone-amd64.tar.gz (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) --2014-11-10 13:04:38-- http://downloads.kitenet.net/.git//annex/objects/3V/g7/SHA256E-s46132091--9712ed0168c2562d504d71cb3efbcac5434acc2f604cabadc42728758b7b3bc6.tar.gz/SHA256E-s46132091--9712ed0168c2562d504d71cb3efbcac5434acc2f604cabadc42728758b7b3bc6.tar.gz -Resolving downloads.kitenet.net (downloads.kitenet.net)... 107.170.31.195 -Connecting to downloads.kitenet.net (downloads.kitenet.net)|107.170.31.195|:80... connected. -</pre> - -AFAICS, you can't clone http://downloads.kitenet.net/ without the .git/, -so this makes me think you did something wrong. -"""]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_2_22f456996079c88865b67caca51dfed9._comment b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_2_22f456996079c88865b67caca51dfed9._comment deleted file mode 100644 index f155a33ca..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_2_22f456996079c88865b67caca51dfed9._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="comment 2" - date="2014-11-11T21:16:02Z" - content=""" -huh! weird. i just made up those \"steps to reproduce\" from memory, as I cloned the repo a while ago. maybe i just forgot to sync it? - -sorry for the noise. -"""]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_3_a617644a0287e11e980448f129ec9b65._comment b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_3_a617644a0287e11e980448f129ec9b65._comment deleted file mode 100644 index 0a17d14eb..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_3_a617644a0287e11e980448f129ec9b65._comment +++ /dev/null @@ -1,51 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 3" - date="2015-02-10T03:02:53Z" - content=""" -still doesn't work here: - -<pre> -$ git clone https://downloads.kitenet.net/.git/ -Clonage dans 'downloads.kitenet.net'... -Vérification de la connectivité... fait. -anarcat@marcos:srv$ -anarcat@marcos:srv$ cd downloads.kitenet.net/ -anarcat@marcos:downloads.kitenet.net(master=)$ ls -git-annex index.html misc talks tmp videos -anarcat@marcos:downloads.kitenet.net(master=)$ cd git-annex/ -anarcat@marcos:git-annex(master=)$ ls -android gpg-pubkey.asc linux mapa OSX presentation.svg windows -anarcat@marcos:git-annex(master=)$ cd linux/ -anarcat@marcos:linux(master=)$ ls -current -anarcat@marcos:linux(master=)$ cd current/ -anarcat@marcos:current(master=)$ ls -git-annex-standalone-amd64.tar.gz git-annex-standalone-amd64.tar.gz.sig git-annex-standalone-armel.tar.gz.info.sig git-annex-standalone-i386.tar.gz.info -git-annex-standalone-amd64.tar.gz.info git-annex-standalone-armel.tar.gz git-annex-standalone-armel.tar.gz.sig git-annex-standalone-i386.tar.gz.info.sig -git-annex-standalone-amd64.tar.gz.info.sig git-annex-standalone-armel.tar.gz.info git-annex-standalone-i386.tar.gz git-annex-standalone-i386.tar.gz.sig -anarcat@marcos:current(master=)$ git annex get git-annex-standalone-amd64.tar.gz -get git-annex-standalone-amd64.tar.gz (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -(from origin...) --2015-02-09 22:01:00-- https://downloads.kitenet.net/.git//annex/objects/4j/Zv/SHA256E-s45566016--3eefaf3ba048a523c6e2539bc5cd7cd082dd077a083a516cd21ab0f907999e08.tar.gz/SHA256E-s45566016--3eefaf3ba048a523c6e2539bc5cd7cd082dd077a083a516cd21ab0f907999e08.tar.gz -Résolution de downloads.kitenet.net (downloads.kitenet.net)… 107.170.31.195 -Connexion à downloads.kitenet.net (downloads.kitenet.net)|107.170.31.195|:443… connecté. -requête HTTP transmise, en attente de la réponse… 404 Not Found -2015-02-09 22:01:01 erreur 404 : Not Found. - ---2015-02-09 22:01:01-- https://downloads.kitenet.net/.git//annex/objects/0c0/1d5/SHA256E-s45566016--3eefaf3ba048a523c6e2539bc5cd7cd082dd077a083a516cd21ab0f907999e08.tar.gz/SHA256E-s45566016--3eefaf3ba048a523c6e2539bc5cd7cd082dd077a083a516cd21ab0f907999e08.tar.gz -Résolution de downloads.kitenet.net (downloads.kitenet.net)… 107.170.31.195 -Connexion à downloads.kitenet.net (downloads.kitenet.net)|107.170.31.195|:443… connecté. -requête HTTP transmise, en attente de la réponse… 404 Not Found -2015-02-09 22:01:01 erreur 404 : Not Found. - - - Unable to access these remotes: origin - - Try making some of these repositories available: - 840760dc-08f0-11e2-8c61-576b7e66acfd -- main repo [origin] - d7fa24ad-d104-4064-ad10-1078a4436e72 -- joey@elephant:~/lib/downloads -failed -git-annex: get: 1 failed -</pre> -"""]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_4_ef630a6b299790ab63bc696d3c5ae0c9._comment b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_4_ef630a6b299790ab63bc696d3c5ae0c9._comment deleted file mode 100644 index b6450b2f1..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_4_ef630a6b299790ab63bc696d3c5ae0c9._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 4" - date="2015-02-10T03:04:20Z" - content=""" -plus it doesn't seem to be the same repo on both places: - -<pre> -anarcat@marcos:current(master=)$ git annex addurl --file=git-annex-standalone-amd64.tar.gz https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz -addurl git-annex-standalone-amd64.tar.gz - while adding a new url to an already annexed file, url does not have expected file size (use --relaxed to bypass this check) https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz -failed -git-annex: addurl: 1 failed -</pre> - -something weird is going on. -"""]] diff --git a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_5_f1bba569b1ccd1d0b2b75a3a26224e65._comment b/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_5_f1bba569b1ccd1d0b2b75a3a26224e65._comment deleted file mode 100644 index e96b5a637..000000000 --- a/doc/bugs/main_repo_not_available_on_downloads.kitenet.net/comment_5_f1bba569b1ccd1d0b2b75a3a26224e65._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 5" - date="2015-02-10T03:06:40Z" - content=""" -oh, and i just noticed that .info file: - -<pre> -anarcat@marcos:current(master *=)$ less git-annex-standalone-amd64.tar.gz.info -GitAnnexDistribution {distributionUrl = \"https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-amd64.tar.gz\", distributionKey = Key {keyName = \"3eefaf3ba048a523c6e2539bc5cd7cd082dd077a083a516cd21ab0f907999e08.tar.gz\", keyBackendName = \"SHA256E\", keySize = Just 45566016, keyMtime = Nothing, keyChunkSize = Nothing, keyChunkNum = Nothing}, distributionVersion = \"5.20150113\", distributionReleasedate = 2015-01-13 16:45:47.236515 UTC, distributionUrgentUpgrade = Nothing} -</pre> - -definitely the wrong data there... -"""]] diff --git a/doc/bugs/make_install_can__39__t_be_used_with_sudo.mdwn b/doc/bugs/make_install_can__39__t_be_used_with_sudo.mdwn deleted file mode 100644 index c43075e58..000000000 --- a/doc/bugs/make_install_can__39__t_be_used_with_sudo.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -What steps will reproduce the problem? -In the git-annex tree, - - $ make - $ sudo make install - -What is the expected output? What do you see instead? - -One would expect git-annex to be installed in the configured prefix. Unfortunately, make tries to rebuild the "all" target before "install". This fails (presumably) due to incorrect environment state, - - ghc -O2 -Wall -ignore-package monads-fd -ignore-package monads-tf -outputdir tmp -IUtility -DWITH_ASSISTANT -DWITH_S3 -DWITH_INOTIFY --make git-annex Utility/libdiskfree.o - - Utility/FileSystemEncoding.hs:17:8: - Could not find module `Data.Bits.Utils': - Use -v to see a list of the files searched for. - make: *** [git-annex] Error 1 - -Removing "all" from the dependencies of "install" allows the process to run to completion, although this is clearly not a satisfactory solution. - -> [[fixed|done]] using an ugly stamp file. --[[Joey]] diff --git a/doc/bugs/make_whereis_output_more_concise.mdwn b/doc/bugs/make_whereis_output_more_concise.mdwn deleted file mode 100644 index bfc82fbb1..000000000 --- a/doc/bugs/make_whereis_output_more_concise.mdwn +++ /dev/null @@ -1,60 +0,0 @@ -### Please describe the problem. - -annex lists all the remotes UUIDs (the same) when whereis is ran across multiple files. This makes output lengthy and harder to process and share for no reason. Why not to list remotes just once on top and then only locations per each file, e.g. instead of -[[!format sh """ - -$> git annex whereis -whereis 2011-Palmour-etal_canadian_consent_forms.pdf (2 copies) - 00000000-0000-0000-0000-000000000001 -- web - 94b3c553-ad30-450e-be56-504b400f9a5c -- yoh@novo:~/proj/open-consent [here] - - web: http://download.springer.com/static/pdf/638/art%253A10.1186%252F1472-6939-12-1.pdf?auth66=1401467160_8992951c5cccc0dbe510c369eba3afa1&ext=.pdf -ok -whereis Arizona_consent.pdf (2 copies) - 00000000-0000-0000-0000-000000000001 -- web - 94b3c553-ad30-450e-be56-504b400f9a5c -- yoh@novo:~/proj/open-consent [here] - - web: http://web.arizona.edu/~arg/papers/fmri/forms/consent.pdf -ok - -"""]] - -get (not sure if I want to see ok much either) - -[[!format sh """ - -$> git annex whereis - 00000000-0000-0000-0000-000000000001 -- web - 94b3c553-ad30-450e-be56-504b400f9a5c -- yoh@novo:~/proj/open-consent [here] - -whereis 2011-Palmour-etal_canadian_consent_forms.pdf (2 copies) - web: http://download.springer.com/static/pdf/638/art%253A10.1186%252F1472-6939-12-1.pdf?auth66=1401467160_8992951c5cccc0dbe510c369eba3afa1&ext=.pdf - -whereis Arizona_consent.pdf (2 copies) - web: http://web.arizona.edu/~arg/papers/fmri/forms/consent.pdf -"""]] - - -### What steps will reproduce the problem? - -run git annex whereis on a directory with multiple files - -### What version of git-annex are you using? On what operating system? - -Debian -[[!format sh """ -$> acpolicy git-annex -git-annex: - Installed: 5.20150205+git57-gc05b522-1~nd80+1 - Candidate: 5.20150205+git57-gc05b522-1~nd80+1 - Version table: - *** 5.20150205+git57-gc05b522-1~nd80+1 0 - 500 http://neuro.debian.net/debian-devel/ jessie/main amd64 Packages - 100 /var/lib/dpkg/status -"""]] - -> See `git annex list`, which comes right after `whereis` in the -> man page, and is described as "similar to whereis but a more compact -> display". -> -> [[done]] --[[Joey]] diff --git a/doc/bugs/man_page_has_example_lines_joined_into_a_single_line.mdwn b/doc/bugs/man_page_has_example_lines_joined_into_a_single_line.mdwn deleted file mode 100644 index 397666a2c..000000000 --- a/doc/bugs/man_page_has_example_lines_joined_into_a_single_line.mdwn +++ /dev/null @@ -1,18 +0,0 @@ - -[[!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 -$> git annex help schedule | grep -A3 examples -man: can't set the locale; make sure $LC_* and $LANG are correct - Some examples: - - fsck self 30m every day at any time fsck self 1h every month at 3 AM fsck self 1h on day 1 of every month at any time fsck self 1h every week divisible by 2 at any time - -$> git annex version -git-annex version: 5.20150409+git126-ga29f683-1~ndall+1 -# about to build a fresh standlone - -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/manpage_has_slight_indentation_error.mdwn b/doc/bugs/manpage_has_slight_indentation_error.mdwn deleted file mode 100644 index 56d9d2266..000000000 --- a/doc/bugs/manpage_has_slight_indentation_error.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -### Please describe the problem. - -The "import" section of the manpage has an indentation error. - -### What steps will reproduce the problem? - -man git-annex - -### What version of git-annex are you using? On what operating system? - -anything after 20130827, i believe. - -### Please provide any additional information below. - -silly patch: - -[[!format diff """ -# 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 -diff --git a/Build/mdwn2man b/Build/mdwn2man -index ba5919b..b3ee404 100755 ---- a/Build/mdwn2man -+++ b/Build/mdwn2man -@@ -25,7 +25,7 @@ while (<>) { - $inlist=1; - $spippara=0; - } -- elsif (/.SH/) { -+ elsif (/^.SH/) { - $skippara=0; - $inlist=0; - } -# End of transcript or log. -"""]] - --- [[anarcat]] - -> [[applied|done]] --[[Joey]] diff --git a/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely.mdwn b/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely.mdwn deleted file mode 100644 index d7cccabeb..000000000 --- a/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. -Doing a git annex command while passing a bad --git-dir can result in the .git directory being deleted. I've never experienced it with plain git, so I assume that it comes for annex. - -### What steps will reproduce the problem? - -[[!format sh """ -$ mkdir annex_destroyed_my_git_directory -$ cd annex_destroyed_my_git_directory -$ git init -$ git annex init -$ ls -a -. .. .git -$ git --git-dir=$PWD annex find -fatal: Not a git repository: '/home/doudou/tmp/annex_destroyed_my_git_directory' -$ ls -a -. .. config -"""]] - -### What version of git-annex are you using? On what operating system? -dpkg -l git-annex reports 5.20141024 - -I am running Debian sid. - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely/comment_1_5c0bdeb0e1fc6b2d524e5c33ff80ce8a._comment b/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely/comment_1_5c0bdeb0e1fc6b2d524e5c33ff80ce8a._comment deleted file mode 100644 index 8edd41aa7..000000000 --- a/doc/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely/comment_1_5c0bdeb0e1fc6b2d524e5c33ff80ce8a._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""yikes!""" - date="2014-11-04T21:47:07Z" - content=""" -I'm very sorry you encountered this bug. I'd like to do anything -possible to recover your repository. While investigating it, it looks -like, when the repository is not a fresh and empty repo, it doesn't -actually get completely nuked. Instead, the contents of the .git directory, -including annexed objects, is left in "removeme". It should be possible to -mostly recover from that. I can try to walk you through it if necessary. - -I know exactly what the cause of this bug is. It's a workaround for a bug -in some by now quite old versions of git-annex (from last year). That old bug -caused a .git/.git directory to be created, and so this workaround looks -for $GIT_DIR/.git and does what turn out to be horrible things in this -case. - -So, I have immediately removed that old workaround, so noone else will -encounter this. -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit.mdwn b/doc/bugs/modified_permissions_persist_after_unlock__44___commit.mdwn deleted file mode 100644 index 907ae99b4..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -### Please describe the problem. - -Modifying an annexed file with unlock then commit leaves the link with permissions 777 and git status reports a typechange, which makes checkout impossible. Resolves by running git unlock on the file. - -### What steps will reproduce the problem? - -echo foo > test.txt -git annex add test.txt -git commit -a -m "first" -git annex unlock test.txt -echo foobar > test.txt -git commit -a -m "second" - -git status (notice typechange message) - -git unlock test.txt (corrects and retains both versions) - -### What version of git-annex are you using? On what operating system? - -git-annex version: 3.20120406 -local repository version: 3 -default repository version: 3 -supported repository versions: 3 -upgrade supported from repository versions: 0 1 2 - -git version 1.7.9.5 - - -### 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. -"""]] - -[[!tag confirmed]] -[[!meta title="git commit of unlocked file leaves typechange staged in index"]] - -> [[fixed|done]]; git-annex pre-commit will block such commits from being -> made. Git devs didn't seem to have a way to improve its behavior. --[[Joey]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_1_875ca12936d4b4505f2e280a454fe558._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_1_875ca12936d4b4505f2e280a454fe558._comment deleted file mode 100644 index 535c20e4d..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_1_875ca12936d4b4505f2e280a454fe558._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 1" - date="2014-10-06T15:47:39Z" - content=""" -I am unable to reproduce any problem with the steps you gave. I don't see any typechange message, and would not expect one. Perhaps your repository is lacking a .git/hooks/pre-commit script to run git-annex when you use `git commit -a`? - -It's not clear to me what problem you experienced, beyond the typechange message that I don't see. - -> git unlock test.txt (corrects and retains both versions) - -I don't understand that line at all. `git unlock` is not a valid git command, and what does \"corrects and retains both versions\" mean? - -Please provide an actual trascript of the problem, rather than the unclear description. -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_2_59f68098fa6edb2fe8902b120fda0280._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_2_59f68098fa6edb2fe8902b120fda0280._comment deleted file mode 100644 index 7938ad9ad..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_2_59f68098fa6edb2fe8902b120fda0280._comment +++ /dev/null @@ -1,94 +0,0 @@ -[[!comment format=sh - username="https://www.google.com/accounts/o8/id?id=AItOawn0hu_TPhLcUM1Ivvn7iIoZ_iD3g_5WDcs" - nickname="Greg" - subject="comment 2" - date="2014-10-06T17:06:27Z" - content=""" -ubuntu@ip-10-170-13-124:~$ mkdir annex -ubuntu@ip-10-170-13-124:~$ cd annex -ubuntu@ip-10-170-13-124:~/annex$ ls -ubuntu@ip-10-170-13-124:~/annex$ git init . -Initialized empty Git repository in /home/ubuntu/annex/.git/ -ubuntu@ip-10-170-13-124:~/annex$ git annex init \"test annex\" -init test annex ok -ubuntu@ip-10-170-13-124:~/annex$ echo \"foo\" > test.txt -ubuntu@ip-10-170-13-124:~/annex$ ls -test.txt -ubuntu@ip-10-170-13-124:~/annex$ ls -al -total 16 -drwxrwxr-x 3 ubuntu ubuntu 4096 Oct 6 16:43 . -drwxr-xr-x 7 ubuntu ubuntu 4096 Oct 6 16:42 .. -drwxrwxr-x 9 ubuntu ubuntu 4096 Oct 6 16:42 .git --rw-rw-r-- 1 ubuntu ubuntu 4 Oct 6 16:43 test.txt -ubuntu@ip-10-170-13-124:~/annex$ git annex add test.txt -add test.txt (checksum...) ok -(Recording state in git...) -ubuntu@ip-10-170-13-124:~/annex$ ls -al -total 16 -drwxrwxr-x 3 ubuntu ubuntu 4096 Oct 6 16:48 . -drwxr-xr-x 7 ubuntu ubuntu 4096 Oct 6 16:42 .. -drwxrwxr-x 9 ubuntu ubuntu 4096 Oct 6 16:48 .git -lrwxrwxrwx 1 ubuntu ubuntu 176 Oct 6 16:43 test.txt -> .git/annex/objects/8Z/1J/SHA256-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c/SHA256-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c -ubuntu@ip-10-170-13-124:~/annex$ git commit test.txt -Aborting commit due to empty commit message. -ubuntu@ip-10-170-13-124:~/annex$ git commit test.txt -m first -[master (root-commit) 38a8e18] first - Committer: Ubuntu <ubuntu@ip-10-170-13-124.us-west-1.compute.internal> -Your name and email address were configured automatically based -on your username and hostname. Please check that they are accurate. -You can suppress this message by setting them explicitly: - - git config --global user.name \"Your Name\" - git config --global user.email you@example.com - -After doing this, you may fix the identity used for this commit with: - - git commit --amend --reset-author - - 1 file changed, 1 insertion(+) - create mode 120000 test.txt -ubuntu@ip-10-170-13-124:~/annex$ ls -al -total 16 -drwxrwxr-x 3 ubuntu ubuntu 4096 Oct 6 16:48 . -drwxr-xr-x 7 ubuntu ubuntu 4096 Oct 6 16:42 .. -drwxrwxr-x 9 ubuntu ubuntu 4096 Oct 6 16:49 .git -lrwxrwxrwx 1 ubuntu ubuntu 176 Oct 6 16:43 test.txt -> .git/annex/objects/8Z/1J/SHA256-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c/SHA256-s4--b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c -ubuntu@ip-10-170-13-124:~/annex$ git annex unlock test.txt -unlock test.txt (copying...) ok -ubuntu@ip-10-170-13-124:~/annex$ cat test.txt -foo -ubuntu@ip-10-170-13-124:~/annex$ echo foobar > test.txt -ubuntu@ip-10-170-13-124:~/annex$ git commit test.txt -m second -add test.txt (checksum...) ok -ok -(Recording state in git...) -[master f265461] second - Committer: Ubuntu <ubuntu@ip-10-170-13-124.us-west-1.compute.internal> -Your name and email address were configured automatically based -on your username and hostname. Please check that they are accurate. -You can suppress this message by setting them explicitly: - - git config --global user.name \"Your Name\" - git config --global user.email you@example.com - -After doing this, you may fix the identity used for this commit with: - - git commit --amend --reset-author - - 1 file changed, 1 insertion(+), 1 deletion(-) -ubuntu@ip-10-170-13-124:~/annex$ git status -# On branch master -# Changes to be committed: -# (use \"git reset HEAD <file>...\" to unstage) -# -# typechange: test.txt -# -# Changes not staged for commit: -# (use \"git add <file>...\" to update what will be committed) -# (use \"git checkout -- <file>...\" to discard changes in working directory) -# -# typechange: test.txt -# -ubuntu@ip-10-170-13-124:~/annex$ - -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_3_22df91abd8c025000e67bdcef891de3b._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_3_22df91abd8c025000e67bdcef891de3b._comment deleted file mode 100644 index 4b0270178..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_3_22df91abd8c025000e67bdcef891de3b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawn0hu_TPhLcUM1Ivvn7iIoZ_iD3g_5WDcs" - nickname="Greg" - subject="comment 3" - date="2014-10-06T17:07:46Z" - content=""" -Looks like its doing it when you specifically commit a filename. -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_4_ecf84eeb4feddafcfa7ba7d4a2f164b1._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_4_ecf84eeb4feddafcfa7ba7d4a2f164b1._comment deleted file mode 100644 index 4ccf2a3a9..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_4_ecf84eeb4feddafcfa7ba7d4a2f164b1._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 4" - date="2014-10-09T20:43:34Z" - content=""" -Ah, ok. git's index has the file listed as not being a symlink, because `git commit $file` stages it in the index that way. Running `git reset --hard` will fix git's index. - -This problem is avoided if you `git annex add $file` before committing. Which is generally a good idea -for other reasons, including avoiding staging a potentially huge file's contents in the git index in the first place. - -git-annex's pre-commit hook should probably update the git index for the committed files, replacing the staged full file contents with the git-annex symlink. That would avoid this problem. -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_5_2ea1d78ec8a652a53391969e43bcb6f0._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_5_2ea1d78ec8a652a53391969e43bcb6f0._comment deleted file mode 100644 index 72495fe66..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_5_2ea1d78ec8a652a53391969e43bcb6f0._comment +++ /dev/null @@ -1,39 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 5" - date="2014-10-10T00:01:54Z" - content=""" -Actually, the pre-commit hook does stage the annexed symlink into the index. But it seems that `git commit $file` causes the pre-commit hook's changes to the index to be partially ignored, in a way that `git commit -a` does not. - -While the pre-commit hook is running, `git commit -a` sets `GIT_INDEX_FILE=index.lock`, while `git commit $file` instead sets `GIT_INDEX_FILE=next-index-$pid.lock`. git's builtin/commit.c refers to this latter file as the \"false index\". Full comment from git: - -<pre> - /* - * A partial commit. - * - * (0) find the set of affected paths; - * (1) get lock on the real index file; - * (2) update the_index with the given paths; - * (3) write the_index out to the real index (still locked); - * (4) get lock on the false index file; - * (5) reset the_index from HEAD; - * (6) update the_index the same way as (2); - * (7) write the_index out to the false index file; - * (8) return the name of the false index file (still locked); - * - * The caller should run hooks on the locked false index, and - * create commit from it. Then - * (A) if all goes well, commit the real index; - * (B) on failure, rollback the real index; - * In either case, rollback the false index. - */ - -</pre> - -So, the pre-commit hook is run on the false index, which has been reset to HEAD. The changes it stages are committed, but do not affect the real index. If I read that comment right, the commit from the false index is then supposed to be committed on the real index, but it seems in this case the real index does not get updated to reflect the changes. - -This seems to be a bug in git. Reproduced w/o git-annex, and bug report sent to the git ML. - -Depending on what happens, this might just get fixed in git. Or, I might need to make git-annex detect this case (by looking at what `GIT_INDEX_FILE` is set to) and have the pre-commit hook cancel the commit. -"""]] diff --git a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_6_2a3ad3f95ee03c79404e3784c9ce1a4b._comment b/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_6_2a3ad3f95ee03c79404e3784c9ce1a4b._comment deleted file mode 100644 index ef86e4880..000000000 --- a/doc/bugs/modified_permissions_persist_after_unlock__44___commit/comment_6_2a3ad3f95ee03c79404e3784c9ce1a4b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 6" - date="2014-10-10T17:26:04Z" - content=""" -upstream bug: <http://www.mail-archive.com/git@vger.kernel.org/msg59587.html> -"""]] diff --git a/doc/bugs/new_AWS_region___40__eu-central-1__41__.mdwn b/doc/bugs/new_AWS_region___40__eu-central-1__41__.mdwn deleted file mode 100644 index 177f7e138..000000000 --- a/doc/bugs/new_AWS_region___40__eu-central-1__41__.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -### Please describe the problem. - -Amazon has opened up a new region in AWS with a datacenter in Frankfurt/Germany. - -* Region Name: EU (Frankfurt) region -* Region: eu-central-1 - -This should be added to the "Adding an Amazon S3 repository" page in the Datacenter dropdown of the webapp. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_1_23d65c7e05f6e7312bbdbd039bf8d308._comment b/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_1_23d65c7e05f6e7312bbdbd039bf8d308._comment deleted file mode 100644 index e56e1beaf..000000000 --- a/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_1_23d65c7e05f6e7312bbdbd039bf8d308._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.96" - subject="comment 1" - date="2014-10-23T18:52:48Z" - content=""" -The S3 library that git-annex is using does not support the authentication method that this region uses. - -It is supported by the aws library that git-annex uses in the `s3-aws` branch in git, and I already added the region there this morning. - -I can't merge `s3-aws` yet; the neccessary version of the aws library is not yet available in eg, Debian. And even upgrading aws from cabal seems to result in dependency hell, due to its needing a newer version of scientific. This should all sort itself out in time. - -If you need this region, you'll need to try to build git-annex's s3-aws branch, for now. -"""]] diff --git a/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_2_6ceb3251b7067591d34cd146d19ccea9._comment b/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_2_6ceb3251b7067591d34cd146d19ccea9._comment deleted file mode 100644 index fab525b66..000000000 --- a/doc/bugs/new_AWS_region___40__eu-central-1__41__/comment_2_6ceb3251b7067591d34cd146d19ccea9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.96" - subject="comment 2" - date="2014-10-23T19:51:46Z" - content=""" -Looks like the cabal dependency hell is managable; if done in system without anything installed, cabal manages to install the new aws, and everything else, except for the dbus library. Still not ready to be merged though. -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange.mdwn b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange.mdwn deleted file mode 100644 index 1dca84346..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. - -Changing a file in a repository from a symlink to a normal file causes annex to create an annexed file from that typechange regardless of weather or not it was an annexed file. - - -### What steps will reproduce the problem? - - git init newrepo - cd newrepo && git annex init - touch realfile - git add . - git commit -m "added realfile" - mkdir newdir && cd newdir - ln -s ../realfile newfile - git add . - git commit -m "Added placeholder until we get assets from designers" - rm newfile - dd bs=1024 count=10000 if=/dev/zero of=newfile - git add . - git commit -m "Finally got assets from designers" - ls -la newfile - # lrwxrwxrwx 1 user user <date> newfile -> ../.git/annex/objects/XX/XX/UUID/UUID - -### What version of git-annex are you using? On what operating system? - -git-annex version: 4.20130802 - -Ubuntu 12.04 LTS - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_1_6ac691645edb483797bee05043fd83b3._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_1_6ac691645edb483797bee05043fd83b3._comment deleted file mode 100644 index a3c162d61..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_1_6ac691645edb483797bee05043fd83b3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="arand" - ip="130.243.226.21" - subject="comment 1" - date="2013-08-12T20:19:37Z" - content=""" -It looks like all the \"add\" operations are missing from the log, which makes it a bit hard to follow... -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_2_5d67e3a60b7cc30c2b1857f50895d363._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_2_5d67e3a60b7cc30c2b1857f50895d363._comment deleted file mode 100644 index c122bd92f..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_2_5d67e3a60b7cc30c2b1857f50895d363._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://caust1c.myopenid.com/" - nickname="asbraithwaite" - subject="comment 2" - date="2013-08-12T20:41:34Z" - content=""" -Sorry about that. I forgot that -a doesn't add files. -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_3_78f1e081b92f418c20893d86a8715501._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_3_78f1e081b92f418c20893d86a8715501._comment deleted file mode 100644 index d00556c75..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_3_78f1e081b92f418c20893d86a8715501._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="arand" - ip="130.243.226.21" - subject="comment 3" - date="2013-08-12T20:48:42Z" - content=""" -There are still no git-annex actions in the log, except for the init. So the end result for ls -la is not possible with those commands. You may want to try to reproduce it again and write down the exact command sequence used ;) -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_4_1e2a59e0eec89ef1a57d1488ff40dcf0._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_4_1e2a59e0eec89ef1a57d1488ff40dcf0._comment deleted file mode 100644 index d68b3ea35..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_4_1e2a59e0eec89ef1a57d1488ff40dcf0._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://caust1c.myopenid.com/" - nickname="asbraithwaite" - subject="comment 4" - date="2013-08-12T21:07:45Z" - content=""" -@arand: That's precisely the problem! I think you'll find if you run those commands exactly, that's what you'll get. - -It's got something to do with the git annex pre-commit hook that runs and checks for typechanges. - -I shortened the output on the last command to be less verbose, but if the full output is needed, I'll add it. -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_5_5e74431048b07631e0dbeca90fdb365b._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_5_5e74431048b07631e0dbeca90fdb365b._comment deleted file mode 100644 index b2f525648..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_5_5e74431048b07631e0dbeca90fdb365b._comment +++ /dev/null @@ -1,47 +0,0 @@ -[[!comment format=mdwn - username="arand" - ip="130.243.226.21" - subject="comment 5" - date="2013-08-12T21:50:47Z" - content=""" -Hmm, I think I see it now, you were missing a `rm` command in the log, and I had no idea the pre-commit hook existed :) - -This reproduces the issue, and it seems to indeed be a bug in the git-annex pre-commit handling, nice catch. - -<pre> -$ git init temp -Initialized empty Git repository in /home/arand/tmp/temp/.git/ -$ cd temp && git annex init -init ok -(Recording state in git...) -$ ln -s broken link -$ git add . -$ git commit -m\"add broken link\" -[master (root-commit) 8125488] add broken link - 1 file changed, 1 insertion(+) - create mode 120000 link -$ rm link -$ echo \"actual file\" >link -$ git add . -$ git commit -m\"replace link with real file\" -add link (checksum...) ok -ok -(Recording state in git...) -[master b58b068] replace link with real file - 1 file changed, 1 insertion(+), 1 deletion(-) -$ git diff HEAD~ | cat -diff --git a/link b/link -index 86a410d..4104f6e 120000 ---- a/link -+++ b/link -@@ -1 +1 @@ --broken -\ No newline at end of file -+.git/annex/objects/v4/GQ/SHA256E-s12--ef29ded6f5ae80d89a838d37e01ed3efaade7a2994aff87d1100697554b7327b/SHA256E-s12--ef29ded6f5ae80d89a838d37e01ed3efaade7a2994aff87d1100697554b7327b -\ No newline at end of file -$ -</pre> - - - -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_6_3724e1c1a5fc6d3589452478249792ec._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_6_3724e1c1a5fc6d3589452478249792ec._comment deleted file mode 100644 index 9c558e05e..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_6_3724e1c1a5fc6d3589452478249792ec._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://caust1c.myopenid.com/" - nickname="asbraithwaite" - subject="comment 6" - date="2013-08-12T21:53:17Z" - content=""" -Ah, you're very right. Thank you. -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_7_7f841ea7bf7d44f3d810ca097ac9eb47._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_7_7f841ea7bf7d44f3d810ca097ac9eb47._comment deleted file mode 100644 index e781beae1..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_7_7f841ea7bf7d44f3d810ca097ac9eb47._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://caust1c.myopenid.com/" - nickname="asbraithwaite" - subject="comment 7" - date="2013-08-12T21:53:56Z" - content=""" -I updated the issue with the `rm` statement I forgot. -"""]] diff --git a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_8_c53ce2274388711ffbde1595b64f932b._comment b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_8_c53ce2274388711ffbde1595b64f932b._comment deleted file mode 100644 index b4ef6b5c7..000000000 --- a/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_8_c53ce2274388711ffbde1595b64f932b._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.154.0.63" - subject="comment 8" - date="2013-08-22T17:25:48Z" - content=""" -Yay for the git-annex community for another fine bug testcase! - -The problem is simply that it assumes any typechanged link was an annexed file, and doesn't doublecheck. Fixing that now.. -"""]] diff --git a/doc/bugs/numcopies_deprecated__44___but_still_in_walkthrough.mdwn b/doc/bugs/numcopies_deprecated__44___but_still_in_walkthrough.mdwn deleted file mode 100644 index 12e2672f3..000000000 --- a/doc/bugs/numcopies_deprecated__44___but_still_in_walkthrough.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -### Please describe the problem. -Within the walkthrough the deprecated annex.numcopies are still used. At least it should be added that "git annex numcopies x" can be used to define it globally without the need for a .gitattribute file. And use .gitattribute only for per directory and fine grained control. -http://git-annex.branchable.com/walkthrough/backups/ - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/package_build_fails_with_missing_man_directory.mdwn b/doc/bugs/package_build_fails_with_missing_man_directory.mdwn deleted file mode 100644 index 03f1d36aa..000000000 --- a/doc/bugs/package_build_fails_with_missing_man_directory.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -When building a debian package, the build fails due to a missing man/ directory. - - ./Build/mdwn2man man/git-annex-vpop.1 1 doc/git-annex-vpop.mdwn > man/git-annex-vpop.1 - /bin/sh: 1: cannot create man/git-annex-vpop.1: Directory nonexistent - -I was able to build the package with the following patch: - -[[!format patch """ -From: Justin Geibel <jtgeibel@gmail.com> -Date: Fri, 27 Mar 2015 16:21:13 -0400 -Subject: Fix build of man pages - ---- - Makefile | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/Makefile b/Makefile -index d6fb1a1..b36cbcd 100644 ---- a/Makefile -+++ b/Makefile -@@ -1,5 +1,5 @@ - mans=$(shell find doc -maxdepth 1 -name git-annex*.mdwn | sed -e 's/^doc/man/' -e 's/\.mdwn/\.1/') --all=git-annex $(mans) docs -+all=git-annex mans docs - - CABAL?=cabal # set to "./Setup" if you lack a cabal program - GHC?=ghc -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__.mdwn b/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__.mdwn deleted file mode 100644 index 4d6e041bb..000000000 --- a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__.mdwn +++ /dev/null @@ -1,107 +0,0 @@ -### Please describe the problem. - -cannot enable an exiting gcrypt special remote after successfully having cloned the git repository; I get this error: "git-annex: uuid mismatch ..." at the end of the enableremote command (see transcript for details) - -maybe my fault but cannot understand what I'm doing wrong - -### What steps will reproduce the problem? - -1. cloned the encrypted repository with: "git clone gcrypt::git.myserver.net:myrepo TEST-myrepo.annex" - -2. enabled the special remote with: "git annex enableremote backup type=gcrypt encryption=hybrid gitrepo=git.myserver.net:myrepo" - -### What version of git-annex are you using? On what operating system? - -[[!format sh """ -git-annex version: 5.20140927~bpo70+2 -build flags: Assistant Pairing S3 Inotify XMPP Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL -remote types: git gcrypt S3 bup directory rsync web tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -"""]] - -### Please provide any additional information below. - -[[!format sh """ - -# transcript of commands and results - -(cloning) -g@renaissance:~$ git clone gcrypt::git.myserver.net:DMS-myrepo TEST-myrepo.annex -Cloning into 'TEST-myrepo.annex'... -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gpg: Signature made Thu 16 Oct 2014 12:58:33 CEST -[...] -gcrypt: Remote ID is :id:8sucFsBZIGQKXFv5ecSW -Receiving objects: 100% (3531/3531), 245.40 KiB | 0 bytes/s, done. -Resolving deltas: 100% (1382/1382), done. -[...] -Receiving objects: 100% (636/636), 66.78 KiB | 0 bytes/s, done. -Resolving deltas: 100% (209/209), done. -Checking connectivity... done. - - -(annex info) -g@renaissance:~/TEST-myrepo.annex$ git annex info -repository mode: indirect -trusted repositories: (merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -0 -semitrusted repositories: 5 - -- here - 00000000-0000-0000-0000-000000000001 -- web - 622362eb-3882-4429-829b-1ec0f299f5a7 -- [omissis] - 69b848ef-dd29-43e4-ae1b-73ec6a01f2f6 -- [omissis] - ffc5c5d1-6166-4753-a2e4-88727d0f8c7b -- backup -untrusted repositories: 1 - b185b2ed-c024-43ac-9049-3bc12a87dacc -- [omissis] -transfers in progress: none -available local disk space: 51.53 gigabytes (+1 megabyte reserved) -local annex keys: 0 -local annex size: 0 bytes -annexed files in working tree: 212 -size of annexed files in working tree: 210.56 megabytes -bloom filter size: 16 mebibytes (0% full) -backend usage: - SHA256E: 212 - - -(list of remotes) -g@renaissance:~/TEST-myrepo.annex$ git annex enableremote -git-annex: Specify the name of the special remote to enable. -Known special remotes: backup - - -(enabling remote) -g@renaissance:~/TEST-myrepo.annex$ git annex enableremote backup type=gcrypt encryption=hybrid gitrepo=git.myserver.net:myrepo -enableremote backup (encryption update) (hybrid cipher with gpg key [omissis]) gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gpg: Signature made Thu 16 Oct 2014 12:58:33 CEST -[omissis] -gcrypt: Remote ID is :id:8sucFsBZIGQKXFv5ecSW -From gcrypt::git.myserver.net:myrepo - * [new branch] synced/master -> backup/synced/master - * [new branch] master -> backup/master - * [new branch] synced/git-annex -> backup/synced/git-annex - * [new branch] git-annex -> backup/git-annex -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gpg: Signature made Thu 16 Oct 2014 12:58:33 CEST -[omissis] -Counting objects: 3, done. -Compressing objects: 100% (2/2), done. -Total 3 (delta 0), reused 1 (delta 0) -gcrypt: Encrypting to: -r [omissis] -gcrypt: Requesting manifest signature -gpg: [omissis]: skipped: public key already present -To gcrypt::git.myserver.net:myserver - 1195dda..3254af7 git-annex -> git-annex -git-annex: uuid mismatch (UUID "78104a6f-16a9-504b-8e8a-d8a3c59351e8",Just (UUID "984e0333-3327-5f21-87a1-35d30f37f337"),":id:8sucFsBZIGQKXFv5ecSW") - -# End of transcript or log. -"""]] - -> [[done]]; see comments. --[[Joey]] diff --git a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_1_72a97bc3ccb00c623baee874609bb4ca._comment b/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_1_72a97bc3ccb00c623baee874609bb4ca._comment deleted file mode 100644 index 70339747e..000000000 --- a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_1_72a97bc3ccb00c623baee874609bb4ca._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlZ-6dtxJY4cP7shhvV8E6YyuV0Rak8it4" - nickname="Giovanni" - subject="I messed up that repo" - date="2014-10-16T13:31:15Z" - content=""" -I'm sure I messed up the repository at some point - -the remote repository have a duplicated (I hope just duplicated and not triplicated) UUID: both ffc5c5d1-6166-4753-a2e4-88727d0f8c7b and 984e0333-3327-5f21-87a1-35d30f37f337 - -on one of my working remotes I already used \"git annex dead 984e0333-3327-5f21-87a1-35d30f37f337\" and synced the special (bare) remote **but** trying to make a new clone and adding the remote special with enableremote i always get the same \"UUID mismatch\" error, listing the (marked) dead UUID - -please is there a way to get rid of the mess I did?!? :-) -I'm tempted to manually add \"annex-uuid = ffc5c5d1-6166-4753-a2e4-88727d0f8c7b\" to the repo \".git/config\" but I fear I'm going to further mess things - -sorry for reportng this as a bug... actually it was my fault - -best regards -Giovanni - -"""]] diff --git a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_2_1bb55c9a35d9447a31237c8bfa24dba9._comment b/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_2_1bb55c9a35d9447a31237c8bfa24dba9._comment deleted file mode 100644 index c26b0a390..000000000 --- a/doc/bugs/problems_with_enableremote_on_gcrypt_remote___40__hosted_with_gitolite__41__/comment_2_1bb55c9a35d9447a31237c8bfa24dba9._comment +++ /dev/null @@ -1,21 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2014-10-28T19:40:37Z" - content=""" -The uuid mismatch message tells me that you have tried to enable a special -remote that has uuid 984e0333-3327-5f21-87a1-35d30f37f337. However, when -it checked the gcrypt repository, it found that it had gcrypt id -":id:8sucFsBZIGQKXFv5ecSW", which means its uuid should be -78104a6f-16a9-504b-8e8a-d8a3c59351e8. I have improved that message to be -more clear. - -Since `git annex info` doesn't list that -78104a6f-16a9-504b-8e8a-d8a3c59351e8 uuid at all, it seems that -this gcrypt repository has not been initialized using `git-annex -initremote`. It's not a gcrypt special remote, but instead is a gcrypt -repository, that was probably created using `git push`. You can convert it -to a gcrypt special remote by running `git-annex initremote` and providing -its repourl. Once that's done and pushed, you will be able to `git annex -enableremote` it elsewhere. -"""]] diff --git a/doc/bugs/problems_with_glacier.mdwn b/doc/bugs/problems_with_glacier.mdwn deleted file mode 100644 index 60e2f7e69..000000000 --- a/doc/bugs/problems_with_glacier.mdwn +++ /dev/null @@ -1,65 +0,0 @@ -### Please describe the problem. -Annex errors when copying to glacier. - -### What version of git-annex are you using? On what operating system? - -OS X 10.9.2 Build 13C64 - - git-annex version: 5.20140318-gdcf93d0 - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - -### 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 - -> git annex initremote glacier type=glacier encryption=hybrid keyid=E9053BDA datacenter=us-west-1 ║██████████╠ ∞ ∞ -initremote glacier (encryption setup) (hybrid cipher with gpg key B608B8F6E9053BDA) ok -(Recording state in git...) -> git annex copy Cobalt\ Strike\ Tradecraft --to=glacier --debug -[2014-03-27 07:27:39 PDT] read: git ["--git-dir=/Users/akraut/Desktop/annexes/media/.git","--work-tree=/Users/akraut/Desktop/annexes/media","show-ref","git-annex"] -[2014-03-27 07:27:39 PDT] read: git ["--git-dir=/Users/akraut/Desktop/annexes/media/.git","--work-tree=/Users/akraut/Desktop/annexes/media","show-ref","--hash","refs/heads/git-annex"] -[2014-03-27 07:27:39 PDT] read: git ["--git-dir=/Users/akraut/Desktop/annexes/media/.git","--work-tree=/Users/akraut/Desktop/annexes/media","log","refs/heads/git-annex..9f59057d857784e6ae6b3dcd6793092264375913","--oneline","-n1"] -[2014-03-27 07:27:39 PDT] chat: git ["--git-dir=/Users/akraut/Desktop/annexes/media/.git","--work-tree=/Users/akraut/Desktop/annexes/media","cat-file","--batch"] -[2014-03-27 07:27:39 PDT] read: git ["config","--null","--list"] -[2014-03-27 07:27:39 PDT] read: git ["--git-dir=/Users/akraut/Desktop/annexes/media/.git","--work-tree=/Users/akraut/Desktop/annexes/media","ls-files","--cached","-z","--","Cobalt Strike Tradecraft"] -copy Cobalt Strike Tradecraft/Tradecraft__1_of_9____Introduction.mp4 (gpg) [2014-03-27 07:27:39 PDT] chat: gpg ["--quiet","--trust-model","always","--decrypt"] - -You need a passphrase to unlock the secret key for -user: "Andrew Mark Kraut <akraut@gmail.com>" -4096-bit ELG-E key, ID 353E49B9, created 2008-11-11 (main key ID E9053BDA) - -(checking glacier...) [2014-03-27 07:27:46 PDT] read: glacier ["--region=us-west-1","archive","checkpresent","git-annex: Maybe.fromJust: Nothing - -# End of transcript or log. -"""]] - -> This was a bug introduced last month, it forgot to receord the -> datacenter and vault used when initializing the glacier repository. -> -> I've fixed the bug, but this does not fix repositories created with -> the broken version. I considered just making it use the default -> datacenter and vault for such a repository, but -> a) those may change in the future -> and I don't want to have to worry about breaking such a repository -> going forward and b) someone may have overridden it to use another -> datacenter or vault name and so it shouldn't blindly assume the defaults. -> -> Instead, there's a manual fix up step you need to do. Luckily quite easy. -> For example: -> -> git annex enableremote myglacier datacenter=us-east-1 vault=myglacier-fae9be57-8eb4-47af-932f-136b9b40e669 -> -> The default datacenter is us-east-1, and the default vault name is -> "$remotename-$uuid". So you just have to tell it these values -> once with an enableremote command, and it will then work. - -> You don't even need to get the fixed version of git-annex to work -> around the bug this way.. Although it does have better error messages -> too. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/problems_with_glacier/comment_1_8d233428a16ae4276d9c69b329e8216b._comment b/doc/bugs/problems_with_glacier/comment_1_8d233428a16ae4276d9c69b329e8216b._comment deleted file mode 100644 index e4556dc82..000000000 --- a/doc/bugs/problems_with_glacier/comment_1_8d233428a16ae4276d9c69b329e8216b._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q" - nickname="Andrew" - subject="comment 1" - date="2014-03-27T14:46:19Z" - content=""" -I just updated to the latest glacier-cli and boto and have confirmed that those are working properly and that the vault has been created on glacier: -[[!format sh \"\"\" -> glacier --region=us-west-1 vault list -glacier-571d1ec3-8870-46cb-977e-15830a2b474d -\"\"\"]] -"""]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt.mdwn b/doc/bugs/protocol_mismatch_after_interrupt.mdwn deleted file mode 100644 index c2c159057..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. - -git annex now fails to transfer a fail with: `protocol version mismatch -- is your shell clean?` - -### What steps will reproduce the problem? - -start a transfer, then switch between your wireless and wired connexions (I am using network-manager), then interrupt the transfer with control-c. - -### What version of git-annex are you using? On what operating system? - -on my side: 5.20140306~bpo70 on debian wheezy amd64 - -on the other side: 4.20130815 on ubuntu saucy i386 - -### Please provide any additional information below. - -[[!format sh """ -anarcat@angela:video$ git annex copy --to t films/foo.mkv -copy films/foo.mkv (checking t...) (to t...) -protocol version mismatch -- is your shell clean? -(see the rsync man page for an explanation) -rsync error: protocol incompatibility (code 2) at compat.c(174) [sender=3.0.9] - - rsync failed -- run git annex again to resume file transfer -failed -git-annex: copy: 1 failed -"""]] - -workaround: `cd .git/annex/; mv transfer transfer.old` on the other side. - --- [[anarcat]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment deleted file mode 100644 index 6247cf42e..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt/comment_1_415de83053dc61a64cf2e301223f1916._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.191" - subject="comment 1" - date="2014-04-20T16:52:15Z" - content=""" -Last time rsync seemed to fail like this it was really the remote git-annex-shell failing on an encoding problem: -[[!commit 0b12db64d834979d49ed378235b0c19b34e4a4d6]] - -It seems I would need to see the transfer info files you moved out of the way to say more. Or you could copy the back, reproduce the problem, find the git-annex-shell command that is being run (using --debug), and see if you can run it on the remote system and reproduce the problem there without rsync in the picture, in order to get the actual error message. -"""]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_2_e0894bd0d0037ee40050697748d4be47._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_2_e0894bd0d0037ee40050697748d4be47._comment deleted file mode 100644 index 5a1566b89..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt/comment_2_e0894bd0d0037ee40050697748d4be47._comment +++ /dev/null @@ -1,47 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - ip="72.0.72.144" - subject="more info" - date="2014-08-11T01:55:28Z" - content=""" -here's another occurence of that bug, with --debug this time: - -[[!format txt \"\"\" -anarcat@angela:video$ git annex --debug get films/Example/ -[2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"films/Example/\"] -get films/Example/Example.mkv [2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"show-ref\",\"git-annex\"] -[2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"log\",\"refs/heads/git-annex..7357c09b70e87f35fdc253316520975c94308299\",\"-n1\",\"--pretty=%H\"] -[2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"log\",\"refs/heads/git-annex..30bd8b2d719734a73cbadba28dbc0c99107c201f\",\"-n1\",\"--pretty=%H\"] -[2014-08-10 21:49:23 EDT] read: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"log\",\"refs/heads/git-annex..bde2aae11f2dcb3fb648ea5e5019fbab56301855\",\"-n1\",\"--pretty=%H\"] -[2014-08-10 21:49:23 EDT] chat: git [\"--git-dir=/home/anarcat/video/.git\",\"--work-tree=/home/anarcat/video\",\"cat-file\",\"--batch\"] -[2014-08-10 21:49:23 EDT] read: git [\"config\",\"--null\",\"--list\"] -(from origin...) [2014-08-10 21:49:23 EDT] read: ssh [\"-O\",\"stop\",\"-S\",\"anarc.at\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"localhost\"] - -[2014-08-10 21:49:23 EDT] read: rsync [\"--progress\",\"--inplace\",\"--perms\",\"-e\",\"'ssh' '-S' '.git/annex/ssh/anarc.at' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-T' 'anarc.at' 'git-annex-shell ''sendkey'' ''/srv/video'' ''SHA256E-s815462420--a9a6eb45540fd7f3f2598453ef0fc948bec9abb764e85624d66c0707cbd93b22.mkv'' --uuid 5adbab10-0f7a-467b-b0d8-5d7af2223103 ''--'' ''remoteuuid=ae3d62e6-49be-4340-ba25-c8736a1637c4'' ''direct='' ''associatedfile=films/Example/Example.mkv'' ''--'''\",\"--\",\"dummy:\",\"/home/anarcat/video/.git/annex/tmp/SHA256E-s815462420--a9a6eb45540fd7f3f2598453ef0fc948bec9abb764e85624d66c0707cbd93b22.mkv\"] -protocol version mismatch -- is your shell clean? -(see the rsync man page for an explanation) -rsync error: protocol incompatibility (code 2) at compat.c(174) [Receiver=3.0.9] - - rsync failed -- run git annex again to resume file transfer - - Unable to access these remotes: origin - - Try making some of these repositories available: - 31912b57-62a5-475c-87a7-582b5492a216 -- WD green 1.5TB backup drive - 5adbab10-0f7a-467b-b0d8-5d7af2223103 -- main (anarcat@marcos:/srv/video) [origin] -failed -git-annex: get: 1 failed -\"\"\"]] - -running rsync directly doesn't give me much more info, however, running the `-e` command does: - -[[!format txt \"\"\" -anarcat@angela:video$ ssh '-S' '.git/annex/ssh/anarc.at' '-o' 'ControlMaster=auto' '-o' 'ControlPersist=yes' '-T' 'anarc.at' 'git-annex-shell ''sendkey'' ''/srv/video'' ''SHA256E-s815462420--a9a6eb45540fd7f3f2598453ef0fc948bec9abb764e85624d66c0707cbd93b22.mkv'' --uuid 5adbab10-0f7a-467b-b0d8-5d7af2223103 ''--'' ''remoteuuid=ae3d62e6-49be-4340-ba25-c8736a1637c4'' ''direct='' ''associatedfile=films/Example/Example.mkv'' ''--''' -(transfer already in progress) -\"\"\"]] - -so it seems that the remote thinks the transfer is still in progress. - -to reproduce this, switch between a wired and wireless connexion before interrupting the process. -"""]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_3_3ff700a3daf515fceb715514a7cbd82a._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_3_3ff700a3daf515fceb715514a7cbd82a._comment deleted file mode 100644 index 742109cd6..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt/comment_3_3ff700a3daf515fceb715514a7cbd82a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 3" - date="2014-08-15T18:02:12Z" - content=""" -Right .. Normally it makes sense to prevent redundant transfers, but this is not the case when git-annex-shell sendkey is sending a file to a remote. Especially since the rsync protocol does not transport stderr output over the link to display to the user. - -Should be an easy fix. -"""]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_4_940209377475ed77170098e32048022c._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_4_940209377475ed77170098e32048022c._comment deleted file mode 100644 index 5141c18e9..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt/comment_4_940209377475ed77170098e32048022c._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="scottgwald@57e4fabac1105bdeb5196fac4525051448d827a4" - nickname="scottgwald" - subject="I am experiencing this as well" - date="2015-06-03T03:36:54Z" - content=""" -Is there a fix? A workaround? - -"""]] diff --git a/doc/bugs/protocol_mismatch_after_interrupt/comment_5_e7bae22caab4eef5ec8b90024e190fbe._comment b/doc/bugs/protocol_mismatch_after_interrupt/comment_5_e7bae22caab4eef5ec8b90024e190fbe._comment deleted file mode 100644 index aa1c51965..000000000 --- a/doc/bugs/protocol_mismatch_after_interrupt/comment_5_e7bae22caab4eef5ec8b90024e190fbe._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-06-03T17:18:35Z" - content=""" -This bug is closed because it was fixed. At least for uploads, which is -what this bug is about. - -Make sure that the remote server and local client both have a recent -version of git-annex, and report a new bug if you have a problem. -"""]] diff --git a/doc/bugs/provide_--version_.mdwn b/doc/bugs/provide_--version_.mdwn deleted file mode 100644 index 50b7f7129..000000000 --- a/doc/bugs/provide_--version_.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -### Please describe the problem. - -I see no easy way to determine version of git-annex (besides as of the debian package). git annex is not aware of "git annex --version" either - -[[done]] diff --git a/doc/bugs/provide_--version_/comment_1_3c7e5fa4627a202e7369e4e115a111be._comment b/doc/bugs/provide_--version_/comment_1_3c7e5fa4627a202e7369e4e115a111be._comment deleted file mode 100644 index 6237a3ca2..000000000 --- a/doc/bugs/provide_--version_/comment_1_3c7e5fa4627a202e7369e4e115a111be._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo" - nickname="Dirk" - subject="comment 1" - date="2015-02-23T19:55:36Z" - content=""" -Try \"git-annex version\". -"""]] diff --git a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__.mdwn b/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__.mdwn deleted file mode 100644 index d104dc91a..000000000 --- a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__.mdwn +++ /dev/null @@ -1,137 +0,0 @@ -### Please describe the problem. - -For a file which I add directly under git (using git -c annex.largefiles='exclude=analysis' annex add * ) upon proxied commit annex renames it with suffix .variant-local. - -### What steps will reproduce the problem? - -see transcript below - -here you could find original demo script http://www.onerussian.com/tmp/demo-script.sh which was intended to do such commits in a loop but ended up growing a swarm of those *-local files. - -### What version of git-annex are you using? On what operating system? - -debian sid 5.20150710-2 - -### 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 -hopa:/tmp/demo1 -$> git init; git annex init; git annex direct; git annex version -Initialized empty Git repository in /tmp/demo1/.git/ -init ok -(recording state in git...) -commit -On branch master - -Initial commit - -nothing to commit -ok -direct ok -git-annex version: 5.20150710-2 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -2 22762.....................................:Tue 28 Jul 2015 05:19:53 PM EDT:. -hopa:/tmp/demo1 -$> echo 'echo 999' >> analysis -zsh: no such file or directory: analysis -2 22763 ->1.....................................:Tue 28 Jul 2015 05:20:05 PM EDT:. -hopa:/tmp/demo1 -$> echo 'echo 999' >| analysis -2 22764.....................................:Tue 28 Jul 2015 05:20:11 PM EDT:. -hopa:/tmp/demo1 -$> git -c annex.largefiles='exclude=analysis' annex add * -add analysis (non-large file; adding content to git repository) ok -(recording state in git...) -2 22765.....................................:Tue 28 Jul 2015 05:20:18 PM EDT:. -hopa:/tmp/demo1 -$> ls -analysis -2 22766.....................................:Tue 28 Jul 2015 05:20:24 PM EDT:. -hopa:/tmp/demo1 -$> git annex proxy -- git commit -m "analysis 1" -ok -[annex/direct/master (root-commit) 56e3ee4] analysis 1 - 1 file changed, 1 insertion(+) - create mode 100644 analysis -2 22767.....................................:Tue 28 Jul 2015 05:20:29 PM EDT:. -hopa:/tmp/demo1 -$> echo 'echo 999' >> analysis -zsh: no such file or directory: analysis -2 22768 ->1.....................................:Tue 28 Jul 2015 05:20:35 PM EDT:. -hopa:/tmp/demo1 -$> ls -analysis.variant-local -2 22769.....................................:Tue 28 Jul 2015 05:20:38 PM EDT:. -hopa:/tmp/demo1 -$> git annex indirect -commit (recording state in git...) - -ok -[annex/direct/master 2c765d9] commit before switching to indirect mode - 1 file changed, 1 deletion(-) - delete mode 100644 analysis -ok -indirect ok -ok -2 22770.....................................:Tue 28 Jul 2015 05:21:56 PM EDT:. -hopa:/tmp/demo1 -$> ls -analysis.variant-local -2 22771.....................................:Tue 28 Jul 2015 05:21:57 PM EDT:. -hopa:/tmp/demo1 -$> git log --stat -commit 2c765d9dee7a53e6aaec1dd7efc0550353998a53 -Author: Yaroslav Halchenko <debian@onerussian.com> -Date: Tue Jul 28 17:21:56 2015 -0400 - - commit before switching to indirect mode - - analysis | 1 - - 1 file changed, 1 deletion(-) - -commit 56e3ee4b3b1ec6fdc1b9e058dcd6cae60bba73ac -Author: Yaroslav Halchenko <debian@onerussian.com> -Date: Tue Jul 28 17:20:29 2015 -0400 - - analysis 1 - - analysis | 1 + - 1 file changed, 1 insertion(+) - - -# End of transcript or log. -"""]] - -> Ok, this is [[fixed|done]]. -> -> What was going on is, proxy was reusing mergeDirectCleanup -> since it's in a similar situation to cleaning up after a direct mode -> merge. But, a direct mode merge can pull in changes to files that exist -> in the local work tree (and may or may not be in the index), but are -> not committed to git locally yet. So, it has to -> detect those and move them aside (to ".varient-local"). The code to do -> that is what was failing in this reuse of mergeDirectCleanup. -> -> So, I made that code path not run when using proxy. And for commits, -> that's good enough. If there's a file in the work tree that's -> not added to git, then a proxied commit can't affect it, so that code -> path is not needed in this case. -> -> Come to think, other proxied actions might affect such a file. For -> example a proxied revert could revert the deletion of a file with the -> same name, that's in the work tree. In this case, should the proxyed revert -> fail because there's a file in the work tree that will be overwritten by -> the revert? Would be good if it did, because git revert will normally fail -> in this situation. -> -> The only way to make a proxied revert, etc exactly match a -> non-proxied revert is to arrange for all files that are in the work -> tree and not checked into git to be present in the temp work tree when -> the proxied command is run. Which I've now done. --[[Joey]] diff --git a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_1_3ebf2dbd5af42988b79b0713f5014f91._comment b/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_1_3ebf2dbd5af42988b79b0713f5014f91._comment deleted file mode 100644 index 75d46b354..000000000 --- a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_1_3ebf2dbd5af42988b79b0713f5014f91._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-30T17:16:09Z" - content=""" -This only happens when the file being added is not an annexed link. -I guess it has something to do with preserveUnannexed -"""]] diff --git a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_2_4bb26a582a320f2703ec6e190b75c977._comment b/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_2_4bb26a582a320f2703ec6e190b75c977._comment deleted file mode 100644 index 3837a1b8e..000000000 --- a/doc/bugs/proxy_--_git_commit__for_a_file_under_git__creates_.variant-local___40__original_file_is_even_get_removed__41__/comment_2_4bb26a582a320f2703ec6e190b75c977._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="comment 2" - date="2015-07-31T14:16:28Z" - content=""" -but logically it shouldn't happen and I shouldn't care about some additional variable, if stuff goes directly into git anyways, right? -"""]] diff --git a/doc/bugs/proxy_command_fails_on_Windows.mdwn b/doc/bugs/proxy_command_fails_on_Windows.mdwn deleted file mode 100644 index 370764e03..000000000 --- a/doc/bugs/proxy_command_fails_on_Windows.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -The new ''git annex proxy'' command fails every call in the 2014-11-28 daily Windows build. - -### What steps will reproduce the problem? - -1) Install daily Windows build via https://downloads.kitenet.net/git-annex/autobuild/windows/. - -2) Run, in git bash: - - $ git annex proxy -- pull - git-annex: pull: createProcess: does not exist (No such file or directory) - failed - git-annex: proxy: 1 failed - -### What version of git-annex are you using? On what operating system? - -Daily Windows build 5.20141128-g70f997e on Windows 7 x64 - -### Please provide any additional information below. - - $ git annex version - git-annex version: 5.20141128-g70f997e - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feed - s Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SH - A256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar ho - ok external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 2 3 4 - -> Seems the man page was mis-read, or possibly I've fixed it, -> since it certianly says you need to specify "-- git cmd", not -> just "-- cmd". [[done]] --[[Joey]] diff --git a/doc/bugs/proxy_command_fails_on_Windows/comment_1_a6d85bd65cd4df957ed108b2966584ef._comment b/doc/bugs/proxy_command_fails_on_Windows/comment_1_a6d85bd65cd4df957ed108b2966584ef._comment deleted file mode 100644 index 0eaf88fa3..000000000 --- a/doc/bugs/proxy_command_fails_on_Windows/comment_1_a6d85bd65cd4df957ed108b2966584ef._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2014-12-01T21:51:40Z" - content=""" -If you want to run "git pull" using the proxy, you need to use: - -git annex proxy -- git pull - -Like it says on the man page. Instead you told it to run a command named -"pull", which would work if you had a program by that name, but you don't. -:) -"""]] diff --git a/doc/bugs/proxy_command_fails_on_Windows/comment_1_f4cb0a0ab445a8e9993c6736a6e23887._comment b/doc/bugs/proxy_command_fails_on_Windows/comment_1_f4cb0a0ab445a8e9993c6736a6e23887._comment deleted file mode 100644 index b242736df..000000000 --- a/doc/bugs/proxy_command_fails_on_Windows/comment_1_f4cb0a0ab445a8e9993c6736a6e23887._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmWBvsZvSsAL8P2ye3F0OBStjFCVnOImzM" - nickname="Jarno" - subject="Not a bug" - date="2014-11-28T18:25:40Z" - content=""" -This was, in fact, just an unclear error message. The command was missing \"git\", and so should have been: - - $ git annex proxy -- git pull -"""]] diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn deleted file mode 100644 index 41122f8a6..000000000 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -### Please describe the problem. - -I've setup a gcrypt based git backup repository as per the examples here: - -http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/ - -It all seems to work well until I try to do any kind git annex operation from the console on the gcrypted repo on the remote server. If I run a `git annex fsck` (this seems a reasonable thing to do) then it initialises the encrypted remote with a different uuid to the one in the creation step. The initial repository that created the repo seems to work okay but it's no longer possible to add further repositories without getting conflicting uuid errors. - -### What steps will reproduce the problem? - - -### What version of git-annex are you using? On what operating system? - - -### 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. -"""]] - -> [[fixed|done]]; <>. I have updated the OSX autobuilder so tonight's -> build will include the fixed git-remote-gcrypt. --[[Joey]] -> -> Note that gcrypt repositories affected by this bug are in fact empty, so -> the first time a push is made with the fixed gcrypt it will probably -> generate a new gcrypt-id and push everything. diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment deleted file mode 100644 index a8a4af4cf..000000000 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_1_11af589cf646cb7552eeb5c7401934f5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 1" - date="2014-04-27T15:04:09Z" - content=""" -Thinking about it some more perhaps it's not a reasonable thing to do if you don't want people to be able to discover info about the repo. However it would be good to somehow prevent git-annex from running a local init operation when working with a gcrypt repo. -"""]] diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_2_d81cb9b47dea34b639dc250bb231010a._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_2_d81cb9b47dea34b639dc250bb231010a._comment deleted file mode 100644 index e3e744127..000000000 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_2_d81cb9b47dea34b639dc250bb231010a._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 2" - date="2014-04-27T19:19:22Z" - content=""" -I'm having a pretty bad time with gcrypt based repos. Seemingly at random a `git-annex sync` will occasionally decide that the remote repo doesn't exist and then attempt to create a new one - it generates a new gcryptid and the repository seems lost. - -This sometimes happens after a good few hours of use, sometimes it happens immediately after creation (but maybe due to the fact that annexs are sullied by previous bad attempts). I've cleaned up making the repo dead, removing via `git remote` and editing the remote.log in the git-annex branch. No idea if that's enough. - -What do you need from me to try to sort this? - -Cheers, - -Matt. -"""]] diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_3_8df00f0ed4a26f702e0935b366521530._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_3_8df00f0ed4a26f702e0935b366521530._comment deleted file mode 100644 index fd2e9f840..000000000 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_3_8df00f0ed4a26f702e0935b366521530._comment +++ /dev/null @@ -1,164 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" - nickname="Matt" - subject="comment 3" - date="2014-04-29T03:00:59Z" - content=""" -Hi, I'm finally through trial and error am able to reproduce the bug... - -On OSX using version 5.20140420-ga25b8bb the creation of an gcrypt remote via initremote does not work properly. See the attached debug log for what happens - no errors but subsequent syncs fail and creates a new repo. - -Using linux and version 5.20140421-g515d251 to create the gcrypt does work without issue. Interestingly the OSX client will happily use the linux created repo without problem (at least it hasn't borked it yet). This suggests something up in the creation step. Perhaps this is fixed in the later version (see the other bug about the latest OSX upgrade having the older binary)? But I didn't see anything in the change log about it? But I did see the gcrypt script in the manifest now... - -<pre>~/iMovies $ git annex initremote isilon-2 type=gcrypt gitrepo=ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 keyid=matt@dancingfrog.co.uk -[2014-04-29 01:54:47 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"git-annex\"] -[2014-04-29 01:54:47 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-04-29 01:54:47 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..3269adaaa41b42dab88399e8212d77301967f436\",\"--oneline\",\"-n1\"] -git [2014-04-29 01:54:47 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..4dc8becdffd42c9af57e0d1007892516f2114c0e\",\"--oneline\",\"-n1\"] -[2014-04-29 01:54:47 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..13d8993b7d9a89ea4198ec3edd63aa575745c64c\",\"--oneline\",\"-n1\"] -[2014-04-29 01:54:47 BST] chat: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"cat-file\",\"--batch\"] -initremote isilon-2 (encryption setup) [2014-04-29 01:54:47 BST] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--with-colons\",\"--list-public-keys\",\"matt@dancingfrog.co.uk\"] -[2014-04-29 01:54:47 BST] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--gen-random\",\"--armor\",\"2\",\"512\"] -[2014-04-29 01:54:47 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--recipient\",\"68D8501429C42E01\",\"--encrypt\",\"--no-encrypt-to\",\"--no-default-recipient\",\"--force-mdc\",\"--no-textmode\"] -(hybrid cipher with gpg key 68D8501429C42E01) [2014-04-29 01:54:47 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"remote\",\"add\",\"isilon-2\",\"gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2\"] -[2014-04-29 01:54:47 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"config\",\"remote.isilon-2.gcrypt-participants\",\"68D8501429C42E01\"] -[2014-04-29 01:54:47 BST] read: git [\"config\",\"--null\",\"--list\"] -[2014-04-29 01:54:48 BST] read: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--with-colons\",\"--list-secret-keys\",\"--fixed-list-mode\"] -[2014-04-29 01:54:48 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"config\",\"remote.isilon-2.gcrypt-signingkey\",\"68D8501429C42E01\"] -[2014-04-29 01:54:48 BST] read: git [\"config\",\"--null\",\"--list\"] -[2014-04-29 01:54:48 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"fetch\",\"isilon-2\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 -[2014-04-29 01:54:49 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"push\",\"isilon-2\",\"refs/heads/git-annex\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 -gcrypt: Setting up new repository -gcrypt: Remote ID is :id:oWSdoSaFhKA19TcXRHPS -Counting objects: 4170, done. -Compressing objects: 100% (3113/3113), done. -Total 4170 (delta 149), reused 146 (delta 3) -gcrypt: Encrypting to: -R 68D8501429C42E01 -gcrypt: Requesting manifest signature - -You need a passphrase to unlock the secret key for -user: \"Matt Ford (Work) <matt.ford@manchester.ac.uk>\" -1024-bit DSA key, ID 29C42E01, created 2010-03-10 - -gpg: 68D8501429C42E01: skipped: public key already present -To gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 - * [new branch] git-annex -> git-annex -[2014-04-29 01:54:52 BST] read: git [\"config\",\"--null\",\"--list\"] -[2014-04-29 01:54:52 BST] call: ssh [\"-S\",\".git/annex/ssh/rss\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"-T\",\"rss\",\"git-annex-shell 'gcryptsetup' '/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2' ':id:oWSdoSaFhKA19TcXRHPS'\"] -ok -[2014-04-29 01:54:53 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"config\",\"remote.isilon-2.annex-gcrypt\",\"shell\"] -[2014-04-29 01:54:53 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"config\",\"remote.isilon-2.annex-uuid\",\"8fc5d933-d76f-5a61-b3a0-96b909e3f06c\"] -ok -[2014-04-29 01:54:53 BST] chat: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"hash-object\",\"-w\",\"--stdin-paths\",\"--no-filters\"] -[2014-04-29 01:54:53 BST] feed: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"update-index\",\"-z\",\"--index-info\"] -[2014-04-29 01:54:53 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -(Recording state in git...) -[2014-04-29 01:54:53 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"write-tree\"] -[2014-04-29 01:54:53 BST] chat: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"commit-tree\",\"8c27761996045cb6daf7dc83920e15bfe0f2b2ed\",\"-p\",\"refs/heads/git-annex\"] -[2014-04-29 01:54:53 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"update-ref\",\"refs/heads/git-annex\",\"0755de89ac06bb3babc73de294a550d9b62f39f1\"] -[2014-04-29 01:54:53 BST] read: ssh [\"-O\",\"stop\",\"-S\",\"rss\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"localhost\"] - - -~/iMovies $ git annex sync -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"git-annex\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..0755de89ac06bb3babc73de294a550d9b62f39f1\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..4dc8becdffd42c9af57e0d1007892516f2114c0e\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..3269adaaa41b42dab88399e8212d77301967f436\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..13d8993b7d9a89ea4198ec3edd63aa575745c64c\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:55 BST] chat: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"cat-file\",\"--batch\"] -commit [2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"commit\",\"-a\",\"-m\",\"git-annex automatic sync\"] -ok -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"symbolic-ref\",\"HEAD\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"refs/heads/master\"] -[2014-04-29 01:57:55 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/heads/synced/master\"] -[2014-04-29 01:57:55 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/master..refs/heads/synced/master\",\"--oneline\",\"-n1\"] -pull isilon -[2014-04-29 01:57:55 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"fetch\",\"isilon\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov -[2014-04-29 01:57:56 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon/master\"] -[2014-04-29 01:57:56 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/master..refs/remotes/isilon/master\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:56 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon/synced/master\"] -[2014-04-29 01:57:56 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/synced/master..refs/remotes/isilon/synced/master\",\"--oneline\",\"-n1\"] -ok -pull isilon-2 -[2014-04-29 01:57:57 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"fetch\",\"isilon-2\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 -[2014-04-29 01:57:57 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon-2/master\"] -[2014-04-29 01:57:57 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon-2/synced/master\"] -ok -[2014-04-29 01:57:57 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"git-annex\"] -[2014-04-29 01:57:57 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2014-04-29 01:57:57 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..0755de89ac06bb3babc73de294a550d9b62f39f1\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:58 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..4dc8becdffd42c9af57e0d1007892516f2114c0e\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:58 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..3269adaaa41b42dab88399e8212d77301967f436\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:58 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/heads/git-annex..13d8993b7d9a89ea4198ec3edd63aa575745c64c\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:58 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"branch\",\"-f\",\"synced/master\"] -[2014-04-29 01:57:58 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon/synced/master\"] -[2014-04-29 01:57:58 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/remotes/isilon/synced/master..refs/heads/synced/master\",\"--oneline\",\"-n1\"] -[2014-04-29 01:57:58 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon/git-annex\"] -[2014-04-29 01:57:58 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"log\",\"refs/remotes/isilon/git-annex..git-annex\",\"--oneline\",\"-n1\"] -push isilon -[2014-04-29 01:57:58 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"push\",\"isilon\",\"+git-annex:synced/git-annex\",\"master:synced/master\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov -gcrypt: Setting up new repository -gcrypt: Remote ID is :id:p4cHPeAFIRIvZTnm4UrK -Counting objects: 5649, done. -Compressing objects: 100% (4579/4579), done. -Total 5649 (delta 151), reused 146 (delta 3) -gcrypt: Encrypting to: -R 68D8501429C42E01 -gcrypt: Requesting manifest signature - -You need a passphrase to unlock the secret key for -user: \"Matt Ford (Work) <matt.ford@manchester.ac.uk>\" -1024-bit DSA key, ID 29C42E01, created 2010-03-10 - -gpg: 68D8501429C42E01: skipped: public key already present -To gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov - * [new branch] git-annex -> synced/git-annex - * [new branch] master -> synced/master -[2014-04-29 01:58:01 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"push\",\"isilon\",\"master\"] - -You need a passphrase to unlock the secret key for -user: \"Matt Ford (Work) <matt.ford@manchester.ac.uk>\" -1024-bit DSA key, ID 29C42E01, created 2010-03-10 - -ok -[2014-04-29 01:58:03 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"show-ref\",\"--verify\",\"-q\",\"refs/remotes/isilon-2/synced/master\"] -push isilon-2 -[2014-04-29 01:58:03 BST] call: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"push\",\"isilon-2\",\"+git-annex:synced/git-annex\",\"master:synced/master\"] -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 -gcrypt: Setting up new repository -gcrypt: Remote ID is :id:wTHlCd+vFviIzoTDv2Xu -Counting objects: 5649, done. -Compressing objects: 100% (4579/4579), done. -Total 5649 (delta 152), reused 146 (delta 3) -gcrypt: Encrypting to: -R 68D8501429C42E01 -gcrypt: Requesting manifest signature - -You need a passphrase to unlock the secret key for -user: \"Matt Ford (Work) <matt.ford@manchester.ac.uk>\" -1024-bit DSA key, ID 29C42E01, created 2010-03-10 - -gpg: 68D8501429C42E01: skipped: public key already present -To gcrypt::ssh://rss/home/matt/mnt/isilon/rss/zzalsmf3/git-annex/mov2 - * [new branch] git-annex -> synced/git-annex - * [new branch] master -> synced/master -[2014-04-29 01:58:06 BST] read: git [\"--git-dir=/Volumes/Media/iTunes Media/Movies/.git\",\"--work-tree=/Volumes/Media/iTunes Media/Movies\",\"push\",\"isilon-2\",\"master\"] - -You need a passphrase to unlock the secret key for -user: \"Matt Ford (Work) <matt.ford@manchester.ac.uk>\" -1024-bit DSA key, ID 29C42E01, created 2010-03-10 - -ok -[2014-04-29 01:58:09 BST] read: ssh [\"-O\",\"stop\",\"-S\",\"rss\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"localhost\"] -</pre> -"""]] diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment deleted file mode 100644 index d40c435db..000000000 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids/comment_4_7eb33c23223dfc634eb3c9c6621f7f3e._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="216.145.95.162" - subject="comment 4" - date="2014-05-19T16:28:01Z" - content=""" -I can reproduce this problem on OSX. - -I've only gotten as far as seeing that the gcrypt repository never gets initialized as a git repository. It has a config file, but no objects are ever pushed to it. This is why gcrypt sees no repository there in subsequent runs. - -This is a bug in gcrypt, so filed: <https://github.com/blake2-ppc/git-remote-gcrypt/issues/15> -"""]] diff --git a/doc/bugs/repo_creation_fails_on_android_4.4.3.mdwn b/doc/bugs/repo_creation_fails_on_android_4.4.3.mdwn deleted file mode 100644 index 335357c10..000000000 --- a/doc/bugs/repo_creation_fails_on_android_4.4.3.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -Hello everyone, -Creating a new repository through the web-app fails on Android 4.4.3, git annex version 5.20140612-g1bebb0d. - -Steps to reproduce the problem: - -1. Install git annex for android 4.4.3 - -2. Launch git annex. - -3. The terminal opens up reporting some (non-fatal?) errors. (I notice that I can't do anything in the terminal, is it supposed to reply to git annex commands? typing in "git annex version" does nothing). - -4. The web-app is launched. - -5. Click on make repository. - -6. Error message. - -I've made a few screenshots to illustrate: - -[terminal screenshot](https://drive.google.com/file/d/0B1qM91oKErVDSEJwbnhiaFJhQVU/edit?usp=sharing) - -This is the webapp error when creating a new repo: - -[first](https://drive.google.com/file/d/0B1qM91oKErVDVHVuLVpacmJaOEU/edit?usp=sharing) - -[second](https://drive.google.com/file/d/0B1qM91oKErVDX3R3cFhyb2VjcHc/edit?usp=sharing) - -Being on android I can't find any ".git/annex/daemon.log to" to report. I tried to look in the repo folder but there was no .git in it (maybe hidden?) - -> dup; [[done]] --[[Joey]] diff --git a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_1_01e638ec9c6d74966d76b6ceb7c06bad._comment b/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_1_01e638ec9c6d74966d76b6ceb7c06bad._comment deleted file mode 100644 index 9994130f5..000000000 --- a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_1_01e638ec9c6d74966d76b6ceb7c06bad._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnxFr-i4nNUVrj3PJ_JKhp7GtZ5Xom7-3w" - nickname="John" - subject="Errors from Screenshots" - date="2014-07-03T20:00:25Z" - content=""" -A low-bandwidth version. - -*terminal screenshot:* - -Falling back to hardcoded app location; cannot find expected files in /data/app-lib -git annex webapp -nex webapp -WARNING: linker: git-annex has text relocations. This is wasting memory and is a security risk. Please fix. -error: fchmod on /sdcard/annex/.git/config.lock failed: Operation not permitted -error: fchmod on /sdcard/annex/.git/config.lock failed: Operation not permitted - -*first:* - -git [Param \"config\",Param \"annex.uuid\",Param \"51e7d274-9723-4b14-8c5 - -*second:* - -ram \"annex.uuid\",Param \"51e7d274-9723-4b14-8c57-1d72263e3982\"] failed - -"""]] diff --git a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_2_07c0f9387433b7107e9def2bfbed3039._comment b/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_2_07c0f9387433b7107e9def2bfbed3039._comment deleted file mode 100644 index 473bfb308..000000000 --- a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_2_07c0f9387433b7107e9def2bfbed3039._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-03T20:13:57Z" - content=""" -Thanks, this is then a dup of [[bugs/Android_fails_on_Google_Nexus_10_Jellybean]]. -"""]] diff --git a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_3_caf4f02677ea9e7fe28dbace99aa6860._comment b/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_3_caf4f02677ea9e7fe28dbace99aa6860._comment deleted file mode 100644 index 0b46416f5..000000000 --- a/doc/bugs/repo_creation_fails_on_android_4.4.3/comment_3_caf4f02677ea9e7fe28dbace99aa6860._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 3" - date="2014-07-04T17:52:41Z" - content=""" -This problem should be fixed in the most recent daily build of git-annex for android. Testing appreciated. -"""]] diff --git a/doc/bugs/rsync_on_windows_broken_by_upgrade.mdwn b/doc/bugs/rsync_on_windows_broken_by_upgrade.mdwn deleted file mode 100644 index 929770ccc..000000000 --- a/doc/bugs/rsync_on_windows_broken_by_upgrade.mdwn +++ /dev/null @@ -1,69 +0,0 @@ -rsync on windows has been broken by the upgrade to a newer version of -cygwin. `rsync user@host:file file` opens the ssh connection, but hangs -up with a protocol error. Apparently it doesn't get even the protocol -version message from the server. - -Problem doesn't seem to affect the bundled ssh, just rsync. --[[Joey]] - -> Update: Apparently there are two ssh's! msysgit bundles one (did it used -> to in PATH?) and git-annex bundles one from cygwin. msysgit's ends up -> in Git/bin and git-annex's in Git/cmd. -> -> Seems that cygwin's rsync cannot use git's ssh for whatever reason. -> -> So the workaround is to -> delete Git/bin/ssh.exe and leave Git/cmd/ssh.exe. Then rsync works. -> However, this may screw up git's use of ssh or other stuff. -> -> Particularly, cygwin's ssh doesn't honor HOME anymore, instead using -> the getpwent home, which doesn't exist. -> -> Also, see -> [[webapp_fails_to_connect_to_ssh_repository___40__windows__41__]] -> which is the inverse of this bug perhaps, or at least seems related. -> -> Using 2 ssh's that try to use config from different places seems like -> a losing propisition. Need to find an rsync that works with git's ssh. -> --[[Joey]] -> -> > Update: The git bin/ directory is only in PATH when inside "git bash". -> > This bug only seems to affect using git-annex that way. The git bash -> > PATH has `bin` before `cmd`. -> > -> > Also, git seems to work ok using the newer ssh from cygwin. -> > However, that ssh tries to write to a .ssh/known_hosts -> > in a cygwin location and so doesn't remember hosts. -> > -> > What a mess. You can install any version of Linux and get rsync, ssh, -> > git that all integrate and work together. Or you can use Windows and -> > enjoy the pain(TM) --[[Joey]] - ->>> Possible fixes: ->>> ->>> * Roll the bundled ssh and rsync back to the older versions. ->>> ->>> **This works**. And, seems that the older version of ssh from cygwin ->>> looks at HOME, rather than getpwent home which the newer ->>> cygwin ssh does. ->>> ->>> * Roll the bundled rsync back, drop ssh. Rely on msysgit's bundled ssh, ->>> copying it into cmd so it's in PATH. Check: Does this combo work? ->>> ->>> **This works**! rsync 3.0.9 works ok with msysgit's bundled ssh. ->>> rsync 3.1.1 is the one that needs a newer ssh. **[[done]]** ->>> ->>> Note that this means we're using an old version of rsync ->>> from cygwin with libraries from a newer cygwin. That might prove ->>> fragile as cygwin is upgraded. ->>> ->>> * Hope that msysgit gets updated to include a newer version of ssh ->>> which works with the new rsync. ->>> ->>> (Seems reasonable as a long-term plan, assuming that the ->>> new rsync's problem with ssh is that it needs a new one, and not some ->>> special cygwin thing.) ->>> ->>> * Get rsync from somewhere else, perhaps msysgit. (Maybe also get ssh ->>> from msysgit?) ->>> * Keep the new rsync from cygwin, and build ssh from source, ->>> patching it to use HOME in preference to getpwent home. diff --git a/doc/bugs/rsync_on_windows_broken_by_upgrade/comment_1_de67cd10dd73fdc4d43eeb7ffbe67568._comment b/doc/bugs/rsync_on_windows_broken_by_upgrade/comment_1_de67cd10dd73fdc4d43eeb7ffbe67568._comment deleted file mode 100644 index 85c5e740f..000000000 --- a/doc/bugs/rsync_on_windows_broken_by_upgrade/comment_1_de67cd10dd73fdc4d43eeb7ffbe67568._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="anton" - subject="Thanks!" - date="2015-05-08T07:11:34Z" - content=""" -Thank you Joey for the great support and all your work on git-annex in general! -"""]] diff --git a/doc/bugs/rsync_remote_is_not_working.mdwn b/doc/bugs/rsync_remote_is_not_working.mdwn deleted file mode 100644 index 766d6e900..000000000 --- a/doc/bugs/rsync_remote_is_not_working.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -Host: Mac OS with git-annex 5.20140919-g0f7caf5 - -Remote: Linux - -* with git-annex 5.20140920-gb0c4300 -* using user&password login - -On Host: - -1. create a repo with git init && git annex init && git annex direct -1. add a rsync repo in git-annex webapp, type "small archive", with shared encryption (same result using command line) -1. copy some new files to the repo, expect the files to appear in the remote repo (check with du) -1. Web app says "synced with remote-name", but remote repo is completely empty -1. run git annex copy --to $remotename, now remote repo is filled with files -1. but the sizes are really small, seems that the actual files are not being transferred -1. convert the repo to indirect repo: git annex indirect -1. re-run git annex copy, now the repo size on the remote seems about right -1. now start git annex assistant, copy some new files, expect new files to be synced -1. actual: the remote becomes completely empty, the existing files are removed! - -The other small issue - -* The add remote interface stops at "check remote" prompt for a long time without completing -* Kill the webapp process, re-run webapp, add remote again, it worked very quickly -* But future interaction with the remote still requires password, both commandline & webapp - -> Closing this bug report since it seems it was largely due to a -> misunderstanding of what "small archive" does. [[done]] --[[Joey]] diff --git a/doc/bugs/rsync_remote_is_not_working/comment_1_8998edf856a411de1f90b27568628feb._comment b/doc/bugs/rsync_remote_is_not_working/comment_1_8998edf856a411de1f90b27568628feb._comment deleted file mode 100644 index 50f0c06cc..000000000 --- a/doc/bugs/rsync_remote_is_not_working/comment_1_8998edf856a411de1f90b27568628feb._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.96" - subject="comment 1" - date="2014-10-21T20:07:40Z" - content=""" -A \"small archive\" only wants to contain files that are located inside archive/ directories. - -That seems to explain everything you reported except for: - -> 6. but the sizes are really small, seems that the actual files are not being transferred - -Maybe the remote is configured to use chunking? What happens if you run `git annex fsck --from $remotename` after copying a file to it? Any problem detected? - -> The add remote interface stops at \"check remote\" prompt for a long time without completing - -Please explain exactly what you did in the webapp. What did you click on, and what did you enter? I need enough detail to be able to reproduce the problem. - -(Also, in the future, one problem per bug report turns out to be a lot less confusing, and have better results all around. True here and really anywhere..) -"""]] diff --git a/doc/bugs/rsync_remote_with_-J2_fails.mdwn b/doc/bugs/rsync_remote_with_-J2_fails.mdwn deleted file mode 100644 index 766f671d7..000000000 --- a/doc/bugs/rsync_remote_with_-J2_fails.mdwn +++ /dev/null @@ -1,57 +0,0 @@ -### Please describe the problem. - -Trying to `git annex copy` to an rsync special remote with the -J flag fails with a lot of errors. (And is slow without it). - -### What steps will reproduce the problem? - -$ git annex copy --to rsync-remote -J2 - -### What version of git-annex are you using? On what operating system? - -5.20150710-g8fd7052 on Ubuntu. - -### Please provide any additional information below. - -[[!format sh """ -$ git annex copy --to freenas-rsync -J2 -E: file has vanished: "/media/depot/annex/.git/annex/tmp/rsynctmp/29637/caa/2d1/SHA256E-s4244--4ec1ea09c7605a589a9bf6cd927e96737c512d17d8053cbfaf0dcd364702400c.txt/SHA256E-s4244--4ec1ea09c7605a589a9bf6cd927e96737c512d17d8053cbfaf0dcd364702400c.txt" -E: rsync warning: some files vanished before they could be transferred (code 24) at main.c(1183) [sender=3.1.1] -E: rsync: change_dir "/media/depot/annex//.git/annex/tmp/rsynctmp/29637" failed: No such file or directory (2) -E: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1] - .git/annex/tmp/rsynctmp/29637/c17: removeDirectory: does not exist (No such file or directory) - .git/annex/tmp/rsynctmp/29637: getDirectoryContents: does not exist (No such file or directory) - .git/annex/tmp/rsynctmp/29637/67e: removeLink: does not exist (No such file or directory) - .git/annex/tmp/rsynctmp/29637: getDirectoryContents: does not exist (No such file or directory) - .git/annex/tmp/rsynctmp/29637: getDirectoryContents: does not exist (No such file or directory) - .git/annex/tmp/rsynctmp/29637/49e/833: removeLink: inappropriate type (Is a directory) -^C - -J1 hangs a long time: -$ git annex copy --to freenas-rsync -J1 -^C - -Works without J flag: -$ git annex copy --to freenas-rsync -copy GarageBand/._.DS_Store (checking freenas-rsync...) ok -copy GarageBand/._My Song.band (checking freenas-rsync...) ok -copy GarageBand/._code monkey.band (checking freenas-rsync...) ok -copy GarageBand/._first of may.band (checking freenas-rsync...) ok - -Version: -$ git annex version -git-annex version: 5.20150710-g8fd7052 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -Repo config: -[remote "freenas-rsync"] - annex-rsyncurl = freenas:/mnt/tank/home/jnewsome/annex-rsync-backend - annex-uuid = f05581cc-7236-41ed-9db8-49424f863307 - -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment b/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment deleted file mode 100644 index eeb4b34af..000000000 --- a/doc/bugs/rsync_remote_with_-J2_fails/comment_1_793bbc86b495dda0328c35cb5abe4fad._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-30T17:18:24Z" - content=""" -The -J1 is a red herring; there's no progress output for -J modes, so the -whole transfer runs quietly there. - -The -J2 failure is because the rsync special remote implementation uses a -local scratch directory which is supposed to be empty. But, since it uses -the pid of the process to create the directory name, concurrently transfers -will use the same scratch directory and so interfere with one-another. -"""]] diff --git a/doc/bugs/rsync_special_remote_fails_to___96__get__96___files_which_have_names_containing_spaces.mdwn b/doc/bugs/rsync_special_remote_fails_to___96__get__96___files_which_have_names_containing_spaces.mdwn deleted file mode 100644 index 040d86bb8..000000000 --- a/doc/bugs/rsync_special_remote_fails_to___96__get__96___files_which_have_names_containing_spaces.mdwn +++ /dev/null @@ -1,50 +0,0 @@ - ~$ mkdir test annex - ~$ cd test - ~$ git init - Initialized empty Git repository in /home/user/test/.git/ - ~$ git annex init test - init test ok - ~$ git annex initremote localrsync encryption=none type=rsync rsyncurl=localhost:annex/ - initremote localrsync ok - ~$ cp /home/user/Music/Charming\ Hostess/Eat/03\ Mi\ Nuera.ogg ./ - ~$ git annex add 03\ Mi\ Nuera.ogg - add 03 Mi Nuera.ogg ok - (Recording state in git...) - ~$ git commit -m "add ogg" - fatal: No HEAD commit to compare with (yet) - fatal: No HEAD commit to compare with (yet) - [master (root-commit) 12608af] add ogg - 1 files changed, 1 insertions(+), 0 deletions(-) - create mode 120000 03 Mi Nuera.ogg - ~$ git annex move 03\ Mi\ Nuera.ogg --to localrsync - move 03 Mi Nuera.ogg (checking localrsync...) (to localrsync...) - sending incremental file list - 1X/ - 1X/39/ - 1X/39/WORM-s6296772-m1311874383--03 Mi Nuera.ogg/ - 1X/39/WORM-s6296772-m1311874383--03 Mi Nuera.ogg/WORM-s6296772-m1311874383--03 Mi Nuera.ogg - 6296772 100% 42.98MB/s 0:00:00 (xfer#1, to-check=0/5) - - sent 6297754 bytes received 43 bytes 4198531.33 bytes/sec - total size is 6296772 speedup is 1.00 - ok - ~$ git annex get 03\ Mi\ Nuera.ogg - get 03 Mi Nuera.ogg (from localrsync...) - rsync: link_stat "/home/user/annex/1X/39/WORM-s6296772-m1311874383--03" failed: No such file or directory (2) - rsync: link_stat "/home/user/Mi" failed: No such file or directory (2) - rsync: change_dir "/home/user/Nuera.ogg" failed: No such file or directory (2) - rsync: link_stat "/home/user/Mi" failed: No such file or directory (2) - rsync: link_stat "/home/user/Nuera.ogg" failed: No such file or directory (2) - - sent 8 bytes received 12 bytes 13.33 bytes/sec - total size is 0 speedup is 0.00 - rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1526) [Receiver=3.0.7] - - rsync failed -- run git annex again to resume file transfer - Unable to access these remotes: localrsync - Try making some of these repositories available: - b8b1ea7a-b93f-11e0-b712-d7bffb6e61e6 -- localrsync - failed - git-annex: 1 failed - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files.mdwn b/doc/bugs/runs_of_of_memory_adding_2_million_files.mdwn deleted file mode 100644 index 3891933a6..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -Make 2 million files and `git annex add` (indirect mode), fails at the end: - -<pre> -add 999996 ok -add 999997 ok -(Recording state in git...) -[2014-06-21 11:49:28 JEST] feed: xargs ["-0","git","--git-dir=/home/joey/tmp/r/.git","--work-tree=/home/joey/tmp/r","add","--"] -add 999998 ok -add 999999 ok -[2014-06-21 11:49:49 JEST] read: git ["--git-dir=/home/joey/tmp/r/.git","--work-tree=/home/joey/tmp/r","diff","--name-only","--diff-filter=T","-z","--","."] -(Recording state in git...) -[2014-06-21 11:52:24 JEST] feed: xargs ["-0","git","--git-dir=/home/joey/tmp/r/.git","--work-tree=/home/joey/tmp/r","add","--"] -Stack space overflow: current size 8388608 bytes. -Use `+RTS -Ksize -RTS' to increase it. -</pre> - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_10_a201485bf41514fde7c61a4dcbb5064f._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_10_a201485bf41514fde7c61a4dcbb5064f._comment deleted file mode 100644 index 9d5c8aab6..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_10_a201485bf41514fde7c61a4dcbb5064f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.54" - subject="comment 10" - date="2014-10-02T15:35:15Z" - content=""" -This got fixed in version 5.20140707 -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_1_8b60b7816b9bf2c8cdd21b5cae431555._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_1_8b60b7816b9bf2c8cdd21b5cae431555._comment deleted file mode 100644 index d4b1c3fd8..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_1_8b60b7816b9bf2c8cdd21b5cae431555._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 1" - date="2014-07-04T18:24:51Z" - content=""" -The diff-filter=T comes from when Command.Add runs its pass to find unlocked files. It's finished adding all the files, so it must either be that or the git-annex branch commit that's running out of memory, I think. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_2_32908da23e4fb38a7d20b765a5ab4656._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_2_32908da23e4fb38a7d20b765a5ab4656._comment deleted file mode 100644 index 7f0e8ba70..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_2_32908da23e4fb38a7d20b765a5ab4656._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 2" - date="2014-07-04T18:36:49Z" - content=""" -Does not seem to be the diff-filter=T command that is the problem. It's not outputting a lot of files, and should stream over them even if it did. - -The last xargs appears to be at or near the problem. It is called by Annex.Content.saveState, which first does a Annex.Queue.flush, followed by a Annex.Branch.commit. I suspect the problem is the latter; at this point there are 2 million files in .git/annex/journal waiting to be committed to the git-annex branch. - -In the same big repo, I can add one more file and reproduce the problem running `git annex add $newfile`. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_3_3cff88b50eb3872565bccbeb6ee15716._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_3_3cff88b50eb3872565bccbeb6ee15716._comment deleted file mode 100644 index 7e2c5568d..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_3_3cff88b50eb3872565bccbeb6ee15716._comment +++ /dev/null @@ -1,27 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 3" - date="2014-07-04T19:26:00Z" - content=""" -Looking at the code, it's pretty clear why this is using a lot of memory: - -<pre> - fs <- getJournalFiles jl - liftIO $ do - h <- hashObjectStart g - Git.UpdateIndex.streamUpdateIndex g - [genstream dir h fs] - hashObjectStop h - return $ liftIO $ mapM_ (removeFile . (dir </>)) fs -</pre> - -So the big list in `fs` has to be retained in memory after the files are streamed to update-index, in order for them to be deleted! - -Fixing is a bit tricky.. New journal files can appear while this is going on, so it can't just run getJournalFiles a second time to get the files to clean. -Maybe delete the file after it's been sent to git-update-index? But git-update-index is going to want to read the file, and we don't really know when it will choose to do so. It could wait a while after we've sent the filename to it, potentially. - -Also, per [[!commit 750c4ac6c282d14d19f79e0711f858367da145e4]], we cannot delete the journal files until *after* the commit, or another git-annex process would see inconsistent data! - -I actually think I am going to need to use a temp file to hold the list of files.. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_4_e991986eb8ae49d2e69f7ed7fd61485f._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_4_e991986eb8ae49d2e69f7ed7fd61485f._comment deleted file mode 100644 index 40ff69d05..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_4_e991986eb8ae49d2e69f7ed7fd61485f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 4" - date="2014-07-04T19:38:18Z" - content=""" -While I fixed the problem analized above, it still runs out of memory in the same place. Must be other strictness problems.. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_5_241ad838135a7a377374ca9ba90aec5c._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_5_241ad838135a7a377374ca9ba90aec5c._comment deleted file mode 100644 index 41382e1c2..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_5_241ad838135a7a377374ca9ba90aec5c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 5" - date="2014-07-04T19:53:43Z" - content=""" -The other memory leak is in getJournalFiles itself! -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_6_744982b77cc867e9e3a7d638c7a653d6._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_6_744982b77cc867e9e3a7d638c7a653d6._comment deleted file mode 100644 index 574cc0dc7..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_6_744982b77cc867e9e3a7d638c7a653d6._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 6" - date="2014-07-04T21:10:17Z" - content=""" -Actually, it is in getDirectoryContents itself, so not even in git-annex's code. Filed a bug w/patch: <https://ghc.haskell.org/trac/ghc/ticket/9266> - -I do not feel this is serious enough to work around in git-annex with a fixed copy of getDirectoryContents, so I'll wait for that get fixed. - -Testing with my patched getDirectoryContents, git-annex still uses up a lot of memory in this situation. It no longer blows the stack, but getDirectoryContents is still using entirely more memory than it needs to. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_7_9add4ee13b7ea846e6495c28da214269._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_7_9add4ee13b7ea846e6495c28da214269._comment deleted file mode 100644 index a6f837dff..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_7_9add4ee13b7ea846e6495c28da214269._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.55" - subject="comment 7" - date="2014-07-04T22:09:38Z" - content=""" -I wrote my own getDirectoryContents' with different exception semantics and entirely fixed this now. git-annex's memory use remains stable at around 1.5 mb during the entire staging of the millions of files. git itself uses a few hundred mb ;) -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_8_7264b57f309d6e824c612eed8a088327._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_8_7264b57f309d6e824c612eed8a088327._comment deleted file mode 100644 index c4d772104..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_8_7264b57f309d6e824c612eed8a088327._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis" - nickname="Mike" - subject="comment 8" - date="2014-07-30T20:33:44Z" - content=""" -Great work Joeyh :-) I will install the new version soon. I is fantastic that you fixed this so thoroughly. -"""]] diff --git a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_9_27a31463bcf28b5c684bb483b46a3baf._comment b/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_9_27a31463bcf28b5c684bb483b46a3baf._comment deleted file mode 100644 index fe421a450..000000000 --- a/doc/bugs/runs_of_of_memory_adding_2_million_files/comment_9_27a31463bcf28b5c684bb483b46a3baf._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmyYyXrtGKiR3Pu2OjdVsETXf4ePmECW54" - nickname="Andrey" - subject="comment 9" - date="2014-09-29T10:48:36Z" - content=""" -Joeyh, in what version it was fixed? I really need it for Ubuntu 14.04 -"""]] diff --git a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking.mdwn b/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking.mdwn deleted file mode 100644 index 1241a0096..000000000 --- a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking.mdwn +++ /dev/null @@ -1,90 +0,0 @@ -I'm trying to upload large files into s3 remote. I'm using a very recent version of git-annex: - - git-annex version: 5.20150616-g4d7683b - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA TorrentParser - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL - remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external - -Here's how my chunking is set up: - - xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx bucket=mybucket chunk=256MiB cipher=xxxxxx cipherkeys=xxxxxx datacenter=US - host=s3.amazonaws.com name=mybucket port=80 s3creds=xxxxxx storageclass=STANDARD type=S3 timestamp=xxxxxx - -If I run an upload and `^C` it in the middle of the upload, then start it again, it will always resume from the beginning. - -I've proven this to myself by using the `--debug` switch, please see blow. I've renamed certain things for security reasons, however GPGHMACSHA1--1111111111 always refers to the same chunk and GPGHMACSHA1--2222222222 always refers to the same chunk, etc. - -You can see that even after it uploads the same chunk once, it tries again. - -This is consistent with the behavior of letting it sit there for an hour and upload half of the large file, and then interrupting it, and having it start from scratch again. - - $ git annex copy --debug * --to mybucket - - [2015-06-23 15:24:07 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","show-ref","git-annex"] - [2015-06-23 15:24:07 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] - [2015-06-23 15:24:07 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","log","refs/heads/git-annex..xxx","-n1","--pretty=%H"] - [2015-06-23 15:24:07 PDT] chat: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","cat-file","--batch"] - [2015-06-23 15:24:07 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","ls-files","--cached","-z","--","aaa.tgz","xxx.tgz","xxx.tgz","xxx.tgz","xxx.tgz","xxx.tgz"] - copy aaa.tgz [2015-06-23 15:24:07 PDT] chat: gpg ["--quiet","--trust-model","always","--decrypt"] - (checking mybucket...) [2015-06-23 15:24:07 PDT] String to sign: "HEAD\n\n\nTue, 23 Jun 2015 22:24:07 GMT\n/mybucket/GPGHMACSHA1--1111111111" - [2015-06-23 15:24:07 PDT] Host: "mybucket.s3.amazonaws.com" - [2015-06-23 15:24:07 PDT] Path: "/GPGHMACSHA1--1111111111" - [2015-06-23 15:24:07 PDT] Query string: "" - [2015-06-23 15:24:07 PDT] Response status: Status {statusCode = 404, statusMessage = "Not Found"} - [2015-06-23 15:24:07 PDT] Response header 'x-amz-request-id': 'xxx' - [2015-06-23 15:24:07 PDT] Response header 'x-amz-id-2': 'xxx' - [2015-06-23 15:24:07 PDT] Response header 'Content-Type': 'application/xml' - [2015-06-23 15:24:07 PDT] Response header 'Transfer-Encoding': 'chunked' - [2015-06-23 15:24:07 PDT] Response header 'Date': 'Tue, 23 Jun 2015 22:24:03 GMT' - [2015-06-23 15:24:07 PDT] Response header 'Server': 'AmazonS3' - [2015-06-23 15:24:07 PDT] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> - (to mybucket...) - 0% 0.0 B/s 0s[2015-06-23 15:24:07 PDT] chat: gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","18","--symmetric","--force-mdc","--no-textmode"] - [2015-06-23 15:24:19 PDT] String to sign: "PUT\n\n\nTue, 23 Jun 2015 22:24:19 GMT\nx-amz-storage-class:STANDARD\n/mybucket/GPGHMACSHA1--2222222222" - [2015-06-23 15:24:19 PDT] Host: "mybucket.s3.amazonaws.com" - [2015-06-23 15:24:19 PDT] Path: "/GPGHMACSHA1--2222222222" - [2015-06-23 15:24:19 PDT] Query string: "" - 3% 636.3KB/s 3h0m[2015-06-23 15:31:01 PDT] Response status: Status {statusCode = 200, statusMessage = "OK"} - [2015-06-23 15:31:01 PDT] Response header 'x-amz-id-2': 'xxx' - [2015-06-23 15:31:01 PDT] Response header 'x-amz-request-id': 'xxx' - [2015-06-23 15:31:01 PDT] Response header 'Date': 'Tue, 23 Jun 2015 22:24:17 GMT' - [2015-06-23 15:31:01 PDT] Response header 'ETag': '"xxx"' - [2015-06-23 15:31:01 PDT] Response header 'Content-Length': '0' - [2015-06-23 15:31:01 PDT] Response header 'Server': 'AmazonS3' - [2015-06-23 15:31:01 PDT] Response metadata: S3: request ID=xxx, x-amz-id-2=xxx - 3% 633.2KB/s 3h1m[2015-06-23 15:31:01 PDT] chat: gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","18","--symmetric","--force-mdc","--no-textmode"] - [2015-06-23 15:31:13 PDT] String to sign: "PUT\n\n\nTue, 23 Jun 2015 22:31:13 GMT\nx-amz-storage-class:STANDARD\n/mybucket/GPGHMACSHA1--3333333333" - [2015-06-23 15:31:13 PDT] Host: "mybucket.s3.amazonaws.com" - [2015-06-23 15:31:13 PDT] Path: "/GPGHMACSHA1--3333333333" - [2015-06-23 15:31:13 PDT] Query string: "" - 3% 617.2KB/s 3h6m^C - - $ git annex copy --debug * --to mybucket - - [2015-06-23 15:31:25 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","show-ref","git-annex"] - [2015-06-23 15:31:25 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"] - [2015-06-23 15:31:25 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","log","refs/heads/git-annex..xxx","-n1","--pretty=%H"] - [2015-06-23 15:31:25 PDT] chat: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","cat-file","--batch"] - [2015-06-23 15:31:25 PDT] read: git ["--git-dir=../../.git","--work-tree=../..","--literal-pathspecs","ls-files","--cached","-z","--","aaa.tgz","xxx.tgz","xxx.tgz","xxx.tgz","xxx.tgz","xxx.tgz"] - copy aaa.tgz [2015-06-23 15:31:25 PDT] chat: gpg ["--quiet","--trust-model","always","--decrypt"] - (checking mybucket...) [2015-06-23 15:31:25 PDT] String to sign: "HEAD\n\n\nTue, 23 Jun 2015 22:31:25 GMT\n/mybucket/GPGHMACSHA1--1111111111" - [2015-06-23 15:31:25 PDT] Host: "mybucket.s3.amazonaws.com" - [2015-06-23 15:31:25 PDT] Path: "/GPGHMACSHA1--1111111111" - [2015-06-23 15:31:25 PDT] Query string: "" - [2015-06-23 15:31:25 PDT] Response status: Status {statusCode = 404, statusMessage = "Not Found"} - [2015-06-23 15:31:25 PDT] Response header 'x-amz-request-id': 'xxx' - [2015-06-23 15:31:25 PDT] Response header 'x-amz-id-2': 'xxx' - [2015-06-23 15:31:25 PDT] Response header 'Content-Type': 'application/xml' - [2015-06-23 15:31:25 PDT] Response header 'Transfer-Encoding': 'chunked' - [2015-06-23 15:31:25 PDT] Response header 'Date': 'Tue, 23 Jun 2015 22:31:21 GMT' - [2015-06-23 15:31:25 PDT] Response header 'Server': 'AmazonS3' - [2015-06-23 15:31:25 PDT] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> - (to mybucket...) - 0% 0.0 B/s 0s[2015-06-23 15:31:25 PDT] chat: gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","18","--symmetric","--force-mdc","--no-textmode"] - [2015-06-23 15:31:37 PDT] String to sign: "PUT\n\n\nTue, 23 Jun 2015 22:31:37 GMT\nx-amz-storage-class:STANDARD\n/mybucket/GPGHMACSHA1--2222222222" - [2015-06-23 15:31:37 PDT] Host: "mybucket.s3.amazonaws.com" - [2015-06-23 15:31:37 PDT] Path: "/GPGHMACSHA1--2222222222" - [2015-06-23 15:31:37 PDT] Query string: "" - 0% 350.1KB/s 5h40m^C - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_1_f6b1991e259bf4b3d2c85a08f465aa4a._comment b/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_1_f6b1991e259bf4b3d2c85a08f465aa4a._comment deleted file mode 100644 index 79f0fe873..000000000 --- a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_1_f6b1991e259bf4b3d2c85a08f465aa4a._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="comment 1" - date="2015-06-24T00:31:43Z" - content=""" -did a single chunk get transfered correctly? i believe git-annex can only resume at the chunk granularity... that is what it is for, no? --[[anarcat]] -"""]] diff --git a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment b/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment deleted file mode 100644 index df12abc03..000000000 --- a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_2_db57d14b983a957c454968477d9de634._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="digiuser" - subject="yes" - date="2015-06-24T00:49:22Z" - content=""" -Yes, a single chunk did get transferred correctly. - -Actually, many times I've run this experiment, many chunks did get transferred correctly. I've even verified that they are in S3, but git-annex is trying to re-upload them. - -(I haven't checked their contents in S3 but the filenames are there and the sizes are there) -"""]] diff --git a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_3_85989f505931ec695d7f3de74db0f5a1._comment b/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_3_85989f505931ec695d7f3de74db0f5a1._comment deleted file mode 100644 index aac24a023..000000000 --- a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_3_85989f505931ec695d7f3de74db0f5a1._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="digiuser" - subject="any updates?" - date="2015-06-29T03:05:53Z" - content=""" -Sorry to post again here but I was wondering if this message got lost. Anyone have a solution here? Thanks! -"""]] diff --git a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_4_bd631d470ee0365a11483c9a2e563b32._comment b/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_4_bd631d470ee0365a11483c9a2e563b32._comment deleted file mode 100644 index ecac7917c..000000000 --- a/doc/bugs/s3_special_remote_does_not_resume_uploads_even_with_new_chunking/comment_4_bd631d470ee0365a11483c9a2e563b32._comment +++ /dev/null @@ -1,30 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-07-16T17:57:44Z" - content=""" -This should have been filed as a bug report... I will move the thread to -bugs after posting this comment. - -In your obfuscated log, it tries to HEAD GPGHMACSHA1--1111111111 -and when that fails, it PUTs GPGHMACSHA1--2222222222. From this, we can -deduce that GPGHMACSHA1--1111111111 is not the first chunk, but is the full -non-chunked file, and GPGHMACSHA1--2222222222 is actually the first chunk. - -For testing, I modifed the S3 remote to make file uploads succeed, but then -report to git-annex that they failed. So, git annex copy uploads the 1st -chunk and then fails, same as it was interrupted there. Repeating the copy, -I see the same thing; it HEADs the full key, does not HEAD the first chunk, -and so doesn't notice it was uploaded before, and so re-uploads the first -chunk. - -The HEAD of the full key is just done for backwards compatability reasons. -The problem is that it's not checking if the current chunk it's gonna -upload is present in the remote. But, there is code in seekResume that -is supposed to do that very check: `tryNonAsync (checker k)` - -Aha, the problem seems to be in the checkpresent action that's passed to -that. Looks like it's passing in a dummy checkpresent action. - -I've fixed this in git, and now it resumes properly in my test case. -"""]] diff --git a/doc/bugs/set_metadata_on_wrong_files.mdwn b/doc/bugs/set_metadata_on_wrong_files.mdwn deleted file mode 100644 index e31714784..000000000 --- a/doc/bugs/set_metadata_on_wrong_files.mdwn +++ /dev/null @@ -1,90 +0,0 @@ -### Please describe the problem. - -For an example I wanted to add different metadata to some test files, -but the outcome is that the last metadata gets applied to all three files. see transcript below. - - - -### What steps will reproduce the problem? - -1. Create a git annex repository -2. add a few files -3. add some metadata to the files, same keys, differnt values -4. watch the metadata, only the last added one is shown for all files - - -### What version of git-annex are you using? On what operating system? - $cat /etc/debian_version; uname -a; git annex version - 7.4 - Linux jupiter 3.13.0ct #33 SMP PREEMPT Tue Jan 21 05:04:01 CET 2014 x86_64 GNU/Linux - git-annex version: 5.20140306~bpo70+1 - build flags: Assistant Webapp Pairing S3 Inotify DBus XMPP Feeds Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt S3 bup directory rsync web tahoe glacier hook external - local repository version: 5 - supported repository version: 5 - upgrade supported from repository versions: 0 1 2 4 - - -### Please provide any additional information below. - -Debian/Wheezy with git annex from backports. The test was done in /tmp which is a tmpfs. - - -[[!format sh """ -$export LC_ALL=C -$mkdir /tmp/annextest -$cd /tmp/annextest -$git init -Initialized empty Git repository in /tmp/annextest/.git/ -$git annex init -init ok -(Recording state in git...) - -$touch a.txt b.txt c.txt -$git annex add a.txt b.txt c.txt -add a.txt ok -add b.txt ok -add c.txt ok -(Recording state in git...) -$git commit -m init -[master (root-commit) 5470bdb] init - 3 files changed, 3 insertions(+) - create mode 120000 a.txt - create mode 120000 b.txt - create mode 120000 c.txt - -$git annex metadata a.txt -s foo=bar -s num=1 -metadata a.txt - foo=bar - num=1 -ok -(Recording state in git...) -$git annex metadata b.txt -s foo=baz -s num=2 -metadata b.txt - foo=baz - num=2 -ok -(Recording state in git...) -$git annex metadata c.txt -s foo=barf -s num=3 -metadata c.txt - foo=barf - num=3 -ok -(Recording state in git...) -$git annex metadata -metadata a.txt - foo=barf - num=3 -ok -metadata b.txt - foo=barf - num=3 -ok -metadata c.txt - foo=barf - num=3 -ok -"""]] - -> [[fixed|done]]; documentation improved --[[Joey]] diff --git a/doc/bugs/set_metadata_on_wrong_files/comment_1_074f124e5d313e90b3e9217325799587._comment b/doc/bugs/set_metadata_on_wrong_files/comment_1_074f124e5d313e90b3e9217325799587._comment deleted file mode 100644 index f7a47d2fe..000000000 --- a/doc/bugs/set_metadata_on_wrong_files/comment_1_074f124e5d313e90b3e9217325799587._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.41" - subject="comment 1" - date="2014-03-26T20:55:07Z" - content=""" -This is because metadata applies to the contents of files, and all 3 of your files have the same single content. I will update the documentation to make it more clear metadata works this way. -"""]] diff --git a/doc/bugs/sharedRepository__61__world_not_working.mdwn b/doc/bugs/sharedRepository__61__world_not_working.mdwn deleted file mode 100644 index 16d54ef9a..000000000 --- a/doc/bugs/sharedRepository__61__world_not_working.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -### Please describe the problem. -As per [this note](https://git-annex.branchable.com/todo/sharedRepository_mode_not_supported_by_git-annex/), `sharedRepository=world` should be supported. However, it does not seem to work with git-annex 5.20150508. When copying files to the public remote, annexed objects’ permission are subject to the remote user’s umask. If it is 077, they will not be world-readable. - - -### What steps will reproduce the problem? - -[[!format sh """ -# Remotely -git init --shared=world public -cd public -git config receive.denyCurrentBranch updateInstead -git annex init -"""]] - -[[!format sh """ -# Locally -git init local -cd local -git annex init -git remote add public $URL:public -echo abc > file -git annex add file -git commit -m init -git annex copy --to public file -git annex sync -# If remote user has umask 077, remote object winds up readable only by him -"""]] - - -### What version of git-annex are you using? On what operating system? -git-annex 5.20150508 -Linux 4.0.4 - -> The problem turned out to be sharedRepository=2 which is not documented, -> so git-annex didn't support it, and left the incoming file permissions -> as-is. I've added support for this magic value, so it will work the same -> as "world" now. [[done]] --[[Joey]] diff --git a/doc/bugs/sharedRepository__61__world_not_working/comment_1_70b0cf42e00d50991fd4764da58adc38._comment b/doc/bugs/sharedRepository__61__world_not_working/comment_1_70b0cf42e00d50991fd4764da58adc38._comment deleted file mode 100644 index 467569057..000000000 --- a/doc/bugs/sharedRepository__61__world_not_working/comment_1_70b0cf42e00d50991fd4764da58adc38._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 1" - date="2015-06-02T12:13:19Z" - content=""" -i often had to do a `chmod` in order to kick things into submission at first. did you try all that is mentionned in [[tips/shared_git_annex_directory_between_multiple_users/]]? -"""]] diff --git a/doc/bugs/sharedRepository__61__world_not_working/comment_2_9bd8e648cc3aa836747e4bfb87d6368e._comment b/doc/bugs/sharedRepository__61__world_not_working/comment_2_9bd8e648cc3aa836747e4bfb87d6368e._comment deleted file mode 100644 index 0c8a80856..000000000 --- a/doc/bugs/sharedRepository__61__world_not_working/comment_2_9bd8e648cc3aa836747e4bfb87d6368e._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-07-06T19:12:02Z" - content=""" -I reproduced this. Note that the .git/annex/objects/xx/yy/key directories -on the remote do end up with the correct perms allowing all to read them, -it's only the actual object file that has the wrong mode. -"""]] diff --git a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file.mdwn b/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file.mdwn deleted file mode 100644 index 16fa60718..000000000 --- a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -I am trying to S3 as a file store for git annex. I have set up the remote via the following command: - - git annex initremote xxx-s3 type=S3 encryption=shared embedcreds=yes datacenter=EU bucket=xxx-git-annex fileprefix=test/ - -The remote gets set up correctly and creates the directory I want, and adds a annex-uuid file. - -Now when I try to copy a file to the xxx-s3 remote, I get the following error: - - $ git annex add ssl-success-and-failure-with-tl-logs.log - add ssl-success-and-failure-with-tl-logs.log ok - (Recording state in git...) - $ git annex copy ssl-success-and-failure-with-tl-logs.log --to xxx-s3 - copy ssl-success-and-failure-with-tl-logs.log (gpg) gpg: no valid OpenPGP data found. - gpg: decrypt_message failed: eof - - git-annex: user error (gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--passphrase-fd","10","--decrypt"] exited 2) - failed - git-annex: copy: 1 failed - -Any ideas what might be wrong? Is shared cipher broken somehow? - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_1_b42ff37be172ba841980c17ad6223e06._comment b/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_1_b42ff37be172ba841980c17ad6223e06._comment deleted file mode 100644 index 1268d8cd0..000000000 --- a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_1_b42ff37be172ba841980c17ad6223e06._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmAINLSovhWM_4_KrbngOcxduIbBuKv8ZA" - nickname="Nuutti" - subject="comment 1" - date="2014-08-01T09:28:21Z" - content=""" -Sorry, this should probably be in bugs. -"""]] diff --git a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_2_c0325903cdb8d24c72fd4e67e18fbdc8._comment b/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_2_c0325903cdb8d24c72fd4e67e18fbdc8._comment deleted file mode 100644 index 57d5ee0cf..000000000 --- a/doc/bugs/shared_cipher_for_S3_attempting_to_decrypt_a_non-encrypted_file/comment_2_c0325903cdb8d24c72fd4e67e18fbdc8._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 2" - date="2014-08-12T19:37:56Z" - content=""" -This is not gpg trying to decrypt some file from the S3 remote. It is trying to decrypt the creds that embedcreds=yes caused to be stored in the git repo. - -I was able to reproduce this using your command line, with the S3 env vars set while running initremote, and then unset for the copy, which causes git-annex to try to get the creds from the git repo, and decrypt them. - -However, since encryption=shared, the encryption key is stored in the git repo, so there is no point at all in encrypting the creds, also stored in the git repo with that key. So `initremote` doesn't. The creds are simply stored base-64 encoded. - -I have fixed this. I will now move this thread to bugs so I can close it. -"""]] diff --git a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink.mdwn b/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink.mdwn deleted file mode 100644 index 3f8c7fc48..000000000 --- a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. - -ATM git annex assistant app is the largest one installed on my phone. I simply keep hitting the available storage space limits and keep pruning some apps - -According to file -$> file lib/armeabi/lib.git-annex.so -lib/armeabi/lib.git-annex.so: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), not stripped -so largest annex's .so is 133M and is not stripped. stripping it seems to half its size: - -$> ls -l lib.git-annex.so -62052 -rw------- 1 yoh yoh 63468304 Nov 25 22:21 lib.git-annex.so -$> file lib.git-annex.so -lib.git-annex.so: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped - -so may be it could be the first step to make the .apk and installation itself more lightweight and thus easier to "manage" - -thanks in advance - -### What steps will reproduce the problem? - -install provided .apk on Android - -### What version of git-annex are you using? On what operating system? - -Android, just fetched the most recent "release" apk from the -http://downloads.kitenet.net/git-annex/android/current/4.0/git-annex.apk -Last-Modified: Mon, 18 Nov 2013 11:57:25 GMT - -### 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. -"""]] - -> Seems that I lost stripping of the git-annex binary when adding the build -> for the newer android versions. [[fixed|done]] (There is not otherwise -> much way to shrink the size.) --[[Joey]] diff --git a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_1_d2faaff98386433110dcf7aae87916b7._comment b/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_1_d2faaff98386433110dcf7aae87916b7._comment deleted file mode 100644 index 894c48784..000000000 --- a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_1_d2faaff98386433110dcf7aae87916b7._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="http://yarikoptic.myopenid.com/" - nickname="site-myopenid" - subject="sure there is no other ways to shrink?" - date="2013-11-27T04:26:35Z" - content=""" -Might be quite a stretch but it is hard to grasp that all 60MB are really needed... although with haskell -- it might indeed be the case, but I thought that may be there could be some symbols pulled in which aren't used, and for which when in gcc/ld world there are ways to get rid of them, e.g. -dead_strip (just excercising ideas) - -"""]] diff --git a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_2_1359ddf1b5db4303f8bd219d3f07df3a._comment b/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_2_1359ddf1b5db4303f8bd219d3f07df3a._comment deleted file mode 100644 index 5f7688d1f..000000000 --- a/doc/bugs/size_of_the_Android_installation_is_HUGE_--_please_seek_possibility_to_shrink/comment_2_1359ddf1b5db4303f8bd219d3f07df3a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 2" - date="2013-11-27T04:55:51Z" - content=""" -The git-annex binary is around 45 mb on Linux. The android binary statically links a few additional C libraries, so is slightly larger. - -The only way I know of to potentially shrink it is to fix certian ghc / ld interactions that, in my limited understanding, cause functions that are never used to be linked into the binary if another function in the same file (or module) is used. That might half its size or something. -"""]] diff --git a/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo.mdwn b/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo.mdwn deleted file mode 100644 index 3aa3188af..000000000 --- a/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. - -When I try to add remote ssh server repository it fails with an error: - -Internal Server Error -ssh-keygen failed" - - -### What steps will reproduce the problem? -1. Select "Add another repository", then choose "Remote server", enter credentials. -2. On the page "Ready to add remote server" click any choice ("Use a git repository on the server" or "Use an encrypted rsync repository on the server") -3. Error is raised - -### What version of git-annex are you using? On what operating system? -git-annex version 4.20130922-g7dc188a - -Fedora 18 x86_64 - -### 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 - -[2013-10-03 19:27:27 NOVT] main: starting assistant version 4.20130922-g7dc188a -(scanning...) [2013-10-03 19:27:27 NOVT] Watcher: Performing startup scan -(started...) -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp -[2013-10-03 19:55:23 NOVT] call: ssh-keygen ["-P","","-f","/tmp/git-annex-keygen.0/key"] -ssh-keygen: symbol lookup error: /lib64/libldap-2.4.so.2: undefined symbol: ber_sockbuf_io_udp - - -# End of transcript or log. -"""]] - -> Added ssh-keygen to bundle. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo/comment_1_52180983b59c247389a55a9523ec435b._comment b/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo/comment_1_52180983b59c247389a55a9523ec435b._comment deleted file mode 100644 index f0f50151a..000000000 --- a/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo/comment_1_52180983b59c247389a55a9523ec435b._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2013-11-08T18:28:37Z" - content=""" -Apologies for not following up on this bug sooner.. - -It seems to me that your system has a broken ssh-keygen program. You didn't say how you installed git-annex, but based on the git rev in the version number, I'm guessing you either built it yourself, or you're using the standalone tarball I build. - -In the case of the latter, it didn't include ssh-keygen, so would try to use the one that comes with fedora. It seems likely that the problem comes from the libraries included in the bundle being used with a binary not in the bundle, that in turn is also using additional libraries. - -So, I think I should add ssh-keygen to the standalone bundle! -"""]] diff --git a/doc/bugs/ssh-options_seems_to_be_ignored.mdwn b/doc/bugs/ssh-options_seems_to_be_ignored.mdwn deleted file mode 100644 index 89800891f..000000000 --- a/doc/bugs/ssh-options_seems_to_be_ignored.mdwn +++ /dev/null @@ -1,48 +0,0 @@ -### Please describe the problem. -The docs say I can set ssh options via `annex.ssh-options` or `remote.NAME.annex-ssh-options`. I tried, and the setting appears to be completely ignored. - -Apologies in advance if I've made a stupid typo. - -### What steps will reproduce the problem? - -I tried all of these: - - git config --local --replace-all annex.ssh-options "-i ~/.ssh/id_git_rsa" - git config --local --replace-all remote.Watt.annex-ssh-options "-i ~/.ssh/id_git_rsa" - -`git config -l | grep Watt` confirms it took: - - remote.Watt.url=ssh://watt.home/home/anthony/Music/ - remote.Watt.fetch=+refs/heads/*:refs/remotes/Watt/* - remote.Watt.annex-uuid=e74b57e5-e78c-4f3d-bde6-4803a0c33837 - remote.Watt.annex-ssh-options=-i ~/.ssh/id_git_rsa - -Then I ran `git annex sync Watt`, and was prompted for a password: - - anthony@Forest:~/Music$ git annex sync Watt - commit ok - pull Watt - Password: - -Running `ps ww $(pidof ssh)` shows that the `-i` option is missing: - - PID TTY STAT TIME COMMAND - 22188 pts/4 S+ 0:00 ssh -S .git/annex/ssh/watt.home -o ControlMaster=auto -o ControlPersist=yes watt.home git-upload-pack '/home/anthony/Music/' - - -### What version of git-annex are you using? On what operating system? - -Debian testing 5.20141125 - -### 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. -"""]] - -> [[fixed|done]], ssh-options is now propigated everywhere that ssh -> connection caching goes --[[Joey]] diff --git a/doc/bugs/ssh-options_seems_to_be_ignored/comment_1_bd9062bd492a36f54883fa3635b1c35f._comment b/doc/bugs/ssh-options_seems_to_be_ignored/comment_1_bd9062bd492a36f54883fa3635b1c35f._comment deleted file mode 100644 index c46c10dc7..000000000 --- a/doc/bugs/ssh-options_seems_to_be_ignored/comment_1_bd9062bd492a36f54883fa3635b1c35f._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 1" - date="2014-12-19T20:41:58Z" - content=""" -The ssh-options are used when git-annex is running git-annex-shell on the remote (eg, when transferring data). However, `git annex sync` does a `git pull` and `git push`, and so it doesn't pass on the ssh-options there. -"""]] diff --git a/doc/bugs/ssh-options_seems_to_be_ignored/comment_2_77af42bd6017d9fa9d356014e62d8bcc._comment b/doc/bugs/ssh-options_seems_to_be_ignored/comment_2_77af42bd6017d9fa9d356014e62d8bcc._comment deleted file mode 100644 index 7d4489c05..000000000 --- a/doc/bugs/ssh-options_seems_to_be_ignored/comment_2_77af42bd6017d9fa9d356014e62d8bcc._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd" - nickname="Anthony DeRobertis" - subject="comment 2" - date="2014-12-19T21:14:30Z" - content=""" -It does manage to pass the ControlMaster, etc. options there, so could the ssh-options be added? Or if backwards-compatibility is a worry, another option be added for that? I guess it's possible someone would want different SSH options for bulk data transfer. - -It would be nice to be able to pass that `-i` option. -"""]] diff --git a/doc/bugs/ssh_fails_in_windows_nightly_build.mdwn b/doc/bugs/ssh_fails_in_windows_nightly_build.mdwn deleted file mode 100644 index a40e3ea71..000000000 --- a/doc/bugs/ssh_fails_in_windows_nightly_build.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -### Please describe the problem. - -After installing a nightly build from https://qa.nest-initiative.org/view/msysGit/job/msysgit-git-annex-assistant-test/, ssh fails to run when launched by the webapp. It shows a system error dialog with the message "The program can't start because msys-crypto-1.0.0.dll is missing...". The dll is present in $PROGRAMFILES/Git/bin, and ssh works when run from the command line. - -[[!format sh """ -Version: 5.20150508-g8e96a31 -Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA TorrentParser -"""]] - -> sigh.. [[fixed|done]] now.. --[[Joey]] diff --git a/doc/bugs/ssh_over_IPv6.mdwn b/doc/bugs/ssh_over_IPv6.mdwn deleted file mode 100644 index b5e9f0358..000000000 --- a/doc/bugs/ssh_over_IPv6.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -### Please describe the problem. -When i try to sync to my server (path in .git/config is "[fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e]:/home/thomas/git/musik") the url gets messed up by annex and i get the error "git-annex: bad url ssh://[fcb8/~/b10:1cb8:c94:58d0:2522:89f9:c89e]:/home/thomas/git/musik". - -### What steps will reproduce the problem? -1. init git & annex -2. add files -3. add a IPv6 address remote -4. push git branches -5. git annex sync - -### What version of git-annex are you using? On what operating system? -``` -git-annex version: 5.20140412ubuntu1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -``` - -> [[Fixed|done]] by adding support for ipv6 addresses when git-annex -> converts a git remote loction into an url. BTW, the -> simple workaround is to give it a valid url from the beginning -> `ssh://[fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e]/home/thomas/git/musik"` -> -> As to any problems using an ipv6 remote once it's set up, I've used them -> with no problems. -> --[[Joey]] diff --git a/doc/bugs/ssh_over_IPv6/comment_1_0287f73c44645a1f854ecfe4ddddb258._comment b/doc/bugs/ssh_over_IPv6/comment_1_0287f73c44645a1f854ecfe4ddddb258._comment deleted file mode 100644 index 13c9794e4..000000000 --- a/doc/bugs/ssh_over_IPv6/comment_1_0287f73c44645a1f854ecfe4ddddb258._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo" - nickname="Justin" - subject="comment 1" - date="2014-08-28T20:46:29Z" - content=""" - -Try using ~/.ssh/config as a workaround - - Host myserver - Hostname fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e - -then just tell git-annex to use myserver - -"""]] diff --git a/doc/bugs/ssh_over_IPv6/comment_2_cfa63d226ae411551a728af5ab043491._comment b/doc/bugs/ssh_over_IPv6/comment_2_cfa63d226ae411551a728af5ab043491._comment deleted file mode 100644 index 032e100ad..000000000 --- a/doc/bugs/ssh_over_IPv6/comment_2_cfa63d226ae411551a728af5ab043491._comment +++ /dev/null @@ -1,29 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlog_5wIICaMcrKTexlFNA6IO6UTp323aE" - nickname="Torkaly" - subject="comment 2" - date="2014-09-01T11:01:30Z" - content=""" -thank you. I workaround this by using the DNS hostname instead the IPv6 address directly. But this is not a nice solution, like any workaround. But now i have problems with `git annex get` over IPv6-only: - -``` -get ***.mp3 (not available) - Try making some of these repositories available: - 5636aefa-c509-4ea0-bebe-f5b96d8eb15a -- hserver -failed -<snip> -``` - -but i can ping it: -``` -thomas@alus:~/Musik$ ping6 hserver.h.b128.net -PING hserver.h.b128.net(fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e) 56 data bytes -64 bytes from fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e: icmp_seq=1 ttl=42 time=453 ms -64 bytes from fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e: icmp_seq=2 ttl=42 time=441 ms -64 bytes from fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e: icmp_seq=3 ttl=42 time=425 ms -64 bytes from fcb8:b10:1cb8:c94:58d0:2522:89f9:c89e: icmp_seq=5 ttl=42 time=413 ms -``` -(the high pings are caused by a download from an other source. Also i have no problems with rsync over IPv6) - -PS: the markdown for code blocks is not working too :) -"""]] diff --git a/doc/bugs/ssh_portnum_bugs.mdwn b/doc/bugs/ssh_portnum_bugs.mdwn deleted file mode 100644 index 0d7199d8e..000000000 --- a/doc/bugs/ssh_portnum_bugs.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -### Please describe the problem. - -Lots of issues setting up assistant using SSH running on non-standard ports. Tested local pairing (which did seem to show other computer, but then wouldn't sync) and Remote Server. - -### What steps will reproduce the problem? - -Change Port 22 in /etc/ssh/sshd_config to Port 9999, restart ssh on both computers. With a clean local .ssh/config and directory, try to set up local pairing or remote server. It appears to work, especially if XMPP is working properly with remote server, but then some operations fail. (Iirc, metadata does sync but not data.) Ultimately, I had to go back to using Port 22 and using denyhosts/fail2ban (which occasionally erroneously ban my IP). - -(Although it's probably not relevant to the bug report, it could be argued that this is security through obscurity. There is some truth in this, but scanning an entire machine is 65,535 times slower than scanning just port 22, so it introduces a real cost to bulk scanning. I almost never, ever have attacks on random ports, whereas I have dozens per day on each server on port 22, and often thousands of attacks.) - -### What version of git-annex are you using? On what operating system? - -When I was experiencing this issue, I was running the default on Jessie/Wheezy. Now I'm running the latest (via auto-update and distributed binary) but don't know if this is still an issue with latest versions (I switched to 22 as a workaround). - -[[!tag moreinfo]] - -> Closing as it seems likely this is an old bug fixed after wheezy. -> [[done]] --[[Joey]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_1_2026785c06e99b55158cd65c221eb598._comment b/doc/bugs/ssh_portnum_bugs/comment_1_2026785c06e99b55158cd65c221eb598._comment deleted file mode 100644 index 35792e2ce..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_1_2026785c06e99b55158cd65c221eb598._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 1" - date="2014-06-05T16:37:27Z" - content=""" -I'm going to assume that the \"jessie/wheezy\" is a typo, since those are two completely different versions. It sounds to me like you were using the git-annex 3.x distributed with debian stable. - -I cannot reproduce ssh port issues with the current release, and there have been ssh port fixes in the over 2 years since the version in Debian stable. -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_2_76551dfcd29b54814809c434d7cb64af._comment b/doc/bugs/ssh_portnum_bugs/comment_2_76551dfcd29b54814809c434d7cb64af._comment deleted file mode 100644 index 0a88c37bb..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_2_76551dfcd29b54814809c434d7cb64af._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="jamieson" - ip="71.11.173.17" - subject="comment 2" - date="2014-06-05T16:50:20Z" - content=""" -Jessie on one machine, Wheezy on the other; exactly, that is the version I was using. Git Annex is awesome. Thanks!! -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_3_ab49a0e307a29c7c20627bbb3b10ab1d._comment b/doc/bugs/ssh_portnum_bugs/comment_3_ab49a0e307a29c7c20627bbb3b10ab1d._comment deleted file mode 100644 index 99dad8dcd..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_3_ab49a0e307a29c7c20627bbb3b10ab1d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 3" - date="2014-06-05T16:50:30Z" - content=""" -I did notice a problem where the same ssh config stanza was used if the webapp set up a repository on a host first using one port, and later using a different port. I've fixed that. -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_4_e0d96a43208453dc29373d0e045751e3._comment b/doc/bugs/ssh_portnum_bugs/comment_4_e0d96a43208453dc29373d0e045751e3._comment deleted file mode 100644 index dd20bf76d..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_4_e0d96a43208453dc29373d0e045751e3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 4" - date="2014-06-05T16:51:42Z" - content=""" -Did the failure occur on the machine running jessie, or on the machine running wheezy? -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_5_9ed44cdb79224dac6b000983d77d53f3._comment b/doc/bugs/ssh_portnum_bugs/comment_5_9ed44cdb79224dac6b000983d77d53f3._comment deleted file mode 100644 index 9f57c64df..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_5_9ed44cdb79224dac6b000983d77d53f3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="jamieson" - ip="71.11.173.17" - subject="comment 5" - date="2014-06-05T16:56:33Z" - content=""" -I'm not sure. I'll do some more testing! -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_6_5360e3c8db03402d2b7d81c0bbe8b35e._comment b/doc/bugs/ssh_portnum_bugs/comment_6_5360e3c8db03402d2b7d81c0bbe8b35e._comment deleted file mode 100644 index cfe43137c..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_6_5360e3c8db03402d2b7d81c0bbe8b35e._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-05-01T18:21:09Z" - content=""" -Any chance of a followup? -"""]] diff --git a/doc/bugs/ssh_portnum_bugs/comment_7_4157337c26a4267323da78dc7609a834._comment b/doc/bugs/ssh_portnum_bugs/comment_7_4157337c26a4267323da78dc7609a834._comment deleted file mode 100644 index 2657443a4..000000000 --- a/doc/bugs/ssh_portnum_bugs/comment_7_4157337c26a4267323da78dc7609a834._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="jamieson" - subject="Follow up" - date="2015-05-01T20:40:49Z" - content=""" -Sorry about that! please close and I'll follow up if I have any more issues. Thanks!! -"""]] diff --git a/doc/bugs/stderr_of_special_external_remotes_is_swallowed.mdwn b/doc/bugs/stderr_of_special_external_remotes_is_swallowed.mdwn deleted file mode 100644 index 8b9bb7563..000000000 --- a/doc/bugs/stderr_of_special_external_remotes_is_swallowed.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -### Please describe the problem. - -complicates troubleshooting of custom special remotes since annex seems to swallow all output, including stderr - -### What version of git-annex are you using? On what operating system? - -5.20150302 - -> I have debugged external special remotes using stdderr, so I -> know this is not the case. [[done]] --[[Joey]] diff --git a/doc/bugs/stderr_of_special_external_remotes_is_swallowed/comment_1_f7685f9e418b46dbe5ce0f9b79b03997._comment b/doc/bugs/stderr_of_special_external_remotes_is_swallowed/comment_1_f7685f9e418b46dbe5ce0f9b79b03997._comment deleted file mode 100644 index 4b79a886b..000000000 --- a/doc/bugs/stderr_of_special_external_remotes_is_swallowed/comment_1_f7685f9e418b46dbe5ce0f9b79b03997._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="sorry about the noise" - date="2015-03-19T04:14:23Z" - content=""" -please ignore... probably was some problem on my end, in new attempts seems to spit out those just fine -"""]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode.mdwn b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode.mdwn deleted file mode 100644 index c016ffc37..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode.mdwn +++ /dev/null @@ -1,72 +0,0 @@ -### Please describe the problem. - -in direct mode files with absent content are promised to become regular files but empty... seems to be not a case for me. page describing direct mode has comments about past problems like that but they were told to be dealt with... so I decided to file a new issue - -### What steps will reproduce the problem? - -switch to direct mode - -### What version of git-annex are you using? On what operating system? - -5.20150519-geaf72fe - -### 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 - -$> git clone ~exppsy/pymvpa2-tutorialdata /tmp/pymvpa2-tutorialdata-clone -Cloning into '/tmp/pymvpa2-tutorialdata-clone'... -done. - -$> cd /tmp/pymvpa2-tutorialdata-clone -debian/ freesurfer/ haxby2001/ hyperalignment_tutorial_data.hdf5.gz@ results/ suma_surfaces/ - -$> ls -l haxby2001/bold_mc.par hyperalignment_tutorial_data.hdf5.gz -lrwxrwxrwx 1 yoh yoh 199 May 29 15:42 haxby2001/bold_mc.par -> ../.git/annex/objects/KM/Jq/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par -lrwxrwxrwx 1 yoh yoh 208 May 29 15:42 hyperalignment_tutorial_data.hdf5.gz -> .git/annex/objects/1g/M2/SHA256E-s15769613--d4b54133f873ff043df22c6250810c1cb9a177b5eb551ca97d98d664edf8ea3f.hdf5.gz/SHA256E-s15769613--d4b54133f873ff043df22c6250810c1cb9a177b5eb551ca97d98d664edf8ea3f.hdf5.gz - -$> git annex enableremote data.pymvpa.org -(merging origin/git-annex into git-annex...) -(recording state in git...) -enableremote data.pymvpa.org ok -(recording state in git...) - -$> git annex get hyperalignment_tutorial_data.hdf5.gz -/tmp/pymvpa2-tutorialdata-clone/.git/annex/tm 100%[==================================================================================================>] 15.04M 11.2MB/s in 1.3s -ok -(recording state in git...) - -$> ls -l haxby2001/bold_mc.par hyperalignment_tutorial_data.hdf5.gz -lrwxrwxrwx 1 yoh yoh 199 May 29 15:42 haxby2001/bold_mc.par -> ../.git/annex/objects/KM/Jq/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par -lrwxrwxrwx 1 yoh yoh 208 May 29 15:42 hyperalignment_tutorial_data.hdf5.gz -> .git/annex/objects/1g/M2/SHA256E-s15769613--d4b54133f873ff043df22c6250810c1cb9a177b5eb551ca97d98d664edf8ea3f.hdf5.gz/SHA256E-s15769613--d4b54133f873ff043df22c6250810c1cb9a177b5eb551ca97d98d664edf8ea3f.hdf5.gz - -$> git annex direct -commit -On branch master -Your branch is up-to-date with 'origin/master'. -nothing to commit, working directory clean -ok -direct hyperalignment_tutorial_data.hdf5.gz ok -direct ok - -$> ls -l haxby2001/bold_mc.par hyperalignment_tutorial_data.hdf5.gz -lrwxrwxrwx 1 yoh yoh 199 May 29 15:42 haxby2001/bold_mc.par -> ../.git/annex/objects/KM/Jq/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par/SHA256E-s106236--64972f56116ba575996a0b2fbd26a033dd3e8369e87fda503fec5a45dcd06f57.par --rw------- 1 yoh yoh 15769613 May 8 03:42 hyperalignment_tutorial_data.hdf5.gz -2 12569.....................................:Fri 29 May 2015 03:43:08 PM EDT:. - -$> git annex version -git-annex version: 5.20150519-geaf72fe -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - - -# End of transcript or log. -"""]] - -> This is behaving as it's intended to. [[done]] --[[Joey]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_1_3d627ce7eb21ceb8431a4275106eca1b._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_1_3d627ce7eb21ceb8431a4275106eca1b._comment deleted file mode 100644 index 83aa2d887..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_1_3d627ce7eb21ceb8431a4275106eca1b._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 1" - date="2015-05-30T12:30:39Z" - content=""" -AFAIK absent files are supposed to be symlinks, even in direct mode. Once you “git annex get“ the files, the will be immediately unlocked. Only on VFAT file-systems (which do not support symlinks), absent files will have 0 byte placeholders. You might be able to force placeholders with the “annex.crippledfilesystem“ config option, but I’m not sure how you would enact it or whether that’s desirable. -"""]] diff --git a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_2_73c0806bd1b57138f7a87f967fb66222._comment b/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_2_73c0806bd1b57138f7a87f967fb66222._comment deleted file mode 100644 index e130959f9..000000000 --- a/doc/bugs/symlinks_to_absent_files_remain_upon_switching_to_direct_mode/comment_2_73c0806bd1b57138f7a87f967fb66222._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-07-30T16:57:52Z" - content=""" -The behavior on crippled filesystems is what git decides to do with -symlinks on such filesystems. Specifically it puts the link target inside -the file, which is not wholly empty. -"""]] diff --git a/doc/bugs/sync_content_has_really_suboptimal_behavior.mdwn b/doc/bugs/sync_content_has_really_suboptimal_behavior.mdwn deleted file mode 100644 index b12d37bbb..000000000 --- a/doc/bugs/sync_content_has_really_suboptimal_behavior.mdwn +++ /dev/null @@ -1,50 +0,0 @@ -### Please describe the problem. - -In a client, backup, smallarchive setup, new non-archive files will be copied to backup, copied to smallarchive, then dropped from smallarchive. - -### What steps will reproduce the problem? - -Create three repos, assign them groups client, backup, smallarchive. - -Add files to the client, not in the archive folder. - -Run sync --content - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20150710 - -### Please provide any additional information below. - -[[!format sh """ -copy SOMEFILE copy SOMEFILE (checking BACKUP...) (to BACKUP...) -SHA256E-s309049--00bb4f52d3d9af507eaf8c837ce29ad133cf1964c0f8fbf586906b1e5676f0af.pdf - 309,049 100% 87.83MB/s 0:00:00 (xfr#1, to-chk=0/1) -ok -copy SOMEFILE copy SOMEFILE (checking SMALLARCHIVE...) (to SMALLARCHIVE...) -ok -drop SMALLARCHIVE SOMEFILE (checking BACKUP...) ok -""" ]] - -> Indeed, but this was fixed in version 5.20150727. -> From the changelog: ->> ->> * sync --content: Fix bug that caused files to be uploaded to eg, ->> more archive remotes than wanted copies, only to later be dropped ->> to satisfy the preferred content settings. -> -> [[done]] --[[Joey]] - ->> Oh, sorry about the noise then. I assumed the version I was running was the latest since it was pretty recent. ->> Thanks. -- [[filippo]] - -Note: it's extremely and unnecessarily hard to report a bug. There are no -links leading to instructions or anything on the home page. The "bugs" link -leads to a list of pages with no instructions. Please at least add -explanation to the bugs page. I had to edit an existing bug and change the -edit URL. - -> Eh? The first thing on the bugs page is a form to add a new post to the -> list of bugs. --[[Joey]] - ->> I'm an idiot. I mistook that for a search box. -- [[filippo]] diff --git a/doc/bugs/sync_content_has_really_suboptimal_behavior/comment_1_e26a33527b0ba6f471db30be9dc89a86._comment b/doc/bugs/sync_content_has_really_suboptimal_behavior/comment_1_e26a33527b0ba6f471db30be9dc89a86._comment deleted file mode 100644 index 389c24cbf..000000000 --- a/doc/bugs/sync_content_has_really_suboptimal_behavior/comment_1_e26a33527b0ba6f471db30be9dc89a86._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="filippo" - subject="numcopies" - date="2015-08-02T17:42:18Z" - content=""" -Maybe it's relevant that I have numcopies=2, which should however be fullfilled already by the BACKUP copy. -"""]] diff --git a/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false.mdwn b/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false.mdwn deleted file mode 100644 index 9b7ec7cf5..000000000 --- a/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false.mdwn +++ /dev/null @@ -1,90 +0,0 @@ -### Please describe the problem. - -The documentation of `git annex sync` states - -> The sync process involves first committing all local changes, then fetching and merging […] -> You can use standard git commands to do each of those steps by hand, or if you -> don't want to worry about the details, you can use sync. - -The documentation of `alwasycommit` states - -> By default, git-annex automatically commits data to the git-annex branch after each -> command is run. To disable these commits, set to false. Then data will only be -> committed when running `git annex merge` (or by automatic merges) or `git annex sync`. - -In fact, however, `git annex sync` will not commit or will not commit some pieces of information when `alwasycommit` is false. This leads to various problems, the first of which is that cloned repositories do not have information about the other remotes. - -It is hard to work around this problem because `git commit` cannot be used in direct mode. - -This problem does not show up when using local, non over-the-network, remotes. - -### What steps will reproduce the problem? - -The following script (available at <https://gist.github.com/gioele/5ffeff8988a535164e5b>) will reproduce this problem. If you do not have SSH running on localhost, you can change the `h` variable to point to another host. - - #!/bin/sh -x - - set -e ; set -u - export LC_ALL=C - - h=${h:-localhost} - dr="/tmp/annex" - - chmod a+rwx -R pc1 pc2 || true - rm -Rf pc1 pc2 - - # create central git repo - ssh $h "chmod a+rwx -R ${dr}/Docs.git" || true - ssh $h "rm -Rf ${dr}/Docs.git" - ssh $h "mkdir -p ${dr}/Docs.git" - ssh $h "cd ${dr}/Docs.git ; git init --bare" - - d=$(pwd) - - # populate repo in PC1 - mkdir -p pc1/Docs - cd pc1/Docs - echo AAA > fileA - echo BBB > fileB - - git init - git config annex.alwayscommit false # change to true to solve this problem - - git remote add origin $h:$dr/Docs.git - git fetch --all - - # simulate a host without git-annex - git config remote.origin.annex-ignore true - - git annex init "pc1" - git annex info - - git annex direct - git annex sync origin - - git annex add . - git annex sync - - # re-create repo on PC2 - cd $d - mkdir -p pc2 - cd pc2 - git clone $h:$dr/Docs.git - cd Docs - - git config remote.origin.annex-ignore true - - git annex init "pc2" - git annex direct - git annex info - - # git annex info shows only pc2, shouldn't pc1 be there as well? - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140708-g8c9c55c on Ubuntu 12.04.4 - -> I have improved the documentation to not imply that sync/merge are a -> special case. They honor the autocommit settings more or less -> intentionally, and to get a commit to be made, just pass -c -> autocommit=true when running them. [[done]] --[[Joey]] diff --git a/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false/comment_1_e6dc7fa1b0a131bb7533f8407e1b5510._comment b/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false/comment_1_e6dc7fa1b0a131bb7533f8407e1b5510._comment deleted file mode 100644 index ee9957648..000000000 --- a/doc/bugs/sync_does_not_commit_with_alwasycommit___61___false/comment_1_e6dc7fa1b0a131bb7533f8407e1b5510._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="comment 1" - date="2014-07-29T14:25:19Z" - content=""" -For the records, the solution Joey suggested works but the correct option to pass to `sync` is `-c annex.alwayscommit=true`. -"""]] diff --git a/doc/bugs/test_failures_on_window_for_5.20131118.mdwn b/doc/bugs/test_failures_on_window_for_5.20131118.mdwn deleted file mode 100644 index 319eae4f1..000000000 --- a/doc/bugs/test_failures_on_window_for_5.20131118.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. - -git annex test reports failures - -### What steps will reproduce the problem? - -running git annex test (from standard cmd, with: git version: 1.7.11.msysgit.1) - -### What version of git-annex are you using? On what operating system? - -5.20131118 from installers - -### Please provide any additional information below. - -operating system: - -windows XP, NTFS = 1 FAIL -windows 7, NTFS = 2 FAILs - -see attachment for full log of git annex test output - -> Reproduced and [[fixed|done]]. --[[Joey]] diff --git a/doc/bugs/test_failures_on_window_for_5.20131118/comment_1_5a7a284625c12d54390fe4a4ec1d4211._comment b/doc/bugs/test_failures_on_window_for_5.20131118/comment_1_5a7a284625c12d54390fe4a4ec1d4211._comment deleted file mode 100644 index d27e69b30..000000000 --- a/doc/bugs/test_failures_on_window_for_5.20131118/comment_1_5a7a284625c12d54390fe4a4ec1d4211._comment +++ /dev/null @@ -1,188 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkJafmCf-sg9_OM0pynFYM3AO4WCgJiaMI" - nickname="Michele" - subject="seems i'm not allowed to attach full logs." - date="2013-11-23T16:06:17Z" - content=""" -here's an excerpt (the context of FAIL), hopefully i've interpreted correctely the test begin message. - -win7: - - unannex (with copy): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -get foo (merging origin/git-annex into git-annex...) -(Recording state in git...) -(from origin...) -foo - 20 100% 0.00kB/s 0:00:00 - 20 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) - -sent 87 bytes received 31 bytes 236.00 bytes/sec -total size is 20 speedup is 0.17 -ok -(Recording state in git...) -unannex foo -git-annex: M:\gitannex.test\.t\tmprepo4\.git\annex\objects\6cd\e82\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77.map4432.tmp: MoveFileEx \"M:\\gitannex.test\\.t\\tmprepo4\\.git\\annex\\objects\\6cd\\e82\\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77\\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77.map4432.tmp\" \"M:\\gitannex.test\\.t\\tmprepo4\\.git\\annex\\objects\\6cd\\e82\\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77\\SHA256E-s20--e394a389d787383843decc5d3d99b6d184ffa5fddeec23b911f9ee7fc8b9ea77.map\": permission denied (Access is denied.) -failed -git-annex: unannex: 1 failed -FAIL - - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - add conflictor (checksum...) ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit - ok - pull origin bash.exe: warning: could not find /tmp, please create! - - ok - push origin bash.exe: warning: could not find /tmp, please create! - To M:/gitannex.test/.t\repo - 32fb7c0..38147e0 git-annex -> synced/git-annex - 7684984..4116595 annex/direct/master -> synced/master - - ok - add conflictor/subfile (checksum...) ok - (Recording state in git...) - (merging origin/git-annex origin/synced/git-annex into git-annex...) - (Recording state in git...) - commit - ok - pull origin bash.exe: warning: could not find /tmp, please create! - From M:/gitannex.test/.t\repo - 7684984..4116595 master -> origin/master - 32fb7c0..38147e0 synced/git-annex -> origin/synced/git-annex - 7684984..4116595 synced/master -> origin/synced/master - Adding conflictor/subfile - CONFLICT (directory/file): There is a directory with name conflictor in HEAD. Adding conflictor as conflictor~refs_remotes_origin_synced_master - Automatic merge failed; fix conflicts and then commit the result. - Ignoring path ./conflictor.variant-cc12 - conflictor: needs merge - [annex/direct/master 27c52e4] git-annex automatic merge conflict fix - - - (Recording state in git...) - - Merge conflict was automatically resolved; you may want to examine the result. - ok - (merging origin/synced/git-annex into git-annex...) - (Recording state in git...) - push origin bash.exe: warning: could not find /tmp, please create! - To M:/gitannex.test/.t\repo - 38147e0..02916ee git-annex -> synced/git-annex - 4116595..27c52e4 annex/direct/master -> synced/master - - ok - commit - ok - pull r2 bash.exe: warning: could not find /tmp, please create! - From ../../.t\tmprepo35 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/master -> r2/synced/master - Updating 4116595..27c52e4 - Fast-forward - conflictor | 1 - - conflictor/subfile | 1 + - 2 files changed, 1 insertion(+), 1 deletion(-) - delete mode 120000 conflictor - create mode 120000 conflictor/subfile - Already up-to-date. - - - - ok - (merging r2/git-annex into git-annex...) - FAIL - - -windowsXP: - - conflict_resolution (mixed directory and file): Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. - Detected a filesystem without fifo support. - Disabling ssh connection caching. - Detected a crippled filesystem. - Enabling direct mode. -add conflictor (checksum...) ok -(Recording state in git...) -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -commit -ok -pull origin bash.exe: warning: could not find /tmp, please create! - -ok -push origin bash.exe: warning: could not find /tmp, please create! -To C:/Documents and Settings/Silvia/.t\repo - edd69f1..83c6a5a git-annex -> synced/git-annex - bed393e..978ac14 annex/direct/master -> synced/master - -ok -add conflictor/subfile (checksum...) ok -(Recording state in git...) -(merging origin/git-annex origin/synced/git-annex into git-annex...) -(Recording state in git...) -commit -ok -pull origin bash.exe: warning: could not find /tmp, please create! -From C:/Documents and Settings/Silvia/.t\repo - bed393e..978ac14 master -> origin/master - edd69f1..83c6a5a synced/git-annex -> origin/synced/git-annex - bed393e..978ac14 synced/master -> origin/synced/master -Adding conflictor/subfile -CONFLICT (directory/file): There is a directory with name conflictor in HEAD. Adding conflictor as conflictor~refs_remotes_origin_synced_master -Automatic merge failed; fix conflicts and then commit the result. -Ignoring path ./conflictor.variant-cc12 -conflictor: needs merge -[annex/direct/master e3e39fc] git-annex automatic merge conflict fix - - -(Recording state in git...) - - Merge conflict was automatically resolved; you may want to examine the result. -ok -(merging origin/synced/git-annex into git-annex...) -(Recording state in git...) -push origin bash.exe: warning: could not find /tmp, please create! -To C:/Documents and Settings/Silvia/.t\repo - 83c6a5a..e1a1678 git-annex -> synced/git-annex - 978ac14..e3e39fc annex/direct/master -> synced/master - -ok -commit -ok -pull r2 bash.exe: warning: could not find /tmp, please create! -From ../../.t\tmprepo35 - * [new branch] annex/direct/master -> r2/annex/direct/master - * [new branch] git-annex -> r2/git-annex - * [new branch] master -> r2/master - * [new branch] synced/master -> r2/synced/master -Updating 978ac14..e3e39fc -Fast-forward - conflictor | 1 - - conflictor/subfile | 1 + - 2 files changed, 1 insertion(+), 1 deletion(-) - delete mode 120000 conflictor - create mode 120000 conflictor/subfile -Already up-to-date. - - - -ok -(merging r2/git-annex into git-annex...) -FAIL -"""]] diff --git a/doc/bugs/too_many_open_files_on_OSX.mdwn b/doc/bugs/too_many_open_files_on_OSX.mdwn deleted file mode 100644 index 2ca89fcf0..000000000 --- a/doc/bugs/too_many_open_files_on_OSX.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -### Please describe the problem. - -error message: - - copy somefile.jpg (checking myserver...) (to myserver...) - git-annex: runInteractiveProcess: pipe: Too many open files - - rsync failed -- run git annex again to resume file transfer - failed - - -### What steps will reproduce the problem? - -1. Start a `git annex copy` with lots of files in the queue. -2. Start a second `git annex copy` on the same set of files. -The intention is to minimize the amount of silent time on the wire due to administrative work between actual file transfers. These two processes will trip over each other and see that transfer X is already going, and skip to the next file Y, so in the end they upload about half of the files each. - -3. Expect all files to be uploaded. Actually observe the above error message for at least one of the processes. - -### What version of git-annex are you using? On what operating system? - - git-annex version: 5.20140420-ga25b8bb - build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - - Darwin mymacbook 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64 - -### Please provide any additional information below. - -[[!format sh """ -lsof -p <my annex process> - -... some .app/** files, tty etc ... -... some unnamed pipes ... -.../.git/annex/ssh/myserver.lock -.../.git/annex/transfer/upload/b4d67c4f-8cca-423c-9363-f3063b7fe3e4/lck.SHA256E-s10448418--4f61fab4... ~200 different files. -"""]] - -> Thanks for a very clear bug report! Was easy from that to find -> where the lock file was not being closed in this situation. -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/too_many_open_files_on_OSX/comment_1_ef23a3c05a6bd187450e10c524d2ced9._comment b/doc/bugs/too_many_open_files_on_OSX/comment_1_ef23a3c05a6bd187450e10c524d2ced9._comment deleted file mode 100644 index d7efcb2b1..000000000 --- a/doc/bugs/too_many_open_files_on_OSX/comment_1_ef23a3c05a6bd187450e10c524d2ced9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://id.clacke.se/" - nickname="Claes" - subject="5.20140830" - date="2014-09-07T19:24:49Z" - content=""" -Will verify if this is still valid for 5.20140830. -"""]] diff --git a/doc/bugs/too_many_open_files_on_OSX/comment_2_798a02e42bfce56c50c9337a8111a57f._comment b/doc/bugs/too_many_open_files_on_OSX/comment_2_798a02e42bfce56c50c9337a8111a57f._comment deleted file mode 100644 index 25b6692dc..000000000 --- a/doc/bugs/too_many_open_files_on_OSX/comment_2_798a02e42bfce56c50c9337a8111a57f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://id.clacke.se/" - nickname="Claes" - subject="yep" - date="2014-09-07T19:42:04Z" - content=""" -Still valid for `git-annex version: 5.20140830-g3c96b79` -"""]] diff --git a/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn b/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn deleted file mode 100644 index a6c8ebe8c..000000000 --- a/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -### Please describe the problem. - -i can't find a key in the JSON output of `git annex info` for the "transfer in progress" field. is it missing on purpose? or am I missing some field? - -### What steps will reproduce the problem? - -<pre> -git annex info -git annex info --json -</pre> - - -### What version of git-annex are you using? On what operating system? -5.20150406-g2a9fbec debian jessie - -### 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 -anarcat@desktop008:mp3$ git annex info --fast --json | grep -i transfer -anarcat@desktop008:mp3$ git annex info --fast | grep -i transfer -transfers in progress: - -# End of transcript or log. -"""]] - -[[anarcat]] - -> JSON output has to be implemented on a case by case basis for stat -> displays; I've now added it to this and more. [[done]] -> --[[Joey]] diff --git a/doc/bugs/transfer_in_progress_not_present_in_json_output/comment_1_ca13b034f7034deea6a8b3a295b8fdd3._comment b/doc/bugs/transfer_in_progress_not_present_in_json_output/comment_1_ca13b034f7034deea6a8b3a295b8fdd3._comment deleted file mode 100644 index 054d6a029..000000000 --- a/doc/bugs/transfer_in_progress_not_present_in_json_output/comment_1_ca13b034f7034deea6a8b3a295b8fdd3._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="comment 1" - date="2015-06-15T19:48:46Z" - content=""" -it seems this is deliberate: there's a `nojson` tag on in the source code. I am just unclear why this is the case... and there doesn't seem to be documentation in the source about the nojson function or why it is desired... -"""]] diff --git a/doc/bugs/transfer_lock_file_removal_bug.mdwn b/doc/bugs/transfer_lock_file_removal_bug.mdwn deleted file mode 100644 index 021ce08a6..000000000 --- a/doc/bugs/transfer_lock_file_removal_bug.mdwn +++ /dev/null @@ -1,61 +0,0 @@ -There's a race that can result in 2 concurrent downloads -of the same key. This can happen because the transfer lock files get -deleted after a transfer completes. - -Scenario: - -1. first process creates lock file, takes lock, starts download -2. second process opens existing lock file -3. first process finishes/fails download, so deletes lock file, and then - drops lock -4. second process takes lock (exclusive, non-blocking) of deleted file! -5. third process sees no lock file, so creates a new one, takes lock, - starts download - -Worst-case, this might result in data loss, if the two concurrent -downloaders confuse one-another. Perhaps the second one overwrites the file -the first was downloading, and then the first, thinking it's written the -file, moves it into the object directory. - -Note that the window between 4-5 can be as long as it takes for a -file to download. However, the window between 2-4 is very narrow indeed, -since the second process is not blocking on the lock. -So, this is very unlikely to happen. - -But, it could. Can it be prevented? - -Yes: The second process, after taking the lock, can check that -the lock file exists, and has the same dev and fileno as the fd it has -locked. If the lock file doesn't exist, or is different, then the -second process can give up. - -Oh BTW, this race cannot happen on windows, since on windows, an open lock -file cannot be deleted by another process. - -> [[fixed|done]] - -Let's also consider if this change will allow for safely expiring stale -lock files.. - -Situation before with expiry would have been buggy (which is why it never -tried to expire them): - -1. first process creates lock file, takes lock, is interrupted (no more - lock) -2. second process wants to delete stale lock file; checks if it's locked; - isn't -3. third process opens existing lock file, prepares to take lock -4. second process deletes lock file -5. third process takes lock -6. third process is now doing a transfer w/o a (visible) lock - -But, after this bug fix, the third process checks if it's lock file -exists after taking the lock. Since the second process deleted it, -the third process fails with an error "transfer in progress" -which is perhaps not accurate, but at least it stopped. - -For this to work though, the second process needs to actually take -the lock, in non-blocking mode. If it succeeds, it can keep the lock -held while deleting the lock file. This ensures that when the third process -takes the lock, the lock file will already be deleted by the time it checks -if it's there. diff --git a/doc/bugs/trust_command_and_gitconfig_contradiction_causing_confusion.mdwn b/doc/bugs/trust_command_and_gitconfig_contradiction_causing_confusion.mdwn deleted file mode 100644 index d67ebe66a..000000000 --- a/doc/bugs/trust_command_and_gitconfig_contradiction_causing_confusion.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -### Please describe the problem. -'trust', 'dead', etc commands completing with 'ok' but fail to acknowledge contradiction in .git/config, causing confusion. - -[[!format sh """ -greg@x200s:~/Photos$ git-annex untrust home # yes, bad remote name -untrust home ok -(Recording state in git...) -greg@x200s:~/Photos$ git-annex status # /me is old-school and forgets -greg@x200s:~/Photos$ git-annex info -repository mode: indirect -trusted repositories: 2 - c0e4106e-2631-11e2-9749-1bfa37a61069 -- rose - c69d6fcc-18d1-11e2-9487-2fe6dbf0516b -- home (photos on eeepc) - -.... - -greg@x200s:~/Photos$ git-annex dead home -dead home ok -(Recording state in git...) -greg@x200s:~/Photos$ git-annex info -repository mode: indirect -trusted repositories: 2 - c0e4106e-2631-11e2-9749-1bfa37a61069 -- rose - c69d6fcc-18d1-11e2-9487-2fe6dbf0516b -- home (photos on eeepc) -"""]] - -The home remote has "annex-trustlevel=trusted" in .git/config - - -Maybe have those commands instead say "Hey, this is different than what you said explicitly in .git/config, ya sure? (y/n)" If y, overwrite config, if n, abort. - -### What version of git-annex are you using? On what operating system? -5.20140127 on Debian - -> [[Fixed|done]], it will now warn about this situation. --[[Joey]] diff --git a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build.mdwn b/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build.mdwn deleted file mode 100644 index 8f5e8c324..000000000 --- a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -As told in http://git-annex.branchable.com/bugs/OSX_app_issues/#comment-2a69d531bd3bb593c1a49dc8cdb34b1e the Mac OS 10.7.5 (Lion) build fails to run. - - $ /Applications/git-annex.app/Contents/MacOS/git-annex - - /Applications/git-annex.app/Contents/MacOS/runshell: line 25: syntax error near unexpected token `&' - -Manually editing /Applications/git-annex.app/Contents/MacOS/runshell as told in http://git-annex.branchable.com/bugs/OSX_app_issues/#comment-5579c2150ad4d2ccc207a253fe57612a fixes the issue. - -Furthermore, this build is quite outdated... - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_1_e8df4b36a89b37edd94f3a318ae93a32._comment b/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_1_e8df4b36a89b37edd94f3a318ae93a32._comment deleted file mode 100644 index d67330a22..000000000 --- a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_1_e8df4b36a89b37edd94f3a318ae93a32._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.246" - subject="comment 1" - date="2013-11-14T15:26:01Z" - content=""" -This is unfortunate.. The Lion autobuilder is running, but has been failing for various reasons for some time, and I have not managed to get ahold of Jimmy to fix them. Also, that machine may be upgraded from Lion before too long. -"""]] diff --git a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_2_3b2c3c84bd1910280c549a2ee1c622b9._comment b/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_2_3b2c3c84bd1910280c549a2ee1c622b9._comment deleted file mode 100644 index bd1763ca0..000000000 --- a/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_2_3b2c3c84bd1910280c549a2ee1c622b9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus" - nickname="Jimmy" - subject="comment 2" - date="2013-11-15T20:57:27Z" - content=""" -The builder is back, I was away from the office when it broke. It should be spitting out builds on a daily basis again. -"""]] diff --git a/doc/bugs/unable_to_change_repository_group_of___34__here__34__.mdwn b/doc/bugs/unable_to_change_repository_group_of___34__here__34__.mdwn deleted file mode 100644 index 4098f8acf..000000000 --- a/doc/bugs/unable_to_change_repository_group_of___34__here__34__.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -### Please describe the problem. -(I assume) following your change to disallow changing the name of "here", I am unable to change the repository group of "here" - - -### What steps will reproduce the problem? -In webapp, edit "here", and try and change repository group. -It highlights the (now empty) name field, and says "value is required". - -### What version of git-annex are you using? On what operating system? -git-annex version: 4.20130618-g333cb8e -Ubuntu 13.04 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/unannex_requires_commit_for_new_directories.mdwn b/doc/bugs/unannex_requires_commit_for_new_directories.mdwn deleted file mode 100644 index 98078d967..000000000 --- a/doc/bugs/unannex_requires_commit_for_new_directories.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -### Please describe the problem. -"git-annex unannex" requires an unexpected (and undesirable) commit only when adding files in a new directory. This is undesirable because whenever "git-annex add" is accidentally run in a new directory, the only way to undo it is to commit first and then unannex, which adds two unwanted commits to the git log. Moreover, this behavior is not consistent with unannex on files in non-new directories: in that case unannex works as expected. - -### What steps will reproduce the problem? -<pre><code>/tmp> mkdir test -/tmp> cd test/ -/tmp/test> git init -Initialized empty Git repository in /tmp/test/.git/ -/tmp/test (master)> git annex init -init ok -(recording state in git...) -/tmp/test (master)> touch foo -/tmp/test (master)> git annex add foo -add foo ok -(recording state in git...) -/tmp/test (master)> git annex unannex foo -unannex foo ok -/tmp/test (master)> mkdir bar -/tmp/test (master)> touch bar/foo -/tmp/test (master)> git annex add bar -add bar/foo ok -(recording state in git...) -/tmp/test (master)> git annex unannex bar -git-annex: Cannot proceed with uncommitted changes staged in the index. Recommend you: git commit -</code></pre> - - -### What version of git-annex are you using? On what operating system? -The issue occurs with last version of git-annex, available at the time of this post (2015-02-19 16:20). I could reproduce the issue in all other versions of git-annex I tried (not many though). I am using Linux, Ubuntu 12.04 amd64. - -> [[done]]; added check for repository too new to have a HEAD. --[[Joey]] diff --git a/doc/bugs/unannex_requires_commit_for_new_directories/comment_1_75814d6b4a59a4b7b950f9f2a27f0789._comment b/doc/bugs/unannex_requires_commit_for_new_directories/comment_1_75814d6b4a59a4b7b950f9f2a27f0789._comment deleted file mode 100644 index 4c0a702d1..000000000 --- a/doc/bugs/unannex_requires_commit_for_new_directories/comment_1_75814d6b4a59a4b7b950f9f2a27f0789._comment +++ /dev/null @@ -1,32 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-25T17:45:50Z" - content=""" -Git provides ample facilities to remove any commits that you don't like -from your repository's history. Eg, `git reset HEAD^^` - -This check for a clean index was added in [[!commit 7dc680415480fbbadc5dfd37f1ce72084fb1887d]] -which made unannex not make 1 commit per file it unannexed. That was a -massive improvement in speed and number of commits. - -In order for unannex to make just 1 commit at the end, instead of 1 per -file, it has to stage its changes in the index. Since it then needs to -commit the index at the end, we have one reason for it to require the index -not have staged changes, since those stages changes would get included in -the unannex commit. - -I suspect I had a second reason in mind when making that change. -The unannex commit has to be run with the pre-commit hook disabled -for complicated reasons. Involving other changes that are not unannex -changes in that commit would thus defeat the fixups that the pre-commit -hook normally does to such changes. This would at least prevent annexed -symlink path fixups from happening, and it might result in whole unlocked -files getting their full contents unexpectedly committed to git. - -There is no inconsistency between new and existing directories. -The difference is between repositories with a HEAD and repositories too -new to have one. Maybe it's a bug that unannex doesn't refuse to run -in a repostory too new to have a HEAD, since it cannot tell if there are -other staged changes with no HEAD to diff against. -"""]] diff --git a/doc/bugs/undefined.mdwn b/doc/bugs/undefined.mdwn deleted file mode 100644 index 8ee37f034..000000000 --- a/doc/bugs/undefined.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -Trying to move files from a local remote that is not mounted: - - git-annex: Prelude.undefined - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/unexpected_double_wildcard_expansion.mdwn b/doc/bugs/unexpected_double_wildcard_expansion.mdwn deleted file mode 100644 index f898a0c84..000000000 --- a/doc/bugs/unexpected_double_wildcard_expansion.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -From the forum, it seems that git-ls-files very unexpectedly expands -wildcards in filenames passed to it. (Not a documented or an expected -behavior.) - -This causes problems when eg, the user does `git annex add *.jpeg` and that -matches no files, but there are some jpegs in subdirectories. git-ls-files -re-expands the wildcard and finds those. - -Seems that the best fix is to make Git.LsFiles paper over this git -misfeature, by always escaping wildcards in paths passed -to git-ls-files. AFAIK, no callers of Git.LsFiles expect to provide it -wildcards, because I was completely surprised when I learned they were -expanded.. --[[Joey]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn b/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn deleted file mode 100644 index 848f1b30b..000000000 --- a/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -### Please describe the problem. - -When using a git remote which doesn't support git-annex (f.e. gitlab) and is configured with `annex-ignore true` the remote is shown as `unfinished repository` in the webapp. - -It would be nice if the webapp would recognize this and show the remote as git-only remote including sync-state and remote name (or even better: the remote details, like the URL to the remote) - -### What steps will reproduce the problem? - -Add a normal git remote and configure `git config remote.<name>.annex-ignore true`. -Start the webapp. - -### What version of git-annex are you using? On what operating system? - - git-annex version: 4.20131101-gf59a6d1 - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA - key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL - remote types: git gcrypt S3 bup directory rsync web webdav glacier hook - local repository version: 3 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - -Kubuntu 13.10 x86_64 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/unlock_with_absolute_path__63__.mdwn b/doc/bugs/unlock_with_absolute_path__63__.mdwn deleted file mode 100644 index 232483602..000000000 --- a/doc/bugs/unlock_with_absolute_path__63__.mdwn +++ /dev/null @@ -1,44 +0,0 @@ -### Please describe the problem. - -"git annex unlock" with an absolute path appears to do nothing. Is this a feature or a bug? - -### What steps will reproduce the problem? - -[[!format sh """ -> mkdir git_annex_test && cd git_annex_test/ -> git init -> git annex init "Local copy" -> touch foo.txt -> git annex add foo.txt -> git commit -m "Checkin" -> git annex unlock foo.txt (correct behavior) -> git annex lock --force foo.txt -> git annex unlock /absolute/path/to/git_annex_test/foo.txt (appears to do nothing) -"""]] - -### What version of git-annex are you using? On what operating system? - -Ubuntu 14.04.02 with git-annex from repo: - -[[!format sh """ -> git annex --version -git-annex version: 5.20140412ubuntu1 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -""" ]] - -> Please upgrade to the current version of git-annex before filing bug -> reports. -> -> I don't know when this was fixed/changed, but sometime in the past 13 -> months since the version you have, it was: -> - - joey@darkstar:~/tmp/x>git annex unlock `pwd`/me - unlock me (copying...) ok - -> [[done]] --[[Joey]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument.mdwn b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument.mdwn deleted file mode 100644 index cc9a4c57f..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument.mdwn +++ /dev/null @@ -1,87 +0,0 @@ -### Please describe the problem. - -#### git annex unused fails with the message: - -... - 86731 SHA256E-s13243--a6c5fe9710975e0b0ca01ec0b7eca6068a01b1b1c06adbd8ad7921e26d3b076d.h - - 86732 SHA256E-s12872--f50b73d313a116ea21649d684f601840dbc8ed3c264165dd77fa5d54a1c57464.c - - 86733 SHA256E-s6557264--6b502d56378b9919fd3c54c3bb2dc2906a326be8e9d477a8f3518419929f4706.dll - - 86734 SHA256E-s141--c6227fe715dab2b4447b6e43af2b170ac66d82043aa81a14013c56be922e11db.out - - 86735 SHA256E-s6564--ec4bcd833d071fff7d8cc81b908558acdeae2c9ba62f7d65b584effe6b36a8c6.c - -git-annex: /bluepool/data/.git/annex/unused32594.tmp: commitBuffer: invalid argument (invalid character) -failed - -git-annex: unused: 1 failed - -#### A subsequent git annex dropunused does not work (there are 86735 files unused). A simple: -"git annex dropunused 1-10" produces: - -git-annex: 1 not valid (run git annex unused for list) - -#### It seems that the list of unused files was not saved (committed) - -### What steps will reproduce the problem? - -I suspect it can be reproduced by having files with non-english characters. -This should be the sequence of commands to reproduce if one knew the invalid character: - -git init . - -git annex init . - -touch "Invalid character in file name" - -git annex add "Invalid character in file name" - -git commit - -git rm "Invalid character in file name" - -git commit - -git unused - -However, I usually have "git annex watch" running so this might also have an influence on how (maybe not-escaped) filenames are added. - -### What version of git-annex are you using? On what operating system? - -git annex standalone: - -git-annex version: 5.20140306-g6e2e021 - -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi TDFA CryptoHash - -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL - -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external - -local repository version: 5 - -supported repository version: 5 - -upgrade supported from repository versions: 0 1 2 4 - - - -Ubuntu Raring: Linux i3 3.11.4-031104-generic - - -### Please provide any additional information below. - -I guess I could provide the full output of git annex unused but I would rather not put it into this bug report for privacy reasons. - -[[!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. -"""]] - -> [[closing|done]], would still be nice to have verification my fix worked. -> --[[Joey]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_1_004cb3015895ad67386276f3e1f0de0d._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_1_004cb3015895ad67386276f3e1f0de0d._comment deleted file mode 100644 index e1db22b2e..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_1_004cb3015895ad67386276f3e1f0de0d._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 1" - date="2014-03-15T16:01:53Z" - content=""" -I see the problem, although I have not quite managed to reproduce it. I think this would probably only happen if you have the unusual character in the extension of the file (or are using the WORM backend). - -I've put a fix in git. It will be available in the next autobuild, in half an hour or so. -"""]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_2_3fe298ebb3ff04d12f2528aa982d7084._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_2_3fe298ebb3ff04d12f2528aa982d7084._comment deleted file mode 100644 index ed5733d04..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_2_3fe298ebb3ff04d12f2528aa982d7084._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="donkeyicydragon" - subject="Problem still occurs but maybe my update did not work" - date="2014-03-16T18:01:24Z" - content=""" -Hi Joey, thanks for the quick response. - -I tried to update and retry my \"git annex unused\" but it gave the same error. Maybe my updating did not work (see below). But is there a way I can retry it without running \"git annex unused\" again? The problem is that each run takes several hours with my amount of files. -It would be nice, if git annex recognized some error in the last approach and recovered. -The tmp files that are created by \"git annex unused\" are still in .git/annex/. - - -Regarding the updating: -I tried to obtain the autobuild version but on this website I could not find a link to download the latest autobuild. I could only find the build reports. But I used the git annex installer script from https://github.com/zerodogg/scriptbucket/blob/master/gitannex-install -and it apparently knows the location of the daily build. Is this the autobuild or is git annex autobuilt more often? - -This is my version after installing it yesterday evening approx. 2h hours after your answer to the bug description. - -git-annex version: 5.20140314-g48e0f18 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external -"""]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_3_9302536d1577c12337d714fa3a9ea7a1._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_3_9302536d1577c12337d714fa3a9ea7a1._comment deleted file mode 100644 index e74ccba1c..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_3_9302536d1577c12337d714fa3a9ea7a1._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 3" - date="2014-03-17T19:28:05Z" - content=""" -No, your version is from before I fixed it. - -You can get an autobuild from [[install/Linux_standalone]] -"""]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_4_c1c8de66192957b7026d99b9ff90589c._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_4_c1c8de66192957b7026d99b9ff90589c._comment deleted file mode 100644 index b229545f6..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_4_c1c8de66192957b7026d99b9ff90589c._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="donkeyicydragon" - subject="Maybe the autobuild is broken?" - date="2014-03-17T20:32:19Z" - content=""" -The latest autobuild log for amd64 says: -Starting at: Fri Mar 14 21:42:07 UTC 2014 - -I downloaded the amd64 autobuild from https://git-annex.branchable.com/install/Linux_standalone/ - -and it indeed is from Friday. - -Cheers, -Marek -"""]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_5_8c2dad766e4115073d49b698919b5ed5._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_5_8c2dad766e4115073d49b698919b5ed5._comment deleted file mode 100644 index 360003fba..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_5_8c2dad766e4115073d49b698919b5ed5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.154" - subject="comment 5" - date="2014-03-18T19:07:25Z" - content=""" -cron was not running them for some reason, but they are up-to-date now. -"""]] diff --git a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_6_8da2a73381309ecef4b2796d8f2bb0bb._comment b/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_6_8da2a73381309ecef4b2796d8f2bb0bb._comment deleted file mode 100644 index 8532afaf7..000000000 --- a/doc/bugs/unused_fails_due_to_commitBuffer_containing_an_invalid_argument/comment_6_8da2a73381309ecef4b2796d8f2bb0bb._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo" - nickname="donkeyicydragon" - subject="Your changes to git annex worked" - date="2014-03-19T21:27:39Z" - content=""" -Thanks a lot. - -BTW, will you start a new funding round? -"""]] diff --git a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories.mdwn b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories.mdwn deleted file mode 100644 index 7fdbc3ca4..000000000 --- a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -I upgraded another one of my git-annex clones. The upgrade worked fine (i.e. -according to the manual) on two other clones before, but this time something is -different. - -After 'git pull' and 'git annex upgrade', which took a long time and seemed to -have succeeded, there are no staged changes in git. Instead there are lots of -untracked directories in .git-annex. Aside from that, nothing seems to be -wrong. - -At the time I had git-annex version 0.20110329 and I've been using the SHA1 -backend since version 1. - -> Yes, I agree with Jimmy, it's the same bug. So I'll be closing this one. -> Please keep us informed how the workaround committed to git-annex -> yesterday for the case insensativity issue works out. [[dup|done]] -> --[[Joey]] diff --git a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_1_9ca2da52f3c8add0276b72d6099516a6._comment b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_1_9ca2da52f3c8add0276b72d6099516a6._comment deleted file mode 100644 index 78309df87..000000000 --- a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_1_9ca2da52f3c8add0276b72d6099516a6._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2011-04-03T02:26:20Z" - content=""" -I'm not sure how this happened, as far as I can see, and based on my testing, `git annex upgrade` does stage the location log files. OTOH, I vaguely rememeber needing to stage some of them when I was doing my own upgrades, but that was a while ago, and I don't remember the details. - -Your upgrade seems to have gone ok from the file lists you sent, so you can just: `git add .git-annex; git commit` -"""]] diff --git a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment deleted file mode 100644 index 4fc9647e8..000000000 --- a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_2_e14e84b770305893f2fc6e4938359f47._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="gernot" - ip="213.168.117.192" - subject="comment 2" - date="2011-04-03T15:35:52Z" - content=""" -'git add .git-annex' didn't do anything. That's when I noticed that this -repository is on a case-insensitive HFS+ file system. - -So, if I get this right it's not a new bug, but similar to this situation: -[[git-annex_directory_hashing_problems_on_osx]] - -Assuming that it was the file system's fault, I went ahead and upgraded yet -another clone. That one (on an ext3 file system) had neither staged changes -nor left-over untracked files. Everything seems to just have fallen right into -place. Is that possible or still weird? - -"""]] diff --git a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_3_ec04e306c96fd20ab912aea54a8340aa._comment b/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_3_ec04e306c96fd20ab912aea54a8340aa._comment deleted file mode 100644 index 99095c156..000000000 --- a/doc/bugs/upgrade_left_untracked_.git-annex__47____42___directories/comment_3_ec04e306c96fd20ab912aea54a8340aa._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus" - nickname="Jimmy" - subject="comment 3" - date="2011-04-03T16:05:39Z" - content=""" -Yes you seem to have come across the same bug that I had initially reported :P -"""]] diff --git a/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn b/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn deleted file mode 100644 index 6f45cb8ff..000000000 --- a/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -## What steps will reproduce the problem? - -After the assistant idles for a while, it queues many transfers to remotes configured annex-ignore=true - -##What is the expected output? What do you see instead? - -No attempts to upload to repos marked 'annex-ignore=true' - -Instead I see many queued transfers to the remote 'origin' - -[Screenshot](https://www.evernote.com/shard/s1/sh/ea0de76c-4b68-4266-b9f6-8a9c343997b6/72baab4a3ce73b0915b151829bbeaf75/res/8a8ab1fb-3173-47ea-875d-b0e320cb827b/skitch.png) - -##What version of git-annex are you using? On what operating system? - - % > git annex version - git-annex version: 4.20130315 - local repository version: 3 - default repository version: 3 - supported repository versions: 3 4 - upgrade supported from repository versions: 0 1 2 - build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS - -Mac OSX 10.8.2 Build 12C3006 - -##Please provide any additional information below. - -The remote in question: - - [remote "origin"] - url = git@git.example.com:annex-home - fetch = +refs/heads/*:refs/remotes/origin/* - annex-ignore = true - -> belived to be [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/uploads_queued_to_annex-ignore_remotes/comment_1_fa1c98f38253db8c2be3604c72eb3726._comment b/doc/bugs/uploads_queued_to_annex-ignore_remotes/comment_1_fa1c98f38253db8c2be3604c72eb3726._comment deleted file mode 100644 index d58d5f5dd..000000000 --- a/doc/bugs/uploads_queued_to_annex-ignore_remotes/comment_1_fa1c98f38253db8c2be3604c72eb3726._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - nickname="joey" - subject="comment 1" - date="2013-03-17T20:03:48Z" - content=""" -I was able to find two ways this could happen: - -* When a removable drive was attached and the annex-ignored repository was on it. -* When the network connection went down and came back up. - -In either case, it would git sync with the ignored repository. And in some cases could scan it for transfers. - -I've pushed a fix for these two cases. If you can try the next autobuild, that would be helpful. - -If you continue to see this happening, you should enable debug logging, and send a log after it happens. -"""]] diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails.mdwn b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails.mdwn deleted file mode 100644 index 887f9f1fd..000000000 --- a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails.mdwn +++ /dev/null @@ -1,57 +0,0 @@ -### Please describe the problem. -git-annex assistant uses wrong key if multiple are available. If there is only one gpg available it works without issue. - -### What steps will reproduce the problem? - -I tried to creating a new key through cli or assistant UI. I also tried to select preexisting key but it always appears to choose the initial key. Log below is creating a new key through assistant UI. - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140709-gc75193e on linux amd64 & os x 10.9.4 - -### 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 - -[2014-07-12 23:22:57 PDT] main: starting assistant version 5.20140709-gc75193e -[2014-07-12 23:22:57 PDT] Cronner: You should enable consistency checking to protect your data. -(Recording state in git...) -(scanning...) [2014-07-12 23:22:57 PDT] Watcher: Performing startup scan -(started...) gpg: Signature made Wed Jul 9 19:09:28 2014 PDT using DSA key ID 89C809CB -gpg: Can't check signature: public key not found - -(encryption setup) (hybrid cipher with gpg key A1FE7E9BECB5C7CA) gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://admin@nappy.local/share/backups/annex/ -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Repository not found: ssh://admin@nappy.local/share/backups/annex/ -gcrypt: Setting up new repository -gcrypt: Remote ID is :id:smTV2DKvbvPIi7ftJLey -gcrypt: Encrypting to: -R A1FE7E9BECB5C7CA -gcrypt: Requesting manifest signature -To gcrypt::ssh://admin@nappy.local/share/backups/annex/ - * [new branch] git-annex -> git-annex -ok -[2014-07-12 23:23:42 PDT] main: Syncing with nappy.local__share_backups_annex -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gpg: anonymous recipient; trying secret key 6DF1BC5D ... -gpg: cannot open tty `/dev/tty': Device not configured -gcrypt: Failed to decrypt manifest! -gcrypt: Development version -- Repository format MAY CHANGE -gcrypt: Decrypting manifest -gpg: anonymous recipient; trying secret key 6DF1BC5D ... -gpg: cannot open tty `/dev/tty': Device not configured -gcrypt: Failed to decrypt manifest! - - -# End of transcript or log. -"""]] - -[[!tag forwarded]] -[[!meta title="using git-remote-gcrypt with multiple keys causes unncessary password prompts for keys that did not encrypt the repository"]] - -> [[fixed|done]]; upgrade git-remote-gcrypt and `git config gcrypt.publish-participants true` -> and after the next push to the repo, it'll stop guessing at keys, and use -> the right one. git-annex will do this by default for new gcrypt -> repositories. --[[Joey]] diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment deleted file mode 100644 index 01b9726a9..000000000 --- a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-14T20:54:32Z" - content=""" -AFAICs, this is a known bug in git-remote-gcrypt: <https://github.com/blake2-ppc/git-remote-gcrypt/issues/9> - -In your log, it encrypts to A1FE7E9BECB5C7CA. I think this is the new key that git-annex generated. The problem comes when trying to decrypt the manifest, then it tries every gpg key until it finds one that works. -"""]] diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_2_51855f5bb857e1b6bc5531cdd7073c31._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_2_51855f5bb857e1b6bc5531cdd7073c31._comment deleted file mode 100644 index df07fd04a..000000000 --- a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_2_51855f5bb857e1b6bc5531cdd7073c31._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="lex" - ip="17.199.80.21" - subject="comment 2" - date="2014-07-14T22:21:32Z" - content=""" -ah. It's bailing due to the first key requiring passphrase, and since it aborts there it never tries the second so the whole thing fails. - -okay thanks for the link. -"""]] diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_3_3a6ff3dbc24850b065d045c7c9398eb1._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_3_3a6ff3dbc24850b065d045c7c9398eb1._comment deleted file mode 100644 index 7dab63081..000000000 --- a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_3_3a6ff3dbc24850b065d045c7c9398eb1._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 3" - date="2014-07-15T20:42:15Z" - content=""" -So let's think about whether gcrypt using gpg -R makes sense from the git-annex perspective. - -Without -R, an attacker who can look at the remote, encrypted git repository can easily see the gpg keys of participants. This could allow them to perform other, more targeted attacks to get at the unencrypted repository. - -If the user is using eg, github to store the gcrypt repo, an attacker can easily find out who owns the repo anyway, so they know who to attack then, even when -R is used. The -R can still prevent them from finding out when it's encrypted to additional users than the owner. - -As far as the assistant goes, it only ever sets up a gcrypt repo with one participant. Using either an existing gpg key of the user, or generating a new one (which doesn't even have their name on it). Adding more participants to a gcrypt repo is tricky, and the assistant doesn't currently support it. But I'd like to have it support setting up multiple participants eventually. So the current limitations of the assistant are not a sufficient reason to avoid using -R. - -So, it seems to come down to the question of whether it's a reasonable goal for git-annex, when used with gcrypt, to hide the identities of people who use a repository. And whether such a goal is worth the security/usability tradeoff of the user getting gpg passphrase prompts for other keys. - -Hmm, when git-annex encrypts files to send them to a special remote, if it's using encryption=pubkey, it does not use -R. So an attacker can get the list of participants that way. Although the more common approach is for git-annex to encrypt using encryption=shared/hybrid, which uses a symmetric cipher, which avoids that problem. There are plenty of other things that git-annex can do that would leak identity. - -It kind of seems to me that if you want to prevent anyone learning who uses your repository, you are going to need to be very cautious (using tor etc) and the most git-annex can do is be open about how it works and avoid adding any obstacles. Looking at it this way, such a user, or group of users, would be well-served by using gpg keys that don't have their names on them... -"""]] diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_4_84168b56288262e01280da59ffaf19f6._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_4_84168b56288262e01280da59ffaf19f6._comment deleted file mode 100644 index 22f0e909f..000000000 --- a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_4_84168b56288262e01280da59ffaf19f6._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 4" - date="2014-07-15T21:06:23Z" - content=""" -@lex, it shouldn't fail due to passphrase if you have gpg-agent set up. You'll only get some unncessary passphrase prompts. -"""]] diff --git a/doc/bugs/view_fails_with___34__invalid_character__34__.mdwn b/doc/bugs/view_fails_with___34__invalid_character__34__.mdwn deleted file mode 100644 index f77f5013f..000000000 --- a/doc/bugs/view_fails_with___34__invalid_character__34__.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -### Please describe the problem. -I have a "person" attribute with the name of the people on the picture. I could create views and filter on that some time ago, but it looks like git annex now chokes on some illegal (accented?) characters. I have non-ASCII characters in names for sure. - -### What steps will reproduce the problem? -Try to create a view using the "person" attribute. - -### What version of git-annex are you using? On what operating system? -5.20150617-gac09445 on ArchLinux - -### Please provide any additional information below. - -[[!format sh """ -% git annex view person="*" -/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) -view (searching...) - -git-annex: fd:14: commitBuffer: invalid argument (invalid character) -failed -git-annex: view: 1 failed - -% git annex version -/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) -git-annex version: 5.20150617-gac09445 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E MD5E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 MD5 WORM URL -remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external -local repository version: 5 -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 -"""]] - -> I'm assuming the setlocale part of this is a misconfigured system locale; -> as also seen by an arch linux user in -> <http://git-annex.branchable.com/bugs/cannot_change_locale___40__en__95__US.UTF-8__41__/> -> -> So, disregarding that part of the bug report, we still have the actual -> failure. -> -> With LANG=C, setting and getting metadata like "Rondò Veneziano" fails, -> as does generating views of that metadata. -> -> In all cases, it's an IO encoding failure, "commitBuffer: invalid argument (invalid character)" -> -> This only occurs when there's a space in the metadata; in this case the - -> value is base64ed. While the 'ò' comes back out as "\242", which is the right -> character, it's not encoded using the filesystem encoding. This means that -> the IO layer can't handle it, when not in a unicode locale. Instead, it -> needs to come back out as "\56515\56498". -> -> Apparently this is a reversion; it worked in an earlier version of -> git-annex. Commits such as 9b93278e8abe1163d53fbf56909d0fe6d7de69e9 -> or the conversion to Sandi may have caused the reversion, unsure. -> -> Fix is to apply the filesystem encoding when decoding base64ed values. -> [[done]] --[[Joey]] diff --git a/doc/bugs/view_fails_with___34__invalid_character__34__/comment_1_7c5447729352f75afd0bde1daf0f849f._comment b/doc/bugs/view_fails_with___34__invalid_character__34__/comment_1_7c5447729352f75afd0bde1daf0f849f._comment deleted file mode 100644 index 71d4f4507..000000000 --- a/doc/bugs/view_fails_with___34__invalid_character__34__/comment_1_7c5447729352f75afd0bde1daf0f849f._comment +++ /dev/null @@ -1,34 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-02T18:18:22Z" - content=""" -It seems like you have some kind of system misconfiguration, -resulting in setlocale(3) failing. Probably `LC_ALL` is set to a locale -that is not available or is somehow broken. - -I tested by setting metadata to a completely bogus unicode value, and it -all works ok here: - - joey@darkstar:~/tmp/annex>git annex metadata -s person=$(perl -le "print chr(0x99999999)") you - Wide character in print at -e line 1. - metadata you - lastchanged=2015-07-02@18-23-34 - person=������� - person-lastchanged=2015-07-02@18-23-34 - ok - (recording state in git...) - joey@darkstar:~/tmp/annex>git annex metadata you - metadata you - lastchanged=2015-07-02@18-23-34 - person=������� - person-lastchanged=2015-07-02@18-23-34 - ok - joey@darkstar:~/tmp/annex>git annex view person='*' - view (searching...) - - Switched to branch 'views/person=_' - ok - joey@darkstar:~/tmp/annex#person=_>ls - Gödel/ \376\202\231\246\231\246\231/ -"""]] diff --git a/doc/bugs/web_app_loops_over_a_non-addable_file.mdwn b/doc/bugs/web_app_loops_over_a_non-addable_file.mdwn deleted file mode 100644 index a1f490061..000000000 --- a/doc/bugs/web_app_loops_over_a_non-addable_file.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -### Please describe the problem. - -I started the webapp on a pre-existing repo today, and it started adding all sorts of files which I didn't manually add, which is a little bit surprising, but "okay". - -The problem is that it would loop over this one file over and over again. Adding it on the commandline yields a proper error, but this doesn't seem to properly propagate to the frontend. - -### What steps will reproduce the problem? - -Unclear. - -### What version of git-annex are you using? On what operating system? - -4.20131105-g8efdc1a - -### Please provide any additional information below. - -Here's the daemon.log: - -[[!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 - -add clips/A31-05-12_21.22.amr (checksum...) [2013-11-06 10:21:10 EST] Committer: Committing changes to git -[2013-11-06 10:21:11 EST] Committer: Adding A31-05-12_21.22.amr -(Recording state in git...) -(Recording state in git...) -add clips/A31-05-12_21.22.amr (checksum...) [2013-11-06 10:21:11 EST] Committer: Committing changes to git -[2013-11-06 10:21:12 EST] Committer: Adding A31-05-12_21.22.amr -(Recording state in git...) -(Recording state in git...) -add clips/A31-05-12_21.22.amr (checksum...) [2013-11-06 10:21:12 EST] Committer: Committing changes to git -[2013-11-06 10:21:13 EST] Committer: Adding A31-05-12_21.22.amr -(Recording state in git...) -add clips/A31-05-12_21.22.amr (checksum...) [2013-11-06 10:21:13 EST] Committer: Committing changes to git -[2013-11-06 10:21:14 EST] Committer: Adding A31-05-12_21.22.amr -(Recording state in git...) -(Recording state in git...) -add clips/A31-05-12_21.22.amr (checksum...) [2013-11-06 10:21:14 EST] Committer: Committing changes to git -# End of transcript or log. -"""]] - -And here's the attempt on the commandline, which is way more informative: - -[[!format sh """ -anarcat@marcos:video$ git annex add . -add clips/96_257.mp3 ok -add clips/A31-05-12_21.22.amr (checksum...) -git-annex: /srv/video/.git/annex/objects/z3/96/SHA256E-s260070--46f0d657cdd79032d431e2aebb04b63685ab26e7d00963036e0b64c9f86998f8.22.amr/SHA256E-s260070--46f0d657cdd79032d431e2aebb04b63685ab26e7d00963036e0b64c9f86998f8.22.amr: setFileMode: permission denied (Operation not permitted) -failed -"""]] - -Turns out that file is owned by root, so it's an expected failure. But the webapp should simply skip this file, not loop over it. - -The workaround is obviously to give this file to the proper user. --[[anarcat]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/webapp_does_not_start_on_android.mdwn b/doc/bugs/webapp_does_not_start_on_android.mdwn deleted file mode 100644 index dc3c4e648..000000000 --- a/doc/bugs/webapp_does_not_start_on_android.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. - -The webapp does not start automatically and instead this message is printed in the terminal: - - Falling back to hardcoded app location; cannot find expected files in /data/app-lib - git annex webapp - COLUMNS=0;LINES=0;export COLUMNS LINES; - -After typing `git annex webapp`, the webapp starts normally. - -If I click the WebApp entry in the terminal menu, nothing happens. - -### What steps will reproduce the problem? - -Launch Git Annex from the applications menu. - -### What version of git-annex are you using? On what operating system? - -Using 4.3/4.4 daily build (nov 1st 2014) apk. -CyanogemMod 11 (M10) - -> Seems to be a dup of [[Android_Default_startup_command]]; [[done]] --[[Joey]] diff --git a/doc/bugs/webapp_doesn__39__t_start_when___126____47__annex_isn__39__t_a_git_repo.mdwn b/doc/bugs/webapp_doesn__39__t_start_when___126____47__annex_isn__39__t_a_git_repo.mdwn deleted file mode 100644 index ac02590e6..000000000 --- a/doc/bugs/webapp_doesn__39__t_start_when___126____47__annex_isn__39__t_a_git_repo.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -### Please describe the problem. -The webapp doesn't start. There is no feedback as to what is wrong when starting the OS X app. Makes for a very confusing behaviour. - -When starting git-annex-webapp directly, it says: -git-annex: no git repository in /Users/lhunath/annex - -### What steps will reproduce the problem? -Create a ~/annex that is not a git repo. - -### What version of git-annex are you using? On what operating system? -git-annex version: 5.20140517-g0aed6d9 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external -local repository version: unknown -supported repository version: 5 -upgrade supported from repository versions: 0 1 2 4 - -### 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 -$ /Applications/git-annex.app/Contents/MacOS/git-annex-webapp -git-annex: no git repository in /Users/lhunath/annex -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__.mdwn b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__.mdwn deleted file mode 100644 index 83fec53ab..000000000 --- a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -### Please describe the problem. - -I added a remote repository, and it successfully tested the ssh connection to the server. Nothing happens, however, once it comes to actually creating the remote repository (or merging with an existing one). It'll just sit there forever, never actually connecting to the server. - -A quick look in process explorer shows something of what's going on: git-annex has launched ssh, and ssh is spamming subprocesses. It's launching ssh.exe which is launching git-annex.exe (yes, on the local machine.) It exits right away, but the command line is "C:\Program Files (x86)\Git\cmd\git-annex.exe" "Please type 'yes' or 'no': ". I've no idea why it's doing that though. - -If I kill that parent ssh process, I get this error message in the transcript: - - Could not create directory '/home/db48x/.ssh'. - -This seems a bit dubious; both my local computer and the remote computer have a ~/.ssh directory. - -In order to rule out a problem with my local computer (an ancient install of Git or cygwin/msys or something, we've tried this on fresh computers which have never had git installed; we get exactly the same problem there. - -### What steps will reproduce the problem? - -Create or connect to a repository via SSH. - -### What version of git-annex are you using? On what operating system? - -Windows 7 - - Version: 5.20150420-gb0ebb23 - Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA TorrentParser - -### Please provide any additional information below. - -While this is going on, the log has is showing that it's executing the following command: - -[[!format sh """ -[2015-04-28 22:34:16 Pacific Daylight Time] chat: ssh ["-oNumberOfPasswordPrompts=1","-p","22","db48x@eambar.db48x.net","sh -c 'mkdir -p '\"'\"'annex'\"'\"'&&cd '\"'\"'annex'\"'\"'&&if [ ! -d .git ]; then if [ -x ~/.ssh/git-annex-wrapper ]; then ~/.ssh/git-annex-wrapper git init --bare --shared; else git init --bare --shared; fi && if [ -x ~/.ssh/git-annex-wrapper ]; then ~/.ssh/git-annex-wrapper git config receive.denyNonFastforwards; else git config receive.denyNonFastforwards; fi ;fi&&mkdir -p ~/.ssh&&if [ ! -e ~/.ssh/git-annex-shell ]; then (echo '\"'\"'#!/bin/sh'\"'\"';echo '\"'\"'set -e'\"'\"';echo '\"'\"'if [ \"x$SSH_ORIGINAL_COMMAND\" != \"x\" ]; then'\"'\"';echo '\"'\"'exec git-annex-shell -c \"$SSH_ORIGINAL_COMMAND\"'\"'\"';echo '\"'\"'else'\"'\"';echo '\"'\"'exec git-annex-shell -c \"$@\"'\"'\"';echo '\"'\"'fi'\"'\"') > ~/.ssh/git-annex-shell; fi&&chmod 700 ~/.ssh/git-annex-shell&&touch ~/.ssh/authorized_keys&&chmod 600 ~/.ssh/authorized_keys&&echo '\"'\"'command=\"env GIT_ANNEX_SHELL_DIRECTORY='\"'\"'\"'\"'\"'\"'\"'\"'annex'\"'\"'\"'\"'\"'\"'\"'\"' ~/.ssh/git-annex-shell\",no-agent-forwarding,no-port-forwarding,no-X11-forwarding,no-pty ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDiPFdIMyYCBmc14f9cUZaG36Zw+NziqX9Z+xGl5GAYq16nORxVc+70Bj+A9cHoHLzTMBJnw7G/f7xJNGbKNgKUPKZohT8AQfg8lnyK8qpyzI2dJB3R0vPBMPxZCBm4IOpdB6ad3B6dUiyNtyMn1hza7GVhIFOsHfGG+K3PGtFgwOz/Zj+2zmcZIL/BHObFsba/yhQxbsjLYPI7mmNV9CLb1+XcR0z2okWvxu28lOrcIXDAdEhp1cjjjpBhwTH1F8/gJcJ6ENBa4JiGt/oEKb1b/pXLaMX6dRjc/gYoy7z0Hw7RD73hH+UtPj5TAeKwoNdaVXdqSsVI+3ql+O5PFTxt db48x@caradhras\n'\"'\"' >>~/.ssh/authorized_keys'"] -"""]] - -> This sounds like it's all down to the newer ssh from cygwin ignoring HOME -> and trying to use /home/user which doesn't work very well outside cygwin. -> -> Since git-annex has switched to not include that ssh any longer, and -> instead use the ssh that's bundled with msysgit, I think this bug is -> closed. [[done]] Upgrading to the latest daily build should fix your -> system's ssh. Please followup if I'm wrong. --[[Joey]] diff --git a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment deleted file mode 100644 index 6db718bf2..000000000 --- a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="anton" - subject="me too" - date="2015-05-07T09:50:09Z" - content=""" -I get similar results on Windows, but I only use the command line. For some reason git-annex ignores the ssh-agent settings (SSH_AUTH_SOCK=...) and uses the wrong path for the ssh config dir -- /home/username/.ssh (that probably doesn't exist) -- instead of c:/Users/username/.ssh (or whatever it really is). Your issue is probably that ssh wrongly looks for known_hosts in /home/username/.ssh and asks whether you wan't to accept the unknown host key. - -SSH works when ran by git itself (like git clone/push/fetch), also for rsync, but seemingly not git-annex. -"""]] diff --git a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_2_0562eb168f7a35262a24346030c4fa9f._comment b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_2_0562eb168f7a35262a24346030c4fa9f._comment deleted file mode 100644 index 9089921ec..000000000 --- a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_2_0562eb168f7a35262a24346030c4fa9f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-05-07T18:26:25Z" - content=""" -See [[rsync_on_windows_broken_by_upgrade]] which is the inverse of this -bug. -"""]] diff --git a/doc/bugs/webapp_missing_on_redhat.mdwn b/doc/bugs/webapp_missing_on_redhat.mdwn deleted file mode 100644 index ad2578b4f..000000000 --- a/doc/bugs/webapp_missing_on_redhat.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -### Please describe the problem. -I am unable to run the webapp on redhat6.5 - -### What steps will reproduce the problem? -yum install git-annex - -### What version of git-annex are you using? On what operating system? -I am using git-annex version 3.20120523 and on redhat 6.5 - -### Please provide any additional information below. -I am seeing the following error when running git annex webapp: - -git-annex: unknown command webapp - -> git-annex can be built without the webapp, and this is -> often done if a distribution does not have the full haskell stack -> packaged yet. The solution is to contact the distribution and let them -> know they need to improve it, and/or use the standalone build from this -> website. -> -> So, please file a bug on redhat. [[done]] --[[Joey]] diff --git a/doc/bugs/webapp_on_windows_7_64_bit_fail_to_add_server_repo.mdwn b/doc/bugs/webapp_on_windows_7_64_bit_fail_to_add_server_repo.mdwn deleted file mode 100644 index c076dfc54..000000000 --- a/doc/bugs/webapp_on_windows_7_64_bit_fail_to_add_server_repo.mdwn +++ /dev/null @@ -1,76 +0,0 @@ -### Please describe the problem. -Cant add Server repo - -### What steps will reproduce the problem? -install linux prebuild torball on server (readynas pro 600) -un-tar and run with ./git-annex -(git-annex test pass without error) -install windows client on win7 64 bit and start webapp -try add server repo as second repo will led to an internal server error about gpg - -followed the assistend video -### What version of git-annex are you using? On what operating system? -Readynas (Linux): -annex@readynas-pro:~/git-annex.linux$ ./git-annex version -git-annex version: 5.20140831-g62e6ad8 -build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL -remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external - -Windows: -Version: 5.20140914-gb169612 -Build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash - -Git on Windows: -C:\Users\Xaver>git --version -git version 1.9.4.msysgit.1 - -GPG on Windows: -C:\Users\Xaver>gpg --version -gpg (GnuPG) 2.0.26 (Gpg4win 2.2.2) -libgcrypt 1.6.1 -Copyright (C) 2013 Free Software Foundation, Inc. -License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> -This is free software: you are free to change and redistribute it. -There is NO WARRANTY, to the extent permitted by law. - -Home: C:/Users/Xaver/AppData/Roaming/gnupg -Unterstützte Verfahren: -Öff. Schlüssel: RSA, ELG, DSA -Verschlü.: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, - CAMELLIA128, CAMELLIA192, CAMELLIA256 -Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 -Komprimierung: nicht komprimiert, ZIP, ZLIB, BZIP2 -### Please provide any additional information below. -Internal Server Error -user error (gpg ["--quiet","--trust-model","always","--with-colons","--list-secret-keys","--fixed-list-mode"] exited 2) - -gpg: fatal: can't create directory `/home/Xaver/.gnupg': No such file or directory - -makes no sense on windows machine - -must be like "C:\Users\Xaver\AppData\Roaming\gnupg" or %Username%\AppData\Roaming\gnupg I guess. - -gpg itself works fine I use it with thunderbird - -[[!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 -gpg: WARNING: using insecure memory! -gpg: please see http://www.gnupg.org/documentation/faqs.html for more information -gpg: fatal: can't create directory `/home/Xaver/.gnupg': No such file or directory -secmem usage: 0/0 bytes in 0/0 blocks of pool 0/65536 -14/Sep/2014:23:17:08 +0200 [Error#yesod-core] user error (gpg ["--quiet","--trust-model","always","--with-colons","--list-secret-keys","--fixed-list-mode"] exited 2) @(yesod-core-1.2.19:Yesod.Core.Class.Yesod .\Yesod\Core\Class\Yesod.hs:503:5) - -# End of transcript or log. -"""]] - -> Thanks for reporting this problem. I've fixed it to not crash when gpg -> fails to list secret keys. -> -> That doesn't fix the problem that the cygnus build of gpg does not find -> the user's home directory properly. But that's only needed for the -> encrypted repository (gcrypt) support, which is listed in -> [[windows_support]] as not yet available for Windows. -> -> So, not leaving this bug report open. [[done]] --[[Joey]] diff --git a/doc/bugs/weird_entry_in_process_list.mdwn b/doc/bugs/weird_entry_in_process_list.mdwn deleted file mode 100644 index 4efa3f8d8..000000000 --- a/doc/bugs/weird_entry_in_process_list.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -### Please describe the problem. - -The standalone linux binaries do not show up as `git-annex` in the process list, but as `ld-linux-x86-64` - it's pretty confusing! - -### What steps will reproduce the problem? - -Install the standalone binaries from downloads.kitenet.net, run git-annex. - -### What version of git-annex are you using? On what operating system? - -Today's snapshot from downloads.k.n. - -### 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 -root@koumbit-mp-test:/var/isuma/media/video# top -b -n 1 | head -10 -top - 14:00:09 up 15 days, 23:25, 4 users, load average: 1.18, 1.26, 1.34 -Tasks: 216 total, 1 running, 213 sleeping, 0 stopped, 2 zombie -Cpu(s): 0.4%us, 0.1%sy, 0.0%ni, 99.3%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st -Mem: 6122044k total, 5469364k used, 652680k free, 321080k buffers -Swap: 2928632k total, 0k used, 2928632k free, 4009592k cached - - PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND -28261 root 20 0 4528 652 528 D 79 0.0 0:01.28 ld-linux-x86-64 - 1381 root 20 0 126m 13m 4060 S 2 0.2 190:25.64 Xorg - 1 root 20 0 8356 812 684 S 0 0.0 0:05.50 init -root@koumbit-mp-test:/var/isuma/media/video# ps axf | grep annex - 9861 pts/2 S+ 0:00 | \_ git annex add hd high high~ ipod ipod~ large low mp4_sd raw small wc xlarge - 9862 pts/2 Sl+ 3:50 | \_ /opt/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /opt/git-annex.linux//etc/ld.so.conf.d:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/opt/git-annex.linux//usr/lib:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu:/opt/git-annex.linux//lib64:/opt/git-annex.linux//lib/x86_64-linux-gnu: /opt/git-annex.linux/shimmed/git-annex/git-annex add hd high high~ ipod ipod~ large low mp4_sd raw small wc xlarge - 9878 pts/2 S+ 0:00 | \_ /opt/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /opt/git-annex.linux//etc/ld.so.conf.d:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/opt/git-annex.linux//usr/lib:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu:/opt/git-annex.linux//lib64:/opt/git-annex.linux//lib/x86_64-linux-gnu: /opt/git-annex.linux/shimmed/git/git --git-dir=.git --work-tree=. check-attr -z --stdin annex.backend annex.numcopies -- - 9881 pts/2 S+ 0:01 | \_ /opt/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /opt/git-annex.linux//etc/ld.so.conf.d:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/opt/git-annex.linux//usr/lib:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu:/opt/git-annex.linux//lib64:/opt/git-annex.linux//lib/x86_64-linux-gnu: /opt/git-annex.linux/shimmed/git/git --git-dir=.git --work-tree=. cat-file --batch - 9882 pts/2 S+ 0:00 | \_ /opt/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /opt/git-annex.linux//etc/ld.so.conf.d:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/opt/git-annex.linux//usr/lib:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu:/opt/git-annex.linux//lib64:/opt/git-annex.linux//lib/x86_64-linux-gnu: /opt/git-annex.linux/shimmed/git/git --git-dir=.git --work-tree=. cat-file --batch -28293 pts/2 R+ 0:00 | \_ /opt/git-annex.linux//lib64/ld-linux-x86-64.so.2 --library-path /opt/git-annex.linux//etc/ld.so.conf.d:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/opt/git-annex.linux//usr/lib:/opt/git-annex.linux//usr/lib/x86_64-linux-gnu:/opt/git-annex.linux//lib64:/opt/git-annex.linux//lib/x86_64-linux-gnu: /opt/git-annex.linux/shimmed/sha256sum/sha256sum .git/annex/misctmp/videonew9862 -# End of transcript or log. -"""]] - -couldn't it alter its process name to make this a little more intuitive? This is especially problematic because i am trying to hook git-annex into Puppet and Facter, which require me to guess where the various git-annex repos are on the server. The way i was doing that so far was with `lsof -c 'git-annex' -F0tn`, which is obviously failing under those circumstances.... Unless there's a better way to find those repos across the system? I assume there's a git-annex assistant running here... --[[anarcat]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment b/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment deleted file mode 100644 index 95fe6cf79..000000000 --- a/doc/bugs/weird_entry_in_process_list/comment_1_61e1fc604b49964ef97f31c9d5546afc._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-16T23:35:08Z" - content=""" -Haskell programs actually cannot alter their process name. I've had a bug -open on ghc for a year about that. - -However, I can make a nicer symlink name than ld-linux.so, and use that, -and it will then be clear what program is being run, although the -parameters to it will still be unusual due to the shimming used in the -standalone build. -"""]] diff --git a/doc/bugs/weird_entry_in_process_list/comment_2_3a551d0144ac55aa54a5d087a705fc28._comment b/doc/bugs/weird_entry_in_process_list/comment_2_3a551d0144ac55aa54a5d087a705fc28._comment deleted file mode 100644 index d0078d7bb..000000000 --- a/doc/bugs/weird_entry_in_process_list/comment_2_3a551d0144ac55aa54a5d087a705fc28._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-02-17T21:39:23Z" - content=""" -Re finding repos, if the assistant is configured to automatically -start managing the repo at boot/login, the repo will be -listed in ~/.config/git-annex/autostart -"""]] diff --git a/doc/bugs/weird_entry_in_process_list/comment_3_0b571abbd2fc18eabd053a07ab46e0fe._comment b/doc/bugs/weird_entry_in_process_list/comment_3_0b571abbd2fc18eabd053a07ab46e0fe._comment deleted file mode 100644 index 21dd57534..000000000 --- a/doc/bugs/weird_entry_in_process_list/comment_3_0b571abbd2fc18eabd053a07ab46e0fe._comment +++ /dev/null @@ -1,27 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="still broken, imho - possible fixes and workarounds" - date="2015-08-11T21:43:32Z" - content=""" -it doesn't look like this is really fixed now: - -<pre> -# ps axfuww | grep git-annex | head -1 -www-data 3277 0.1 0.5 704928 35804 ? Sl aoû07 11:11 /usr/lib/git-annex.linux/exe/git-annex --library-path /usr/lib/git-annex.linux//usr/lib/x86_64-linux-gnu/gconv:/usr/lib/git-annex.linux//usr/lib/x86_64-linux-gnu/audit:/usr/lib/git-annex.linux//etc/ld.so.conf.d:/usr/lib/git-annex.linux//lib64:/usr/lib/git-annex.linux//usr/lib:/usr/lib/git-annex.linux//lib/x86_64-linux-gnu:/usr/lib/git-annex.linux//usr/lib/x86_64-linux-gnu: /usr/lib/git-annex.linux/shimmed/git-annex/git-annex assistant -</pre> - -this is pretty nasty... ;) i use this stupid sed trick to remove some of the noise: - -<pre> -# ps axfuww | sed -e 's/--library-path.*git-annex//'| grep annex | head -1 -www-data 3277 0.1 0.5 704928 35804 ? Sl aoû07 11:11 /usr/lib/git-annex.linux/exe/git-annex assistant -</pre> - -still.. it would be nice to be able to have a cleaner process table, especially since it seems the standalone build is pretty much a must nowadays. - -can we see what is the URL to that GHC bug report? - -there seems to be an horrible, C-based hack documented here that could help: http://stackoverflow.com/questions/26657699/how-to-change-the-name-of-a-haskell-process-under-linux - -thanks! -"""]] diff --git a/doc/bugs/weird_entry_in_process_list/comment_3_84ef8c257fd7bbd1db4ac124af241929._comment b/doc/bugs/weird_entry_in_process_list/comment_3_84ef8c257fd7bbd1db4ac124af241929._comment deleted file mode 100644 index c7a7e1a28..000000000 --- a/doc/bugs/weird_entry_in_process_list/comment_3_84ef8c257fd7bbd1db4ac124af241929._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-08-11T22:54:48Z" - content=""" -I made it "more intuitive", to the extent reasonably possible. - -I don't see why the standalone build is a must. Builds of current versions of -git-annex are available from many distributions. - -That C hack would work, but I'm not at all convinced that it's worth adding -such a potentially fragile hack for such a minor inconvenience. - -The GHC bug report is <https://ghc.haskell.org/trac/ghc/ticket/9143>. -"""]] diff --git a/doc/bugs/weird_entry_in_process_list/comment_5_3771422efb065ffc71e6e7ce39610599._comment b/doc/bugs/weird_entry_in_process_list/comment_5_3771422efb065ffc71e6e7ce39610599._comment deleted file mode 100644 index 2def6afc8..000000000 --- a/doc/bugs/weird_entry_in_process_list/comment_5_3771422efb065ffc71e6e7ce39610599._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="thanks" - date="2015-08-12T00:22:31Z" - content=""" -thanks for the URL for the GHC bug report, hopefully that can be worked out eventually - but i'm not holding my breath... :) - -as for standalone, builds for the distribution i am interested in (debian and ubuntu, mainly) are too out of date for my needs. Debian wheezy has a backport from october 2014 and jessie doesn't have a recent backport either, having only a version from november available. Ubuntu packages are also [pretty old](https://launchpad.net/ubuntu/+source/git-annex) as well, with 3.201204 in the Precise LTS and 5.2014 in Trusty LTS... Package uploads only started resuming in Debian unstable something like a month ago (which is a welcome change). - -Basically, because we require 5.20150610 for the public amazon S3 support, we are stuck using the neurodebian standalone builds, so we are stuck with this bug. My feeling is that git-annex is still under rapid development, and the older versions become stale quite quickly. I know this can only stabilise over time, but this makes the standalone builds a must for my projects right now... - -but i understand why the C hack isn't considered at this point, thanks for looking into this again so quickly. -"""]] diff --git a/doc/bugs/wget_and_android_4.4.mdwn b/doc/bugs/wget_and_android_4.4.mdwn deleted file mode 100644 index a695bc978..000000000 --- a/doc/bugs/wget_and_android_4.4.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. -audio file won't download when it's sole source is the internet - -### What steps will reproduce the problem? -on my laptop git annex addurl --fast http://path/to/file.mp3 in folder phone/ -sync to homeserver -sync to phone -phone is set to prefer phone/* and present -after the phone receives the sync from homeserver, it looks to start the download and fails. -https://www.dropbox.com/s/ozcwub2mzo40z4y/2014-01-12%2012.36.01.png -> says wget doesn't recognize option --clobber - -https://www.dropbox.com/s/x1jhb6rcp17c7t8/2014-01-12%2013.13.56.png -> git annex get . -d output - -### What version of git-annex are you using? On what operating system? -android is version 5.20131230-g4aa88d8 for android 4.3+ - -### 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. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files.mdwn b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files.mdwn deleted file mode 100644 index 2a756cc4d..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files.mdwn +++ /dev/null @@ -1,55 +0,0 @@ -### Please describe the problem. -I've a undirect repository that I sync with a direct one (that is on a -crippled filesystem). My repository contain tex file that are directly -in git, and binary file that are annexed. - -If I create or modify an standard git files in my undirect repository, -then sync it with the direct repository, the new file is not created -there, or the modified file is deleted there. - - -### What steps will reproduce the problem? - - $ cd direct - $ echo foo > bar.tex - $ git commit bar.tex -m "new tex file" - $ git annex sync - $ cd /media/direct-repo - $ git annex sync - $ ls bar.tex - -There the bar.tex file don't exist, and the next `git annex sync` will -commit the change. - -The problem exist for some time (I first believed I add a problem with -my usb stick), but now that direct repository are treated somewhat as -bare repository, I don't know of an easy fix. - -### What version of git-annex are you using? On what operating system? - -On Debian, since at least git annex 5.20131120 I believe. - -### 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 -mkdir direct -cd direct -git init && git annex init "direct" -git annex direct -cd .. -git clone direct indirect -cd indirect -git annex init "indirect" -echo bla > test.tex -git add test.tex -git commit -m "test" -git annex sync -cd ../direct -git annex sync -ls -# End of transcript or log. -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_1_6c9f5fe14e46ac96254426e1e9cff23f._comment b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_1_6c9f5fe14e46ac96254426e1e9cff23f._comment deleted file mode 100644 index b3f10176d..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_1_6c9f5fe14e46ac96254426e1e9cff23f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnm19dBCRphmtjXfopm_NpvnRwz-qIJ2Tw" - nickname="Remi" - subject="Checking out the file" - date="2013-12-03T10:29:40Z" - content=""" -If I run `GIT_WORK_TREE=/media/direct-repo git checkout bar.tex` I have my file back. -"""]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_2_04dfbf4b1f6b545075d50f43b1d73ef6._comment b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_2_04dfbf4b1f6b545075d50f43b1d73ef6._comment deleted file mode 100644 index e0ff4c5c5..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_2_04dfbf4b1f6b545075d50f43b1d73ef6._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmLdL4zLty4fsfaIXNtPMS5RXs4y8OAk0o" - nickname="Marc" - subject="Similar problem" - date="2013-12-08T12:30:12Z" - content=""" -I've described the same (or similar) problem here: -http://git-annex.branchable.com/tips/replacing_Sparkleshare_or_dvcs-autosync_with_the_assistant/#comment-015d93573c7c34d10f3815a22bdc13c0 -"""]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_3_f449f259f076ea1b11bd289bdbcc9339._comment b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_3_f449f259f076ea1b11bd289bdbcc9339._comment deleted file mode 100644 index 3aadbc513..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_3_f449f259f076ea1b11bd289bdbcc9339._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnpmMRq6lo2NBrlmoxZQljaU_IaWsWB7qw" - nickname="Lukas" - subject="direct mode and vanishing files" - date="2013-12-10T12:40:51Z" - content=""" -Hi - -I have the same problem with git-annex 4.20131106 on debian jessie (powerpc) in direct mode and 4.20131101 on mac osx 10.8.5 (self compiled from haskell) in indirect mode. -Files directly added to git on the mac (indirect mode) are not created in the direct repository and are removed in the indirect repo after the next sync roundtrip. - -Thanks a lot for all your efforts and greetings, Lukas -"""]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_4_78ccd70a17d776f14ea9193ab55c6732._comment b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_4_78ccd70a17d776f14ea9193ab55c6732._comment deleted file mode 100644 index 20992d2ab..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_4_78ccd70a17d776f14ea9193ab55c6732._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 4" - date="2013-12-12T19:56:50Z" - content=""" -I have fixed this bug. I apologise for the trouble. - -I did not try to make it clean up, so I recommend doing the checkout as shown above, or doing a `git revert` to get the file added back, if you experienced this bug. -"""]] diff --git a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_5_95fcc19327b57222844302bb81236ee9._comment b/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_5_95fcc19327b57222844302bb81236ee9._comment deleted file mode 100644 index af319430a..000000000 --- a/doc/bugs/when_syncing_a_direct_repository__44___git_annex_delete_non_annexed_new_git_files/comment_5_95fcc19327b57222844302bb81236ee9._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmLdL4zLty4fsfaIXNtPMS5RXs4y8OAk0o" - nickname="Marc" - subject="comment 5" - date="2013-12-13T15:43:46Z" - content=""" -That's great, Joey, thanks a lot! -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode.mdwn b/doc/bugs/whereis_does_not_work_in_direct_mode.mdwn deleted file mode 100644 index 824c91afd..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode.mdwn +++ /dev/null @@ -1,91 +0,0 @@ -### Please describe the problem. - -`git annex whereis` says that there are no copies of any of the files that have been added in repositories running in direct mode when `annex.alwayscommit` is set to `false`. - -In other words, if I add a file from PC1 in direct mode, `whereis` in PC2 will fail. Instead, if I add the same file from PC1 in indirect mode, `whereis` in PC2 will work correctly and will report that the file is present in PC1. - -This is the error received in PC2: - - $ git annex whereis - whereis fileA (0 copies) failed - whereis fileB (0 copies) failed - git-annex: whereis: 2 failed - -### What steps will reproduce the problem? - -The following script (available at <https://gist.github.com/gioele/dde462df89edfe17c5e3>) will reproduce this problem. - -[[!format sh """ -#!/bin/sh -x - -set -e ; set -u -export LC_ALL=C - -# alwayscommit must be set globally to affects whereis and sync -git config --global annex.alwayscommit false - -direct=true # set to false to make the problem disappear - -h=${h:-localhost} -dr="/tmp/annex" - -sync='sync -c annex.alwayscommit=true' - -chmod a+rwx -R pc1 pc2 || true -rm -Rf pc1 pc2 - -# create central git repo -ssh $h "chmod a+rwx -R ${dr}/Docs.git" || true -ssh $h "rm -Rf ${dr}/Docs.git" -ssh $h "mkdir -p ${dr}/Docs.git" -ssh $h "cd ${dr}/Docs.git ; git init --bare" - -d=$(pwd) - -# populate repo in PC1 -mkdir -p pc1/Docs -cd pc1/Docs -echo AAA > fileA -echo BBB > fileB - -git init -git remote add origin $h:$dr/Docs.git -git fetch --all - -# simulate a host without git-annex -git config remote.origin.annex-ignore true - -git annex init "pc1" -git annex info - -$direct && git annex direct - -git annex add . -git annex $sync origin - -# re-create repo on PC2 -cd $d -mkdir -p pc2 -cd pc2 -git clone $h:$dr/Docs.git -cd Docs - -git config remote.origin.annex-ignore true - -git annex init "pc2" -git annex info - -git annex whereis || true -echo "I was expecting location info to be available after info (press Enter)" ; read enter - -git annex $sync origin - -git annex whereis || true -echo "Why isn't location info available even after sync? (press Enter)" -"""]] - -### What version of git-annex are you using? On what operating system? - -git-annex version: 5.20140716-g8c14ba8 - -> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_1_f119d2b322a7b33c08b8187deba690c2._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_1_f119d2b322a7b33c08b8187deba690c2._comment deleted file mode 100644 index 5775addc0..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_1_f119d2b322a7b33c08b8187deba690c2._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 1" - date="2014-08-12T17:29:16Z" - content=""" -I don't seem to reproduce this bug when I run the script provided. - -<pre> -whereis fileA (1 copy) - c311d5b9-2f59-4153-a0e5-61707edd28ef -- pc1 -ok -whereis fileB (1 copy) - c311d5b9-2f59-4153-a0e5-61707edd28ef -- pc1 -ok -</pre> -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_2_d1005e29c32bddad109dd426d4dd8803._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_2_d1005e29c32bddad109dd426d4dd8803._comment deleted file mode 100644 index d139aed36..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_2_d1005e29c32bddad109dd426d4dd8803._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 2" - date="2014-08-12T17:33:25Z" - content=""" -It seems to me that there are only 3 ways that pc2 could not know that pc1 has the file, in decreasing order of probability: - -1. pc1 has not pushed git-annex branch to origin (or pushed it after pc2 pulled) -2. pc2 has not fetched git-annex branch from origin -3. an actual bug, such as bad info being written to the git-annex branch or the git-annex branch merge failing - -So, if you have 3 repositories that exhibit a problem like this, those are the things to check. -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_3_44dd6e0c6e7a7abd6483a4367baa7f0f._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_3_44dd6e0c6e7a7abd6483a4367baa7f0f._comment deleted file mode 100644 index 6fb3b8046..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_3_44dd6e0c6e7a7abd6483a4367baa7f0f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="comment 3" - date="2014-08-13T06:36:52Z" - content=""" -This is strange: I can replicate the problem on three different Ubuntu machines (12.04.5 32 and 64 bit, 14.04 64 bit) using that script. - -I attached to the gist [the execution log in direct mode](https://gist.github.com/gioele/dde462df89edfe17c5e3#file-annex-direct-log) (where the bug is shown), the [log in indirect mode](https://gist.github.com/gioele/dde462df89edfe17c5e3#file-annex-indirect-log) (where the bug does not appear), and a [diff between the two](https://gist.github.com/gioele/dde462df89edfe17c5e3#file-log-diff). I hope this helps. -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_4_f334a85d6dd6c4971f0609ae0831766a._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_4_f334a85d6dd6c4971f0609ae0831766a._comment deleted file mode 100644 index ffbbcc12a..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_4_f334a85d6dd6c4971f0609ae0831766a._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="comment 4" - date="2014-08-13T06:40:12Z" - content=""" -Talking about the three possible causes for this bug, - -> 1) pc1 has not pushed git-annex branch to origin (or pushed it after pc2 pulled) - -pc1 pushes using `git annex sync -c annex.alwayscommit=true origin`. This should be enough, isn't it? - -> 2) pc2 has not fetched git-annex branch from origin - -The pc2 repository is created with `git clone localhost:/tmp/annex/Docs.git`, so there branches should all be there. I tried adding a `git fetch --all` to the script but it makes no difference. This is the list of branches in pc2: - - * master - remotes/origin/HEAD -> origin/master - remotes/origin/master - remotes/origin/synced/git-annex - remotes/origin/synced/master - -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment deleted file mode 100644 index 5873167be..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://svario.it/gioele" - nickname="gioele" - subject="comment 5" - date="2014-08-31T10:15:30Z" - content=""" -I have found out that there is a connection between this problem and the _global_ configuration of `annex.alwayscommit`. This problem will appear only if `annex.alwayscommit` is globally set to `false`. What is very strange is that setting `annex.alwayscommit` locally does not make this bug appear; only a globally set `annex.alwayscommit` will trigger this problem. - -I fixed the test script to set `annex.alwayscommit` globally. - -Now I see why I could reproduce this bug on different machines but Joey could not: all my machines have the same `~/.gitconfig`. -"""]] diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_6_7f68d9daa542f992c61b7b7c36819933._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_6_7f68d9daa542f992c61b7b7c36819933._comment deleted file mode 100644 index 7f5fa824e..000000000 --- a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_6_7f68d9daa542f992c61b7b7c36819933._comment +++ /dev/null @@ -1,49 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.132" - subject="comment 6" - date="2014-09-11T18:34:02Z" - content=""" -It looks like there might be some minor inconsistency in when git-annex syncs when in indirect mode vs direct mode. This results in the location tracking information not being committed until after the git-annex sync in the pc1/Docs repository has pushed the git-annex branch to origin. Since that is the only -time that pc1/Docs syncs with origin, the location tracking info never reaches origin, and the rest of the behavior follows. - -Here is the direct mode sync, showing the git-annex branch commit occurring after the push. Specifically, when the sync merges the git-annex branch, it also commits any deferred changes at that point: - -<pre> -commit ok -pull origin -ok -push origin -Counting objects: 6, done. -Delta compression using up to 4 threads. -Compressing objects: 100% (5/5), done. -Writing objects: 100% (6/6), 574 bytes | 0 bytes/s, done. -Total 6 (delta 0), reused 0 (delta 0) -To localhost:/tmp/annex/Docs.git - * [new branch] git-annex -> synced/git-annex - * [new branch] annex/direct/master -> synced/master -ok -(Recording state in git...) -</pre> - -And here is the indirect mode sync, showing a \"commit\" which includes committing deferred changes to the git-annex branch: - -<pre> -commit (Recording state in git...) -ok -pull origin -ok -push origin -Counting objects: 15, done. -Delta compression using up to 4 threads. -Compressing objects: 100% (12/12), done. -Writing objects: 100% (15/15), 1.32 KiB | 0 bytes/s, done. -Total 15 (delta 0), reused 0 (delta 0) -To localhost:/tmp/annex/Docs.git - * [new branch] git-annex -> synced/git-annex - * [new branch] master -> synced/master -ok -</pre> - -It seems that [[!commit 2cfda59174b9cbc02e87c069982096d44601cd40]] and some subsequent changes accidentially removed the Annex.Branch.commit from the direct mode code path within the first part of `sync`. So, easily fixed. -"""]] diff --git a/doc/bugs/windows_install_failure.mdwn b/doc/bugs/windows_install_failure.mdwn deleted file mode 100644 index 5253468f1..000000000 --- a/doc/bugs/windows_install_failure.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -### Please describe the problem. -When installing the windows aplha dated 2013-06-21 12:17 it gives an error: - -Error opening file for writing: -c:\program files (x86)\Git\cmd\git-annex.exe -Abort,retry or ignore? - -If you run as administrator it works. - - - -### What steps will reproduce the problem? - -Download the alpha installer and run as normal user. - -### What version of git-annex are you using? On what operating system? -Windows 7 64 bit - - -### 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. -"""]] - -[[!meta title="windows installer fails unless run as admin user"]] - -> [[dup|done]] of -> [[git-annex_does_not_install_on_windows_without_admin_rights]] --[[Joey]] diff --git a/doc/bugs/windows_install_failure/comment_1_f339574c7cfa35c1f0dfd515fde457f5._comment b/doc/bugs/windows_install_failure/comment_1_f339574c7cfa35c1f0dfd515fde457f5._comment deleted file mode 100644 index a1e10da20..000000000 --- a/doc/bugs/windows_install_failure/comment_1_f339574c7cfa35c1f0dfd515fde457f5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnI6EUnvCSB6JG3KsjCDpBIBWYniaZkhXs" - nickname="Jason" - subject="expected behavior" - date="2013-06-27T02:44:37Z" - content=""" -I expect it should automatically ask for privileged escalation rather than fail. -"""]] diff --git a/doc/bugs/windows_install_failure/comment_2_1d3364d8f5c4963f3a7e473298ec6ed1._comment b/doc/bugs/windows_install_failure/comment_2_1d3364d8f5c4963f3a7e473298ec6ed1._comment deleted file mode 100644 index 84966d647..000000000 --- a/doc/bugs/windows_install_failure/comment_2_1d3364d8f5c4963f3a7e473298ec6ed1._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnrFnHRRNUQBB5RCDaIwhVmCcxQp8_yiYw" - nickname="Oliver" - subject="comment 2" - date="2013-06-28T08:37:39Z" - content=""" -Indeed, but the windows installer (whether built by hand or from the prebuilts) does not. Might have a poke at it when I'm back at my machine again - should be a fairly easy fix. -"""]] diff --git a/doc/bugs/windows_isExecutable_fail.mdwn b/doc/bugs/windows_isExecutable_fail.mdwn deleted file mode 100644 index 41e5b29a2..000000000 --- a/doc/bugs/windows_isExecutable_fail.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -On Windows, isExecutable fails to detect a file that is indeed executable -as such. This prevents git-annex from running the pre-commit-hook -on Windows. - -getFileStatus yields a fileMode of 100666, which is -clearly a dummy mode. Not surprising, since unix-compat is partial stubs -on windows. - -Actually, isExecutable is ok (it needs to check unix modes because it is -used on file modes coming out of git). But, getFileStatus is the wrong -thing to be using on Windows to check if a hook exists and is executable. - -I don't see anything in Win32 or Win32-extras on hackage that can check -executablility. Looking at git's source, it uses `access(path, X_OK) < 0`; -haskell equivilant is System.Posix.Files.fileAccess, but the version -in unix-compat has the same problem as checking getFileStatus's fileMode. - -I think it's reasonable to assume that if a hook exists on windows, it's -intended to be executable, and try to run it. Actually, testing with -msysgit, it runs hooks whether or not they have the execute bit set! -So, done that now. - -However, now git-annex tries to run the hook but fails when it's a shell -script because #!/bin/sh is useless on windows. It looks to me like msysgit -runs "sh hook" to work around that, and it is in fact parsing the shebang -line and dispatching the interpreter. Ugh. (Also, pre-commit.bat doesn't -get run.) Ok, added this same hack to git-annex. [[done]] --[[Joey]] diff --git a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter.mdwn b/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter.mdwn deleted file mode 100644 index 9c8f1b5ba..000000000 --- a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -### Please describe the problem. -When git-annex is started using one of its start menu shortcuts (git-annex or git-annex-autostart) wscript.exe calls itself in an infinite loop. This is also described under the [section ".vbs failure" in a forum post](https://git-annex.branchable.com/forum/Windows_installation_notes/). - -### What steps will reproduce the problem? -Install git and git-annex according to the [installation guide](https://git-annex.branchable.com/install/Windows/). Click on one of the shortcuts in the start menu. - -### What version of git-annex are you using? On what operating system? -git version 1.9.5.msysgit.1. git-annex version: 5.20150317-g237d5b0. Windows 7 Professional, 64-bit. - -### Please provide any additional information below. - -This seems to be fixed by editing the shortcuts and setting the "Start in" parameter to the git installation directory. For me this is "C:\Program Files (x86)\Git". - -> I've renamed it. The old git-annex.lnk will be -> deleted by the installer if it exists. [[done]] --[[Joey]] diff --git a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_1_5af705ddb453588711f3e70b2e297f55._comment b/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_1_5af705ddb453588711f3e70b2e297f55._comment deleted file mode 100644 index 2922515d6..000000000 --- a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_1_5af705ddb453588711f3e70b2e297f55._comment +++ /dev/null @@ -1,28 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-09T18:15:31Z" - content=""" -Thanks for reporting this. - -Is git in your path? (Ie, can you run git from command.exe?) - -I notice that the -<http://git-annex.branchable.com/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/> -page, which had this problem, was a user who neglected to have git add -itself to path, contrary to what the installation instructiins say to do. - -So, it's not surprising that disregarding the instructions break, but this -is a bad way for it to break. It would be better to at least avoid the -loop, and perhaps Just Work. - -I don't understand why it loops.. the git-annex-webapp.vbs runs "git-annex -webapp". If git-annex is not in path (because git is not in path and it -piggybacks off git's path settings), that should fail to do anything. -Or is Windows really sufficiently DWIM that it will search for **different -spellings** of program names?! - -I don't see how I can add a "Start in" parameter; git-annex has no way of -knowing where the user intended to install git if they didn't add git to -the path. -"""]] diff --git a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_2_f68896dee17aa663749912e663f10a9f._comment b/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_2_f68896dee17aa663749912e663f10a9f._comment deleted file mode 100644 index 070fbdbad..000000000 --- a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_2_f68896dee17aa663749912e663f10a9f._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eliasson" - nickname="eliasson" - subject="comment 2" - date="2015-04-09T20:43:08Z" - content=""" -Yes, Git is in my path. This is my full (system, not user) path, copied from System Properties->Advanced->Environment Variables: - - C:\ProgramData\Oracle\Java\javapath;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Git\cmd - -I've done some more experimentation now. I believe that in Windows the current working directory is always first in the path. I also think that \"Start in\" sets the CWD of a shortcut and if unset, its CWD is its location in the Start menu. The shortcut is named git-annex.lnk and executes a VBscript that runs \"git-annex webapp\". This is probably why the shortcut executes itself. - -Setting the Start in parameter to anything (doesn't have to be Git's installation directory) *or* renaming the shortcut to something other than git-annex makes it work. A third way of fixing it is to open git-annex-webapp.vbs and changing \"git-annex webapp\" to \"git annex webapp\". I don't know which option is the cleanest solution. - -I take it back that git-annex-autostart loops. I seem to remember that it did on another computer (running a version of git-annex downloaded today) but probably remember wrong. Now I can only reproduce this with the webapp shortcut. - -"""]] diff --git a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_3_6c3e6b1344c533857611c0f6033c0dce._comment b/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_3_6c3e6b1344c533857611c0f6033c0dce._comment deleted file mode 100644 index 77472dcda..000000000 --- a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_3_6c3e6b1344c533857611c0f6033c0dce._comment +++ /dev/null @@ -1,25 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-04-09T20:53:17Z" - content=""" -I'm guessing this doesn't affect XP, so I'm going to need to rely on you -guys for help and testing for the newer Windows.. - -Makes sense about git-annex.lnk trying to run itself, I suppose. Sort of. - -The DSL I'm using to generate the NSIS installer and thus this file -doesn't currently seem to have a way to set the "Start in" parameter. -I can get that added, but it would take a while. - -I don't see any reason not to use the "git annex webapp" approach. -Should be the same as long as git's in path, and if git's not in path, -well. - -Alternatively, though, I could rename the menu item to something else, like -"git-annex-menu.lnk". Seems that would also avoid the problem, and somewhat -more robustly. I don't like this business of conflicting command-names -being in path. Renaming the menu item has the downside of needing a -uninstall/reinstall cycle to avoid getting a duplicate menu item, but -otherwise seems reasonable. -"""]] diff --git a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_4_7bec797548ff4ea270b96f9c0aada62c._comment b/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_4_7bec797548ff4ea270b96f9c0aada62c._comment deleted file mode 100644 index 1b9a4dcf3..000000000 --- a/doc/bugs/windows_start_menu_shortcuts_are_missing___34__Start_in__34___parameter/comment_4_7bec797548ff4ea270b96f9c0aada62c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://launchpad.net/~eliasson" - nickname="eliasson" - subject="comment 4" - date="2015-04-10T15:35:30Z" - content=""" -Perhaps both? Changing the VBscript for existing users, and renaming the link as a more long term solution for new installations. - -I would argue that testing with newer Windows versions than XP is somewhat important. If you need money for a Windows license you could always launch another crowdfunding campaign... -"""]] diff --git a/doc/bugs/wrong_synopsis_in_manpage_of_git_annex_pre-commit.mdwn b/doc/bugs/wrong_synopsis_in_manpage_of_git_annex_pre-commit.mdwn deleted file mode 100644 index f94786b03..000000000 --- a/doc/bugs/wrong_synopsis_in_manpage_of_git_annex_pre-commit.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -The synopsis in the manpage of git annex pre-commit mentions -git annex instead of git annex pre-commit. - -I'll attach a patch to fix the manpage, below: - -[[!format diff """ -From f5fed6ccdcef3bcb8be07691265842d437037dec Mon Sep 17 00:00:00 2001 -From: Felix Gruber <felgru@gmx.de> -Date: Fri, 1 May 2015 02:05:32 +0200 -Subject: [PATCH] fix synopsis in manpage of git annex pre-commit - ---- - doc/git-annex-pre-commit.mdwn | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/doc/git-annex-pre-commit.mdwn b/doc/git-annex-pre-commit.mdwn -index e0f6fdb..bc1e86e 100644 ---- a/doc/git-annex-pre-commit.mdwn -+++ b/doc/git-annex-pre-commit.mdwn -@@ -4,7 +4,7 @@ git-annex pre-commit - run by git pre-commit hook - - # SYNOPSIS - --git annex `[path ...]` -+git annex pre-commit `[path ...]` - - # DESCRIPTION - --- -2.1.4 -"""]] - -> You know, this is a wiki, you could fix it yourself. With git push even. -> In any case [[done]] now. --[[Joey]] diff --git a/doc/bugs/youtube_support_suddenly_stopped_working.mdwn b/doc/bugs/youtube_support_suddenly_stopped_working.mdwn deleted file mode 100644 index bedda7674..000000000 --- a/doc/bugs/youtube_support_suddenly_stopped_working.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -### Please describe the problem. - -[[This|design/assistant/blog/day_314__quvi/]] says that I can download youtube videos with git-annex, but I can't - it downloads the HTML of the page instead! - -### What steps will reproduce the problem? - - git annex addurl http://www.youtube.com/watch?v=BTzNLhxPzjo - -Should have downloaded a Bill Hicks video, instead it downloads the HTML. - -### What version of git-annex are you using? On what operating system? - -[[!format txt """ -git-annex version: 4.20130912-ga1faca3 -build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi -local repository version: 3 -default repository version: 3 -supported repository versions: 3 4 -upgrade supported from repository versions: 0 1 2 -"""]] - -Note that quvi is still capable of fetching that video, no problem there. - -### 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 -anarcat@marcos:clips$ git annex addurl http://www.youtube.com/watch?v=BTzNLhxPzjo -addurl www.youtube.com_watch_v=BTzNLhxPzjo ok -anarcat@marcos:clips$ file www.youtube.com_watch_v\=BTzNLhxPzjo -www.youtube.com_watch_v=BTzNLhxPzjo: broken symbolic link to `.git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b' -anarcat@marcos:clips$ file www.youtube.com_watch_v\=BTzNLhxPzjo ^C -anarcat@marcos:clips$ file .git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b -.git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b: ERROR: cannot open `.git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b' (No such file or directory) -anarcat@marcos:clips$ git annex get www.youtube.com_watch_v\=BTzNLhxPzjo -get www.youtube.com_watch_v=BTzNLhxPzjo (from web...) ---2013-09-14 17:24:23-- http://www.youtube.com/watch?v=BTzNLhxPzjo -Résolution de www.youtube.com (www.youtube.com)... 173.194.43.96, 173.194.43.97, 173.194.43.98, ... -Connexion vers www.youtube.com (www.youtube.com)|173.194.43.96|:80...connecté. -requête HTTP transmise, en attente de la réponse...200 OK -Longueur: non spécifié [text/html] -Sauvegarde en : «/srv/video/clips/.git/annex/tmp/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b» - - [ <=> ] 123 245 346K/s ds 0,3s - -2013-09-14 17:24:23 (346 KB/s) - «/srv/video/clips/.git/annex/tmp/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b» sauvegardé [123245] - -ok -(Recording state in git...) -anarcat@marcos:clips$ file www.youtube.com_watch_v\=BTzNLhxPzjo -www.youtube.com_watch_v=BTzNLhxPzjo: symbolic link to `.git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b' -anarcat@marcos:clips$ file .git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b -.git/annex/objects/qZ/q1/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b/SHA256E-s123162--96fe8634aaf035373077473ac2b166c5ad22bfe099112c414eee9fe753f4ce2b: HTML document, UTF-8 Unicode text, with very long lines -# End of transcript or log. -"""]] - -### Workaround - -Use the `quvi` prefix. - -> Typo introduced in last release. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/youtube_web_download_gives_Prelude.undefined_in_webapp.mdwn b/doc/bugs/youtube_web_download_gives_Prelude.undefined_in_webapp.mdwn deleted file mode 100644 index 2b4a62538..000000000 --- a/doc/bugs/youtube_web_download_gives_Prelude.undefined_in_webapp.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -### Please describe the problem. - -I'm downloading a video with 'git annex addurl' from youtube. The webapp shows the transfer, but when I click the 'web' link it takes me to a page that says "internal server error" and "Prelude.undefined" - -### What steps will reproduce the problem? - -1. start webapp -2. download youtube video -3. click 'web' link on transfer in git-annex - -### What version of git-annex are you using? On what operating system? - -* Version: 5.20140717 -* OS: Debian sid - -### Please provide any additional information below. - -Not much in the logs, I see this: - -[[!format sh """ - -[2014-07-25 08:40:14 BST] TransferWatcher: transfer starting: Download UUID "00000000-0000-0000-0000-000000000001" URL--quvi:https://www.youtube.com/watch,63v,61Z8_8jNLsZms Nothing -[2014-07-25 08:40:14 BST] TransferWatcher: transfer starting: Download UUID "00000000-0000-0000-0000-000000000001" Chase_Adam_at_Startup_School_NY_2014.mp4 Nothing - -"""]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/news/version_5.20150930/comment_1_f77fe435289343ae0511ffceade23ba7._comment b/doc/news/version_5.20150930/comment_1_f77fe435289343ae0511ffceade23ba7._comment deleted file mode 100644 index dd0db2260..000000000 --- a/doc/news/version_5.20150930/comment_1_f77fe435289343ae0511ffceade23ba7._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="jephte.clain@f0da2444b164953b596ac5e3e38da30b8c04e5e3" - nickname="jephte.clain" - subject="thanks" - date="2015-10-01T04:25:02Z" - content=""" -hello, - -thanks, this version works on debian squeeze lts, unlike the previous. this is very good news, and a fine piece of software! - -I wonder: why do you depend on a minimum kernel version? for example, I have a NAS with a very old 2.6.16 embedded linux kernel which cannot be updated, and because of this, I'm stuck with an ancient git-annex version. - -"""]] diff --git a/doc/news/version_5.20150930/comment_2_77faf81efaffb2637cfa0caba1758768._comment b/doc/news/version_5.20150930/comment_2_77faf81efaffb2637cfa0caba1758768._comment deleted file mode 100644 index d4a4bd111..000000000 --- a/doc/news/version_5.20150930/comment_2_77faf81efaffb2637cfa0caba1758768._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="jephte.clain@f0da2444b164953b596ac5e3e38da30b8c04e5e3" - nickname="jephte.clain" - subject="it does not work with debian squeeze lts" - date="2015-10-01T12:13:11Z" - content=""" -hmmm... nope, it still does not work on debian squeeze lts with kernel 2.6.32-5-amd64 (when I tested earlier, I was using a more recent kernel...) -"""]] diff --git a/doc/news/version_5.20150930/comment_3_1cd9afc5c56781844fbff908c910056b._comment b/doc/news/version_5.20150930/comment_3_1cd9afc5c56781844fbff908c910056b._comment deleted file mode 100644 index 8a974ad11..000000000 --- a/doc/news/version_5.20150930/comment_3_1cd9afc5c56781844fbff908c910056b._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 3" - date="2015-10-01T20:14:48Z" - content=""" -There's an \"ancient kernels\" build you can use on those old systems. -"""]] diff --git a/doc/news/version_5.20150930/comment_4_42c068c99a7658bdad61fbb740ffe603._comment b/doc/news/version_5.20150930/comment_4_42c068c99a7658bdad61fbb740ffe603._comment deleted file mode 100644 index 8949b5840..000000000 --- a/doc/news/version_5.20150930/comment_4_42c068c99a7658bdad61fbb740ffe603._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="jephte.clain@f0da2444b164953b596ac5e3e38da30b8c04e5e3" - nickname="jephte.clain" - subject="comment 4" - date="2015-10-03T09:11:02Z" - content=""" -ohh... I see. I have a script that download the latest release and did not notice the new files. - -Can you make an \"ancient kernel\" release for amd64? I don't have any computers with 32bits kernels. thanks in advance - -"""]] diff --git a/doc/news/version_5.20150930/comment_5_f52b7d5c1cffaae12aac1cd7905481a2._comment b/doc/news/version_5.20150930/comment_5_f52b7d5c1cffaae12aac1cd7905481a2._comment deleted file mode 100644 index 02d120701..000000000 --- a/doc/news/version_5.20150930/comment_5_f52b7d5c1cffaae12aac1cd7905481a2._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-10-04T19:31:47Z" - content=""" -The 32 bit build will also work on amd64 as long as the kernel supports -32 bit executables. Are you having some difficulty using that on amd64? -"""]] diff --git a/doc/news/version_5.20150930/comment_6_0141dbe3955b54f9fbfd67dc8ba64f48._comment b/doc/news/version_5.20150930/comment_6_0141dbe3955b54f9fbfd67dc8ba64f48._comment deleted file mode 100644 index 6651d4de9..000000000 --- a/doc/news/version_5.20150930/comment_6_0141dbe3955b54f9fbfd67dc8ba64f48._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="jephte.clain@f0da2444b164953b596ac5e3e38da30b8c04e5e3" - nickname="jephte.clain" - subject="comment 6" - date="2015-10-05T05:48:38Z" - content=""" -wow. I guess I'm getting old... of course the 32bits version run on a 64bits kernel. I should know, I have a lot of binary that I run this way :-| - -thanks again for you valuable time. It's all good now! - -"""]] diff --git a/doc/news/version_5.20151019/comment_1_9e8ab90c2156bded887d534471492c99._comment b/doc/news/version_5.20151019/comment_1_9e8ab90c2156bded887d534471492c99._comment deleted file mode 100644 index 672e8613b..000000000 --- a/doc/news/version_5.20151019/comment_1_9e8ab90c2156bded887d534471492c99._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="anarcat" - subject="comment 1" - date="2015-10-19T19:44:32Z" - content=""" -> Allow building with S3 disabled again. - -I'm confused: is S3 enabled or disabled? :) -"""]] diff --git a/doc/news/version_5.20151019/comment_2_86e58bc881269cb29fcbeefec94f8846._comment b/doc/news/version_5.20151019/comment_2_86e58bc881269cb29fcbeefec94f8846._comment deleted file mode 100644 index 865e6730e..000000000 --- a/doc/news/version_5.20151019/comment_2_86e58bc881269cb29fcbeefec94f8846._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - subject="comment 2" - date="2015-10-19T19:58:36Z" - content=""" -S3 is enabled by default; this version can be built with it disabled if desired -"""]] diff --git a/doc/news/version_5.20151116/comment_1_72d65412edd7af7df1e6e6817b7572c5._comment b/doc/news/version_5.20151116/comment_1_72d65412edd7af7df1e6e6817b7572c5._comment deleted file mode 100644 index 286be07ff..000000000 --- a/doc/news/version_5.20151116/comment_1_72d65412edd7af7df1e6e6817b7572c5._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="jtgeibel@4ad445b2ef940dedb1b6d9b19e3888e56b33541b" - nickname="jtgeibel" - subject="Git tag" - date="2015-11-21T00:38:13Z" - content=""" -Joey, I couldn't find a tag for this in the repo. It appears to be 76139a93. -"""]] diff --git a/doc/news/version_5.20151116/comment_2_6e44ceeb20d008ee3a073a83a21a9dd5._comment b/doc/news/version_5.20151116/comment_2_6e44ceeb20d008ee3a073a83a21a9dd5._comment deleted file mode 100644 index ab88b1b95..000000000 --- a/doc/news/version_5.20151116/comment_2_6e44ceeb20d008ee3a073a83a21a9dd5._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-11-24T14:21:27Z" - content=""" -Hmm, my tag push must have failed at release time. Re-pushed that tag. -"""]] diff --git a/doc/news/version_6.20160114/comment_1_756c63fc0fef191444df98923b4df852._comment b/doc/news/version_6.20160114/comment_1_756c63fc0fef191444df98923b4df852._comment deleted file mode 100644 index dde699d2f..000000000 --- a/doc/news/version_6.20160114/comment_1_756c63fc0fef191444df98923b4df852._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="db48x" - subject="hexapodia!" - date="2016-01-14T21:38:57Z" - content=""" -:D -"""]] diff --git a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo.mdwn b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo.mdwn deleted file mode 100644 index c8c2dd83e..000000000 --- a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -One problem I keep having when using a direct repo is that in order to get to the previous versions of a file you have to convert that repo to indirect and then checkout previous commits this becomes problematic when the repo in question is large conversion takes a long time and applications gets confused if there are open files from the repo as they go from actual files to symlinks. Is it possible to have a separate annex command that will checkout a previous version of a file to a different directory so we can replace/inspect it. - -> I recently added a `git annex proxy` command, which can be used -> to amoung other things, rewind a direct mode repo to have some old -> version checked out. -> -> For example, you can do: `git annex proxy git checkout old-version` -> And then the old version of all annexed files will be checked out. -> -> If the old version of a file is not available, it'll be a broken -> symlink and you can then use `git annex get` etc to get the content from -> some remote. -> -> Once you have the old version of the file, you can -> make a copy, and then switch back to the present with `git annex proxy -> git checkout annex/direct/master`. Then you can add the copy of the old -> version of the file to the repo, or whatever. -> -> Or, sometimes more simply, you can `git annex proxy git revert $commit` -> to revert a commit that made an unwanted change to a file. -> -> Or, simpler still, `git annex undo $file` will undo the last change -> that git-annex committed to that file, bringing back the old version. -> -> So, this seems [[done]]! --[[Joey]] diff --git a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment deleted file mode 100644 index e97e40f62..000000000 --- a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_1_6f477af942aeb98683a56bcf0e819a38._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 1" - date="2014-05-13T20:25:22Z" - content=""" -I’ve added a bug on basically the same issue. -http://git-annex.branchable.com/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__/ - -One problem is that if your direct-mode repo is on VFAT, you can’t even switch to indirect mode temporarily. -"""]] diff --git a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_2_45c22f596a18d5dc2331cfeef8c767fa._comment b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_2_45c22f596a18d5dc2331cfeef8c767fa._comment deleted file mode 100644 index 200210a02..000000000 --- a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_2_45c22f596a18d5dc2331cfeef8c767fa._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 2" - date="2014-05-17T14:18:31Z" - content=""" -It occured to me that one could do something like that by «git show -earlier-commit:file > filename». A problem with this is that a -subsequent «get» will get the old content, but won’t put it in place -until invoking «fsck». - -"""]] diff --git a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_3_cbca264d86fe733b8106a4bf50c0c6ff._comment b/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_3_cbca264d86fe733b8106a4bf50c0c6ff._comment deleted file mode 100644 index 265e0995a..000000000 --- a/doc/todo/A_Way_To_Extract_Previous_Versions_of_a_File_From_a_Direct_Repo/comment_3_cbca264d86fe733b8106a4bf50c0c6ff._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="92.227.51.179" - subject="comment 3" - date="2014-05-17T14:24:20Z" - content=""" -Plus it seems that the file can’t be dropped normally afterwards. -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync.mdwn b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync.mdwn deleted file mode 100644 index d055a3556..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -I like the way btsync search for the peer. So if I need to sync my laptop and other family laptop both with a total different and changing network setup the two device found each other do NAT traversal if needed use relays but the end the two folders are synced. But its closed-source :( I like git and git-annex looks really great. I'm learning it now. - -First I thought with xmpp I can sync files without ssh/rsync or other remote access to my devices just with two jabber account. Now I know I can't. :( - -It would be just great to have some means to sync files without cloud just the two device. Without the ssh / rsync jut share some secret and the devices do the rest. :-o - -Anyway thanks for hearing. I'm looking forward to know more about git-annex. Thank you for that sw. =-<>-= - -> [[design/assistant/telehash]] --[[Joey]] - -> > telehash has been mostly put aside for now, but there are interesting alternatives, including an [[special_remotes/ipfs]] special remote available. see [[todo/Bittorrent-like_features]] for followup on the discussion. so i'm marking this as a [[duplicate|done]]. --[[anarcat]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_1_d828bc374e50a49101c0b863f9b33080._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_1_d828bc374e50a49101c0b863f9b33080._comment deleted file mode 100644 index 13571e681..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_1_d828bc374e50a49101c0b863f9b33080._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkEHjHAWnJ0BJzdv_hePwU1my8X4wCseh8" - nickname="Sz" - subject="comment 1" - date="2013-07-23T11:00:21Z" - content=""" -Why not use xmpp for file transfer too not only for git sync? -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_2_a4badfc248be428e6426a936212cc896._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_2_a4badfc248be428e6426a936212cc896._comment deleted file mode 100644 index 2bff793f0..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_2_a4badfc248be428e6426a936212cc896._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://johan.kiviniemi.name/" - ip="83.145.237.224" - subject="comment 2" - date="2013-07-23T11:37:53Z" - content=""" -Transferring the data over XMPP would almost certainly take too much XMPP server bandwidth, but using something like [libjingle](https://developers.google.com/talk/libjingle/) to set up P2P connections should work nicely. That would require libjingle (or equivalent) bindings for Haskell, though. Libjingle negotiates over XMPP to set up the P2P connection and provides a TCP-like layer for reliable, ordered communication. One could use that for both git metadata and the file transfers. -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_3_0b04089d3d33fdb48eeb46bf168e9a3c._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_3_0b04089d3d33fdb48eeb46bf168e9a3c._comment deleted file mode 100644 index d0c000d2b..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_3_0b04089d3d33fdb48eeb46bf168e9a3c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkEHjHAWnJ0BJzdv_hePwU1my8X4wCseh8" - nickname="Sz" - subject="comment 3" - date="2013-07-24T09:08:45Z" - content=""" -I'm for it! +1 -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_4_2bcab1b7998b4df08fca41b8d810f115._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_4_2bcab1b7998b4df08fca41b8d810f115._comment deleted file mode 100644 index f3bafca89..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_4_2bcab1b7998b4df08fca41b8d810f115._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 4" - date="2013-08-03T07:12:40Z" - content=""" -NAT traversal requires central infrastructure and is unreliable at best. Obviously, a for-profit entity like bittorrent can shoulder that. - -For LAN situations, [zeroconf](http://www.zeroconf.org/) along with passphrase-based pairing may be the long-term answer. Arguably, that would enhance vanilla Git almost as much as it would enhance git-annex, but that does not seem likely to happen. -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_5_677e958c3f2effec7528b484aeb6478d._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_5_677e958c3f2effec7528b484aeb6478d._comment deleted file mode 100644 index 07b001c2e..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_5_677e958c3f2effec7528b484aeb6478d._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA" - nickname="Laszlo" - subject="comment 5" - date="2013-08-25T07:48:18Z" - content=""" -What is the problem with bittorrent protocol in general? -It is some technicality or purely philosophical? - -Best, - Laszlo - -"""]] diff --git a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_6_56e53803fdede895cba717e6b6e9a1bb._comment b/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_6_56e53803fdede895cba717e6b6e9a1bb._comment deleted file mode 100644 index 41e1bda78..000000000 --- a/doc/todo/A_really_simple_way_to_pair_devices_like_bittorent_sync/comment_6_56e53803fdede895cba717e6b6e9a1bb._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" - nickname="develop" - subject="comment 6" - date="2013-08-25T08:39:15Z" - content=""" -I just did a cursory search on haskell torrent support. And the required pieces do seem to be be there. -https://github.com/jlouis/combinatorrent or https://github.com/astro/haskell-torrent for downloading. i'm not sure if either supports DHT, but that exists here https://github.com/aninhumer/haskell-dht - -That said, i think implementing this would require some quite major overhauls in the system. It probably won't be trivial to implement. - -Note: This is for straight \"bittorrent\", not for \"bittorrent sync\". Bittorrent sync is closed source, and while an API might come at some point, it doesn't currently exist. - -I do seem to recall joeyh talking about supporting further transport protocols(perhaps through hooks). So I'm adding the above links for future reference if this does get implemented. - -But IMHO, this doesn't seem like a trivial feature to add. It might have to take some refactoring of some core git-annex parts. Certain things have to be changed quite a bit. - -Currently a git-annex client doesn't really require anything(except rsync) to sync from a remote. With bittorrent with DHT support to share between clients, suddenly git-annex will have to maintain a constant bittorrent thread(maybe multiple) that constantly seeds all the files in the git-annex repository, while waiting for a potential remote to request data. - -So even if this happens, it is probably gonna take some time. - -Just my 2cents. -"""]] diff --git a/doc/todo/Add___39__dir__39___option_to_addurl.mdwn b/doc/todo/Add___39__dir__39___option_to_addurl.mdwn deleted file mode 100644 index 834b6309f..000000000 --- a/doc/todo/Add___39__dir__39___option_to_addurl.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -Is it possible to add a '--dir' option to addurl (or some other mechanic) to make git annex create the symlinks in the specified directory? - -> --prefix makes sense, and might as well also add --suffix. [[done]] -> --[[Joey]] diff --git a/doc/todo/Add___39__dir__39___option_to_addurl/comment_1_0156942b1629ee994bf3699a56b3ceb7._comment b/doc/todo/Add___39__dir__39___option_to_addurl/comment_1_0156942b1629ee994bf3699a56b3ceb7._comment deleted file mode 100644 index 112c4bb6b..000000000 --- a/doc/todo/Add___39__dir__39___option_to_addurl/comment_1_0156942b1629ee994bf3699a56b3ceb7._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-20T16:19:15Z" - content=""" ---file=subdir/foo will work, assuming subdir already exists. - -If the goal is just to add whatever filename addurl comes up with by -default to a subdirectory, why not just `cd` to that subdir before -running addurl? -"""]] diff --git a/doc/todo/Add___39__dir__39___option_to_addurl/comment_2_15a6571d57794c3f1268c7a064e05bef._comment b/doc/todo/Add___39__dir__39___option_to_addurl/comment_2_15a6571d57794c3f1268c7a064e05bef._comment deleted file mode 100644 index 95504b1b2..000000000 --- a/doc/todo/Add___39__dir__39___option_to_addurl/comment_2_15a6571d57794c3f1268c7a064e05bef._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 2" - date="2015-07-21T12:11:45Z" - content=""" -I was hoping something like tar's *-C*, or unzip's *-d* options would be easy to implement, given that git-annex will already create required directories when using --pathdepth. As far as I can tell, you can't mix --file and --pathdepth.. I'd have to reimplemnt --pathdepth and the directory creation in my script, which while not a major problem in Perl (aside from reinventing a potentially inferior wheel), may be if someone is using shell scripting. - -Maybe this request can be more generalised to *--prefix*? - -Then people could use --prefix to either just prefix the filename or set a directory for it to be put into. I had a look at Command/AddUrl.hs to see how feasible that would be but I'm struggling to follow it (not knowing Haskell yet). - -In the meantime(?), I have made my script remember the original directory it was started in and it cd's about as needed. -"""]] diff --git a/doc/todo/Add___39__dir__39___option_to_addurl/comment_3_62601714648631a31dee366a5a2e8f44._comment b/doc/todo/Add___39__dir__39___option_to_addurl/comment_3_62601714648631a31dee366a5a2e8f44._comment deleted file mode 100644 index d521008bc..000000000 --- a/doc/todo/Add___39__dir__39___option_to_addurl/comment_3_62601714648631a31dee366a5a2e8f44._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 3" - date="2015-07-22T07:41:53Z" - content=""" -Yay! Awesome, thank you :) -"""]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider.mdwn b/doc/todo/Add_gitlab.com_as_cloud_provider.mdwn deleted file mode 100644 index 65c14b736..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -Hi, - -[I don't know if this should go to todo or bugs or should be plainly ignored. Hope it's OK]. - -Gitlab.com and Gitlab enterprise edition, but unfortunately not Gitlab community edition, now [provides git annex support](https://about.gitlab.com/2015/02/17/gitlab-annex-solves-the-problem-of-versioning-large-binaries-with-git/). It works fairly based for the repos I have enabled it on. At the moment it's free, but one may have to pay for repos larger than 5Gb [in the future](https://about.gitlab.com/2015/02/22/gitlab-7-8-released/#comment-1870271594). - -Perhaps gitlab.com should be added to preconfigured cloud providers? - -> [[done]] although there are a few known bugs in the webapp's -> implementation. --[[Joey]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment deleted file mode 100644 index ab80ad5ee..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_1_0dad4b86cda93dd5ca0c4fb049ff6d97._comment +++ /dev/null @@ -1,18 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-04T14:23:05Z" - content=""" -This uses ssh, so the repository address can be pasted into the webapp -as a ssh server, and it should work already. - -It probably does make sense to add gitlab.com as a canned solution alongside -box.com and rsync.net in the webapp. - -Since the remote will be a full git repository, it should prompt the user -if they want to enable gcrypt to encrypt all the content client-side. - -If gitlab has a reasonable API for creating a new repository, the webapp -could optionally use that, instead of needing the user to create one -themselves. -"""]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_2_441c879e7aa60eb74e3a881de9c4e8ea._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_2_441c879e7aa60eb74e3a881de9c4e8ea._comment deleted file mode 100644 index ce3541f5f..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_2_441c879e7aa60eb74e3a881de9c4e8ea._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="Rasmus" - subject="comment 2" - date="2015-03-04T14:35:19Z" - content=""" -It easy to setup. And it seems like as good a \"canned\" solution as box.net or whatever. I don't know if I would use it for sensitive stuff, but for a couple of repos, it makes sense to use it. - -There seems to be some support for creating new projects (which I assume is repos) [here](http://doc.gitlab.com/ee/api/projects.html). -"""]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_3_9d60cfa947c5ce82c69fb77961db2d25._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_3_9d60cfa947c5ce82c69fb77961db2d25._comment deleted file mode 100644 index 40b49f875..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_3_9d60cfa947c5ce82c69fb77961db2d25._comment +++ /dev/null @@ -1,31 +0,0 @@ -[[!comment format=mdwn - username="http://rfhbuk.pip.verisignlabs.com/" - nickname="rfhb" - subject="git-annex: bad url ssh://git@gitlab.com:~/gitlabname/reponame.git" - date="2015-04-26T12:19:37Z" - content=""" -Adding an encrypted remote works (mind \":~/\"): - - > git remote add encrypted gcrypt::ssh://git@gitlab.com:~/gitlabname/reponame.git - > git push encrypted master - gcrypt: Repository not found: ssh://git@gitlab.com:~/gitlabname/reponame.git - gcrypt: Setting up new repository - gcrypt: Remote ID is :id:abcdefghijklmnopqrst - Counting objects: 53, done. - Compressing objects: 100% (52/52), done. - Total 53 (delta 12), reused 0 (delta 0) - gcrypt: Encrypting to: --throw-keyids --default-recipient-self - gcrypt: Requesting manifest signature - ... - To gcrypt::ssh://git@gitlab.com:~/gitlabname/reponame.git - * [new branch] master -> master - > - -However, git-annex then fails: - - > git annex sync - git-annex: bad url ssh://git@gitlab.com:~/gitlabname/reponame.git - -Should the encrypted repository be configured or added in a different way? Sorry, did not find it so easy to set up. - -"""]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_4_94c0a53da4f3bc89afd97a036d832f78._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_4_94c0a53da4f3bc89afd97a036d832f78._comment deleted file mode 100644 index ec8d18cd1..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_4_94c0a53da4f3bc89afd97a036d832f78._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-29T18:05:56Z" - content=""" -Current status is that I'm waiting to see git-annex-shell on gitlab actally -work. I get an API error. I've emailed the gitlab people about this. -"""]] diff --git a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_5_edb7d9de2ec51ab3f51a35848b63c842._comment b/doc/todo/Add_gitlab.com_as_cloud_provider/comment_5_edb7d9de2ec51ab3f51a35848b63c842._comment deleted file mode 100644 index bfa5d36f7..000000000 --- a/doc/todo/Add_gitlab.com_as_cloud_provider/comment_5_edb7d9de2ec51ab3f51a35848b63c842._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 5""" - date="2015-07-20T19:07:18Z" - content=""" -Update: Gitlab is working with git-annex for me now. -"""]] diff --git a/doc/todo/Chunks_support_in_all_special_remotes.mdwn b/doc/todo/Chunks_support_in_all_special_remotes.mdwn deleted file mode 100644 index 6d25ba684..000000000 --- a/doc/todo/Chunks_support_in_all_special_remotes.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -The special remote `directory` support files split in chunks, other special remotes do not. - -Support for chunks is useful, for example, to be able to upload large files over slow, unreliable connections or to minimize the amount of data to be sent when only part of a big file has been changed. - -Couldn't the code used to split, checksum and reconstruct the files in the `directory` remote be used also in all the other special remotes? - -> [[done]]; nearly all special remotes support chunking now, and the ones -> that don't omit it for their own reasons, for example bup is not sped up -> by using chunks, and glacier needs some additional work to support them. -> --[[Joey]] diff --git a/doc/todo/Chunks_support_in_all_special_remotes/comment_1_d12604dbeb42bbb6850425d237cb01e7._comment b/doc/todo/Chunks_support_in_all_special_remotes/comment_1_d12604dbeb42bbb6850425d237cb01e7._comment deleted file mode 100644 index 93ff8e53f..000000000 --- a/doc/todo/Chunks_support_in_all_special_remotes/comment_1_d12604dbeb42bbb6850425d237cb01e7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-11T20:17:05Z" - content=""" -See [[design/assistant/chunks]] -"""]] diff --git a/doc/todo/Deduplicate_archive___40__i.e._zip__41___files.mdwn b/doc/todo/Deduplicate_archive___40__i.e._zip__41___files.mdwn deleted file mode 100644 index c551b08d7..000000000 --- a/doc/todo/Deduplicate_archive___40__i.e._zip__41___files.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -I've just come across this issue and I'm not sure if git-annex is the right place to put it, but in case it is easy enough to do.. may as well ask! - -In this scenario, an online service (Bandcamp), automatically creates the archive file when downloading an album each and every time you download it. This results in identical files inside a zip, but different hashes due to the slightly different timestamps on the archive itself. - -Would it be possible for git-annex to be able to detect this scenario (in a manner similar to zipcmp) and redirect an add/import to the already existing copy? - -I've found this due to trying to decommission an old annex by `git annex import --clean-duplicates ~/annex_old/.git/annex/objects` and finding these files being left. - -[[done]] --[[Joey]] diff --git a/doc/todo/Deduplicate_archive___40__i.e._zip__41___files/comment_1_619840f2337b018ff165565325cf1a61._comment b/doc/todo/Deduplicate_archive___40__i.e._zip__41___files/comment_1_619840f2337b018ff165565325cf1a61._comment deleted file mode 100644 index 19548edb3..000000000 --- a/doc/todo/Deduplicate_archive___40__i.e._zip__41___files/comment_1_619840f2337b018ff165565325cf1a61._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.7" - subject="comment 1" - date="2014-08-12T19:51:38Z" - content=""" -All you need to do is unzip your zip file, and then `git annex add` or `git annex import` its contents. It will then automatically deduplicate. - -Due to the way compression works, two zip (or gz) files with identical contents but different checksums are unlikely to share many bytes in common. So git-annex cannot help with de-duplicating unless you unzip them. -"""]] diff --git a/doc/todo/Deleting_Unused_Files_by_Age.mdwn b/doc/todo/Deleting_Unused_Files_by_Age.mdwn deleted file mode 100644 index babcb5633..000000000 --- a/doc/todo/Deleting_Unused_Files_by_Age.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -I periodically move unused files to one of my servers. What I would like to -do is drop any unused file that has been unused for say more than 6 months? -I would like to not drop all unused files. - -> It strikes me that this is quite similar to how git handles deleting -> stale refs with the reflog. So, if `git annex unused` were changed to -> also look at the reflog, it would keep all files referred to by all refs -> in the reflog, until the reflog expires. You could then set reflog expiry -> to 6 months, and be done. -> -> However, I think that many users expect git annex unused to be able to -> immediately find and remove a file after it's been deleted. So this -> probably needs to be a configurable behavior. --[[Joey]] - ->> Implemented this, `git annex unused --used-refspec=+refs/heads/*:reflog` ->> will consider all head refs as used (the default), plus consider all ->> refs in the reflog as used. [[done]] --[[Joey]] diff --git a/doc/todo/Expose_auto-merge_for_manual__44___local_merges.mdwn b/doc/todo/Expose_auto-merge_for_manual__44___local_merges.mdwn deleted file mode 100644 index c2cf26f83..000000000 --- a/doc/todo/Expose_auto-merge_for_manual__44___local_merges.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -The automatic conflict resolution currently seems to only work within -the context of sync, when merging «synced/foo» into «foo». It would be -convenient if this functionality were exposed for manual merges -between local branches. - -E.g., one might invoke «git annex merge» or «git annex autoresolve» -after «git merge» when conflicts are found. - -> [[done]] as resolvemerge. --[[Joey]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory.mdwn b/doc/todo/New_special_remote_suggeston_-_clean_directory.mdwn deleted file mode 100644 index 98dd58d5e..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -The [[special remotes]] available all do great things and enable a ton of different services to be integrated. - -Strikingly, the one service I can't satisfactorily integrate with git-annex is a remote folder on a eg NAS (think: computer without git-annex installed) that I want to look like the original annex. As in, when I do a 'tree annexdir' it'd look the same on both locations (except, on the remote there would not be any symlinks, it'd be like it was in directmode, and there would not be a .git subdir). - -## Why? Use Case? - -I have a Synology NAS that I share access with with my wife. I want her to be able to access the files (photos/videos/music) in a sane manner (ie: not traversing sub-sub-sub 'randomly' named directories) but I also want to be able to manage them with git-annex on my machine (to gain the standard git-annex benefits, specifically the bob the archivist use case). The NAS has the ability to use ssh+rsync, so I'll assume those two tools can be used. - -This special remote could be thought of as the 'least common denominator of special remotes'; almost any server with ssh+rsync could be a remote, no matter if you have install privs or if the architecture (eg: ARM) is supported by git-annex. - -## Issues? - -First and foremost, this can't be (really really shouldn't be) a trusted remote; my wife could accidentally delete all files on the NAS while I am away. So my local git-annex shouldn't assume the NAS counts towards numcopies (unless I'm a real masochist). - -Secondly, what to do when files change/are added/removed on the special remote? Probably the same thing that the assistant does with everything. The only thing special is that new/modified files will need to be copied locally from this special remote before being added to the annex (to get hash and such). - -> This is not feaisble given git-annex's design. If I wanted to -> make something completely unlike git-annex, I suppose it could be done, -> but it's off topic here. [[wontfix|done]]. -> -> If you want to use git-annex on a Synology NAS, the arm standalone build -> will work, and then you can use the command-line, or the assistant -> to maintain a git repository that contains your files as desired. --[[Joey]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment deleted file mode 100644 index 575748b56..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_10_4829c2a2302b4b9611deddfedfbaa944._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 10" - date="2013-12-16T20:41:47Z" - content=""" -How is that better than `rsync -a gitrepo cleandirectory`? - -Perhaps better related to the original problem of getting git-annex running on a Synology NAS, [[forum/new linux arm tarball build]]. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment deleted file mode 100644 index 1ec5bbc54..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_1_4d81941fe53881eebff97109a07ba2f4._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="TroisSinges" - ip="82.227.207.5" - subject="comment 1" - date="2013-11-27T14:59:11Z" - content=""" -You could mount this NAS as a network drive on your computer (via samba for example or, even better, nfs), couldn't you? In this case you could use a real annex repository, and not a remote one. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment deleted file mode 100644 index 89663893e..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_2_660a5b764ad42468154b2bb94f8ec004._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="mounting over NFS/etc ..." - date="2013-11-27T16:01:50Z" - content=""" -TroisSinges: Yeah, I could, but that'd limit me to being on the local network when I want to interact with the repo; not ideal. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment deleted file mode 100644 index 60d422838..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_3_eed178ce4bc4d2b3f08a1e3d3d62c086._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://a-or-b.myopenid.com/" - ip="203.45.2.230" - subject="comment 3" - date="2013-11-28T02:36:15Z" - content=""" -+1 on this suggestion. - -Not all NASs are created equal so SAMBA/NFS isn't always the most recent version, upgrades aren't always possible (yes, I'm looking at you Drobo!) so sometimes you just can't do what g-a needs to do (locks are my big problem). - -This would be a great option to have, even with the downsides of losing a lot of the awesome-sauce of git-annex. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment deleted file mode 100644 index f79fb4940..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_4_1dae745cff1c0a38232d033dcc542ac4._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmVICFY2CDP08xdsPr3cgmScomy9HA-1sk" - nickname="Andrew" - subject="comment 4" - date="2013-11-29T04:11:24Z" - content=""" -+1 for this style of repository (again). - -Presenting the content of a git-annex repository in a way that - -1. is transparent (nobody but me need know or care it's a git-annex repository) -2. doesn't require installation (NAS or other device I can't install to) -3. works without thinking (doesn't required commits or checkouts or manual deferencing symlinks - see also point 1) - -would fulfil the \"like dropbox but awesome\" idea from the Kickstarter. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment deleted file mode 100644 index f87bf1aec..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_5_8d6c791e5e2daec7b25828f6884a67c6._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 5" - date="2013-12-05T19:52:52Z" - content=""" -Comment #1 was my initial reaction. A regular direct mode git-annex repository on the mounted NAS share. - -I don't quite understand the response to it \"that'd limit me to being on the local network when I want to interact with the repo\". How could git-annex update this NAS if it's not on the local network? - -So far, the only reason that has been brought up that makes sense to me is locking. git-annex does use locking in its repository to prevent 2 git-annex commands run at the same time doing conflicting operations. (Lack of that locking could in some cases cause data loss.) I think git-annex's locking is limited entirely to files within the .git directory. So, if a SMB mount for a NAS does not support locking, one approach could be to move the .git directory to local disk, and use `GIT_DIR` to make it be used when operating in that repository. This should get you exactly what was requested. Whether it makes sense or is sufficiently easy to use is another question. - -I tend to think that a better use of a NAS in many cases is to put a directory or rsync (if it supports rsync) special remote on the NAS, and have git-annex on the individual client machines. The webapp could have a UI that makes setting up a NAS like that simple, and it would be easy to do. - -The use case for having a mirrored directory tree on the NAS seems to be limited to when the clients using it are something that cannot run git-annex itself, but that still cares about filenames, as opposed to just operating on file contents. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment deleted file mode 100644 index 75614d69f..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_6_92ef2d4a7ed47000fda02732b4794dc0._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.64" - subject="comment 6" - date="2013-12-05T19:57:32Z" - content=""" -The other problem with this idea is that it seems to want the assistant to watch the file tree in the NAS, and make commits etc when files there are changed. - -But, any computer on the network that has the NAS mounted can change a file! AFAIK there is no interface to detect when such changes have happened; inotify does not help. It seems git-annex would have to expensively periodically scan the directory to find changes. -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment deleted file mode 100644 index 7ff072d4c..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_7_78fb5cdd61220ffcf0ae1eaf266985ec._comment +++ /dev/null @@ -1,28 +0,0 @@ -[[!comment format=mdwn - username="http://grossmeier.net/" - nickname="greg" - subject="comment 7" - date="2013-12-05T21:20:54Z" - content=""" -> How could git-annex update this NAS if it's not on the local network? - -ssh and port forwarding, like any home server. - -> I tend to think that a better use of a NAS in many cases is to put a directory or rsync (if it supports rsync) special remote on the NAS, and have git-annex on the individual client machines. - -I'm thinking of this like the public view of a git-annex repository. I want anyone to be able to view/download the files as they normally would. - -> The use case for having a mirrored directory tree on the NAS seems to be limited to when the clients using it are something that cannot run git-annex itself, but that still cares about filenames, as opposed to just operating on file contents. - -That's exactly my use case. - -> So far, the only reason that has been brought up that makes sense to me is locking. - -Locking is actually tangential to the issue/use case. Direct mode would solve that issue, but git-annex isn't built for the Synology NAS platform, so it isn't an option. - -> The other problem with this idea is that it seems to want the assistant to watch the file tree in the NAS, and make commits etc when files there are changed. - -I think you read too much into that part. :) I only want git-annex to do things when I 'sync' or similar. I'm actually not wanting *the assistant* to do much in this case. This might even be a non-assistant applicable use case. (I don't use the assistant in my large repositories, like photos and videos and music.) I only mentioned the assistant to point out that it has some of the logic (what to do with changed/deleted files) already. - -And honestly, I'd be fine with an implementation that overwrote all changes on this special remote on each sync (as needed). The response to that suggestion is \"just use rsync by itself to put the files on the NAS\" but that assumes I have all of the files on my local checkout (I don't). -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment deleted file mode 100644 index 3aeb04e53..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_8_21712dfee4f37232c34eddbce2427691._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="gan" - ip="85.224.8.104" - subject="Hook implementation?" - date="2013-12-07T01:15:46Z" - content=""" -1. I would propose the name \"plain directory\" for this special remote. Clean is not a good description, IMHO. - -2. When I read this a week ago I took the opportunity to play with the special remote hook, because as far as I can understand this could be a relatively trivial implementation that need not necessarily be in git-annex \"core\". And I'd like to contribute back to the git-annex community and help a brother out... I used the method of calling a single script from all hook points, and inside it look at what operation was requested. -I didn't get that far before giving up however. I got the feeling that hook would benefit from some extension and a bit more complete API to really create the opportunity for third-party extensions to git-annex this way. I would prefer that the hook script can handle several instances of remotes without creating custom hook scripts for each instance. Specifically I think a hook is needed also for \"init\" of a new remote (to get a unique identifier, and other parameters given by the user such as in this particular case, the path to the \"clean directory\") What do you think? -"""]] diff --git a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment b/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment deleted file mode 100644 index d96ac6987..000000000 --- a/doc/todo/New_special_remote_suggeston_-_clean_directory/comment_9_0ba57952532d5ef1f2bbfb163faa3b2f._comment +++ /dev/null @@ -1,35 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmicVKRM8vJX4wPuAwlLEoS2cjmFXQkjkE" - nickname="Thomas" - subject="pseudocode" - date="2013-12-08T15:23:36Z" - content=""" -The implementation should really be nothing more than the following to be run from a regular git annex repository with a configures special plain directory remote: - - foreach(path : allAnnexedFiles) { - if(remote.exists(path) && remote.filesize(path) === expectedFilesize) goto finally; - - if(fileAvailableLocally(path)) { - copyFileToRemote(path); - goto finally; - } - - if(shouldCopyFromElsewhere && canCopyFileFromSomeOtherRemote(path)) { - copyFileFromSomeOtherRemoteToRemote(path); - } - - finally: - logThatFileExistsOnRemote(path); - } - - foreach(remotePath : filesInRemoteDir) { - if(fileIsAnnexed(remotePath) || fileIsIgnored(remotePath) continue; - - delete(remotePath); - } - -The above pseude code assumes -- that the no other process is working on the remote at the same time. -- that the remote is not trusted. -- that nobody expects changes done at the remote to propagate to other clones. -"""]] diff --git a/doc/todo/Output_key_with_import__47__deduplicate.mdwn b/doc/todo/Output_key_with_import__47__deduplicate.mdwn deleted file mode 100644 index 81bb653fc..000000000 --- a/doc/todo/Output_key_with_import__47__deduplicate.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -When using - - git annex import --deduplicate -- ~/directory/to/import - -would it be possible to output the keys for duplicate files? This would allow people to find where in the annex the files already exist. - -e.g. - - import ~/directory/to/import/001.txt ok - import ~/directory/to/import/002.txt ok - import ~/directory/to/import/002_d.txt (duplicate SHA256E-s261--fb1230987ac123098...) ok - import ~/directory/to/import/003.txt ok - -Then you could use - - git log -S SHA256E-s261--fb1230987ac123098... - -to find out where it is already. - -Not sure if that is the nicest layout.. (or what it might break). - -> [[done]] --[[Joey]] diff --git a/doc/todo/Output_key_with_import__47__deduplicate/comment_1_9eefceaa052a4587b8448c2f8fd24d97._comment b/doc/todo/Output_key_with_import__47__deduplicate/comment_1_9eefceaa052a4587b8448c2f8fd24d97._comment deleted file mode 100644 index 56072128b..000000000 --- a/doc/todo/Output_key_with_import__47__deduplicate/comment_1_9eefceaa052a4587b8448c2f8fd24d97._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-31T19:22:47Z" - content=""" -Yeah, that seems fairly reasonable, it already says "duplicate..." -and it's easy to add the key. - -I don't see a good place to add a note about git log -S$KEY though, -so I guess the user will need to find out how to do that on their -own, if they want to search for eg, deleted keys. -"""]] diff --git a/doc/todo/Recovering_from_a_bad_sync.mdwn b/doc/todo/Recovering_from_a_bad_sync.mdwn deleted file mode 100644 index d60406568..000000000 --- a/doc/todo/Recovering_from_a_bad_sync.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -Instead of using `sync origin` for the first sync and a simple `sync` for the other syncs, - - # on pc1 - git annex init "pc1" - git annex direct - git annex add . - git annex sync origin # remote specified on the first sync - - # add some files - git annex add . - git annex sync - -I used `sync` first and only later I used `sync origin` - - # on pc1 - git annex init "pc1" - git annex direct - git annex add . - git annex sync - - # add some files - git annex add . - git annex sync origin # remote specified on a later sync - -These sequences of commands create two completely different git histories. - -More important, if one clones on pc2 the first repository, they will see both the pc1 remote and the pc2 remote. Instead, if one clones on pc2 the repository created by the second combination of commands, they will see only the pc2 remote. - -What commands should I use on pc1 to fix the history so that when pc2 clones from the origin repository it will see both the pc1 remote and its own local remote? - -> [[done]]; fixed per my comments. --[[Joey]] diff --git a/doc/todo/Recovering_from_a_bad_sync/comment_1_6f5f518a3190534b737203787149ef3c._comment b/doc/todo/Recovering_from_a_bad_sync/comment_1_6f5f518a3190534b737203787149ef3c._comment deleted file mode 100644 index fc354be3d..000000000 --- a/doc/todo/Recovering_from_a_bad_sync/comment_1_6f5f518a3190534b737203787149ef3c._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 1" - date="2014-07-14T18:27:43Z" - content=""" -If this is a todo item at all, it may make sense to make `git annex sync` sync even with git remotes that have no annex-uuid. - -As far as solving the problem, I think you just need to sync more in order to get the full list of remotes propigated around to all the remotes. Sync automatically merges disconnected git histories no matter how they got that way or how long they have been disconnected or diverged. -"""]] diff --git a/doc/todo/Recovering_from_a_bad_sync/comment_2_e494df56dcede4d14bcaa4cdbf3da4f5._comment b/doc/todo/Recovering_from_a_bad_sync/comment_2_e494df56dcede4d14bcaa4cdbf3da4f5._comment deleted file mode 100644 index 011129336..000000000 --- a/doc/todo/Recovering_from_a_bad_sync/comment_2_e494df56dcede4d14bcaa4cdbf3da4f5._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 2" - date="2014-07-14T18:38:58Z" - content=""" -It seems that the person who filed this todo item also filed [[bugs/sync does not commit with alwasycommit = false]] and got pretty confused by that. - -So, repurposing this todo item to be about perhaps syncing with remotes that have no annex-uuid by default. -"""]] diff --git a/doc/todo/Recovering_from_a_bad_sync/comment_3_4d4904bcbf97401c7c11338f32577f96._comment b/doc/todo/Recovering_from_a_bad_sync/comment_3_4d4904bcbf97401c7c11338f32577f96._comment deleted file mode 100644 index 1d173f0ef..000000000 --- a/doc/todo/Recovering_from_a_bad_sync/comment_3_4d4904bcbf97401c7c11338f32577f96._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 3" - date="2014-07-15T18:23:50Z" - content=""" -Making `git annex sync` automatically sync with remotes with no annex-uuid is more complicated than I first thought. - -In the case of a remote accessed over ssh, `git annex sync` already does sync with such a remote. Of course, it will set annex-ignore on it, since it has no annex-uuid. (Needed eg, for github, or just for preventing a repo from being used by git-annex if you don't want it to be.) Still, the git branches get synced, which is the behavior that we want. - -So, only local remotes are affected. Note that `git annex assistant` automatically git-annex inits the local remote when it lacks a uuid, and syncs with it. That seems ok. - -However `git annex sync` currently ignores the local remote when it has no uuid. Seems that this happens due to a bug, not intentionally. tryGitConfigRead tries to bootstrap up an annex state to read the repos's config, but this cannot be done in a repo that is not yet initialized. Result is the repo state is not read, and so it's treated as a local remote that is not currently available (ie, a disconnected disk). -"""]] diff --git a/doc/todo/Recursive_addurl_simlar_to_wget_--recursive.mdwn b/doc/todo/Recursive_addurl_simlar_to_wget_--recursive.mdwn deleted file mode 100644 index 629a9a120..000000000 --- a/doc/todo/Recursive_addurl_simlar_to_wget_--recursive.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -## Use Case - -I want to import a bunch of files that are hosted somewhere, they nicely sorted by year and such. Instead of addurl'ing each by hand (or writing a custom script each time this happens) I want to simply: - -git-annex addurl --recursive http://somehost.tld/somedir/ - -For sanity, mimicking wget closely with default depth of 5, but customizable with the --level switch. - -> [[done]] --[[Joey]] diff --git a/doc/todo/Recursive_addurl_simlar_to_wget_--recursive/comment_1_4ecd9ddba1b63b571555ec9bef18e2d8._comment b/doc/todo/Recursive_addurl_simlar_to_wget_--recursive/comment_1_4ecd9ddba1b63b571555ec9bef18e2d8._comment deleted file mode 100644 index 72326c478..000000000 --- a/doc/todo/Recursive_addurl_simlar_to_wget_--recursive/comment_1_4ecd9ddba1b63b571555ec9bef18e2d8._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.244" - subject="comment 1" - date="2014-04-07T20:10:51Z" - content=""" -Recursively traversing websites is *hard*, so I would rather leave it out of git-annex. -"""]] diff --git a/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn b/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn deleted file mode 100644 index 4b618e72b..000000000 --- a/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn +++ /dev/null @@ -1,14 +0,0 @@ -Submitting here from https://github.com/joeyh/git-annex/pull/36 - - commit 05b7e0d2e87c1c92df773d72ee0ac7c9638be058 - Author: Eric OConnor <eric@oco.nnor.org> - -> I've applied this patch. Thanks Eric. -> -> Of course, nothing is preventing filenames > 255 being added in the -> future. Based on the number that had to be renamed, this is pretty low -> probability, but it does happen. It would need changes to ikiwiki to add -> an enforced limit. If someone wants to patch ikiwiki that way, I'll -> enable it. -> -> For now, [[done]]. --[[Joey]] diff --git a/doc/todo/Specify_a_version_for_the___39__feed__39___build_dependency..mdwn b/doc/todo/Specify_a_version_for_the___39__feed__39___build_dependency..mdwn deleted file mode 100644 index 45da3273a..000000000 --- a/doc/todo/Specify_a_version_for_the___39__feed__39___build_dependency..mdwn +++ /dev/null @@ -1,9 +0,0 @@ -(I'm not sure how you would like to do this -- should I send commits for you to pull, or do you prefer a patch pasted in here?) - -In any case, here's a build-deps fix, originally sent as a pull request [1]. - -https://github.com/joeyh/git-annex/compare/master...jlebar:build-deps - -[1] https://github.com/joeyh/git-annex/pull/37 - -> This is fine. Thanks, I merged your patch. [[done]] --[[Joey]] diff --git a/doc/todo/Support_--jobs_option_for___39__sync_--content__39__.mdwn b/doc/todo/Support_--jobs_option_for___39__sync_--content__39__.mdwn deleted file mode 100644 index 9923dcff6..000000000 --- a/doc/todo/Support_--jobs_option_for___39__sync_--content__39__.mdwn +++ /dev/null @@ -1,14 +0,0 @@ -As the subject says. I mostly use `git annex sync --content` to transfer -files between repositories, as its easier than running `git annex sync`, a -bunch of `git annex copy`s and then a `git annex get` to make sure I have -all the files I should have. It would be good if the shortcut could also -work in parallel. - -> It also can be faster to push concurrent. OTOH, concurrent pulls -> can lead to the same git objects being downloaded redundantly, so best to -> avoid those I think. -> -> I've implemented this. It suffers from the same -> lack of support for displaying progress when running it parallel as -> documented on [[parallel_get]]. Other than that wart, this is [[done]]. -> --[[Joey]] diff --git a/doc/todo/Support_dbus_monitor_for_networkd.mdwn b/doc/todo/Support_dbus_monitor_for_networkd.mdwn deleted file mode 100644 index c2936dc51..000000000 --- a/doc/todo/Support_dbus_monitor_for_networkd.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -As of late, systemd-networkd supports a network monitor via dbus under “org.freedesktop.network1“. It would be convenient if the assistant supported this. - -Cf. this [commit](http://cgit.freedesktop.org/systemd/systemd/commit/?id=e331e24649213f2e093e16e4d3d64ee823dfc375). - -> patches! Awesome! merged [[done]] --[[Joey]] diff --git a/doc/todo/Support_dbus_monitor_for_networkd/comment_1_c34efaec014646bd52b5a4cc36913982._comment b/doc/todo/Support_dbus_monitor_for_networkd/comment_1_c34efaec014646bd52b5a4cc36913982._comment deleted file mode 100644 index 554e8d01c..000000000 --- a/doc/todo/Support_dbus_monitor_for_networkd/comment_1_c34efaec014646bd52b5a4cc36913982._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="eigengrau" - subject="comment 1" - date="2015-06-02T14:40:47Z" - content=""" -Submitted a patch. -"""]] diff --git a/doc/todo/Time_Stamping_of_Events_in_Webapp.mdwn b/doc/todo/Time_Stamping_of_Events_in_Webapp.mdwn deleted file mode 100644 index 0762f47ba..000000000 --- a/doc/todo/Time_Stamping_of_Events_in_Webapp.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -Currently events happening in the webapp (sync upload etc. on the right) has no time stamp thus user has no way to tell when was the last sync happened. Which is problematic when not using XMPP and repos lag behind. - -> [[dup|done]] of <http://git-annex.branchable.com/todo/wishlist__91__minor__93__:_add_time_stamps_to_annex_log_popups_in_webapp/> --[[Joey]] diff --git a/doc/todo/Views_Demo.mdwn b/doc/todo/Views_Demo.mdwn deleted file mode 100644 index 54704afa6..000000000 --- a/doc/todo/Views_Demo.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -Joey, - -I've been thinking about leveraging git-annex for a workgroup document repository and I have just watched your views demo. The timing of the demo is great because I need to deploy a document repository with per-document metadata and your views concept seems like a great mechanism for associating metadata to documents and for displaying that metadata. - -While I don't expect to use your views concept for my workgroup repostory, a later iteration might do. - -The metadata in my use case begins with all the weird metadata seen on a book's copyright page. In addition, per-document provenance, like how one found the document and (if we're lucky) a URL where the latest version of the document may be found. Metadata values may be simple strings or may be markdown text. - -So, are you considering a metadata syntax that can support complex metadata? One example is multiple authors. Another issue is complex metadata values, like key=abstract and value="markdown text...". - -FWIW, - -Bob - -> [[closing|done]]; requested feature was already present --[[Joey]] diff --git a/doc/todo/Views_Demo/comment_1_d7c83a0e9a83e4a05aa74a34a7e1cf19._comment b/doc/todo/Views_Demo/comment_1_d7c83a0e9a83e4a05aa74a34a7e1cf19._comment deleted file mode 100644 index 4c9b05635..000000000 --- a/doc/todo/Views_Demo/comment_1_d7c83a0e9a83e4a05aa74a34a7e1cf19._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.172" - subject="comment 1" - date="2014-02-24T18:17:04Z" - content=""" -All that should work fine. All metadata fields are multivalued, and the value can be any arbitrary data. -"""]] diff --git a/doc/todo/What_if_the_active_annex__39__ed_files_were_not_symlinks__63__.mdwn b/doc/todo/What_if_the_active_annex__39__ed_files_were_not_symlinks__63__.mdwn deleted file mode 100644 index 320976925..000000000 --- a/doc/todo/What_if_the_active_annex__39__ed_files_were_not_symlinks__63__.mdwn +++ /dev/null @@ -1,26 +0,0 @@ -So annex is super cool and all. But there is one really annoying thing about it. The symlinks disrupt workflow really horribly! For example if I have a .psd file that is annex'd and I open that file in photoshop, edit it, then try to save it again. It doesn't allow me, because the actual file is the one deep in the annex sub structure that is read only. There a bunch of other annoyances like this. But you basically can't work with annex'd files without some additional struggle. - -But there is a solution to this. Just don't symlink the files that are active. I think potentially the simplest way to do this is to have a 'annex' and 'unannex' command. Or rather, a 'create symlink' and 'uncreate symlink' command. - -So then you can be going along, doing your work, nothing in your directory symlinked. - -You then type you 'annex symlink' command all priorly annexed filed will be deleted and replaced with their symlinks. - -Then you can add your new files to annex. Adding new files will just automatically symlink them unless you put like a -ns or something to signify to not symlink them. - -With all priorly annexed filed symlinked and all your new files symlinked, you then git commit and push. - -Then you do a git annex unsymlink command. And then all your symlinks are deleted and the actual file placed there. - -Then you just type git annex symlink again to re-symlink them all. - -> I think you are looking for the `unlock` and `add` (or `lock`) commands. Basically, to edit the file in photoshop, you want: -> -> <pre> -> git annex unlock file.psd -> photoshop file.psd # ... -> git annex add file.psd # if you are happy with your changes or... -> git annex lock file.psd # if you want to discard your changes -> </pre> -> -> So basically what you are asking for is already [[done]], in my mind. I still think there are significant [[usability issues|forum/usability:_what_are_those_arrow_things__63__/]] with symlinks, but that's another story. --[[anarcat]] diff --git a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode.mdwn b/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode.mdwn deleted file mode 100644 index 751ee1942..000000000 --- a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -Please let me know if there already is a way of achieving this; I’ve googled around a lot, but could not find any information pertaining to my particular problem. - -I am using direct mode in a bunch of repositories where I need quick write access to content and where I am not interested in preserving history. Some of these repositories do contain regular symlinks, however. Now, I suppose that in indirect repos, the way of adding symlinks would be to just «git add» them. However, since these are direct mode repos, I cannot do this. - -Is there already a good way of adding symlinks in direct mode? If not, I would find it useful if there were one. - -Best regards, -T. - -> [[fixed|done]] --[[Joey]] diff --git a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_1_6c6e192bc0f70a386cd4275f98e1bd6f._comment b/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_1_6c6e192bc0f70a386cd4275f98e1bd6f._comment deleted file mode 100644 index 83ccf32de..000000000 --- a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_1_6c6e192bc0f70a386cd4275f98e1bd6f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="zardoz" - ip="134.147.14.84" - subject="comment 1" - date="2014-07-07T12:48:07Z" - content=""" -Can it be considered safe adding symlinks via «git -c core.bare=false add symlink; git -c core.bare=false commit -m Update»? If not, is there a better way? -"""]] diff --git a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_2_8e22cfdbeb2c841870a623cf4c7baf60._comment b/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_2_8e22cfdbeb2c841870a623cf4c7baf60._comment deleted file mode 100644 index b88ec65ae..000000000 --- a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_2_8e22cfdbeb2c841870a623cf4c7baf60._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.2" - subject="comment 2" - date="2014-07-10T19:54:30Z" - content=""" -That is safe, but you have to be very careful anytime you override with -c core.bare=false. For example, if you did a `git commit -a`, it would commit your large files directly into git, which you don't want. - - -"""]] diff --git a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_3_0039faa19e35eada1ff17eac6fbcab29._comment b/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_3_0039faa19e35eada1ff17eac6fbcab29._comment deleted file mode 100644 index d9b2d2b77..000000000 --- a/doc/todo/__171__git_annex_add__187___for_symlinks_in_direct_mode/comment_3_0039faa19e35eada1ff17eac6fbcab29._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-07-07T20:02:02Z" - content=""" -Recently, `git annex add` started adding files -to git, if annex.largefiles didn't match them. - -So, it's possible to use that to add eg, source files. But it currently -skips symlinks (unless they're git-annex symlinks). - -What I think makes sense to do is make it also process -symlinks, and always check them into git as-is. So, git-annex add becomes -like git-add except smart about adding large files to the annex. -"""]] diff --git a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks.mdwn b/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks.mdwn deleted file mode 100644 index 80d5a3d25..000000000 --- a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -In my quest to get git-annex to do what I want, even if it is weird and unusual.. - -Would it be possible for 'git annex fix' to work even on untracked symlinks (perhaps only with '--force'?), where the symlink is otherwise in a git-annexy format? - -This would allow me to do stuff like this: - - $ cd ~/old_broken_annex - $ cp -t ~/other_annex/presentcheck * - $ cd ~/other_annex/presentcheck - - ### This currently does nothing if the symlinks are untracked - $ git annex fix --force . - - $ find -type l -not -xtype l -print0 | xargs -0 git add - $ git commit -m "yay, we found some files!" - $ find -type l -xtype l -print0 | xargs -0 mv -t ~/files_not_found - -Admittedly, to do this now, you just have to stage the symlinks before you fix but there may be other situations where this is useful (and I can't think of anything else you would want 'fix --force' to do).. - -> Per my comment, this is not a good idea, so [[done]] --[[Joey]] diff --git a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_1_b795d0bfa64654bf82684da961815cea._comment b/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_1_b795d0bfa64654bf82684da961815cea._comment deleted file mode 100644 index f8eb04775..000000000 --- a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_1_b795d0bfa64654bf82684da961815cea._comment +++ /dev/null @@ -1,22 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-03-27T20:48:07Z" - content=""" -Currently git-annex uses git-ls-files to find the files to act on. -This would requires running git-ls-files twice, once with --others to find -the files not checked into git. - -I don't like the added complexity, the slowdown for everyone else, -etc. - -Also, I think it's very reasonable that git-annex commands do not -act on files that are not checked into git (except for git-annex add of -course). Acting on files that are not checked into git violates least -surprise. - -So, just add the file to git if you want git-annex fix to -act on it. You don't even have to commit the file, you can just -stage it in the index, and then un-stage it after git-annex is done with -it, if for some reason you don't want to check it into git. -"""]] diff --git a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_2_0ab89dad1289b5d349ecd452c3f5e4f5._comment b/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_2_0ab89dad1289b5d349ecd452c3f5e4f5._comment deleted file mode 100644 index 8fe0a8ccd..000000000 --- a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_2_0ab89dad1289b5d349ecd452c3f5e4f5._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 2" - date="2015-03-28T01:59:51Z" - content=""" -Okie dokie, thank you for considering it :) -"""]] diff --git a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_3_dcb651fa8a1ec52d6016e11bf06fab5d._comment b/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_3_dcb651fa8a1ec52d6016e11bf06fab5d._comment deleted file mode 100644 index 421f3750a..000000000 --- a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_3_dcb651fa8a1ec52d6016e11bf06fab5d._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnm19dBCRphmtjXfopm_NpvnRwz-qIJ2Tw" - nickname="Remi" - subject="comment 3" - date="2015-03-28T07:51:09Z" - content=""" -I completely disagree with the last surprise argument. I'm regularly in this situation, and each time I'm surprised when `git annex fix` do not fix the symlinks, even when I'm explicitly listing the list I want to fix. -"""]] diff --git a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_4_1e10274827564902047c72a81affd92c._comment b/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_4_1e10274827564902047c72a81affd92c._comment deleted file mode 100644 index 34d959578..000000000 --- a/doc/todo/__34__git-annex_fix__34___on_untracked__44___but_git-annexy_symlinks/comment_4_1e10274827564902047c72a81affd92c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnVnsqEy82M-MuS2gLri-az83wSQ6lXSrc" - nickname="Jean" - subject="I'm with Remy here" - date="2015-04-09T05:02:50Z" - content=""" -I can't even comprehend how git-annex gets into this situation. From what angle does it make sense to ever have a symlink pointing at a `.git/annex/objects/...` and not be tracked? -"""]] diff --git a/doc/todo/add_--quiet_option_to_fsck.mdwn b/doc/todo/add_--quiet_option_to_fsck.mdwn deleted file mode 100644 index 67412bf02..000000000 --- a/doc/todo/add_--quiet_option_to_fsck.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -ATM it floods the screen with ok for every file (in non-interactive session even split across 2 lines). As such it is just a pure noise if I care to check if entire repo is ok -- a single summary line, possibly preceeded with reports about broken files would be much better imho. - -Cheers! - -> I jumped in a time machine, popped out in 2010 and implemented it -> them, to ensure the bug is already fixed on your computer. [[done]] -> --[[Joey]] diff --git a/doc/todo/add_--quiet_option_to_fsck/comment_1_9c70dcdf11d23a33d1007005bbd58e60._comment b/doc/todo/add_--quiet_option_to_fsck/comment_1_9c70dcdf11d23a33d1007005bbd58e60._comment deleted file mode 100644 index e38c72fa2..000000000 --- a/doc/todo/add_--quiet_option_to_fsck/comment_1_9c70dcdf11d23a33d1007005bbd58e60._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-05-30T15:30:13Z" - content=""" -git-annex fsck already has this --quiet option. (Same option works with -most other git-annex commands too. -"""]] diff --git a/doc/todo/allow_removing_jabber_configuration.mdwn b/doc/todo/allow_removing_jabber_configuration.mdwn deleted file mode 100644 index 62370258d..000000000 --- a/doc/todo/allow_removing_jabber_configuration.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -right now it is unclear through the webapp how to unconfigure a jabber -account, which is especially critical considering the password needs to be -stored in the clear (where?). -- [[anarcat]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__.mdwn b/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__.mdwn deleted file mode 100644 index b1adfdcc2..000000000 --- a/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -When maintaining several replica of the same git-annex repo "git annex sync" is quite handy. -But it would be even handier if "git annex sync" would also perform automatic "git merge synced/*" actions on all remotes. - -Clearly, this is beneficial when the user wants to keep all working copies synchronized. -This is likely the case in git annex assistant like scenarios. And it's always the case in my day to day scenarios :-) -I'm not sure about other use cases that I've hard time imagining... - -As just discussed on IRC (#vcs-home/OFTC), this could be implemented in various ways: - -1) By doing ssh on each remote and running the appropriate "git merge ..." commands there. - The drawback of this is that quite often it won't be permitted to ssh on the remote and run arbitrary commands there. - -2) Having a default post-receive hook, created at the time of "git annex init" that automatically does the merges when contacted by other remotes as a consequence of "git annex sync". - - -Thanks for git-annex! - -> [[done]]; use new git feature instead. --[[Joey]] diff --git a/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__/comment_1_60e5067c2be9e8df7bd1b6d954c60cad._comment b/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__/comment_1_60e5067c2be9e8df7bd1b6d954c60cad._comment deleted file mode 100644 index 4b0ea8e1c..000000000 --- a/doc/todo/automatic_merge_of_synced_branches_upon___34__git_annex_sync__34__/comment_1_60e5067c2be9e8df7bd1b6d954c60cad._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-07T19:54:07Z" - content=""" -Git recently got receive.denyCurrentBranch=updateInstead, -which allows the remote working tree to be updated automatically -(as long as there are no changes in the work tree or staged in the index). - -This seems much better than putting a hack into git-annex. -"""]] diff --git a/doc/todo/better_git-annex-shell_init_workflow.mdwn b/doc/todo/better_git-annex-shell_init_workflow.mdwn deleted file mode 100644 index 58bf0216a..000000000 --- a/doc/todo/better_git-annex-shell_init_workflow.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -Currently, the workflow for initializing a remote repo has to involve -manually pushing the git-annex branch to the repo, first. This primes -git-annex-shell to auto-initialize the repo. Only after that first push, -can git-annex sync be used. If git-annex sync is run earlier, it will try -to get the remore uuid, fail, and set annex-ignore. - -This should be improved.. It ought to be possible to add a new remote and -have git-annex sync do everything needed. - -> [[done]]; the remote needs git-annex-shell 5.20150805 installed, and so -> does the user, and then `git-annex sync` will automatically handle -> initialization of the remote. --[[Joey]] diff --git a/doc/todo/cheaper_global_fsck.mdwn b/doc/todo/cheaper_global_fsck.mdwn deleted file mode 100644 index 70d1380a2..000000000 --- a/doc/todo/cheaper_global_fsck.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -Global fsck updates all location log entries for a repo. This wastes disk -space. - -I realized now that it can be implemented w/o such waste. Probably cheaply -enough to be the default! - -What we need is a new log file, call it fscktimes.log. -This records the time of the last fsck of each repo. - -`git annex fsck --expire` no longer needs to look at the location log at -all. It can just check the repo's fscktimes.log entry. If the entry is -recent enough, we know that the repo has fscked recently, and its location -log is good, and nothing needs to be done. Otherwise, we know that the repo -has stopped fscking, and we simply expire *all* its location logs. - -Note that fscktime.log is only used by fsck; it does not impact git-annex -generally or make it slower. And, it's very low overhead to update the one -file. Repos could do a fsck --fast on a daily basis and not grow the -git-annex branch much. Maybe on an hourly basis even. - -(BTW, there is some overlap with the fsck.log file that is currently used to -hold the timestamp of the last local fsck. May be able to eliminate that -file too.) - ----- - -It might be worth making the fsck.log record --fast and full fscks -separately so we know the last of each for each repo. This would let ---expire require periodic full fscks and more frequent fast fscks. - ----- - -Hmm, --expire updates all the location logs when it thinks a repo has gone -missing. Why not just mark it dead? Again, this would save a lot of space! -It would complicate recovery if a repo had been offline and came back; it -would need to mark itself as not dead any longer. - -> [[done]] --[[Joey]] diff --git a/doc/todo/clear_file_names_in_special_remotes.mdwn b/doc/todo/clear_file_names_in_special_remotes.mdwn deleted file mode 100644 index 1b6a9f935..000000000 --- a/doc/todo/clear_file_names_in_special_remotes.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -To properly use amazon AWS S3 for CDN, we need to publish videos to S3. Ideally, we would like to do this via git-annex as the back-end of video.debian.net is being migrated to git-annex by me, atm. - -Obviously, we will need clear text names and proper directory structure, not SHA512E file names. This would need to be supported by the S3 special remote. - -I talked to TobiasTheViking in the past and he hinted at a reasonably clean way to do this, but that a clean solution would need support from git-annex. I will link him to this page and ask him to supply whatever info is needed. - - -Thanks, -Richard - -> This is not feaisble given git-annex's design. If I wanted to -> make something completely unlike git-annex, I suppose it could be done, -> but it's off topic here. [[wontfix|done]] --[[Joey]] diff --git a/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment b/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment deleted file mode 100644 index 7ca8e1916..000000000 --- a/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.41" - subject="comment 1" - date="2014-03-26T17:26:37Z" - content=""" -I don't see how this can possibly be done. A single git-annex object can have any number of file names, which can change at any time. -"""]] diff --git a/doc/todo/clear_file_names_in_special_remotes/comment_2_823c279683ac3f39c921be3fcbf6bfe2._comment b/doc/todo/clear_file_names_in_special_remotes/comment_2_823c279683ac3f39c921be3fcbf6bfe2._comment deleted file mode 100644 index b7f5a409e..000000000 --- a/doc/todo/clear_file_names_in_special_remotes/comment_2_823c279683ac3f39c921be3fcbf6bfe2._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" - nickname="Richard" - subject="comment 2" - date="2014-03-26T22:32:18Z" - content=""" -In that case, we would need to export the same file name several times, just like direct mode does. - -Could files be tracked via metadata? And yes, fsck would be... interesting... -"""]] diff --git a/doc/todo/clear_file_names_in_special_remotes/comment_3_4704e465025b543e47c18d565abd2747._comment b/doc/todo/clear_file_names_in_special_remotes/comment_3_4704e465025b543e47c18d565abd2747._comment deleted file mode 100644 index a925cb2de..000000000 --- a/doc/todo/clear_file_names_in_special_remotes/comment_3_4704e465025b543e47c18d565abd2747._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.41" - subject="comment 3" - date="2014-03-27T17:44:46Z" - content=""" -Sounds like \"I want a pony to me\". -"""]] diff --git a/doc/todo/command_line_interface_for_required_content_setthings.mdwn b/doc/todo/command_line_interface_for_required_content_setthings.mdwn deleted file mode 100644 index 30889f8bb..000000000 --- a/doc/todo/command_line_interface_for_required_content_setthings.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -Someone in the forum noticed that `git annex wanted` -handles preferred content settings, but there is no analagous `git annex -required`. - -Probably worth adding that, although required content is not an often -used feature, and vicfg can already configure it. - -(I don't much like the `git annex required` name. Nor the `git annex wanted` -one when it comes to that. Oh well.) - ---[[Joey]] - -> [[done]] --[[Joey]] diff --git a/doc/todo/commit_in_direct_mode.mdwn b/doc/todo/commit_in_direct_mode.mdwn deleted file mode 100644 index 93dbf40bf..000000000 --- a/doc/todo/commit_in_direct_mode.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -As of right now, the only way to commit changes to direct repositories is `git annex sync [remote]`. -There is no way to specify what directory to operate on. -When moving around files on a larger scale, the ability to commit specific subsets of changes would be rather nice. - -`git annex commit [path]` or `git annex sync [remote] -- [path]` would probably make sense. - - -Thanks, -Richard - -> I've documented in the git-annex-proxy man page how to use it to do -> per-file commits. [[done]] --[[Joey]] diff --git a/doc/todo/commit_in_direct_mode/comment_1_7d9e62010905e0d70cb586534cc09a75._comment b/doc/todo/commit_in_direct_mode/comment_1_7d9e62010905e0d70cb586534cc09a75._comment deleted file mode 100644 index 55454db7e..000000000 --- a/doc/todo/commit_in_direct_mode/comment_1_7d9e62010905e0d70cb586534cc09a75._comment +++ /dev/null @@ -1,67 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-03T17:59:39Z" - content=""" -I am reluctant to make direct mode grow to replicate significant (and -really quite complex) git commands like commit. Which is why I have not -added this. - -`git annex proxy` brings a lot of regular git commands to -direct mode. - -It's possible to use it to make a commit in direct mode. You only have -to manually `git annex add` the modified files first, to get them staged -in the index. - - joey@darkstar:~/tmp/a>date > newfile - joey@darkstar:~/tmp/a>echo modified > foo - joey@darkstar:~/tmp/a>git annex add newfile foo - add newfile ok - add foo ok - (recording state in git...) - joey@darkstar:~/tmp/a>git annex proxy -- git commit foo -m foo - ok - (recording state in git...) - [annex/direct/master 739c518] foo - 1 file changed, 1 insertion(+), 1 deletion(-) - joey@darkstar:~/tmp/a>git show - commit 739c518997cc9d0a21e920213394079fce9e7a11 - Author: Joey Hess <joeyh@joeyh.name> - Date: Fri Jul 3 14:04:19 2015 -0400 - - foo - - diff --git a/foo b/foo - index 4925a0e..0f22f36 120000 - --- a/foo - +++ b/foo - @@ -1 +1 @@ - -.git/annex/objects/fV/Zq/SHA256E-s30--79d01999a1e7d689136859f7462651dbe179b9c779c45d4e0b2815f426628b75/SHA256E-s30--79d01999a1e7d689136859f7462651dbe179b9c779c45d4e0b2815f426628b75 - \ No newline at end of file - +.git/annex/objects/qw/8m/SHA256E-s9--4487e24377581c1a43c957c7700c8b49920de7b8500c05590cee74996ef73f42/SHA256E-s9--4487e24377581c1a43c957c7700c8b49920de7b8500c05590cee74996ef73f42 - \ No newline at end of file - joey@darkstar:~/tmp/a>git annex proxy -- git commit -a -m added\ newfile - ok - [annex/direct/master 9abe7a4] added newfile - 1 file changed, 1 insertion(+) - create mode 120000 newfile - joey@darkstar:~/tmp/a>git show - commit 9abe7a4fa083ea0e4529df0054f44f4e30d9e0ae - Author: Joey Hess <joeyh@joeyh.name> - Date: Fri Jul 3 14:04:38 2015 -0400 - - added newfile - - diff --git a/newfile b/newfile - new file mode 120000 - index 0000000..1bb8d0d - --- /dev/null - +++ b/newfile - @@ -0,0 +1 @@ - +.git/annex/objects/23/q9/SHA256E-s30--42fb3eaea7c7932a9056e531f764ca83d117c69c79d4458f9860c6e525f8e498/SHA256E-s30--42fb3eaea7c7932a9056e531f764ca83d117c69c79d4458f9860c6e525f8e498 - \ No newline at end of file - -This works because `git annex proxy` sets up a temporary work tree, -using the content of the index. So you can commit any/all staged files. -"""]] diff --git a/doc/todo/credentials-less_access_to_s3.mdwn b/doc/todo/credentials-less_access_to_s3.mdwn deleted file mode 100644 index dca0a16c9..000000000 --- a/doc/todo/credentials-less_access_to_s3.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -My situation is this: while i know i can *read and write* to [[special_remotes/S3]] fairly easily with the credentials, I cannot read from there from other remotes that do not have those credentials enabled. - -This seems to be an assumption deeply rooted in git-annex, specifically in `Remote/S3.hs:390`. - -It would be *very* useful to allow remotes to read from S3 transparently. I am aware of the tips mentionned in the comments of [[tips/publishing_your_files_to_the_public/]] that use the `addurl` hack, but this seems not only counter-intuitive, but also seem to add significant per-file overhead in the storage. It also requires running an extra command after every `git annex add` which is a problem if you are running the assistant that will add stuff behind your back. - -Besides, you never know if and when the file really is available on s3, so running addurl isn't necessarily accurate. - -How hard would it be to fix that in the s3 remote? - -Thanks! --[[anarcat]] - -> [[done]], see [[tips/public_Amazon_S3_remote/]] --[[Joey]] diff --git a/doc/todo/credentials-less_access_to_s3/comment_1_eda703c0902d346e063c6d7ae00f6400._comment b/doc/todo/credentials-less_access_to_s3/comment_1_eda703c0902d346e063c6d7ae00f6400._comment deleted file mode 100644 index e6218a799..000000000 --- a/doc/todo/credentials-less_access_to_s3/comment_1_eda703c0902d346e063c6d7ae00f6400._comment +++ /dev/null @@ -1,38 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-06-02T17:24:10Z" - content=""" -The S3 remote already does it when using the IA as a special case -- -it knows how to map from IA S3 buckets to archive.org urls, and so the -special remote adds the url automatically. It would be quite easy to -add that for non-IA; the user would just need to configure the url where -the files in the bucket can be found. - -As noted, this does increase storage needs, since that's written to the -git-annex branch. Although I'd expect it will compress pretty well when git -gets around to packing it, since the added data is static base of the -url, plus the key. Plus a little bit of overhead for hash directories and -timestamps. Oh, and plus modifying the location tracking info to indicate -that the file is present in the web special remote. Ok, maybe it's a lot of -overhead. :) - -Could avoid writing this info to the git-annex branch, and just use a -function to generate urls for keys that are known to be in S3. The -`whereisKey` interface already exists -- it's how the web special remote -adds urls to `whereis` display itself. - -But I'm not sure what to do about the complication that the S3 -special remote may not be enabled -- and if not, it doesn't get the -opportunity to register such a function. - -Maybe this would need the S3 special remote to be enabled in read-only -mode? Although, if we're going to do that, it could just handle the -read-only retrieval itself, and not involve the web special remote at all. - -So: - - git annex initremote S3 type=s3 ... bucket=foo readonlyurl=http://foo.s3.amazon.com/ - # elsewhere - git annex enableremote S3 readonly=true -"""]] diff --git a/doc/todo/credentials-less_access_to_s3/comment_2_cefe0fbf1c3c6037c677ec6cff0aa6d6._comment b/doc/todo/credentials-less_access_to_s3/comment_2_cefe0fbf1c3c6037c677ec6cff0aa6d6._comment deleted file mode 100644 index 4455a4fe4..000000000 --- a/doc/todo/credentials-less_access_to_s3/comment_2_cefe0fbf1c3c6037c677ec6cff0aa6d6._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="autodetection?" - date="2015-06-02T18:11:15Z" - content=""" -couldn't the remote fallback to readonly mode when no credentials are available? - -also, it seems to me that once you have the bucket name, you can automatically guess the URL (http://$bucket.s3.amazon.com or whatever)... -"""]] diff --git a/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment b/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment deleted file mode 100644 index 8a9ff4db2..000000000 --- a/doc/todo/credentials-less_access_to_s3/comment_3_26de94e8e3fefc9b47d1510bfb2dac9b._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2015-06-05T20:17:38Z" - content=""" -The remote can indeed fallback when there are no creds. - -Also, git-annex can set an ACL on files it uploads, if the remote is -configured with public=yes, so no manual ACL setting will be needed. -"""]] diff --git a/doc/todo/direct_mode_undo.mdwn b/doc/todo/direct_mode_undo.mdwn deleted file mode 100644 index 82c2e4ab8..000000000 --- a/doc/todo/direct_mode_undo.mdwn +++ /dev/null @@ -1,88 +0,0 @@ -A fairly common request is that a repo is using direct mode, and the user -has made some change, and now wants to undo it. Since direct mode doesn't -allow using `git revert`, the repo would need to be switched to indirect -mode first, which can range from annoying to really annoying to impossible -(on eg FAT). - -## general approach - -`git annex proxy $gitcmd` could: - -1. check out a local clone of the repo -2. run "git $gitcmd" inside the clone -3. Merge any changes from the clone back into the direct mode repo - and update the work tree the same as is done by `git annex merge`. -4. If a different branch was checked out in the clone, update the repo - to have that same branch checked out. - -This is a general bypass for the direct mode guard. It should work anywhere -(even on FAT). It avoids problems like `git commit -a` being unsafe in -direct mode, since running such a command in a local clone, which does not -use direct mode is always safe. - -Beyond handling undo, #4 means that this can be used to check -out past versions of the repo (eg, `git annex proxy checkout HEAD^^`) - -One problem with it is that it can only operate on changes that have been -committed. If you've just accidentially deleted a file and want to undo -that, and haven't run `git annex sync` to commit it, you can't revert it. - -The need to make a local clone will make it a bit slow, since the whole -work tree will need to be set up. It might be possible to reuse the clone -next time (after resetting it to reflect the current HEAD). - -Some things like the reflog and local branches don't get cloned, so -git commands that try to act on those wouldn't work. Maybe it would be -better to make it use a separate work tree, but the same .git directory? -Then step #3 would instead update the direct mode work tree to refect -the new HEAD, and step #4 would not be needed. - -> This is done.. But, I think an undo command would also be good -> to do, as a nicer user interface that can integrate well with a file -> manager. --[[Joey]] - -## git annex undo - -I don't want to recapitulate all of the git commands in git-annex for -direct mode. So I don't want to add `git annex revert` and `git annex -branch` etc, etc. - -So, adding `git annex undo` feels like a step down a slippery slope. But it -might be justified as providing just enough functionality to make direct -mode a lot more useful, without trying to recapitulate all the flexability -of git. Like `git annex merge` and `git annex sync` also do. - -Another use case is binding `git annex undo $file` to an action in a file -manager. - -Here's a design for undo: - -1. Can be passed one or more files. Which may or may not exist in the work tree. -2. First, commits the current state of the files as staged in the index, - or in the working tree. This may involve checksumming modified files. -3. Then, for each file, looks back through git history, to find the commit - just before the most recent change that was made to that file. - Stage the version of the file as it was in that commit. -4. Updates work tree, and leaves the changes staged - but not committed. (To allow the user to bundle up multiple undos in a - single commit). -6. Does not get or drop content. The content may even be completely - missing after an undo. - -Note that undoing an undo should get back to the original state. This is -why #2 commits changes first. This way, if a file has a staged change, -it gets committed, and then that commit is reverted, resulting in another -commit. Which a later run of undo can in turn revert. If it didn't commit, -the history about the staged change that was reverted would be lost. - -What about undoing changes to a whole directory? Recursively undoing -the last change to each file would be expensive, and likely confusing. -Instead, when a directory is passed, it could find the most recent commit -that touched files in that directory, and undo the changes to those files. - -> [[done]] --[[Joey]] - -Also, --depth could make undo look for an older commit than the most -recent one to affect the specified file. - -See [[direct_mode]] for documentation about this feature. diff --git a/doc/todo/direct_mode_undo/comment_1_bd7e9f152805a57cce97bef64e4891dd._comment b/doc/todo/direct_mode_undo/comment_1_bd7e9f152805a57cce97bef64e4891dd._comment deleted file mode 100644 index 35e1b90b0..000000000 --- a/doc/todo/direct_mode_undo/comment_1_bd7e9f152805a57cce97bef64e4891dd._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 1" - date="2015-02-15T05:46:01Z" - content=""" -> This way, if a file has a staged change, it gets committed, and then that commit is reverted, resulting in another commit. Which a later run of undo can in turn revert. If it didn't commit, the history about the staged change that was reverted would be lost. - -so far, my experience with this is that unstaged changes get dropped and the change that gets undoed is the last committed change. In other words, if i have: - - $ git annex status - M file - -`git annex undo` is going to drop that modification and `git revert HEAD`. but maybe i got confused, in which care some of the documentation i just did in [[direct mode]] needs to be corrected. --[[anarcat]] -"""]] diff --git a/doc/todo/direct_mode_undo/comment_2_b826160420e0f343aadc5353e50aed2b._comment b/doc/todo/direct_mode_undo/comment_2_b826160420e0f343aadc5353e50aed2b._comment deleted file mode 100644 index 1f300b881..000000000 --- a/doc/todo/direct_mode_undo/comment_2_b826160420e0f343aadc5353e50aed2b._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="sigh... nevermind" - date="2015-02-15T05:52:02Z" - content=""" -seems like i was wrong. i could have sworn i saw a committed file get unstaged. what i saw was: - - $ git annex status - M file - $ git annex undo file - $ git annex status - ? file - -the thing is: the file was *removed* in a previous version, so i thought this was what it reverted to. i'm unsure as to why the file was marked as missing there - i ended up reverting from a backup (from another remote, by hand). after trying to reproduce this, i failed, so there may have been some PEBKAC in action again. - -this feature is so useful though, thanks for this. --[[anarcat]] -"""]] diff --git a/doc/todo/do_not_commit_with_empty_messages.mdwn b/doc/todo/do_not_commit_with_empty_messages.mdwn deleted file mode 100644 index 3c6c8415a..000000000 --- a/doc/todo/do_not_commit_with_empty_messages.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -it seems that `git-annex` sometimes does commits with empty commit messages. this makes rebasing git-annex branches much much harder than they need to, because rebase freaks out on those weird commits: - -<pre> -anarcat@marcos:video$ git rebase --continue -Waiting for Emacs... -Aborting commit due to empty commit message. -Could not commit staged changes. -</pre> - -This was trying to fix [[a broken merge|forum/canceling_wrong_repository_merge/]]... --[[anarcat]] - -> While I think it's silly to use empty dummy commit messages when there -> is nothing of value to say about the commit, I guess I can add value -> by putting in the name of the repository where the commit was made. So, -> [[done]] --[[Joey]] diff --git a/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment b/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment deleted file mode 100644 index c2cd7833f..000000000 --- a/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-11T17:15:04Z" - content=""" -It's completely legal for git commits to have empty commit messages. Why -would rebase care? Seems like a bug in rebase. - -Note that only the git-annex assistant currently uses empty commit -messages. -"""]] diff --git a/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment b/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment deleted file mode 100644 index 0ce37dc7c..000000000 --- a/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="git bug indeed" - date="2015-02-11T18:14:34Z" - content=""" -i agree. this does seems like a bug in git. i tried various ways of coercing git into doing what i need, but in the end just ended up adding comments to those commits. - -i thought of reporting this to the mailing list, but it turns out there's already patches floating around to fix a bunch of issues with rebase: - -<http://search.gmane.org/?query=rebase+empty+commit+message&group=gmane.comp.version-control.git> - -in particular: - -<http://article.gmane.org/gmane.comp.version-control.git/255411/> - -not sure what those will become. -"""]] diff --git a/doc/todo/enable_fsck_--fast_for_S3_remotes.mdwn b/doc/todo/enable_fsck_--fast_for_S3_remotes.mdwn deleted file mode 100644 index 77392b36d..000000000 --- a/doc/todo/enable_fsck_--fast_for_S3_remotes.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -At the moment, ``git annex fsck --fast -f S3remote`` fails as - -[[!format sh """ -> git annex fsck --fast -f S3remote -(checking cloud...) [2015-04-24 21:39:35 BST] String to sign: "HEAD\n\n\nFri, 24 Apr 2015 20:39:35 GMT\n/BUCKET/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1" -[2015-04-24 21:39:35 BST] Host: "BUCKET.s3-ap-southeast-2.amazonaws.com" -[2015-04-24 21:39:35 BST] Path: "/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1" -[2015-04-24 21:39:35 BST] Query string: "" -[2015-04-24 21:39:36 BST] Response status: Status {statusCode = 200, statusMessage = "OK"} -[2015-04-24 21:39:36 BST] Response header 'x-amz-id-2': 'D9wtD8voZZgijJRc6i8i0QasAo85REdMMf4GpRaER5+g6sDaUYtCKi42RCdYU0kBxrx4d4dM4xM=' -[2015-04-24 21:39:36 BST] Response header 'x-amz-request-id': 'DDF95C327078E584' -[2015-04-24 21:39:36 BST] Response header 'Date': 'Fri, 24 Apr 2015 20:39:37 GMT' -[2015-04-24 21:39:36 BST] Response header 'Last-Modified': 'Sun, 02 Nov 2014 05:42:48 GMT' -[2015-04-24 21:39:36 BST] Response header 'ETag': '"3bd1b766a68a305ba0495af36b353a07"' -[2015-04-24 21:39:36 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-24 21:39:36 BST] Response header 'Content-Type': '' -[2015-04-24 21:39:36 BST] Response header 'Content-Length': '775647' -[2015-04-24 21:39:36 BST] Response header 'Server': 'AmazonS3' -[2015-04-24 21:39:36 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> - - failed to download file from remote - -failed -"""]] - - -while ``git annex fsck -f S3remote`` works fine. But, to check for the presence of a file (which is my understanding of what ``--fast`` is for here), it shouldn't be necessary to download the file. - -> [[fixed|done]]; it was not supposed to fail at all in this case, and -> won't anymore. --[[Joey]] diff --git a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_1_b9c1da34a1d55333f864f2b7f9f4e4c7._comment b/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_1_b9c1da34a1d55333f864f2b7f9f4e4c7._comment deleted file mode 100644 index 83e95b6df..000000000 --- a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_1_b9c1da34a1d55333f864f2b7f9f4e4c7._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-25T01:28:34Z" - content=""" -It's HEADing the file, you can see it in the transcript. - -Appears the error message could be better though. -"""]] diff --git a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_2_cf86f921db2a9f1f5ffad14616e3279b._comment b/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_2_cf86f921db2a9f1f5ffad14616e3279b._comment deleted file mode 100644 index 90c39d2ae..000000000 --- a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_2_cf86f921db2a9f1f5ffad14616e3279b._comment +++ /dev/null @@ -1,84 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="Output for a full fsck" - date="2015-04-25T08:07:35Z" - content=""" -Sorry, I should have provided this output also, which is when I do a non-fast fsck. Below that is the output for a fsck in a file not in the remote. Basically, they both work. The case of a file not present with --fast also works (it gets a 404 response). But fscking a file with --fast that *is* there gets a 200 response for the HEAD, and then decides it didn't get downloaded properly (it shouldn't download it), and reports a fail. It should see the 200 response and report OK. - -I guess this should have been a bug report instead of todo. - -[[!format sh \"\"\" -> git annex fsck -f cloud file --debug -[2015-04-25 08:52:51 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-25 08:52:51 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-25 08:52:51 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..7f6b0b58ef362edd43fc89d8ef641e18cfebcb4a\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 08:52:51 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..19ca78351e854273ccb2b6a83fbaf7e2ed9b32da\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 08:52:51 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-25 08:52:51 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"file\"] -[2015-04-25 08:52:51 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"] -[2015-04-25 08:52:51 BST] read: git [\"--version\"] -fsck file [2015-04-25 08:52:51 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] -(checking cloud...) [2015-04-25 08:52:51 BST] String to sign: \"HEAD\n\n\nSat, 25 Apr 2015 07:52:51 GMT\n/BUCKET/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1\" -[2015-04-25 08:52:51 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-25 08:52:51 BST] Path: \"/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1\" -[2015-04-25 08:52:51 BST] Query string: \"\" -[2015-04-25 08:52:52 BST] Response status: Status {statusCode = 200, statusMessage = \"OK\"} -[2015-04-25 08:52:52 BST] Response header 'x-amz-id-2': 'mLGNeVBzsS7BusAEsDpIyECSpmErjO0HLA/G04svlIgIwsD+K8FpquTvtuA/UoIJK5FrJV0geCE=' -[2015-04-25 08:52:52 BST] Response header 'x-amz-request-id': '2E977E4D5EC072F6' -[2015-04-25 08:52:52 BST] Response header 'Date': 'Sat, 25 Apr 2015 07:52:53 GMT' -[2015-04-25 08:52:52 BST] Response header 'Last-Modified': 'Sun, 02 Nov 2014 05:42:48 GMT' -[2015-04-25 08:52:52 BST] Response header 'ETag': '\"3bd1b766a68a305ba0495af36b353a07\"' -[2015-04-25 08:52:52 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-25 08:52:52 BST] Response header 'Content-Type': '' -[2015-04-25 08:52:52 BST] Response header 'Content-Length': '775647' -[2015-04-25 08:52:52 BST] Response header 'Server': 'AmazonS3' -[2015-04-25 08:52:52 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> - -[2015-04-25 08:52:52 BST] String to sign: \"GET\n\n\nSat, 25 Apr 2015 07:52:52 GMT\n/BUCKET/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1\" -[2015-04-25 08:52:52 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-25 08:52:52 BST] Path: \"/GPGHMACSHA1--6e7e880f80de44ddd845c6241198622b9102eaa1\" -[2015-04-25 08:52:52 BST] Query string: \"\" -[2015-04-25 08:52:53 BST] Response status: Status {statusCode = 200, statusMessage = \"OK\"} -[2015-04-25 08:52:53 BST] Response header 'x-amz-id-2': 'QufZ3GyBdogXO8nVnqmJGU5mKZ7+I4DnU95aBUhy04f4158CGAIlp8vHrnGAMDVgLnLuM2TA70A=' -[2015-04-25 08:52:53 BST] Response header 'x-amz-request-id': 'A4EBAB4DD9E11352' -[2015-04-25 08:52:53 BST] Response header 'Date': 'Sat, 25 Apr 2015 07:52:54 GMT' -[2015-04-25 08:52:53 BST] Response header 'Last-Modified': 'Sun, 02 Nov 2014 05:42:48 GMT' -[2015-04-25 08:52:53 BST] Response header 'ETag': '\"3bd1b766a68a305ba0495af36b353a07\"' -[2015-04-25 08:52:53 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-25 08:52:53 BST] Response header 'Content-Type': '' -[2015-04-25 08:52:53 BST] Response header 'Content-Length': '775647' -[2015-04-25 08:52:53 BST] Response header 'Server': 'AmazonS3' -[2015-04-25 08:52:53 BST] Response metadata: S3: request ID=A4EBAB4DD9E11352, x-amz-id-2=QufZ3GyBdogXO8nVnqmJGU5mKZ7+I4DnU95aBUhy04f4158CGAIlp8vHrnGAMDVgLnLuM2TA70A= -74% 189.4KB/s 1s[2015-04-25 08:52:56 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--batch\",\"--passphrase-fd\",\"15\",\"--decrypt\"] -(checksum...) -ok -\"\"\"]] - - -In contrast, here is the output for a file that isn't in the remote -[[!format sh \"\"\" -> git annex fsck -f cloud notpresent --debug -git annex fsck -f cloud notpresent --debug --numcopies 1 -[2015-04-25 09:00:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-25 09:00:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-25 09:00:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..071d29cd21384f0ca129c76442c95c705b4ddc7b\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:00:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..7f6b0b58ef362edd43fc89d8ef641e18cfebcb4a\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:00:34 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-25 09:00:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"notpresent\"] -fsck notpresent [2015-04-25 09:00:34 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] -(checking cloud...) [2015-04-25 09:00:35 BST] String to sign: \"HEAD\n\n\nSat, 25 Apr 2015 08:00:35 GMT\n/BUCKET/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:00:35 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-25 09:00:35 BST] Path: \"/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:00:35 BST] Query string: \"\" -[2015-04-25 09:00:35 BST] Response status: Status {statusCode = 404, statusMessage = \"Not Found\"} -[2015-04-25 09:00:35 BST] Response header 'x-amz-request-id': 'AFA9934844CD547C' -[2015-04-25 09:00:35 BST] Response header 'x-amz-id-2': 'sDLFvcFj1pBh4Dhar/nxGGneN2ZP9XXPlI7GHyzuO1XiyW94b52pypel/1uSeFouWl8dXo4xOjc=' -[2015-04-25 09:00:35 BST] Response header 'Content-Type': 'application/xml' -[2015-04-25 09:00:35 BST] Response header 'Transfer-Encoding': 'chunked' -[2015-04-25 09:00:35 BST] Response header 'Date': 'Sat, 25 Apr 2015 08:00:34 GMT' -[2015-04-25 09:00:35 BST] Response header 'Server': 'AmazonS3' -[2015-04-25 09:00:35 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> -ok -\"\"\"]] -"""]] diff --git a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_3_b7402508dfc7bbbd09382692aa740c39._comment b/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_3_b7402508dfc7bbbd09382692aa740c39._comment deleted file mode 100644 index daa24f0cc..000000000 --- a/doc/todo/enable_fsck_--fast_for_S3_remotes/comment_3_b7402508dfc7bbbd09382692aa740c39._comment +++ /dev/null @@ -1,88 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" - nickname="Walter" - subject="comment 3" - date="2015-04-25T08:36:25Z" - content=""" -I also obtain the expected result if a file is thought to be present, but isn't. - -[[!format sh \"\"\" -> git annex setpresentkey `git annex lookupkey notpresent` be992080-b1db-11e1-8f79-1b10bb4092ef 1 -setpresentkey SHA256E-s37--2f9b7d77d43f49b59fb00148bc1b3d31a887ba717c988be55b9377d403a91f53 ok - -> git annex fsck --debug -f cloud --fast notpresent -[2015-04-25 09:24:25 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-25 09:24:25 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-25 09:24:25 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..0547dfd2d61ff9a24a08ff97cf4984bebbd4f0f1\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:24:25 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..b43028d651236ce59a3e47240bead91cdbfc37ea\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:24:25 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-25 09:24:25 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"notpresent\"] -fsck notpresent [2015-04-25 09:24:25 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] -(checking cloud...) [2015-04-25 09:24:25 BST] String to sign: \"HEAD\n\n\nSat, 25 Apr 2015 08:24:25 GMT\n/BUCKET/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:24:25 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-25 09:24:25 BST] Path: \"/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:24:25 BST] Query string: \"\" -[2015-04-25 09:24:25 BST] Response status: Status {statusCode = 404, statusMessage = \"Not Found\"} -[2015-04-25 09:24:25 BST] Response header 'x-amz-request-id': 'D562150974717AB1' -[2015-04-25 09:24:25 BST] Response header 'x-amz-id-2': 'Geq6BKC3Sg1rUuhgOHE7fOa5fq+L5ecShidW0ktI/ri3zNXKudhK5O5qT2qmUraJP6BCzDFuj1Q=' -[2015-04-25 09:24:25 BST] Response header 'Content-Type': 'application/xml' -[2015-04-25 09:24:25 BST] Response header 'Transfer-Encoding': 'chunked' -[2015-04-25 09:24:25 BST] Response header 'Date': 'Sat, 25 Apr 2015 08:24:24 GMT' -[2015-04-25 09:24:25 BST] Response header 'Server': 'AmazonS3' -[2015-04-25 09:24:25 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> -(fixing location log) - ** Based on the location log, notpresent - ** was expected to be present, but its content is missing. -failed -\"\"\"]] - - -That leaves only one case: when the file isn't thought to be in cloud, but is. For completeness - -[[!format sh \"\"\" -> git annex copy --to cloud notpresent -copy notpresent (checking cloud...) (to cloud...) -ok -(recording state in git...) -> git annex setpresentkey `git annex lookupkey notpresent` be992080-b1db-11e1-8f79-1b10bb4092ef 0 -setpresentkey SHA256E-s37--2f9b7d77d43f49b59fb00148bc1b3d31a887ba717c988be55b9377d403a91f53 ok - -> git annex fsck --debug -f cloud --fast notpresent -[2015-04-25 09:26:33 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"git-annex\"] -[2015-04-25 09:26:33 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -[2015-04-25 09:26:33 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..dca379d2631cd39bd205ccb7d6c192faea7c05c5\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:26:33 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"log\",\"refs/heads/git-annex..b43028d651236ce59a3e47240bead91cdbfc37ea\",\"-n1\",\"--pretty=%H\"] -[2015-04-25 09:26:33 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"cat-file\",\"--batch\"] -[2015-04-25 09:26:33 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"ls-files\",\"--cached\",\"-z\",\"--\",\"notpresent\"] -fsck notpresent [2015-04-25 09:26:33 BST] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--decrypt\"] -(checking cloud...) [2015-04-25 09:26:33 BST] String to sign: \"HEAD\n\n\nSat, 25 Apr 2015 08:26:33 GMT\n/BUCKET/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:26:33 BST] Host: \"BUCKET.s3-ap-southeast-2.amazonaws.com\" -[2015-04-25 09:26:33 BST] Path: \"/GPGHMACSHA1--e46ce4a11bc47622fb40affac818d6128bcd94bd\" -[2015-04-25 09:26:33 BST] Query string: \"\" -[2015-04-25 09:26:34 BST] Response status: Status {statusCode = 200, statusMessage = \"OK\"} -[2015-04-25 09:26:34 BST] Response header 'x-amz-id-2': '4Ti/62fBMzjW0woyrX5C++tQUw4uV97bbowjSiCkUNI6X2bAt+JCKbRYvZf/Is1QSY6SI2Aqgv4=' -[2015-04-25 09:26:34 BST] Response header 'x-amz-request-id': '9311809D4C8485FD' -[2015-04-25 09:26:34 BST] Response header 'Date': 'Sat, 25 Apr 2015 08:26:35 GMT' -[2015-04-25 09:26:34 BST] Response header 'Last-Modified': 'Sat, 25 Apr 2015 08:26:22 GMT' -[2015-04-25 09:26:34 BST] Response header 'ETag': '\"c5c3c0f720110210e73c7bf962d76390\"' -[2015-04-25 09:26:34 BST] Response header 'Accept-Ranges': 'bytes' -[2015-04-25 09:26:34 BST] Response header 'Content-Type': 'binary/octet-stream' -[2015-04-25 09:26:34 BST] Response header 'Content-Length': '99' -[2015-04-25 09:26:34 BST] Response header 'Server': 'AmazonS3' -[2015-04-25 09:26:34 BST] Response metadata: S3: request ID=<none>, x-amz-id-2=<none> - - failed to download file from remote -(fixing location log) failed -[2015-04-25 09:26:34 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"hash-object\",\"-w\",\"--stdin-paths\",\"--no-filters\"] -[2015-04-25 09:26:34 BST] feed: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"update-index\",\"-z\",\"--index-info\"] -[2015-04-25 09:26:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] -(recording state in git...) -[2015-04-25 09:26:34 BST] read: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"write-tree\"] -[2015-04-25 09:26:34 BST] chat: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"commit-tree\",\"83cec04d148757f98565eacda236d6e9dbd48678\",\"--no-gpg-sign\",\"-p\",\"refs/heads/git-annex\"] -[2015-04-25 09:26:34 BST] call: git [\"--git-dir=.git\",\"--work-tree=.\",\"--literal-pathspecs\",\"update-ref\",\"refs/heads/git-annex\",\"31d4a714f6977197029faf23b099ea32a298be59\"] -git-annex: fsck: 1 failed -\"\"\"]] - -This correctly determines that the file is present, and updates the location log. But I don't understand why the message ``failed to download file from remote`` is used (which is also used when a file is present, and thought to be present). For a fast fsck it shouldn't be trying to download the file. Also, I don't think this is specific to S3, I expect any remote will have the same behaviour. - -"""]] diff --git a/doc/todo/extensible_addurl.mdwn b/doc/todo/extensible_addurl.mdwn deleted file mode 100644 index 44b19fef0..000000000 --- a/doc/todo/extensible_addurl.mdwn +++ /dev/null @@ -1,88 +0,0 @@ -`git annex addurl` supports regular urls, as well as detecting videos that -quvi can download. We'd like to extend this to support extensible uri -handling. - -Use cases range from torrent download support, to pulling data -from scientific data repositories that use their own APIs. - -The basic idea is to have external special remotes (or perhaps built-in -ones in some cases), which addurl can use to download an object, referred -to by some uri-like thing. The uri starts with "$downloader:" to indicate -that it's not a regular url and so is not handled by the web special -remote. - - git annex addurl torrent:$foo - git annex addurl CERN:$bar - -Problem: This requires mapping from the name of the downloader, which is -probably the same as the git-annex-remote-$downloader program implementing -the special remote protocol (but not always), to the UUID of a remote. -That's assuming we want location tracking to be able to know that a file is -both available from CERN and from a torrent, for example. - -Solution: Add a new method to remotes: - - claimUrl :: Maybe (URLString -> Annex Bool) - -Remotes that implement this method (including special remotes) will -be queried when such an uri is added, to see which claims it. - -Once the remote is known, addurl --file will record that the Key is present -on that remote, and record the uri in the url log. - ----- - -What about using addurl to add a new file? In this mode, the Key is not yet -known. addurl currently handles this by generating a dummy Key for the url -(hitting the url to get its size), and running a Transfer using the dummy -key that downloads from the web. Once the download is done, the dummy Key -is upgraded to the final Key. - -Something similar could be done for other remotes, but the url log for the -dummy key would need to have the url added to it, for the remote to know -what to download, and then that could be removed after the download. Which -causes ugly churn in git, and would leave a mess if interrupted. - -One option is to add another new method to remotes: - - downloadUrl :: Maybe (URLString -> Annex FilePath) - -Or, the url log could have support added for recording temporary key -urls in memory. (done) - -Another problem is that the size of the Key isn't known. addurl -could always operate in relaxed mode, where it generates a size-less Key. -Or, yet another method could be added: (done) - - sizeUrl :: URLString -> Annex (Maybe Integer) - ----- - -Retrieval of the Key works more or less as usual. The only -difference being that remotes that support this interface can look -at the url log to find the one with the right "$downloader:" prefix, -and so know where to download from. (Much as the web special remote already -does.) - -Prerequisite: Expand the external special remote interface to support -accessing the url log. (done) - ----- - -It would also be nice to be able to easily configure a regexp that normal -urls, if they match, are made to use a particular downloader. So, for -torrents, this would make matching urls have torrent: prefixed to them. - - git config annex.downloader.torrent.regexp '(^magnet:|\.torrent$)' - -It might also be useful to allow bypassing the complexity of the external -special remote interface, and let a downloader be specified simply by: - - git config annex.downloader.torrent.command 'aria2c %url $file' - -This could be implemented in either the web special remote or even in an -external special remote. - -Some other discussion at <https://github.com/datalad/datalad/issues/10> - -> [[done]]! --[[Joey]] diff --git a/doc/todo/extensible_addurl/comment_1_5dca2eb8ee9e8676d372cd4bc6934975._comment b/doc/todo/extensible_addurl/comment_1_5dca2eb8ee9e8676d372cd4bc6934975._comment deleted file mode 100644 index 857df4254..000000000 --- a/doc/todo/extensible_addurl/comment_1_5dca2eb8ee9e8676d372cd4bc6934975._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="allow multiple urls" - date="2014-12-04T21:59:25Z" - content=""" -echoing https://github.com/datalad/datalad/issues/9 \"parallel download of a file from multiple URLs (and special remotes?)\" -might be worth adding e.g. - -git config annex.downloader.torrent.allowmultiple True - -and then using downloader which could fetch from multiple originating URLs simultaneously. In respect to aria2 (which seems to not support ATM specification of the output filename) see -https://github.com/tatsuhiro-t/aria2/issues/190 -"""]] diff --git a/doc/todo/extensible_addurl/comment_2_0e27f12c998a3ac4f0d4c3d4c9898d26._comment b/doc/todo/extensible_addurl/comment_2_0e27f12c998a3ac4f0d4c3d4c9898d26._comment deleted file mode 100644 index 191cc3ff7..000000000 --- a/doc/todo/extensible_addurl/comment_2_0e27f12c998a3ac4f0d4c3d4c9898d26._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2014-12-05T17:45:57Z" - content=""" -I think this issue of multiple files in a torrent is another place that -using an external special remote (or maybe one built into git-annex) -is better than just specifying a download command. A special remote for -torrents could use a temp directory that accumulates all the files in the -torrent, and then pluck out specific files as git-annex requests them. - -When git-annex exits, the special remote could clean up any unused files. -"""]] diff --git a/doc/todo/fast_migrate.mdwn b/doc/todo/fast_migrate.mdwn deleted file mode 100644 index 1571d880a..000000000 --- a/doc/todo/fast_migrate.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -Moved this comment to todo list --[[Joey]] - -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnfM7ZF0Q5U9k1LljyDXH37cuXU5Gx6gtM" - nickname="A" - subject="fast migrate" - date="2014-07-05T08:21:20Z" - content=""" -dear Joey and everybody else, - some time ago I used \"git annex migrate\" to bring all my repositories up-to-date; after that I found (to my dismay) that some keys are SHA256, some others are SHA256E, so my data is not really deduplicated ; now, it would possible to migrate from SHAnnnE to SHAnnn (and vice versa) very fast... but currently AFAICS git-annex recomputes the whole checksum, and this (on my USB2.0 old disks) takes forever; may somebody please implement a fast migration? -"""]] - -> Certianly doable, for $hashE to $hash. Probably about an hour's work. -> --[[Joey]] - ->> [[done]] --[[Joey]] diff --git a/doc/todo/fcntl_locks_break_with_threaded_concurrency.mdwn b/doc/todo/fcntl_locks_break_with_threaded_concurrency.mdwn deleted file mode 100644 index 3743886a9..000000000 --- a/doc/todo/fcntl_locks_break_with_threaded_concurrency.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -When using git-annex get -J2, one thread can clear another thread's -transfer lock. - -This happens because fcntl locking is used, and it is not thread-safe. -<https://github.com/haskell/unix/issues/44> - -> * If a process closes any file descriptor referring to a -> file, then all of the process's locks on that file are -> released, regardless of the file descriptor(s) on which the -> locks were obtained. - -One thread starts a transfer and locks it; the second thread starts a -transfer of a different file, and in order to check annex.diskreserve, -checks to see which other transfers are currently running. In doing this -check, it closes a fd attached to the first thread's lock, which causes the -lock to be dropped. - -This only affects -J mode. - -To fix it, probably need to use STM to keep a list of transfers all threads -in the current process are doing. Then the lock checking code can avoid -re-opening locks for transfers in the STM list. - -A more generic approach is to use Annex.LockFile for everything, -and make it check its lock pool via STM for other threads holding a lock. -(Currently, the pool is only used for shared locks.) ---[[Joey]] - -> [[fixed|done]] via LockPools. --[[Joey]] diff --git a/doc/todo/get_--incomplete.mdwn b/doc/todo/get_--incomplete.mdwn deleted file mode 100644 index 783108beb..000000000 --- a/doc/todo/get_--incomplete.mdwn +++ /dev/null @@ -1,8 +0,0 @@ -Use case: Resuming downloads that are incomplete (files in .git/annex/tmp), -without needing to remember the original get command(s) that started the -download. - -`git annex get --incomplete` could do this. (With or without --from to -specify which remote to get from.) --[[Joey]] - -> [[done]] --[[Joey]] diff --git a/doc/todo/git-annex-standalone_Debian_package.mdwn b/doc/todo/git-annex-standalone_Debian_package.mdwn deleted file mode 100644 index e45a72843..000000000 --- a/doc/todo/git-annex-standalone_Debian_package.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -As proposed with a sketch in https://github.com/joeyh/git-annex/pull/39, for DataLad we would need to get recent annex on older Debian/Ubuntu releases to get our testing farm and perspective users equipped with bleeding edge annex - -> merged [[done]] --[[Joey]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_1_ef36b0265127611ffeea3a5ed8c29515._comment b/doc/todo/git-annex-standalone_Debian_package/comment_1_ef36b0265127611ffeea3a5ed8c29515._comment deleted file mode 100644 index ad3f8b9e5..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_1_ef36b0265127611ffeea3a5ed8c29515._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-04-11T13:52:28Z" - content=""" -I think this will work. I don't see a way to do it other than as a patch -to debian/ though.. Unless perhaps you could pass flags to stuff to make -a different directory be used. If you could do that, it could be included -in git-annex's master. - -The package needs to depend on git (any version) so that the user can run -"git annex". - -The rest of the depends are not necessary though. The standalone tarball -includes its own wget, rsync, gpg, curl, and ssh, so git-annex will be able -to use those. - -If removing eg, the depends on wget though, you will want to add a -recommends on ca-certificates.. -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_2_456413718e9faf3561a11000ee611611._comment b/doc/todo/git-annex-standalone_Debian_package/comment_2_456413718e9faf3561a11000ee611611._comment deleted file mode 100644 index 50a2bf516..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_2_456413718e9faf3561a11000ee611611._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="now available" - date="2015-04-12T13:49:04Z" - content=""" -from stock NeuroDebian repository across all debian/ubuntu releases. Packaging is within debian-standalone branch of http://github.com/yarikoptic/git-annex - -So far -- built manually (well -- debian/build-standalone) on my laptop. Later will be automated on the buildbot. -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_3_22539df11d1a514987b9c257fd8b1998._comment b/doc/todo/git-annex-standalone_Debian_package/comment_3_22539df11d1a514987b9c257fd8b1998._comment deleted file mode 100644 index 7f0d1d51a..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_3_22539df11d1a514987b9c257fd8b1998._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY" - nickname="Yaroslav" - subject="missed the comment" - date="2015-04-12T13:55:50Z" - content=""" -blind me managed to miss your comment, for which I am thankful. A branch sounded like the best way to go so I don't need to mess with patching BUT now thinking about it, I might just indeed move it into a new debian/patch/series-standalone which would be the quilt series to use to patch things for building standalone. Then it could be shipped in the main repo and applied only when necessary. Sounds good? -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_4_0aecbfdc9048df2131d99ad316f5d6f7._comment b/doc/todo/git-annex-standalone_Debian_package/comment_4_0aecbfdc9048df2131d99ad316f5d6f7._comment deleted file mode 100644 index 0f2393fc1..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_4_0aecbfdc9048df2131d99ad316f5d6f7._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-04-14T19:14:16Z" - content=""" -The quilt series sounds reasonable if there's tooling to support building -that way. -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_5_b0730c577937f57547fabdd1ec57c01c._comment b/doc/todo/git-annex-standalone_Debian_package/comment_5_b0730c577937f57547fabdd1ec57c01c._comment deleted file mode 100644 index 3d19477c9..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_5_b0730c577937f57547fabdd1ec57c01c._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 5" - date="2015-06-08T19:27:02Z" - content=""" -is there a plan to distribute those packages officially somewhere? as mentionned in [[todo/git-annex_in_debian_sid/]], the official debian packages are seriously lagging behind... -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_6_18bc628db6b9ec8942552fdf587e7d4f._comment b/doc/todo/git-annex-standalone_Debian_package/comment_6_18bc628db6b9ec8942552fdf587e7d4f._comment deleted file mode 100644 index ab0ff4ec4..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_6_18bc628db6b9ec8942552fdf587e7d4f._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 6" - date="2015-06-09T13:51:10Z" - content=""" -nevermind, i found [the neurodebian archive](http://neuro.debian.net/pkgs/git-annex-standalone.html) and i think it's what i was looking for - although it does pull in way more stuff than just git-annex, which is unfortunate. - -i have documented this in the [[install]] page, i hope that's alright. -"""]] diff --git a/doc/todo/git-annex-standalone_Debian_package/comment_7_f8cce1be3153f2b2e069800cb60c4fd3._comment b/doc/todo/git-annex-standalone_Debian_package/comment_7_f8cce1be3153f2b2e069800cb60c4fd3._comment deleted file mode 100644 index 0b7fa25cc..000000000 --- a/doc/todo/git-annex-standalone_Debian_package/comment_7_f8cce1be3153f2b2e069800cb60c4fd3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="frederik@ffbea6a549cb3f460d110386c0f634c1ddc6a68a" - nickname="frederik" - subject="comment 7" - date="2015-06-10T12:43:45Z" - content=""" -Longshot, but would it be an option for [Yaroslav](https://alioth.debian.org/users/yoh/) to take over git-annex maintenance in Debian, given he's involved in creating this version for NeuroDebian? -"""]] diff --git a/doc/todo/git-annex_in_debian_sid.mdwn b/doc/todo/git-annex_in_debian_sid.mdwn deleted file mode 100644 index 99befd98a..000000000 --- a/doc/todo/git-annex_in_debian_sid.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -git-annex in debian sid is still at version 5.20141125: [https://tracker.debian.org/pkg/git-annex](https://tracker.debian.org/pkg/git-annex) - -Any chance that it gets updated soon? - -> Let's track this in the Debian bts, it can't be fixed here. [[done]] -> --[[Joey]] diff --git a/doc/todo/git-annex_in_debian_sid/comment_1_6225fd6237f77ab753429c72d60a9a9b._comment b/doc/todo/git-annex_in_debian_sid/comment_1_6225fd6237f77ab753429c72d60a9a9b._comment deleted file mode 100644 index 78952c679..000000000 --- a/doc/todo/git-annex_in_debian_sid/comment_1_6225fd6237f77ab753429c72d60a9a9b._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-06-09T16:50:04Z" - content=""" -I don't know what the holdup is. <http://bugs.debian.org/777577> -"""]] diff --git a/doc/todo/git-annex_info___34__du__34___remote_support.mdwn b/doc/todo/git-annex_info___34__du__34___remote_support.mdwn deleted file mode 100644 index e20cdc928..000000000 --- a/doc/todo/git-annex_info___34__du__34___remote_support.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -so i know about the various discussions around a `du` that follows git-annex symlinks (e.g. [[forum/__34__du__34___equivalent_on_an_annex__63__/]] or [[forum/gadu_-_git-annex_disk_usage/]]. this is not about that, or at least not directly. :) - -i believe there's a distinct use-case for a simpler `du` subcommand that will calculate the disk space used locally (in case of the default `--in here`) but could also use the tracking log to determine the space usage in *other* locations. this would be especially useful on remotes that we don't have shell access to, s3 comes to mind. i thought that `git annex info` could output that, but it seems it doesn't: - -<pre> -$ git annex info . --in s3 --exclude='video/original/*' -directory: . -local annex keys: 0 -local annex size: 0 bytes -annexed files in working tree: 0 -size of annexed files in working tree: 0 bytes -numcopies stats: -repositories containing these files: -$ git annex info --in s3 --exclude='video/original/*' -repository mode: indirect -trusted repositories: 0 -semitrusted repositories: 6 - 00000000-0000-0000-0000-000000000002 -- bittorrent - 2d61a8de-a24e-44e3-9aa0-54f033fec1e9 -- host-mp20120507-1.mp.isuma.tv - 9401d7b3-44d2-48ab-a9f1-c77fac469a1a -- s3 - c510ddad-24cd-4353-b5f4-03581f6f9dca -- cs.isuma.tv [here] - d2a7d4ff-1dbf-4bfa-bb97-ae593626daf6 -- sneakernet - e747d5c8-ea47-480f-8c5d-2986ce65ed89 -- isuma.tv -untrusted repositories: 2 - 00000000-0000-0000-0000-000000000001 -- web - 36d2cb94-e0a2-446a-87c9-02f73135b302 -- anarcat@desktop008:~/src/isuma/isuma-files -transfers in progress: none -available local disk space: 67.66 gigabytes (+1 megabyte reserved) -local annex keys: 0 -local annex size: 0 bytes -annexed files in working tree: 0 -size of annexed files in working tree: 0 bytes -bloom filter size: 16 mebibytes (0% full) -backend usage: -</pre> - -just to be clear here, the problem isn't as much providing `du-like output`, which `git annex info $path` does pretty well. the problem is that it doesn't work on remote servers, at least that is what i observed above. - -i still think it would be nice to have a `du` command, just because it's a command "WTF" situation users seem to get stuck into.. but this issue is only about having this work on remote repositories. thanks! -- [[anarcat]] - -> Fixed via time machine. [[done]] --[[Joey]] diff --git a/doc/todo/git-annex_info___34__du__34___remote_support/comment_1_9d3ac51bdf3bb749bc40a1bb05edbc76._comment b/doc/todo/git-annex_info___34__du__34___remote_support/comment_1_9d3ac51bdf3bb749bc40a1bb05edbc76._comment deleted file mode 100644 index 59607928e..000000000 --- a/doc/todo/git-annex_info___34__du__34___remote_support/comment_1_9d3ac51bdf3bb749bc40a1bb05edbc76._comment +++ /dev/null @@ -1,30 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-07-02T19:58:10Z" - content=""" -Actually, this was added in version 5.20150420, when info is run -with a directory parameter. - - joey@darkstar:~/lib/sound/misc>git annex info . - directory: . - local annex keys: 2 - local annex size: 10.5 megabytes - annexed files in working tree: 21 - size of annexed files in working tree: 288.98 megabytes - numcopies stats: - numcopies +3: 19 - numcopies +4: 2 - repositories containing these files: 11 - 288.98 MB: 0c443de8-e644-11df-acbf-f7cd7ca6210d -- oldgnu - 288.98 MB: 1b5ecc94-abb3-45f7-8f4c-5bc65f78d518 -- toshiba passport 1tb [passport] - 288.98 MB: 6fa26a5f-cb05-4ef0-951b-bc59266ee4e4 -- archive-10 [archive] - 288.98 MB: 7570b02e-15e9-11e0-adf0-9f3f94cb2eaa -- archive-4 sata drive - 288.98 MB: 8da3593e-63d2-11e1-a026-43b95a8b93d2 -- archive-7 sata drive - 288.98 MB: b0bb7176-98e6-457d-b68e-41bfd49be147 -- joey@gnu:~/lib/sound [gnu] - 288.98 MB: b238695e-e617-11df-9d8b-c350f0825fb0 -- turtle internal [turtle] - 288.98 MB: ca9c5d52-f03a-11df-ac14-6b772ffe59f9 -- archive-5 sata drive - 288.98 MB: f1c0ce8d-d848-4d21-988c-dd78eed172e8 -- archive-8 sata drive - 10.5 MB: 587b9ccf-4548-4d6f-9765-27faecc4105f -- darkstar [here] - -"""]] diff --git a/doc/todo/git-annex_info___34__du__34___remote_support/comment_2_1547eb348bf30e5a06686aee082062f4._comment b/doc/todo/git-annex_info___34__du__34___remote_support/comment_2_1547eb348bf30e5a06686aee082062f4._comment deleted file mode 100644 index d7e59b6a0..000000000 --- a/doc/todo/git-annex_info___34__du__34___remote_support/comment_2_1547eb348bf30e5a06686aee082062f4._comment +++ /dev/null @@ -1,45 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-07-02T20:04:19Z" - content=""" -Note that using `--in remote` also limits the display to files that -are present in the specified remote, much as --exclude limits the display. - - joey@darkstar:~/lib/sound/podcasts/Agile_in_3_Minutes>git annex info . --in archive-10 - directory: . - local annex keys: 13 - local annex size: 27.88 megabytes - annexed files in working tree: 13 - size of annexed files in working tree: 27.88 megabytes - numcopies stats: - numcopies +1: 9 - numcopies +2: 4 - repositories containing these files: 5 - 27.88 MB: 00000000-0000-0000-0000-000000000001 -- web - 27.88 MB: 1b5ecc94-abb3-45f7-8f4c-5bc65f78d518 -- toshiba passport 1tb [passport] - 27.88 MB: 587b9ccf-4548-4d6f-9765-27faecc4105f -- darkstar [here] - 27.88 MB: 6fa26a5f-cb05-4ef0-951b-bc59266ee4e4 -- archive-10 [archive] - 8.3 MB: b0bb7176-98e6-457d-b68e-41bfd49be147 -- joey@gnu:~/lib/sound [gnu] - joey@darkstar:~/lib/sound/podcasts/Agile_in_3_Minutes>git annex info . - directory: . - local annex keys: 16 - local annex size: 34.32 megabytes - annexed files in working tree: 16 - size of annexed files in working tree: 34.32 megabytes - numcopies stats: - numcopies +1: 9 - numcopies +2: 4 - numcopies +0: 3 - repositories containing these files: 5 - 34.32 MB: 00000000-0000-0000-0000-000000000001 -- web - 34.32 MB: 1b5ecc94-abb3-45f7-8f4c-5bc65f78d518 -- toshiba passport 1tb [passport] - 34.32 MB: 587b9ccf-4548-4d6f-9765-27faecc4105f -- darkstar [here] - 27.88 MB: 6fa26a5f-cb05-4ef0-951b-bc59266ee4e4 -- archive-10 [archive] - 8.3 MB: b0bb7176-98e6-457d-b68e-41bfd49be147 -- joey@gnu:~/lib/sound [gnu] - -In the first command above, it is only considering files that are in the archive-10 remote, -and it shows what size those files are taking up on each listed repository. The second command -considers all files and we can see that some other repos have files not present in the archive-10 remote. - -"""]] diff --git a/doc/todo/git-annex_metadata_extractor_progress_bar.mdwn b/doc/todo/git-annex_metadata_extractor_progress_bar.mdwn deleted file mode 100644 index 87fcdae92..000000000 --- a/doc/todo/git-annex_metadata_extractor_progress_bar.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -it can take a significant amount of time for the [[automatic metadata script|tips/automatically_adding_metadata/]] to run on commit. it would be nice to have some progress, otherwise it just looks like the command is hanging. - -here it's been processing my photos for more than three hours, and it's probably not even halfway done, according to ps... [[anarcat]] - -> Well, I added an echo of each file as it's processed. More complex -> progress could be done, patches accepted. But I suppose a file list is -> good enough; it's good enough for git-annex itself. [[done]] --[[Joey]] diff --git a/doc/todo/git_annex_get___60__file__62___should_verify_file_hash.mdwn b/doc/todo/git_annex_get___60__file__62___should_verify_file_hash.mdwn deleted file mode 100644 index fd93554ec..000000000 --- a/doc/todo/git_annex_get___60__file__62___should_verify_file_hash.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -### Please describe the problem. -git annex get fileName- should perform a hash check on the file content before adding to the local repository - - -### What steps will reproduce the problem? -Two scenarios: -1) Malicious user and owner of repository being pulled from can edit his/her local .git/annex/objects directory -to alter the file content. For src code, this could be to insert a bug, insert a backdoor, or for example -to replace an image file artifact for a website, with a pornographic image. -The user pulling the file content with "git annex get fileName" might not be aware of the file contents -until they actually examine the file or perform an fsck or commit locally. -In the meantime a kiddy porn image could be sitting in their repository or a src code backdoor can get incorporated and deployed etc. -2) a file could also simply get corrupted during download. An inherent hash check during the 'annex get' would -point out the problem immediately. -To reproduce: create repoNum1, and clone it to create repoNum2. manual edit/replace content in repoNum1/.git/annex/objects/... -then perform a 'git annex get <fileName>' from repoNum2 on the file that has been manipulated - - -### What version of git-annex are you using? On what operating system? -3.2012112ubuntu2 on running linux mint - - -### Please provide any additional information below. - -Aside: Thanks Joey - this is fantastic work you are doing. You have really improved git. The ability to checkout -an entire tree - but selectively get only the content actually needed is a real killer feature. -Kudos and again many many thanks -M. - - -# End of transcript or log. -"""]] - -> [[duplicate|done]] of [[checksum_verification_on_transfer]] --[[Joey]] diff --git a/doc/todo/git_annex_get___60__file__62___should_verify_file_hash/comment_1_650e01a04104120ef1db4ff16fedc4f1._comment b/doc/todo/git_annex_get___60__file__62___should_verify_file_hash/comment_1_650e01a04104120ef1db4ff16fedc4f1._comment deleted file mode 100644 index 621e01d6f..000000000 --- a/doc/todo/git_annex_get___60__file__62___should_verify_file_hash/comment_1_650e01a04104120ef1db4ff16fedc4f1._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.87" - subject="comment 1" - date="2013-12-15T19:38:48Z" - content=""" -If you don't trust a remote repository, then you should either - -a) Not use that repository at all, because its malicious owner could put any evil file he wants in it with an entirely correct hash. - -b) Make it a gcrypt remote so all content stored on it is encrypted. Decrypting it will include validating that you get out what you originally put in. - -So these scenarios are not good arguments for validating every file after it's downloaded. - -If it were possible to do a rolling checksum as part of the download, rather than needing to pull the entire file back off disk and checksum it, I'd do so. But it's generally not; for example when git-annex is downloading a file using rsync it may resume part way through a previous interrupted download, and rsync is storing the file to disk, not streaming it to git-annex. -"""]] diff --git a/doc/todo/git_annex_grep.mdwn b/doc/todo/git_annex_grep.mdwn deleted file mode 100644 index 8cff25e9b..000000000 --- a/doc/todo/git_annex_grep.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -### Please describe the problem. - -inability to quickly grep locally present files - -### What steps will reproduce the problem? - -run "git annex grep" - -> i don't understand this request. just running `grep` will grep all the locally present files: sure there will be warnings, but you can use `2>/dev/null` to silence those. as for the suggested solution in comment, that greps for the filenames. please clarify the feature request here or this is [[invalid|done]]. --[[anarcat]] - ->> The reason `git grep` exists is partly speed (git objects can ->> sometimes be read more efficiently than traversing the fileststem), ->> and partly the ability to grep a whole tree of source code, but ->> avoid grepping build artifacts, etc. The former reason doesn't apply ->> with git-annex. The latter reason applies somewhat, but it's much less ->> common to want to grep large binary files than it is to want to grep a ->> source tree. `git annex find` can be fed to `grep` when one wants to do ->> that. So I don't see a compelling case to add this to git-annex. ->> --[[Joey]] diff --git a/doc/todo/git_annex_grep/comment_1_890b3ecb679b941f9c0075ed360b203e._comment b/doc/todo/git_annex_grep/comment_1_890b3ecb679b941f9c0075ed360b203e._comment deleted file mode 100644 index 30351c2ed..000000000 --- a/doc/todo/git_annex_grep/comment_1_890b3ecb679b941f9c0075ed360b203e._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="CandyAngel" - subject="comment 1" - date="2015-06-04T12:31:32Z" - content=""" -You can do this: - - git annex find --in here | grep -"""]] diff --git a/doc/todo/inject_on_import.mdwn b/doc/todo/inject_on_import.mdwn deleted file mode 100644 index d33267987..000000000 --- a/doc/todo/inject_on_import.mdwn +++ /dev/null @@ -1,63 +0,0 @@ -Would it be possible to add an `--inject` option to import? - -Say, for example, I have an annex on computer A which has a subset of files and a directory of files which are potentional duplicates of files in the annex. - -I would like to do something like this: - - mkdir ~/annex/import - cd ~/annex/import - git annex import --deduplicate --inject ~/directory/of/files - -This would do the same as `--deduplicate`, except if the file is not present in the annex, it would be injected. For example: - -Annex knows about A and B, A is present but B is not. -$DIR contains A, B and C. - -A would be deleted from $DIR due to `--deduplicate`. -B would be injected into the repo (making it present) due to `--inject`, then deleted from $DIR. -C would be added to the annex, resulting in this - - $ ls ~/annex/import - C - -> You seem to have described exactly what --deduplicate already does. -> For example: - -<pre> -# mkdir x -# cd x -# l -# git init -Initialized empty Git repository in /home/joey/tmp/x/.git/ -# git annex init -init ok -(Recording state in git...) -# echo hello > foo -# git annex add foo -add foo ok -(Recording state in git...) -# mkdir ../src -# echo hello > ../src/bar -# echo new > ../src/baz -# git annex import --deduplicate ../src -import src/bar (duplicate) ok -import src/baz ok -(Recording state in git...) -# ls -foo@ src/ -# ls ../src/ -# ls src -baz@ -</pre> - -> And, if you look at the documentation for --deduplicate, -> this is what it says: - -<pre> - To only import files whose content has not been seen - before by git-annex, use the --deduplicate option. - Duplicate files will be deleted from the import loca‐ - tion. -</pre> - -> So, [[done]] I suppose... --[[Joey]] diff --git a/doc/todo/inject_on_import/comment_1_314de82da94f47539e754e9bec950d7b._comment b/doc/todo/inject_on_import/comment_1_314de82da94f47539e754e9bec950d7b._comment deleted file mode 100644 index 693f967cf..000000000 --- a/doc/todo/inject_on_import/comment_1_314de82da94f47539e754e9bec950d7b._comment +++ /dev/null @@ -1,67 +0,0 @@ -[[!comment format=mdwn - username="Xyem" - subject="comment 1" - date="2015-03-20T10:51:59Z" - content=""" -I just tested this and git-annex does not act according to its documentation. - - ## git init annex - Initialized empty Git repository in ./annex/.git/ - ## mkdir to_import - mkdir: created directory ‘to_import’ - ## echo A > annex/A - ## echo B > annex/B - ## echo A > to_import/A - ## echo B > to_import/B - ## echo C > to_import/C - ## cd annex/ - ## git annex init - init ok - (Recording state in git...) - ## git annex add . - add A ok - add B ok - (Recording state in git...) - ## git commit -m \"commit\" - [master (root-commit) f2628f0] commit - 2 files changed, 2 insertions(+) - create mode 120000 A - create mode 120000 B - - ## git annex drop B --force - drop B ok - (Recording state in git...) - -Annex knows about A and B, A is present but B is not. - -to_import contains A, B and C. - - ## git annex import --deduplicate ../to_import/ - import to_import/C ok - import to_import/A (duplicate) ok - import to_import/B ok - (Recording state in git...) - ## ls -R - .: - A B to_import - - ./to_import: - B C - -According to the docs, it would look like this: - - ## ls -R - .: - A B to_import - - ./to_import: - C - -and B would be a dangling symlink (due to the content having been seen by the annex before, but not present). - -So '--import --deduplicate' actually imports/deduplicates files whose content /is not present/ in the annex, rather than 'has not been seen before'. - -Fortunately, this error is on the side of caution and data is never lost, but you do end up with duplicates (2 symlinks pointing to the same content). - -The behaviour is acceptable (to me at least, better duplicate symlinks than lost data), but the documentation is misleading and should probably refer to content presence rather than having ever been present. -"""]] diff --git a/doc/todo/inject_on_import/comment_2_205ecbc7401f99fc83719acbf5da174e._comment b/doc/todo/inject_on_import/comment_2_205ecbc7401f99fc83719acbf5da174e._comment deleted file mode 100644 index acd661feb..000000000 --- a/doc/todo/inject_on_import/comment_2_205ecbc7401f99fc83719acbf5da174e._comment +++ /dev/null @@ -1,26 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2015-03-26T15:28:45Z" - content=""" -Well, you've found an edge case here. - -It behaves as documented as long as the file being imported is located in some -repository know to git-annex. The file content does not have to be present in -the local repository for it to behave as documented. - -In your case, the file being imported has a symlink in the git repo, but -git-annex knows about 0 annexed copies of the file, so it's treated as -if it's a new file and not a duplicate. - -Since import is working at the key level, there's not a good way to look up -that there are some symlinks in the git repo even though the content is -gone. And even if there was, I think I'd be uncomfortable with it deleting -the file as "duplicate" when its content is not available in any known -repository. The only behavior improvement might be to import the content -but not make a redundant symlink in this case. - -I think it's best to change the documentation. I've added a new -paragraph that more exactly and clearly explains what duplicate files -are for the purposes of importing. -"""]] diff --git a/doc/todo/merge_in_ram___40__disk__41____63__.mdwn b/doc/todo/merge_in_ram___40__disk__41____63__.mdwn deleted file mode 100644 index 42090f673..000000000 --- a/doc/todo/merge_in_ram___40__disk__41____63__.mdwn +++ /dev/null @@ -1,8 +0,0 @@ -git-annex is great. But for my repos the merge and recording state operations take forever. - -(merging fotos_enc_pg/synced/git-annex into git-annex...) - -Since git-annex is another branch (than master) and git usually needs a worktree for merging I assume that git-annex branch is temporarily checked out somewhere. Would it be possible to move this operation to RAM? Or a RAM-Disk? - -> No, it is not checked out. All operations are done with the most -> effective available git plumbing. [[done]] --[[Joey]] diff --git a/doc/todo/notifications.mdwn b/doc/todo/notifications.mdwn deleted file mode 100644 index d332d1029..000000000 --- a/doc/todo/notifications.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -Just started today with git-annex and it looks great replacement for proprietary syncing solutions (well in allot of aspects it's much better than proprietary solutions) but I do believe desktop and email notifications are must have features. - -I think these services would be nice to have: growl, libnotify, email, twitter (publicly sharing with a group or repository stored on public server for users to download). - -> git-annex has desktop notifications. I think that if you want something -> beyond that, you should script it. So, [[done]] --[[Joey]] diff --git a/doc/todo/podcatching_handling_updated_files.mdwn b/doc/todo/podcatching_handling_updated_files.mdwn deleted file mode 100644 index 2d9800283..000000000 --- a/doc/todo/podcatching_handling_updated_files.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -Files in feeds can be updated, and if this update includes changing the -url, `importfeed` will treat this as a new file. This results in `foo.mp3` -having a `2_foo.mp3` added next to it. - -This seems to happen especially commonly with feeds using FeedBurner. -Saw several with same size, different checksum and url. - -To detect this, `importfeed` could store the item's guid in the metadata -of the key. Where it currently builds a `Map URLString Key` of all -known items, it could instead build a `Map (Either URlString GUID) Key`. - -This would at least prevent the duplication, when the feed has guids. - -> [[done]] --[[Joey]] - -It would be even nicer if the old file could be updated with the new -content. But, since files can be moved around, deleted, tagged, etc, -that only seems practical at all if the file is still in the directory -where `importfeed` created it. diff --git a/doc/todo/remote_groups_support_for_sync.mdwn b/doc/todo/remote_groups_support_for_sync.mdwn deleted file mode 100644 index b49016427..000000000 --- a/doc/todo/remote_groups_support_for_sync.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -`git remote update $group` looks at the $group.away git config and fetches -from the listed remotes. It would be useful if `git annex sync $group` did the same. ---[[Joey]] - -[[done]] diff --git a/doc/todo/replace_dataenc_with_sandi.mdwn b/doc/todo/replace_dataenc_with_sandi.mdwn deleted file mode 100644 index 9ce29663b..000000000 --- a/doc/todo/replace_dataenc_with_sandi.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -<https://github.com/joeyh/git-annex/pull/15> - -sandi is available in jessie, but not wheezy, so this is pending -EOL of wheezy support. --[[Joey]] - -> [[fixed|done]] --[[Joey]] diff --git a/doc/todo/resuming_encrypted_uploads.mdwn b/doc/todo/resuming_encrypted_uploads.mdwn deleted file mode 100644 index 44a58a141..000000000 --- a/doc/todo/resuming_encrypted_uploads.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -Resuming interrupted uploads to encrypted special remotes is not currently -possible, because gpg does not produce consistent output. Special remotes -that could support resuming include rsync and glacier. - -Without consistent output, git-annex would need to locally cache the encrypted -file, and reuse that cache when resuming an upload. This would make -encrypted uploads more expensive in terms of both file IO and disk space -used. - -[It would be possible to write to the cache at the same time the special -remote is being fed data, and if the special remote upload fails, continue -writing the rest of the file. That would avoid half the overhead, since -the file would not need to be read from, just written to. (Although OS -caching may accomplish the same thing.)] - -Also, `git annex unused` would need to show temp files for uploads, -the same as it currently shows temp files for downloads, and users would -sometimes need to manually dropunused old uploads, that never completed. - -The question, then, is whether resuming uploads is useful enough to add -this overhead and user-visible complexity. ---[[Joey]] - -> The new-style chunking code chunks and then encrypts. This means that -> each individual chunk is a stand-alone file that can be decrypted later, -> and so resumes of uploads to encrypted, chunked remotes works now. -> -> I think that's better than the ideas discussed above, so [[done]] -> --[[Joey]] diff --git a/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment b/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment deleted file mode 100644 index cf35de049..000000000 --- a/doc/todo/resuming_encrypted_uploads/comment_1_1832a6fb78e8ad7c838582f46731ac3b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://phil.0x539.de/" - nickname="Philipp Kern" - subject="comment 1" - date="2012-12-28T23:23:29Z" - content=""" -Doesn't the encryption part already write an encrypted version completely to disk before starting to upload? (At least with the rsync remote?) So the disk space and I/O usage is already there. (Except that it's probably a temporary file that's deleted after it was created, so that it's not kept around by the filesystem when certain destructive events strike.) -"""]] diff --git a/doc/todo/resuming_encrypted_uploads/comment_2_2ecc8e782f49e90ed1549e9179eb1a1e._comment b/doc/todo/resuming_encrypted_uploads/comment_2_2ecc8e782f49e90ed1549e9179eb1a1e._comment deleted file mode 100644 index a2bab9244..000000000 --- a/doc/todo/resuming_encrypted_uploads/comment_2_2ecc8e782f49e90ed1549e9179eb1a1e._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" - nickname="Michael" - subject="comment 2" - date="2012-12-29T08:00:56Z" - content=""" -Being able to resume transfers of encrypted files would absolutely be useful! Disk space is cheap, but bandwidth is not. -"""]] diff --git a/doc/todo/server-level_daemon__63__.mdwn b/doc/todo/server-level_daemon__63__.mdwn deleted file mode 100644 index 544624031..000000000 --- a/doc/todo/server-level_daemon__63__.mdwn +++ /dev/null @@ -1,203 +0,0 @@ -coming from [[bugs/weird_entry_in_process_list]] - are there plans to make an init.d / systemd .service file for git-annex? - -my use case is that i have dedicated machines that will sync a common directory. they will run only one assistant - would patches to make a `git-annex` user, and the associated startup scripts, in the debian package be welcome? --[[anarcat]] - -Here's a sample startup script: - -<pre> -#!/bin/sh -### BEGIN INIT INFO -# Provides: gitannex -# Required-Start: $local_fs $network $remote_fs $syslog -# Required-Stop: $local_fs $network $remote_fs $syslog -# Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 -# Short-Description: start the git-annex assistant -# Description: start the git-annex assistant in the given directory -### END INIT INFO - -# Author: Antoine Beaupré <anarcat@koumbit.org> - -# Do NOT "set -e" - -# PATH should only include /usr/* if it runs after the mountnfs.sh script -PATH=/sbin:/usr/sbin:/bin:/usr/bin -DESC="gitannex" -NAME=gitannex -USER=$NAME -DAEMON=git-annex -DAEMON_ARGS="assistant" -PIDFILE=/var/run/$NAME.pid -SCRIPTNAME=/etc/init.d/$NAME -ANNEX=auto - -# Read configuration variable file if it is present -[ -r /etc/default/$NAME ] && . /etc/default/$NAME - -# Exit if the package is not installed -[ -x "$DAEMON" ] || exit 0 - -# Load the VERBOSE setting and other rcS variables -. /lib/init/vars.sh - -# Define LSB log_* functions. -# Depend on lsb-base (>= 3.2-14) to ensure that this file is present -# and status_of_proc is working. -. /lib/lsb/init-functions - -if [ "$ANNEX" = "auto" ]; then - DAEMON_ARGS="$DAEMON_ARGS --autostart" -else - cd $ANNEX - PIDFILE="$ANNEX/.git/annex/daemon.pid" - EXTRA_OPTS="--chdir $ANNEX" -fi - -# -# Function that starts the daemon/service -# -do_start() -{ - # Return - # 0 if daemon has been started - # 1 if daemon was already running - # 2 if daemon could not be started - start-stop-daemon --start --quiet --user $USER --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ - || return 1 - start-stop-daemon --start --quiet --user $USER --chuid $USER $EXTRA_OPTS --pidfile $PIDFILE --exec $DAEMON -- \ - $DAEMON_ARGS \ - || return 2 - # The above code will not work for interpreted scripts, use the next - # six lines below instead (Ref: #643337, start-stop-daemon(8) ) - #start-stop-daemon --start --quiet --pidfile $PIDFILE --startas $DAEMON \ - # --name $NAME --test > /dev/null \ - # || return 1 - #start-stop-daemon --start --quiet --pidfile $PIDFILE --startas $DAEMON \ - # --name $NAME -- $DAEMON_ARGS \ - # || return 2 - - # Add code here, if necessary, that waits for the process to be ready - # to handle requests from services started subsequently which depend - # on this one. As a last resort, sleep for some time. -} - -# -# Function that stops the daemon/service -# -do_stop() -{ - # Return - # 0 if daemon has been stopped - # 1 if daemon was already stopped - # 2 if daemon could not be stopped - # other if a failure occurred - su $USER -c "$DAEMON $DAEMON_ARGS --stop" && return 0 - # Wait for children to finish too if this is a daemon that forks - # and if the daemon is only ever run from this initscript. - # If the above conditions are not satisfied then add some other code - # that waits for the process to drop all resources that could be - # needed by services started subsequently. A last resort is to - # sleep for some time. - start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --user $USER --exec $DAEMON - [ "$?" = 2 ] && return 2 - # Many daemons don't delete their pidfiles when they exit. - rm -f $PIDFILE - return "$RETVAL" -} - -# -# Function that sends a SIGHUP to the daemon/service -# -do_reload() { - # - # If the daemon can reload its configuration without - # restarting (for example, when it is sent a SIGHUP), - # then implement that here. - # - start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME - return 0 -} - -case "$1" in - start) - [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" - do_start - case "$?" in - 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; - 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; - esac - ;; - stop) - [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" - do_stop - case "$?" in - 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; - 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; - esac - ;; - status) - status_of_proc -p "$PIDFILE" "$DAEMON" "$NAME" && exit 0 || exit $? - ;; - #reload|force-reload) - # - # If do_reload() is not implemented then leave this commented out - # and leave 'force-reload' as an alias for 'restart'. - # - #log_daemon_msg "Reloading $DESC" "$NAME" - #do_reload - #log_end_msg $? - #;; - restart|force-reload) - # - # If the "reload" option is implemented then remove the - # 'force-reload' alias - # - log_daemon_msg "Restarting $DESC" "$NAME" - do_stop - case "$?" in - 0|1) - do_start - case "$?" in - 0) log_end_msg 0 ;; - 1) log_end_msg 1 ;; # Old process is still running - *) log_end_msg 1 ;; # Failed to start - esac - ;; - *) - # Failed to stop - log_end_msg 1 - ;; - esac - ;; - *) - #echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2 - echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 - exit 3 - ;; -esac - -: -</pre> - -Now this is not without problems: - - 1. it assumes a gitannex user is created outside of the script - 2. it assumes a gitannex repository is created outside of the script and specified in the `/etc/default/gitannex` file (or added to the autostart file) - 3. it is Debian-specific (a proper init script would be POSIX only and/or a `.service` file) - -Maybe using [metainit](https://wiki.debian.org/MetaInit) would be a good idea here? --[[anarcat]] - -> This strikes me as a bad idea if the system has regular desktop etc -> users; the assistant can already start itself when they login and -> a separate user has the same problems the separate mpd user seems to; -> of separating the user from the files that effcetively belong to them. -> -> It's fine if you're doing something more specialized, but that seems -> like an unusual case and not one that git-annex should cater to. -> -> Anyway, it's about 5 lines to write a systemd service file. I've added -> `git annex assistant --autostop` that such a service can use if desired. -> -> Since I don't want to include that in git-annex and be stuck supporting -> it, and it should be easy for users to add if they need it, I think I'm -> going to call this [[done]]. --[[Joey]] diff --git a/doc/todo/server-level_daemon__63__/comment_1_1abea0cbfcc603da779a811731c38b5f._comment b/doc/todo/server-level_daemon__63__/comment_1_1abea0cbfcc603da779a811731c38b5f._comment deleted file mode 100644 index e6d6e297a..000000000 --- a/doc/todo/server-level_daemon__63__/comment_1_1abea0cbfcc603da779a811731c38b5f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 1""" - date="2015-02-25T18:06:57Z" - content=""" -That strikes me as a bad idea in general. Why a dedicated user? What's wrong -with starting the assistant from the user account where you want it -to run on boot? (Using cron @reboot, or systemd, or logind, or surely -many other methods.) -"""]] diff --git a/doc/todo/server-level_daemon__63__/comment_2_4a5ccb0e772352adbf20940c010895a5._comment b/doc/todo/server-level_daemon__63__/comment_2_4a5ccb0e772352adbf20940c010895a5._comment deleted file mode 100644 index cc6ab9848..000000000 --- a/doc/todo/server-level_daemon__63__/comment_2_4a5ccb0e772352adbf20940c010895a5._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 2" - date="2015-02-26T23:52:52Z" - content=""" -because this is a server without a generic \"user account\". there are multiple admins with each their own account, and i'd like to have git-annex run as its own account. and yes, probably under systemd, but under wheezy, under init.d. - -i would avoid @reboot cron jobs because systemd can't restart it if they fail. -"""]] diff --git a/doc/todo/server-level_daemon__63__/comment_3_60c5030a21c28b79f634f0655bc6c05d._comment b/doc/todo/server-level_daemon__63__/comment_3_60c5030a21c28b79f634f0655bc6c05d._comment deleted file mode 100644 index 974cc0a11..000000000 --- a/doc/todo/server-level_daemon__63__/comment_3_60c5030a21c28b79f634f0655bc6c05d._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="comment 3" - date="2015-02-26T23:53:32Z" - content=""" -why would that be a bad idea anyways? -"""]] diff --git a/doc/todo/subsecond_timestamping_of_the_--debug_output.mdwn b/doc/todo/subsecond_timestamping_of_the_--debug_output.mdwn deleted file mode 100644 index 8d963c432..000000000 --- a/doc/todo/subsecond_timestamping_of_the_--debug_output.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -ATM --debug uses timestamps at second precision. Would be nice (to see where time is spent) to have subsecond timing - -> [[done]], I was able to get fractional seconds down to 0.000001 -> in the debug output. --[[Joey]] diff --git a/doc/todo/unused_by_refspec.mdwn b/doc/todo/unused_by_refspec.mdwn deleted file mode 100644 index ea84599bb..000000000 --- a/doc/todo/unused_by_refspec.mdwn +++ /dev/null @@ -1,41 +0,0 @@ -Currently `git annex unused` assumes that all branches (including remote -tracking branches) and tags are "used" and finds only objects not used by -any of those refs. - -That's a reasonable default, but in some cases, we don't care about -specific refs. Perhaps we don't consider remote tracking branches -important. Or perhaps we only want objects in HEAD to be considered used. - -This could be handled by adding an option to specify a refspec when running -git-annex unused. Only matching refs would be checked. It's probably worth -making this be both a command-line option --used-refspec, as well as a -annex.used-refspec config setting. - -git's refspec format is not quite right (since it specifies a local side -and a remote side for push/pull). But, it can be used as a point of -departure. Let's allow wildcards as it does, and use leading '+' to add a -ref, and '-' to remove. Let the user specify multiple such expressions, -separated by ':'. - - +refs/heads/*:+HEAD^:+refs/tags/*:-refs/tags/old-tag - -This is processed by starting with an empty set of refs, and walking the -refspec in order. - -* Each + is matched against all known refs (from `git show-ref`), and adds - everything it matches to the set. If the + does not contain a wildcard, - it is literally added to the set, rather than looking in the known refs. - This allows "+refs/heads/*" to match all heads, and "+HEAD" - to match HEAD, or even "+sha" to match a given SHA, or "+HEAD^" to match - the previous head. -* Each - is matched against the contents of the set, and removes everything - it matches, using a lexographic matching with wildcards (not looking at - the SHAs that the refs point to, so -refs/heads/master does not remove - +HEAD). - -Hmm, unused currently does a separate pass to find files used in the work -tree. I think it's best to keep that as-is. - ---[[Joey]] - -> [[done]] --[[Joey]] diff --git a/doc/todo/unused_by_refspec/comment_1_4612b5f485b313d59eb51bb519eb9471._comment b/doc/todo/unused_by_refspec/comment_1_4612b5f485b313d59eb51bb519eb9471._comment deleted file mode 100644 index 44cc30731..000000000 --- a/doc/todo/unused_by_refspec/comment_1_4612b5f485b313d59eb51bb519eb9471._comment +++ /dev/null @@ -1,7 +0,0 @@ -[[!comment format=mdwn - username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" - subject="comment 1" - date="2015-05-14T16:17:08Z" - content=""" -since, if I got it right, I will be able to point to any treeish (or collection of those), I should be able to implement any strategy in mind (e.g. for upgrade drop all not referenced in master, or even its HEAD and HEAD^ to allow a quick roll back). So sounds good to me -- thanks joey! -"""]] diff --git a/doc/todo/vicfg_comment_gotcha.mdwn b/doc/todo/vicfg_comment_gotcha.mdwn deleted file mode 100644 index 910af01a4..000000000 --- a/doc/todo/vicfg_comment_gotcha.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -A user might run vicfg and want to reset a line back to the default value -from the value they have periously set. A natural way to do that is to -comment out the line (or delete it). However, what that actually does is -vicfg parses the result and skips over that setting, since it's not -present, and so no change is saved. - -It could try to parse commented out lines and detect deleted lines, -but that way lies madness. Also, it's not at all clear what the "default" -should be in response to such an action. The default varies per type of -configuration, and vicfg does't know about defaults. - -> [[fixed|done]]; this was a job for Data.Default! --[[Joey]] - -Instead, I think it should detect when a setting provided in the input -version of the file is not present in the output version, and plop the user -back into the editor with an error, telling them that cannot be handled, -and suggesting they instead change the value to the value they now want it -to have. - -> Nah, too complicated. diff --git a/doc/todo/view_git_annex_log_in_webapp.mdwn b/doc/todo/view_git_annex_log_in_webapp.mdwn deleted file mode 100644 index 63b2792a8..000000000 --- a/doc/todo/view_git_annex_log_in_webapp.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -Just gave git annex a quick try for a few minutes and I must admit it's pretty great. - -A must have feature for me is to be able to view git annex log in the web app as "git annex log" doesn't got BIDI support (RTL scripts like Arabic, Farsi, Hebrew). -Adding Bi-directional text support would be too much to ask from a developer that don't know these languages thus the solution is to use the already the web browser to handle that. - -> Closing as it's not clear what the submitter wanted done here. [[done]] -> --[[Joey]] diff --git a/doc/todo/view_git_annex_log_in_webapp/comment_1_945054441d93423b2c7b81712b364a3c._comment b/doc/todo/view_git_annex_log_in_webapp/comment_1_945054441d93423b2c7b81712b364a3c._comment deleted file mode 100644 index 362119bae..000000000 --- a/doc/todo/view_git_annex_log_in_webapp/comment_1_945054441d93423b2c7b81712b364a3c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawmHp5oVW8Z9v_vHs5FRtlYj80TYMQWVTS0" - nickname="dhead" - subject="comment 1" - date="2014-05-30T00:13:27Z" - content=""" -...the already built in BIDI support the web browser to handle that. -"""]] diff --git a/doc/todo/view_git_annex_log_in_webapp/comment_2_0f434dfe80e90951870218bc1b76c374._comment b/doc/todo/view_git_annex_log_in_webapp/comment_2_0f434dfe80e90951870218bc1b76c374._comment deleted file mode 100644 index f9e14a55f..000000000 --- a/doc/todo/view_git_annex_log_in_webapp/comment_2_0f434dfe80e90951870218bc1b76c374._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="209.250.56.176" - subject="comment 2" - date="2014-05-30T00:32:25Z" - content=""" -I don't understand this request at all - -* There are plenty of console emulators with bidi support. If you need bidi support, surely you have already found and are using one of them? -* `git annex log` does not output much that seems likely to need bidi support. At least no more than any other git-annex command, specifically names of remotes, and names of files. -* `git annex log` is a low-level tool, almost a debugging tool. Users of the webapp might be interested in which repositories a file has gotten to, but surely not the history of past locations of files. -"""]] diff --git a/doc/todo/windows_git-annex_service.mdwn b/doc/todo/windows_git-annex_service.mdwn deleted file mode 100644 index 5a7e91752..000000000 --- a/doc/todo/windows_git-annex_service.mdwn +++ /dev/null @@ -1,30 +0,0 @@ -## git-annex as service on windows - -Use nssm to run git-annex as a service. Will need to include it in the -git-annex bundle. - -Problem: nssm runs git-annex as a service as a LocalService user. (Or some -similar user.) This leads to permission problems, when the normal user -tries to write to its directory. - -Solution: Make `git-annex mkservice $repo` command (only avilable on -Windows) that does: - -1. git -c core.sharedRepository=true init $repo -2. cd $repo; git annex init -4. chmod 777 -R $repo -5. Add $repo to C:\.config\git-annex\autostart -6. If git-annex service does not yet exist in nssm, set it up and start it. - -**Problem**: With 2 users writing to one repository, files and subdirs -will end up owned by git-annex or by the desktop user, and the other user -won't be able to eg, edit a file or remove a file from a directory. - -Make git-annex read `C:\.config\git-annex\autostart` -on Windows, in addition to the one in $HOME. This way, `git annex assistant ---autostart` and `git annex webapp` will use it, no matter which user. - -WIP git branch: `winservice` - -> I am calling this [[done]], it's not done using a service, but it works. -> --[[Joey]] diff --git a/doc/todo/windows_git-annex_service/comment_11_c3af14453e99dae5425deaa26ca7310e._comment b/doc/todo/windows_git-annex_service/comment_11_c3af14453e99dae5425deaa26ca7310e._comment deleted file mode 100644 index 83e2ba514..000000000 --- a/doc/todo/windows_git-annex_service/comment_11_c3af14453e99dae5425deaa26ca7310e._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" - nickname="Dominik" - subject="running as service" - date="2014-05-13T17:40:57Z" - content=""" -Hey, just tried git-annex on windows. Love the idea, but the windows port still seems to be a work in progress. I thought I'd check in here and see if i could help. Maybe this is a start: - -You can setup any executable file as a windows service using Sc.exe included in the Windows Resource Kit. -https://support.microsoft.com/kb/251192?SmcNavTabIndex=1 -Its pretty easy and straightforward - -Another option would be installing the service using nsis, here is one possible plugin that should do the trick: http://nsis.sourceforge.net/NSIS_Simple_Service_Plugin -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_11_e2dda1037cc85f03613f2774c139ad56._comment b/doc/todo/windows_git-annex_service/comment_11_e2dda1037cc85f03613f2774c139ad56._comment deleted file mode 100644 index df945b517..000000000 --- a/doc/todo/windows_git-annex_service/comment_11_e2dda1037cc85f03613f2774c139ad56._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 11" - date="2014-06-16T23:47:36Z" - content=""" -I am stuck with apparently intractable permissions problems, if the git-annex service doesn't run as the same user who wants to use the git-annex repository. - -nssm is supposed to let the user the service runs as be set on the Log on tab, but I cannot get it to accept any user/password there, on my XP test VM. If anyone gets that tab in nssm to work, let me know. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_12_249a48a241f14f32dab49f381d2de3b3._comment b/doc/todo/windows_git-annex_service/comment_12_249a48a241f14f32dab49f381d2de3b3._comment deleted file mode 100644 index 9b7e87654..000000000 --- a/doc/todo/windows_git-annex_service/comment_12_249a48a241f14f32dab49f381d2de3b3._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" - nickname="Dominik" - subject="comment 12" - date="2014-06-17T00:01:35Z" - content=""" -To get rid of permission problems, you may find setacl useful. Chmod and chown from msys dont't seem to work correctly with windows 8 -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_12_d3d91ddc00bc275455022d86b779b148._comment b/doc/todo/windows_git-annex_service/comment_12_d3d91ddc00bc275455022d86b779b148._comment deleted file mode 100644 index df4545911..000000000 --- a/doc/todo/windows_git-annex_service/comment_12_d3d91ddc00bc275455022d86b779b148._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 12" - date="2014-05-15T20:36:09Z" - content=""" -@Dominik, thanks for the links. Now that the webapp handles prompting for ssh passwords, the console is entirely vestigial and I'd like to get rid of it. The sc commands seems possible to use; there are also haskell libraries for building windows services. - -The tricky part is that multiple git-annex assistant processes can be running, if there are multiple local repositories. This seems to be hard to do as a service. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_13_59fbe4d07cdbeb786bae792f9c709ddd._comment b/doc/todo/windows_git-annex_service/comment_13_59fbe4d07cdbeb786bae792f9c709ddd._comment deleted file mode 100644 index 3d630ed0c..000000000 --- a/doc/todo/windows_git-annex_service/comment_13_59fbe4d07cdbeb786bae792f9c709ddd._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://johan.kiviniemi.name/" - nickname="Johan" - subject="comment 13" - date="2014-05-16T02:27:51Z" - content=""" -“The tricky part is that multiple git-annex assistant processes can be running, if there are multiple local repositories.” - -This would probably mean a lot of work, but it might be nice if there was just a single git-annex assistant per user which could take care of multiple local repos. The UI would be nicer, too, since the status of and notifications from every repository could be shown in the same place. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_13_f1d254fe85b0e5cbc7edf9096af4f942._comment b/doc/todo/windows_git-annex_service/comment_13_f1d254fe85b0e5cbc7edf9096af4f942._comment deleted file mode 100644 index 894eb4b6c..000000000 --- a/doc/todo/windows_git-annex_service/comment_13_f1d254fe85b0e5cbc7edf9096af4f942._comment +++ /dev/null @@ -1,27 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 13" - date="2014-06-17T16:52:55Z" - content=""" -I have messed with the windows ACLs some yesterday, but I don't know how or if it's possible to set ACLs on a directory, such that everything created inside it will be writable by two different users. Certainly this is doable on POSIX; if it's doable on Windows, I'll revisit services. - ----- - - -For now, it seems that a better option may be to not run git-annex as a service, but use various dos-window hiding technologies. - -<http://stackoverflow.com/questions/21031171/how-to-run-a-command-on-the-background-on-windows/21031281#21031281> - -I have successfully gotten this to work using nircmd. make a git-annex-webapp.bat, containing: - -<pre> -title GitAnnex -nircmd.exe win hide ititle \"GitAnnex\" -git annex webapp -</pre> - -This works, although the DOS box flashes onscreen for maybe 1/10th of a second before nircmd hides it. A git-annex-assistant.bat could run git-annex assistant --autostart, and would be suitable to be setup to run on startup. - -(It seems that it's possible to write a VBScript or C# program that sets up a hidden WScript.Shell and runs a command in it. That might avoid the window flash. However, it seems hard to get VBScript to run, and I have not investigated C#.) -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_14_79fc0ff98c5bba2ed616e52e5a58e28f._comment b/doc/todo/windows_git-annex_service/comment_14_79fc0ff98c5bba2ed616e52e5a58e28f._comment deleted file mode 100644 index 9d7fb9ff0..000000000 --- a/doc/todo/windows_git-annex_service/comment_14_79fc0ff98c5bba2ed616e52e5a58e28f._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" - nickname="Dominik" - subject="multiple git-annex assistant processes" - date="2014-05-16T23:05:28Z" - content=""" -shouldn't be a problem though if all processes are spawned from the same service though, right? Or what problems did you have in mind? -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_14_7d5fdac0084c4742967879f5f0f9fccf._comment b/doc/todo/windows_git-annex_service/comment_14_7d5fdac0084c4742967879f5f0f9fccf._comment deleted file mode 100644 index 5aba4e8e4..000000000 --- a/doc/todo/windows_git-annex_service/comment_14_7d5fdac0084c4742967879f5f0f9fccf._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 14" - date="2014-06-17T16:56:32Z" - content=""" -Note that nircmd is not free software; but can be distributed free of charge, provided all the files in the zip are included and unmodified. Sucks, but it's windows.. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_15_8f10491f8c0a151284e6d81a83eab212._comment b/doc/todo/windows_git-annex_service/comment_15_8f10491f8c0a151284e6d81a83eab212._comment deleted file mode 100644 index c7247ce45..000000000 --- a/doc/todo/windows_git-annex_service/comment_15_8f10491f8c0a151284e6d81a83eab212._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 15" - date="2014-06-17T17:10:28Z" - content=""" -<http://www.ntwind.com/software/hstart.html> is another option. - -How to run VB script: - -<http://stackoverflow.com/questions/289498/running-batch-file-in-background-when-windows-boots-up> -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_15_fcd34607116183cc1a764fb307eabe0a._comment b/doc/todo/windows_git-annex_service/comment_15_fcd34607116183cc1a764fb307eabe0a._comment deleted file mode 100644 index 57505d1d9..000000000 --- a/doc/todo/windows_git-annex_service/comment_15_fcd34607116183cc1a764fb307eabe0a._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 15" - date="2014-06-04T20:49:26Z" - content=""" -`sc` can only be used by the administrator. That is problimatic. - -Also, in order for sc to be used, the program has to have support for it. It cannot be any arbitrary program. win32-service adds such support. However, I have not been able to get programs using win32-service to build: <https://github.com/mikesteele81/Win32-services/issues/3> -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_16_51800fd83cd979b021eabdd4c44cfd61._comment b/doc/todo/windows_git-annex_service/comment_16_51800fd83cd979b021eabdd4c44cfd61._comment deleted file mode 100644 index 7efe7b338..000000000 --- a/doc/todo/windows_git-annex_service/comment_16_51800fd83cd979b021eabdd4c44cfd61._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 16" - date="2014-06-17T17:18:34Z" - content=""" -Using wscript to run a file containing this will start the webapp w/o any console flicker: - -<pre> -Set objshell=CreateObject(\"Wscript.Shell\") -objShell.Run(\"git-annex webapp\"), 0, False -</pre> -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_16_6a6424f23772e57f1adb1807ca8b93fa._comment b/doc/todo/windows_git-annex_service/comment_16_6a6424f23772e57f1adb1807ca8b93fa._comment deleted file mode 100644 index 53b705d05..000000000 --- a/doc/todo/windows_git-annex_service/comment_16_6a6424f23772e57f1adb1807ca8b93fa._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="service not needed" - date="2014-06-04T21:16:06Z" - content=""" -Seems that all I need to do is pass -optl-mwindows when building git-annex; this will produce a binary that does not open a console window when started from the start menu, but still runs in the background. So it will work as the webapp. - -**However**, it can't be used at the command line. So, I think I should make a git-annex-webapp shim that's built that way and starts the real webapp. - -But, some work needs to be done, because when run this way, git-annex can't write to stdout or stderr, which it tries to do, and so crashes on startup. - -Also, when git-annex is built that way and tries to run git.. windows helpfully opens a command.exe to display any output git might have. So we get lots of flickering command.exe windows. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_17_62a1a33c2aaf4b0b8a0149ec526907d7._comment b/doc/todo/windows_git-annex_service/comment_17_62a1a33c2aaf4b0b8a0149ec526907d7._comment deleted file mode 100644 index 520e50154..000000000 --- a/doc/todo/windows_git-annex_service/comment_17_62a1a33c2aaf4b0b8a0149ec526907d7._comment +++ /dev/null @@ -1,16 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" - nickname="Dominik" - subject="comment 17" - date="2014-06-05T16:42:02Z" - content=""" -Actually you can create a service from any program or batch file using srvany.exe from the windows resource kit: http://support.microsoft.com/kb/137890. An alternative would be the Non-Sucking Service Manager http://nssm.cc/ -Also nsis has some plugins for creating services, but i havent tried any of them: http://nsis.sourceforge.net/How_do_I_start/stop/create/remove/check_a_service - -Upsides: -1) You don't have to touch your code or change anything in the compilation just to create the service -2) git-annex will still work fine from the console -Downside: You'd have to include an extra binary or plugin in your installer for creating the service - -But I'm pretty sure that none of the commandline calls would pop up in a new window that way, but if you need the verbose mode, you could still start the webapp from console instead as service and everything will show as expected -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_18_3a408492107ca6f120b631ce8c41faef._comment b/doc/todo/windows_git-annex_service/comment_18_3a408492107ca6f120b631ce8c41faef._comment deleted file mode 100644 index 494e3f43a..000000000 --- a/doc/todo/windows_git-annex_service/comment_18_3a408492107ca6f120b631ce8c41faef._comment +++ /dev/null @@ -1,23 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="nssm notes" - date="2014-06-10T18:16:00Z" - content=""" -* Have to install and run nssm as an administrator. (It may be possible to get it to run as a non-administrator user if the admin sets it up. I haven't succeeded.) -* `nssm install git-annex` -* Set path to git-annex, and set Arguments to: `assistant --autostart` -* In Exit tab, change Restart to \"No action\" -* In Process tab, uncheck \"Console window\" -* Repositories to start up have to be listed in `C:\Documents and Settings\LocalService\.config\git-annex\autostart` - (rather than the normal user home directory) - -After all that it works! Even opening git-annex webapp from the menu avoids the console window (it appears briefly but then goes away). - -Most of this setup could be boiled down to a command line invocation, which git-annex could do at install time. However, it would still need to be run by the admin. Luckily the git-annex installation process already only works as admin (and I guess I could close the bug about that if it gets a legitimate reason to need admin..) - -Some changes in git-annex would improve this. - -* Maybe have a way to specify the user that git-annex is running on behalf of, and look in that user's home directory, rather than LocalService. (Other parts of the webapp UI, like adding a new repository, also use LocalService as the home directory, which is confusing). -* Starting the webapp for the first time to create a repository still opens a console window, so find a workaround for this. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_19_c6cbc8fe9218f90c661cd1026658c939._comment b/doc/todo/windows_git-annex_service/comment_19_c6cbc8fe9218f90c661cd1026658c939._comment deleted file mode 100644 index ec3cf7b09..000000000 --- a/doc/todo/windows_git-annex_service/comment_19_c6cbc8fe9218f90c661cd1026658c939._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawm9ocq1Kb0WL-cz-LPpvd2Xm-q8tIQvqXA" - nickname="Dominik" - subject="comment 19" - date="2014-06-10T18:24:22Z" - content=""" -That sounds great! I'll try it out on windows 8 aswell once i get around to it. -"""]] diff --git a/doc/todo/windows_git-annex_service/comment_20_ca245781a37db5546da3f7204adbeebb._comment b/doc/todo/windows_git-annex_service/comment_20_ca245781a37db5546da3f7204adbeebb._comment deleted file mode 100644 index badb5308a..000000000 --- a/doc/todo/windows_git-annex_service/comment_20_ca245781a37db5546da3f7204adbeebb._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="108.236.230.124" - subject="comment 20" - date="2014-06-10T19:11:57Z" - content=""" -This seems pretty close to a command line to install the service with nssm. - -<pre> -nssm install git-annex 'C:\Program Files\Git\cmd\git-annex.exe' assistant --autostart -nssm set git-annex AppExit 0 Ignore -nssm set git-annex AppExit 1 Ignore -nssm set git-annex AppDirectory C:\ -nssm set git-annex AppNoConsole 1 -nssm start git-annex -</pre> -"""]] |
