diff options
28 files changed, 74 insertions, 8 deletions
diff --git a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn b/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn index 2bba743e4..9c6a0c9fc 100644 --- a/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn +++ b/doc/bugs/Allow_syncing_to_a_specific_directory_on_a_USB_remote.mdwn @@ -1,9 +1,30 @@ -This follows up to the [comment made by Laszlo](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/#comment-f26d3b6b45bb66601ecfaa883ace161c) on the [recent poll](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/). +This follows up to the [comment made by +Laszlo](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/#comment-f26d3b6b45bb66601ecfaa883ace161c) +on the [recent +poll](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/). -I too need to be able to select the directory on the remote drive that the annex will be synced to. +I too need to be able to select the directory on the remote drive that the +annex will be synced to. -If I just add a remote drive via the web app, it syncs the repository to `/mnt/usb/annex`, and it looks like it just creates a bare repository in that folder. I need the repository to be synced to something like `/mnt/usb/subfolder/myspecifiedfoldername` and I need that remote to be a full repository. +If I just add a remote drive via the web app, it syncs the repository to +`/mnt/usb/annex`, and it looks like it just creates a bare repository in +that folder. I need the repository to be synced to something like +`/mnt/usb/subfolder/myspecifiedfoldername` and I need that remote to be a +full repository. -My use case is that I use the USB drive to keep annexes in sync between two computers. I have multiple annexes that need to be synced between the two computers, and none of them are in a directory called `annex`. I also need to be able to plug the drive into other computers and access the files directly, without doing a `git clone` or anything like that. I have all of this setup and working fine with just plain old git annex, but the web app does not seem to support creating new repositories with this workflow. +My use case is that I use the USB drive to keep annexes in sync between two +computers. I have multiple annexes that need to be synced between the two +computers, and none of them are in a directory called `annex`. I also need +to be able to plug the drive into other computers and access the files +directly, without doing a `git clone` or anything like that. I have all of +this setup and working fine with just plain old git annex, but the web app +does not seem to support creating new repositories with this workflow. -I think it makes a lot of sense to allow the web application to add a new remote that is simply a directory. People like me could specify the path of the directory to be on the mounted USB drive. Others may want to add a remote that is a mounted network share or something like that. +I think it makes a lot of sense to allow the web application to add a new +remote that is simply a directory. People like me could specify the path of +the directory to be on the mounted USB drive. Others may want to add a +remote that is a mounted network share or something like that. + +> [[done]], the webapp now has a "Add another repository" option, +> and you can just enter the path to whatever place you like inside a USB +> drive. --[[Joey]] diff --git a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn index 832ad8021..c8110eaa0 100644 --- a/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn +++ b/doc/bugs/Assistant_uses_obsolete_GDU_volume_monitor.mdwn @@ -24,3 +24,5 @@ Alternatively, git-annex should stop relying on any per-user services, and use k ### What version of git-annex are you using? On what operating system? git-annex 3.20130102 on Linux 3.7.1, GNOME 3.7 + +> [[done]] --[[Joey]] diff --git a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn index 85a311716..223568ca8 100644 --- a/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn +++ b/doc/bugs/Building_in_cabal_using_--bindir___126____47__bin_breaks_the_desktop_link.mdwn @@ -12,3 +12,4 @@ Latest Head from git, Ubuntu 12.04 Please provide any additional information below. I'm not sure whether this is a bug or not. I just ran into problems because I did not expect the cabal build process to create my desktop file but instead thought that git-annex will create it by it-self taking its own path. Perhaps it would make sense to produce an error if the bindir is invalid. An automatic expansion of '~' in the build script would be even better. +> [[done]], I think it was a typo. --[[Joey]] diff --git a/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client.mdwn b/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client.mdwn index 1b90fb3f4..ef59954b7 100644 --- a/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client.mdwn +++ b/doc/bugs/Can__39__t_access_files_from___39__Removable_drive__39___repo_even_if_set_as_client.mdwn @@ -17,3 +17,5 @@ What version of git-annex are you using? On what operating system? I'm using 9e57edff287ac53fc4b1cefef7271e9ed17f2285 (Fri Feb 22 15:19:25 2013 +0000). Ubuntu 12.10 x86_64 + +[[!tag /design/assistant]] diff --git a/doc/bugs/Cannot_clone_an_annex.mdwn b/doc/bugs/Cannot_clone_an_annex.mdwn index 62e9ed27f..77989ecb6 100644 --- a/doc/bugs/Cannot_clone_an_annex.mdwn +++ b/doc/bugs/Cannot_clone_an_annex.mdwn @@ -65,3 +65,5 @@ the `SHA256` key is not present. It looks like I'll have to rollback my ZFS snapshots and start over, but I'm wondering: how was I even able to create this situation? + +> [[Done]]; user error. --[[Joey]] diff --git a/doc/bugs/Crash_when_adding_jabber_account_.mdwn b/doc/bugs/Crash_when_adding_jabber_account_.mdwn index aac1b3321..678890cad 100644 --- a/doc/bugs/Crash_when_adding_jabber_account_.mdwn +++ b/doc/bugs/Crash_when_adding_jabber_account_.mdwn @@ -28,3 +28,5 @@ OS: Ubuntu 12.04.1 LTS 3.2.0-35-generic-pae #55-Ubuntu SMP Wed Dec 5 18:04:39 UT On dmesg: [45773.212717] git-annex[26779]: segfault at b724e840 ip 09699150 sp b4cfd038 error 7 in git-annex[8048000+1762000] +[[!tag /design/assistant]] +> [[done]], see comments --[[Joey]] diff --git a/doc/bugs/Creating_an_encrypted_S3_does_not_check_for_presence_of_GPG.mdwn b/doc/bugs/Creating_an_encrypted_S3_does_not_check_for_presence_of_GPG.mdwn index aab03cd7f..f497c8756 100644 --- a/doc/bugs/Creating_an_encrypted_S3_does_not_check_for_presence_of_GPG.mdwn +++ b/doc/bugs/Creating_an_encrypted_S3_does_not_check_for_presence_of_GPG.mdwn @@ -15,3 +15,4 @@ What version of git-annex are you using? On what operating system? Please provide any additional information below. +[[!tag /design/assistant/OSX]] diff --git a/doc/bugs/Enable__47__paus_syncing_to_remote_ssh_server_with_multiple_directories.mdwn b/doc/bugs/Enable__47__paus_syncing_to_remote_ssh_server_with_multiple_directories.mdwn index 83ae9ccdc..6306a4bd1 100644 --- a/doc/bugs/Enable__47__paus_syncing_to_remote_ssh_server_with_multiple_directories.mdwn +++ b/doc/bugs/Enable__47__paus_syncing_to_remote_ssh_server_with_multiple_directories.mdwn @@ -15,3 +15,5 @@ Version: 4.20130314, Debian Please provide any additional information below. I am an "webinterface only" user. + +[[!tag /design/assistant]] diff --git a/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn b/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn index dd92591e6..6bf458141 100644 --- a/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn +++ b/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn @@ -21,3 +21,5 @@ What version of git-annex are you using? On what operating system? Please provide any additional information below. +[[!meta title="strange OSX behavior when killed"]] +[[!tag /design/assistant/OSX unreproducible]] diff --git a/doc/bugs/OSX_app_issues/comment_4_4cda124b57ddc87645d5822f14ed5c59._comment b/doc/bugs/OSX_app_issues/old/comment_4_4cda124b57ddc87645d5822f14ed5c59._comment index 758140903..758140903 100644 --- a/doc/bugs/OSX_app_issues/comment_4_4cda124b57ddc87645d5822f14ed5c59._comment +++ b/doc/bugs/OSX_app_issues/old/comment_4_4cda124b57ddc87645d5822f14ed5c59._comment diff --git a/doc/bugs/OSX_app_issues/comment_5_0d1df34f83a8dac9c438d93806236818._comment b/doc/bugs/OSX_app_issues/old/comment_5_0d1df34f83a8dac9c438d93806236818._comment index 89078a7da..89078a7da 100644 --- a/doc/bugs/OSX_app_issues/comment_5_0d1df34f83a8dac9c438d93806236818._comment +++ b/doc/bugs/OSX_app_issues/old/comment_5_0d1df34f83a8dac9c438d93806236818._comment diff --git a/doc/bugs/OSX_app_issues/comment_6_bc44d5aea5f77e331a32913ada293730._comment b/doc/bugs/OSX_app_issues/old/comment_6_bc44d5aea5f77e331a32913ada293730._comment index 187197e81..187197e81 100644 --- a/doc/bugs/OSX_app_issues/comment_6_bc44d5aea5f77e331a32913ada293730._comment +++ b/doc/bugs/OSX_app_issues/old/comment_6_bc44d5aea5f77e331a32913ada293730._comment diff --git a/doc/bugs/OSX_app_issues/comment_7_acd73cc5c4caa88099e2d2f19947aadf._comment b/doc/bugs/OSX_app_issues/old/comment_7_acd73cc5c4caa88099e2d2f19947aadf._comment index bdbdfc9ab..bdbdfc9ab 100644 --- a/doc/bugs/OSX_app_issues/comment_7_acd73cc5c4caa88099e2d2f19947aadf._comment +++ b/doc/bugs/OSX_app_issues/old/comment_7_acd73cc5c4caa88099e2d2f19947aadf._comment diff --git a/doc/bugs/Provide_64-bit_standalone_build.mdwn b/doc/bugs/Provide_64-bit_standalone_build.mdwn index 856e22b9a..7f24e0055 100644 --- a/doc/bugs/Provide_64-bit_standalone_build.mdwn +++ b/doc/bugs/Provide_64-bit_standalone_build.mdwn @@ -1 +1,6 @@ The 32-bit standalone build appears to require two libraries (lib32-libyaml and lib32-gsasl) that are not available on Arch Linux. [See the comments on the AUR package](https://aur.archlinux.org/packages/git-annex-bin/). I'd appreciate it if you could bring back the 64-bit build. + +> [[done]], based on <https://aur.archlinux.org/packages/git-annex-bin/> +> they are managing with what I am providing. Also, Arch Linux has a +> proper build of git-annex from source, so I'm not going to worry about +> git-annex-bin, the rationalle for which I don't even understand. --[[Joey]] diff --git a/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn b/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn index 605027f28..ccf6ef1ca 100644 --- a/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn +++ b/doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn @@ -26,3 +26,5 @@ Workaround: * rename `metaarray` to `ma` again using the webapp Perhaps the renaming of the remote not surviving clones is unavoidable, but the webapp should be able to cope with the situation. Thanks. + +[[!tag /design/assistant]] diff --git a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn b/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn index da486c30b..65a2c8fdc 100644 --- a/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn +++ b/doc/bugs/Rsync_encrypted_remote_asks_for_ssh_key_password_for_each_file.mdwn @@ -24,3 +24,4 @@ What version of git-annex are you using? On what operating system? Please provide any additional information below. +[[!meta title="rsync special remote does not use ssh connection caching"]] diff --git a/doc/bugs/Tries_to_upload_to_remote_although_remote_is_dead.mdwn b/doc/bugs/Tries_to_upload_to_remote_although_remote_is_dead.mdwn index 6b8f66d02..73f8a046a 100644 --- a/doc/bugs/Tries_to_upload_to_remote_although_remote_is_dead.mdwn +++ b/doc/bugs/Tries_to_upload_to_remote_although_remote_is_dead.mdwn @@ -48,4 +48,4 @@ git-annex HEAD from yesterdays git. Ubuntu 12.10 Please provide any additional information below. - +[[!tag /design/assistant unreproducible]] diff --git a/doc/bugs/assistant_-_GTalk_collision.mdwn b/doc/bugs/assistant_-_GTalk_collision.mdwn index 62e7062eb..b814166ae 100644 --- a/doc/bugs/assistant_-_GTalk_collision.mdwn +++ b/doc/bugs/assistant_-_GTalk_collision.mdwn @@ -13,3 +13,5 @@ I expect to remain invisible, but I get the following warning: "Oops! You are no ##Please provide any additional information below. Syncing between the repositories works ok. + +[[!tag /design/assistant]] diff --git a/doc/bugs/creating_a_remote_server_repository.mdwn b/doc/bugs/creating_a_remote_server_repository.mdwn index 90e85bc8b..280b7a662 100644 --- a/doc/bugs/creating_a_remote_server_repository.mdwn +++ b/doc/bugs/creating_a_remote_server_repository.mdwn @@ -21,4 +21,4 @@ Version: 3.20130124 Please provide any additional information below. [[!tag /design/assistant]] -[[!meta title="ssh password prompting"]] +[[!meta title="ssh password prompting issue with assistant"]] diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn b/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn index fd90406cf..a2817661e 100644 --- a/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn +++ b/doc/bugs/git-annex:_Not_in_a_git_repository._.mdwn @@ -17,3 +17,6 @@ Debian wheezy with git-annex version: 3.20130114 Please provide any additional information below. Its working if i start `git-annex webapp` as root. I had the same error on previous version. + +> I've made some improvements. Think this was user error. [[done]] +> --[[Joey]] diff --git a/doc/bugs/host_with_rysnc_installed__44___not_recognized.txt b/doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn index e5dd7dd4b..e411eaf9c 100644 --- a/doc/bugs/host_with_rysnc_installed__44___not_recognized.txt +++ b/doc/bugs/host_with_rysnc_installed__44___not_recognized.mdwn @@ -10,3 +10,6 @@ What version of git-annex are you using? On what operating system? Please provide any additional information below. ssh keys were installed to allow login, when ssh-askpass was not found on osx version + +[[!meta title="webapp rsync probe command failed on FreeNAS box"]] +[[!tag /design/assistant]] diff --git a/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn b/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn index 0d362db21..63dfec4ac 100644 --- a/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn +++ b/doc/bugs/map_not_respecting_annex_ssh_options__63__.mdwn @@ -35,3 +35,4 @@ relevant part of .git/config: supported repository versions: 3 upgrade supported from repository versions: 0 1 2 +> [[done]], see comment --[[Joey]] diff --git a/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn b/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn index 549147dcc..6f45cb8ff 100644 --- a/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn +++ b/doc/bugs/uploads_queued_to_annex-ignore_remotes.mdwn @@ -30,3 +30,5 @@ The remote in question: 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/watcher_commits_unlocked_files.mdwn b/doc/bugs/watcher_commits_unlocked_files.mdwn index 37c79e353..37e50fca0 100644 --- a/doc/bugs/watcher_commits_unlocked_files.mdwn +++ b/doc/bugs/watcher_commits_unlocked_files.mdwn @@ -28,3 +28,10 @@ Possible approaches: how to find the file to unlock it. [[!meta title="assistant: watcher_commits_unlocked_files"]] + +> [[done]]; I just tested and somehow this no longer happens; +> the watcher/assistant leaves the unlocked file alone, and then +> as soon as it's modified re-adds it. +> +> Also, of course, there is direct mode, which avoids needing to unlock... +> --[[Joey]] diff --git a/doc/bugs/webapp_hang.mdwn b/doc/bugs/webapp_hang.mdwn index 73fcbbe99..a1d296893 100644 --- a/doc/bugs/webapp_hang.mdwn +++ b/doc/bugs/webapp_hang.mdwn @@ -139,3 +139,6 @@ expecting a request body? 0x0020: 8010 0800 fe28 0000 0101 080a 004a dfe0 .....(.......J.. 0x0030: 004a b3da .J.. </pre> + +[[!tag /design/assistant]] +[[done]] diff --git a/doc/bugs/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn b/doc/todo/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn index 383410704..a7b30ded5 100644 --- a/doc/bugs/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn +++ b/doc/todo/assistant_cannot_set_up_remote_repo_via_an_ssh_alias_or_an_ip_address.mdwn @@ -8,7 +8,9 @@ alias for a hostname at no-ip.com.) Despite the fact that "homeworld" is a viable ssh target because of the alias, the assistant doesn't recognize it as a valid host to ssh to. -I had trouble with an ip address the first time I tried it but just tried it again and it worked fine, so please disregard that part of the title of this bug report. +I had trouble with an ip address the first time I tried it but just tried +it again and it worked fine, so please disregard that part of the title of +this bug report. What is the expected output? What do you see instead? diff --git a/doc/bugs/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 index 361585a78..361585a78 100644 --- a/doc/bugs/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 diff --git a/doc/bugs/optinally_transfer_file_unencryptedly.mdwn b/doc/todo/optinally_transfer_file_unencryptedly.mdwn index d622fcdab..d622fcdab 100644 --- a/doc/bugs/optinally_transfer_file_unencryptedly.mdwn +++ b/doc/todo/optinally_transfer_file_unencryptedly.mdwn |