From b143883e45c09461e927f2bf960d07940fdb007d Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkW9u-8uqR62QBZjeTNCXsL7Ds55dAMGbA" Date: Tue, 28 Apr 2015 10:15:24 +0000 Subject: [PATCH 1/6] Added a comment --- ...comment_2_200a869f335909566b9ddab3032fd5a2._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Git-annex_deleted_all_my_files__44___how_can_I_recover_them__63__/comment_2_200a869f335909566b9ddab3032fd5a2._comment diff --git a/doc/forum/Git-annex_deleted_all_my_files__44___how_can_I_recover_them__63__/comment_2_200a869f335909566b9ddab3032fd5a2._comment b/doc/forum/Git-annex_deleted_all_my_files__44___how_can_I_recover_them__63__/comment_2_200a869f335909566b9ddab3032fd5a2._comment new file mode 100644 index 0000000000..bb55a04eda --- /dev/null +++ b/doc/forum/Git-annex_deleted_all_my_files__44___how_can_I_recover_them__63__/comment_2_200a869f335909566b9ddab3032fd5a2._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkW9u-8uqR62QBZjeTNCXsL7Ds55dAMGbA" + nickname="Horea" + subject="comment 2" + date="2015-04-28T10:15:24Z" + content=""" +Apparently what happened is that whenever you want to set up git annex, you have to create just one repository, them *move* your files to a temporary folder on all your other media, *clone* the repository to the other media, and then copy all your files back to the clone and add them to git annex. This is a horrible workflow and not mentioned anywhere. If you do the intuitive thing and start by making a bunch of repos, because all repos are created equal, git annex will happily delete all your stuff on some of them. + +Indeed, as you correctly mention, this can go horribly wrong if you use direct mode and cannot recover your files. A shame, really, that direct mode is the only mode in which you actually have write and copy access to your files, and thus, for most - including myself - the only sane way of managing your files. For the record, I was able to retrieve my files, but to this day git annex is the only software I ever used that ever managed to lose my data. +"""]] From 42893969482ac00e93da1dd983a6b7acc9f4c7fa Mon Sep 17 00:00:00 2001 From: "http://rfhbuk.pip.verisignlabs.com.pip.verisignlabs.com/" Date: Tue, 28 Apr 2015 13:54:50 +0000 Subject: [PATCH 2/6] --- ...6____47__gitlabname__47__reponame.git.mdwn | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/bugs/_git-annex:_bad_url_ssh:__47____47__git__64__gitlab.com:__126____47__gitlabname__47__reponame.git.mdwn diff --git a/doc/bugs/_git-annex:_bad_url_ssh:__47____47__git__64__gitlab.com:__126____47__gitlabname__47__reponame.git.mdwn b/doc/bugs/_git-annex:_bad_url_ssh:__47____47__git__64__gitlab.com:__126____47__gitlabname__47__reponame.git.mdwn new file mode 100644 index 0000000000..74e9235dd9 --- /dev/null +++ b/doc/bugs/_git-annex:_bad_url_ssh:__47____47__git__64__gitlab.com:__126____47__gitlabname__47__reponame.git.mdwn @@ -0,0 +1,33 @@ +### Please describe the problem. +An encrypted remote is added to a working git annex repository (mind ":~/" in the remote add command). However, after that any git annex command fails. + +### What steps will reproduce the problem? + > 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 + > + > git annex sync + git-annex: bad url ssh://git@gitlab.com:~/gitlabname/reponame.git + +### What version of git-annex are you using? On what operating system? +5.20150419-g900e1b6 on Mac OS X + +### 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. +"""]] From a6b1c894ace60a829ebcae9e8d20b7d014eabc1b Mon Sep 17 00:00:00 2001 From: db48x Date: Tue, 28 Apr 2015 18:15:41 +0000 Subject: [PATCH 3/6] --- ...t_run_from_inside_a_git_annex_repository.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository.mdwn 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 new file mode 100644 index 0000000000..41e921befc --- /dev/null +++ b/doc/bugs/git_annex_assistant_--stop_fails_if_not_run_from_inside_a_git_annex_repository.mdwn @@ -0,0 +1,16 @@ +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 +"""]] From 0fd405ced917544957e59ad3bce2d7d72bc7877a Mon Sep 17 00:00:00 2001 From: anarcat Date: Tue, 28 Apr 2015 21:32:36 +0000 Subject: [PATCH 4/6] Added a comment: how does the queue get built now? --- ...omment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment diff --git a/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment b/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment new file mode 100644 index 0000000000..df273afb2c --- /dev/null +++ b/doc/todo/wishlist:___39__get__39___queue_and_schedule./comment_1_d6ab311beee2ce5f73ae325a4ae463d4._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="anarcat" + subject="how does the queue get built now?" + date="2015-04-28T21:32:36Z" + content=""" +how does the queue get created now? is it random or is there some deterministic thing that could be abuse to prioritise some content already (say alphabetical order or some similar hack)? + +the scheduling I think i can work around with clunky cron jobs to start/stop the assistant, but the queue I feel is a different beast. would you be available for hire to implement this feature in priority? + +thanks! +"""]] From b9f552b3474435faf0424620b17e38d54f5aa7ff Mon Sep 17 00:00:00 2001 From: db48x Date: Wed, 29 Apr 2015 05:43:07 +0000 Subject: [PATCH 5/6] --- ...to_ssh_repository___40__windows__41__.mdwn | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__.mdwn 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 new file mode 100644 index 0000000000..f0038fa9f5 --- /dev/null +++ b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__.mdwn @@ -0,0 +1,30 @@ +### 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. + +### 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'"] +"""]] From b5d91005f3af1c4ad21affc374427c4fd3126e21 Mon Sep 17 00:00:00 2001 From: db48x Date: Wed, 29 Apr 2015 05:48:05 +0000 Subject: [PATCH 6/6] --- ..._fails_to_connect_to_ssh_repository___40__windows__41__.mdwn | 2 ++ 1 file changed, 2 insertions(+) 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 index f0038fa9f5..bd4f4d8a69 100644 --- 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 @@ -10,6 +10,8 @@ If I kill that parent ssh process, I get this error message in the transcript: 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.