diff options
Diffstat (limited to 'doc/bugs')
499 files changed, 16045 insertions, 270 deletions
diff --git a/doc/bugs/400_mode_leakage.mdwn b/doc/bugs/400_mode_leakage.mdwn new file mode 100644 index 000000000..63f0fb11d --- /dev/null +++ b/doc/bugs/400_mode_leakage.mdwn @@ -0,0 +1,25 @@ +git-annex tends to preserve files that are added to an annex with +a mode such as 400. (Happens to me sometimes with email attachments.) +As these files are rsynced around, and end up on eg, a +publically visible repo with a webserver frontend, or a repo that is +acessible to a whole group of users, they will not be readable. + +I think it would make sense for git-annex to normalize file permissions +when adding them. Of course, there's some tension here with generally +storing file metadata when possible. Perhaps the normalization should only +ensure that group and other have read access? + +(Security: We can assume that a repo that is not intended to be public is +in a 700 directory. And since git-annex cannot preserve file modes when +files transit through a special remote, using modes to limit access to +individual files is not wise.) + +--[[Joey]] + +> Revisiting this, git-annex already honors core.sharedrepository settings, +> so I just needed to set it to `world` to allow everyone to read. +> +> There was a code path in direct mode where that didn't work; fixed that. +> +> [[done]] +> --[[Joey]] diff --git a/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn b/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn new file mode 100644 index 000000000..ab98c631e --- /dev/null +++ b/doc/bugs/Adding_unencrypted_repo_on_drive_in_webapp_gives_internal_server_error__.mdwn @@ -0,0 +1,69 @@ +### Please describe the problem. + +"Internal Server Error This git repository is encrypted with a GnuPG key that you do not have" after having asked *not* to use encryption. + +### What steps will reproduce the problem? + +Here's what I did: + +On Ubuntu 10.4, install git-annex according to http://git-annex.branchable.com/install/Ubuntu/ then: + +$ git-annex webapp + +Create repo at suggested path Desktop/annex/. +Add a file to that dir. Create subdir, move file there. +Select "Add another repository" in webapp, "Removable drive", select external usb drive, leave suggested path "annex", "Use this drive", "Do not encrypt repository". + +-> shows "Internal Server Error +This git repository is encrypted with a GnuPG key that you do not have. +git-annex version 4.20131002" + + +### What version of git-annex are you using? On what operating system? + +git-annex version 4.20131002, Ubuntu 12.04.3 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 wit[2013-10-19 00:33:55 BST] main: starting assistant version 4.20131002 +(Recording state in git...) +(scanning...) [2013-10-19 00:33:55 BST] Watcher: Performing startup scan +(started...) + + The installed version of git is too old for .gitignores to be honored by git-annex. +[2013-10-19 00:35:56 BST] Committer: Adding Git Annex..ation.odt +add Git Annex installation.odt (checksum...) [2013-10-19 00:35:57 BST] Committer: Committing changes to git +[2013-10-19 00:37:38 BST] Committer: Adding Git Annex..ation.odt +[2013-10-19 00:37:38 BST] Committer: Committing changes to git +git: 'remote-gcrypt' is not a git command. See 'git --help'. +ok +(Recording state in git...) +(Recording state in git...) +ok +(Recording state in git...) +(Recording state in git...) +19/Oct/2013:00:38:54 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) +git: 'remote-gcrypt' is not a git command. See 'git --help'. +19/Oct/2013:00:39:09 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) +.........+++++ + +Not enough random bytes available. Please do some other work to give +the OS a chance to collect more entropy! (Need 66 more bytes) +.............+++++ +gpg: key E0424680 marked as ultimately trusted +git: 'remote-gcrypt' is not a git command. See 'git --help'. +19/Oct/2013:00:41:19 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) +git: 'remote-gcrypt' is not a git command. See 'git --help'. +19/Oct/2013:00:54:33 +0100 [Error#yesod-core] This git repository is encrypted with a GnuPG key that you do not have. @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) +h the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] + +I'm not at my computer, will check upstream Git later. Sorry if this has been reported before. + +> This only occurred when git-remote-gcrypt was not installed. +> I've fixed the bug. [[done]] --[[Joey]] diff --git a/doc/bugs/Android_v4.3_-_Framework_18_-___34__Git_annex_webapp_CANNOT_LINK_EXECUTABLE:_git-annex_invalid_R__95__ARM__95__COPY_relocation_against_DT__95__SYMBOLIC_shared_library_libc.so___40__built_with_-Bsymbolic__63____41__.mdwn b/doc/bugs/Android_v4.3_-_Framework_18_-___34__Git_annex_webapp_CANNOT_LINK_EXECUTABLE:_git-annex_invalid_R__95__ARM__95__COPY_relocation_against_DT__95__SYMBOLIC_shared_library_libc.so___40__built_with_-Bsymbolic__63____41__.mdwn deleted file mode 100644 index 0f2c4305d..000000000 --- a/doc/bugs/Android_v4.3_-_Framework_18_-___34__Git_annex_webapp_CANNOT_LINK_EXECUTABLE:_git-annex_invalid_R__95__ARM__95__COPY_relocation_against_DT__95__SYMBOLIC_shared_library_libc.so___40__built_with_-Bsymbolic__63____41__.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. -Git-annex v20130802 abends on Android v4.3 framework 18 - -Android v4.3 - Framework 18 - "Git annex webapp CANNOT LINK EXECUTABLE: git-annex invalid R_ARM_COPY relocation against DT_SYMBOLIC shared library libc.so (built with -Bsymbolic?) - -### What steps will reproduce the problem? -Start git-annex -git-annex webapp (auto launch) - -### What version of git-annex are you using? On what operating system? -Git-annex v20130802 abends on Android v4.3 framework 18 -Android app v1.00.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. -"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn new file mode 100644 index 000000000..a2f79aa6c --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux.mdwn @@ -0,0 +1,75 @@ +### Please describe the problem. + +I am experiencing a weird issue with any install I've had on this one (and only) ArchLinux machine: all of aur/git-annex 4.20130516-1, aur/git-annex-bin-4.20130909-1, aur/git-annex-standalone-4.20130909-1 and a Cabal install just stall when trying to create the initial Git annex repo in the webapp. + +When started, it offers me to create the annex in ~/annex/ or ~/Desktop/annex/, where ~ gets turned into /home/USER when I press “Make repository”, but nothing else happens. This is regardless of if that repo exists when I try to create it or start the webapp. + +If I start the webapp from an existing annex (now in ~/annex), it seems to work a bit better, but any other remote (SSH) server that I try to add fails. I just get a fleeting Bootstrap message box when I click “Check this server”, and nothing in the logs of eithr git annex webapp or the ssh logs of the server. + +If an annex exists, but I start the webapp from another directory, it just behaves as if none were found. + +Calls to git annex assistant --autostart complain that "Nothing listed in /home/omehani/.config/git-annex/autostart". I have checked the permissions on that directory, and tried deleting it to let git-annex recreate it, which it did, to no avail. + + +### What steps will reproduce the problem? + +Install any of the git-annex packages available from AUR + +### What version of git-annex are you using? On what operating system? + +* up-to-date ArchLinux, Linux cancey 3.10.10-1-ARCH #1 SMP PREEMPT Fri Aug 30 11:30:06 CEST 2013 x86_64 GNU/Linux +* aur/git-annex 4.20130516-1, aur/git-annex-bin-4.20130909-1, aur/git-annex-standalone-4.20130909-1 or through Cabal (on 2013-09-12) + +### Please provide any additional information below. + +The following is the output of webapp --debug. Nothing actually appears when trying to add/edit a repo. + +[[!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 + +~/annex (master)$ git annex webapp --debug +[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","show-ref","git-annex"] +[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","show-ref","--hash","refs/heads/git-annex"] +[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..27c891f84f6ea7a10c68c0dd696ab84d88ef0cec","--oneline","-n1"] +[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..d0a1cb518045af01b443694aa2cd9af6386de38a","--oneline","-n1"] +[2013-09-16 10:26:55 EST] read: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","log","refs/heads/git-annex..3ff23e23d74ace008b03143120e84f07e52ed8ee","--oneline","-n1"] +[2013-09-16 10:26:55 EST] chat: git ["--git-dir=/home/omehani/annex/.git","--work-tree=/home/omehani/annex","cat-file","--batch"] +[2013-09-16 10:26:55 EST] logging to /home/omehani/annex/.git/annex/daemon.log +[2013-09-16 10:26:55 EST] logging to /home/omehani/annex/.git/annex/daemon.log +Launching web browser on file:///home/omehani/annex/.git/annex/webapp.html +START /usr/lib/firefox/firefox "/home/omehani/annex/.git/annex/webapp.html" + +(process:2699): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed + + +# End of transcript or log. +"""]] + +Running git annex from a different directory. +[[!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 webapp --debug +Launching web browser on file:///tmp/webapp3934.html +START /usr/lib/firefox/firefox "/tmp/webapp3934.html" + +(process:4008): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed + +# End of transcript or log. +"""]] + +Trying the autostart: +[[!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 assistant --autostart --debug +git-annex: Nothing listed in /home/omehani/.config/git-annex/autostart + + +# End of transcript or log. +"""]] + +> workaround is in place [[done]] --[[Joey]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment new file mode 100644 index 000000000..b0d0bdd55 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_10_ec4a7388ea7106a953f599b664b37f1d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 10" + date="2013-10-23T03:30:17Z" + content=""" +Right, I actually have 4.20131023-g9898139. This makes more sense. +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment new file mode 100644 index 000000000..ed9ace976 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_1_6a60c23850a5e2a7bba355e1317abc69._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 1" + date="2013-09-16T01:27:14Z" + content=""" +The version with which the following tests were run (installed with Cabal) + +[[!format sh \"\"\" +git-annex version: 4.20130827 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus DNS +\"\"\"]] +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment new file mode 100644 index 000000000..703be9a84 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_2_90b6ed232b2917b9fe041532284e1212._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.14.105" + subject="comment 2" + date="2013-09-19T17:12:39Z" + content=""" +Please send the content of the file /home/omehani/annex/.git/annex/daemon.log + +It would also help if you could better describe what happens. Perhaps make a screenshot? +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment new file mode 100644 index 000000000..39f0f39b8 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_3_5a89d79395d96c43d7d8a6fd9dc275f1._comment @@ -0,0 +1,248 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 3" + date="2013-09-30T01:29:50Z" + content=""" +This is when having manually created the local annex, and trying to add a remote one. Surprisingly, I cannot find any reference to the remote server's address or username... + + [2013-09-30 11:14:38 EST] main: starting assistant version 4.20130827 + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"git-annex\"] + [2013-09-30 11:14:38 EST] read: xdg-open [\"file:///home/USERNAME/annex/.git/annex/webapp.html\"] + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"log\",\"refs/heads/git-annex..9d87789505628a2da8347574cc600e358ff76107\",\"--oneline\",\"-n1\"] + [2013-09-30 11:14:38 EST] Merger: watching /home/USERNAME/annex/.git/refs + [2013-09-30 11:14:38 EST] TransferWatcher: watching for transfers + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"] + + No known network monitor available through dbus; falling back to polling + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-tree\",\"-z\",\"--\",\"refs/heads/git-annex\",\"uuid.log\",\"remote.log\",\"trust.log\",\"group.log\",\"preferred-content.log\"] + (scanning...) [2013-09-30 11:14:38 EST] Watcher: Performing startup scan + [2013-09-30 11:14:38 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"ls-files\",\"--deleted\",\"-z\",\"--\",\"/home/USERNAME/annex\"] + (started...) [2013-09-30 11:14:38 EST] Watcher: watching . + [2013-09-30 11:14:38 EST] MountWatcher: Started DBUS service org.gtk.Private.UDisks2VolumeMonitor to monitor mount events. + [2013-09-30 11:14:39 EST] 127.0.0.1 GET / Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"git-annex\"] + [2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] + [2013-09-30 11:14:39 EST] read: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"log\",\"refs/heads/git-annex..9d87789505628a2da8347574cc600e358ff76107\",\"--oneline\",\"-n1\"] + [2013-09-30 11:14:39 EST] chat: git [\"--git-dir=/home/USERNAME/annex/.git\",\"--work-tree=/home/USERNAME/annex\",\"cat-file\",\"--batch\"] + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /notifier/transfers Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:39 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:40 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:40 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:40 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:40 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:14:40 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /config Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /sidebar/NotificationId%200 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /transfers/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%200)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:16 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:17 EST] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:17 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:17 EST] 127.0.0.1 GET /sidebar/NotificationId%201 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /config/addrepository Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:19 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:20 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:20 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:20 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:20 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:20 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%201)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /sidebar/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:31 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /sidebar/NotificationId%203 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:32 EST] 127.0.0.1 GET /sidebar/NotificationId%203 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET / Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /notifier/transfers Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:37 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /about Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%204 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /transfers/NotificationId%202 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%202)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20True%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%205 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:47 EST] 127.0.0.1 GET /sidebar/NotificationId%205 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /config Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /sidebar/NotificationId%206 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:50 EST] 127.0.0.1 GET /sidebar/NotificationId%206 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /config/addrepository Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.widget.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.mouse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.core.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/jquery.ui.sortable.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /notifier/repolist/RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:51 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:52 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /repolist/RepoListNotificationId%20(NotificationId%203)%20(RepoSelector%20%7BonlyCloud%20=%20False,%20onlyConfigured%20=%20False,%20includeHere%20=%20True,%20nudgeAddMore%20=%20False%7D) Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%207 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:15:56 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 POST /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%208 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:23 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 POST /config/repository/add/ssh Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /sidebar/NotificationId%209 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:44 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:45 EST] 127.0.0.1 GET /sidebar/NotificationId%2010 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:16:45 EST] 127.0.0.1 GET /sidebar/NotificationId%2010 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /shutdown Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/css/bootstrap.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/css/bootstrap-responsive.css Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/jquery.full.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-dropdown.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-modal.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/js/bootstrap-collapse.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/longpolling.js Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/img/glyphicons-halflings.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /static/img/glyphicons-halflings-white.png Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /notifier/sidebar Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /sidebar/NotificationId%2011 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:01 EST] 127.0.0.1 GET /sidebar/NotificationId%2011 Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + [2013-09-30 11:17:02 EST] 127.0.0.1 GET /static/favicon.ico Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 + + +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment new file mode 100644 index 000000000..4ee062a80 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_4_cdd26c71875428dbe3c100944a443d3f._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 4" + date="2013-09-30T01:31:26Z" + content=""" +Hum, I'm not allowed to upload images: + git-annex-webapp1.png prohibited by allowed_attachments (user is not an admin) +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment new file mode 100644 index 000000000..28a0f7cc4 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_5_76242f5d6c815acd5bd58213bd8bb0fe._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.80" + subject="comment 5" + date="2013-09-30T16:13:20Z" + content=""" +I see a lot of activity, which looks like you started up the webapp and it ran displaying stuff for some minutes. I see that you clicked on pages to eg, add a ssh repository. + +So, what then do you mean by saying it stalls? You have still not described whatever problem you are having. +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment new file mode 100644 index 000000000..452a898f6 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_6_10852171c0207ca61ea6df1082107353._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 6" + date="2013-10-04T05:14:16Z" + content=""" +Right. By “it stalls”, I mean I get redirected to the same dialog page (either the one asking for the path to the repo to create, or the one asking for the details of the remote to add) that I just validated, rather than going further in the process. +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment new file mode 100644 index 000000000..b6df85923 --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_7_73e8a5696709f8154e63693ba5e569c3._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 7" + date="2013-10-14T16:18:01Z" + content=""" +I just ran into this problem myself. Some investigating shows it is a problem with Yesod's XSRF token. Apparently yesod is not seeing the _token, or is seeing one it does not like. However, I verified in chromium inspector that the form post was including the token with the same value used on the page. Also, it would intermittently accept the form, if I kept posting it over and over again. + +It seems this must be a bug in yesod, or on something with how I'm using yesod, or possibly in deeper layers like WAI not seeing the form post include the token, but I have not been able to figure out what. As a workaround, since git-annex webapp does its own authentication and only listens to localhost, and so does not actually need XSRF protection, I am going to change it to bypass that. +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment new file mode 100644 index 000000000..37acd5e9a --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_8_392fc344e5833b0eb665fcd38f956b7a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 8" + date="2013-10-23T03:00:58Z" + content=""" +I just tried installing git-annex using Cabal today, but only got git-annex-4.20131002, even from source, which seems to predate your last comment, and no other branch seem to provide the yesod fix. Should I get the source from somewhere else than kitenet to try this out (if you think it is in shape to be tested)? +"""]] diff --git a/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment new file mode 100644 index 000000000..1e7aa897b --- /dev/null +++ b/doc/bugs/Assistant_stalls_when_adding__47__creating_repo_on_ArchLinux/comment_9_9f0fc19a7fcaf7a5827e59e1495cf8c9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://olivier.mehani.name/" + nickname="olivier-mehani" + subject="comment 9" + date="2013-10-23T03:03:30Z" + content=""" +Strike that. It actually works. I could create the ~/annex store, and adding a remote also seems to work (I'm on a hotel Wi-Fi at the moment, so I fear the ssh connection will fail, but nothing to do with git-annex). +"""]] diff --git a/doc/bugs/Build_error_on_Linux.mdwn b/doc/bugs/Build_error_on_Linux.mdwn new file mode 100644 index 000000000..af560788a --- /dev/null +++ b/doc/bugs/Build_error_on_Linux.mdwn @@ -0,0 +1,29 @@ +### Please describe the problem. +Building on Linux, with a particular combination of flags, failed due to missing `async`. + +### What steps will reproduce the problem? +1. Configure with the following flag combination + + cryptohash -quvi -feed tdfa -testsuite -android production -dns -xmpp -pairing -webapp -assistant dbus inotify -webdav s3 + +2. Attempt to build and you'll get an error on line 16 of `Utility/Batch.hs` because `Control.Concurrent.Async` isn't available. + +### What version of git-annex are you using? On what operating system? +Version 4.20131024 on Linux + +### Please provide any additional information below. + +This is the patch I applied to `git-annex.cabal`: + + CPP-Options: -DWITH_KQUEUE + C-Sources: Utility/libkqueue.c + + + if os(linux) + + Build-Depends: async + + + if os(linux) && flag(Dbus) + Build-Depends: dbus (>= 0.10.3) + CPP-Options: -DWITH_DBUS + +> Feel async is core enough it should depend on it unconditionally. +> [[done]] --[[Joey]] 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 new file mode 100644 index 000000000..fa9bd3dd3 --- /dev/null +++ b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_2_38696178e658d1d32deec37dbea66a3d._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..14cfa2686 --- /dev/null +++ b/doc/bugs/Can__39__t_clone_on_Windows_because_some_filenames_have_a_colon_in_them/comment_3_f34d996827f5e7662bec409cbcce961b._comment @@ -0,0 +1,12 @@ +[[!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_start_on_Cyanogenmod_10.2_nightly.mdwn b/doc/bugs/Can__39__t_start_on_Cyanogenmod_10.2_nightly.mdwn new file mode 100644 index 000000000..c28794622 --- /dev/null +++ b/doc/bugs/Can__39__t_start_on_Cyanogenmod_10.2_nightly.mdwn @@ -0,0 +1,158 @@ +### 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/Conflicting_archive_descriptions.mdwn b/doc/bugs/Conflicting_archive_descriptions.mdwn new file mode 100644 index 000000000..832daa4ea --- /dev/null +++ b/doc/bugs/Conflicting_archive_descriptions.mdwn @@ -0,0 +1,16 @@ +This is confusing: + +"Next we come to the archive repositories.The archive repositories coordinate together, so that each file is archived in only one place. **When you move files into a folder named "archive"**, they'll be moved to an archive repository, and removed from all your client repositories. This is handy if you have old files you don't need anymore, but want to keep archived for later. When you copy or move a file out of an "archive" folder, it'll be retrieved from the archive repository." + +"The small archive repositories are like other archive repositories, but smaller. While archive repositories normally accumulate every file they can, small archive repositories only accumulate files **once you put them in an "archive" directory.**" + +Based upon those descriptions, I don't know what the difference is. + +> Improved wording to not imply that files are only put into archive +> repositories once the files are moved to archive directories. +> (Which is how small archive repositories work.) +> +> If you're still confused about it, see +> <http://git-annex.branchable.com/assistant/archival_walkthrough/> +> +> [[done]] --[[Joey]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too.mdwn b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too.mdwn new file mode 100644 index 000000000..de879f522 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too.mdwn @@ -0,0 +1,33 @@ +### Please describe the problem. + +On my raspberry pi, an SSH remote was in /var/lib/store (symlinked with /home/carlo/store), which contained a LVM volume spanning several USB drives. One of the drives got corrupted, which lead to this: + +$ cd /home/carlo/store +$ ls +Input/Output Error + +On my desktop machine, I then had a lot of transfers. After transfer, the file was turned into a symlink. + +### What steps will reproduce the problem? + +* Create an annex and a remote ssh server. +* [Simulate a corrupted drive](http://stackoverflow.com/questions/1361518/how-can-i-simulate-a-failed-disk-during-testing) for the remote, creating an input output error. +* Wait until the annex starts syncing on the desktop machine. If there were no further unidentified causes on my side, the assistant will start transfers that revert files to symlinks. + +### What version of git-annex are you using? On what operating system? + +Ubuntu 12.04 64bit +git annex 3.20121017 ([from Ubuntu PPA](https://launchpad.net/~rubiojr/+archive/git-annex)) + +### 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 see [all my daemon.log](http://capocasa.name/daemon.tgz) files. + +I noticed the problem yesterday afternoon (Thu 24 Oct). + +# End of transcript or log. +"""]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_1_80ca50f5305eda71fe32f2b0bc922c34._comment b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_1_80ca50f5305eda71fe32f2b0bc922c34._comment new file mode 100644 index 000000000..e47cbd327 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_1_80ca50f5305eda71fe32f2b0bc922c34._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-10-26T19:22:57Z" + content=""" +It seems to me that if a subdirectory of the repository is on a corrupted drive, and so it's not possible to list the files on it, this is basically the same as if you'd 'rm -rf' that subdirectory. So when it starts up, the assistant will see that these files are not present, and commit a removal to git. + +Then when another machine syncs with that, it would delete the files from its repository too. However, it actually keeps the contents of the files stashed away in `.git/annex`. So to recover from this, all you have to do is `git annex indirect` and `git revert` the commit that deleted the files. All your files would then be available again. + +However, what you describe is instead that the assistant chose to drop the content associated with the files, but kept the symlinks for them checked into git. +I don't understand why it would do that. Can you show the output of running, on the desktop machine: + + git annex whereis $somefile + git annex get $somefile + +Where $somefile is one of the files that has been reduced to a symlink. + +Looking at your logs, they appear to be the logs from the server. The strange thing that appears in one of them is \"git-annex: Not in a git repository.\" +which was logged around 2013-10-24 20:07:25 CEST. I am not sure, but I think it might have been the rpi git-annex saying that, because there is also \"fatal: '~/store/annex/' does not appear to be a git repository\" +"""]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_2_e6bc6d1c0eb8c469e9e00b37bbcc9b86._comment b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_2_e6bc6d1c0eb8c469e9e00b37bbcc9b86._comment new file mode 100644 index 000000000..18959ed68 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_2_e6bc6d1c0eb8c469e9e00b37bbcc9b86._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="comment 2" + date="2013-10-27T19:26:42Z" + content=""" +Thanks for looking into it and the recover instructions, will recover and post back when I'm back at work. I also have an another indirect mode repo on my home desktop as an extra backup so nothing real bad happened, but it's reassuring data's still there at work. + +"""]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_0d0f6b6b46d0153433fead2bbd1bbe64._comment b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_0d0f6b6b46d0153433fead2bbd1bbe64._comment new file mode 100644 index 000000000..a254b31a8 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_0d0f6b6b46d0153433fead2bbd1bbe64._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="comment 5" + date="2013-10-30T15:05:37Z" + content=""" +The assistant autorecovered my work repo before I noticed, so it looks like I can't provide the necessary info. There were a bunch of files missing that got re-synced from my home PC. + +For what it's worth, I noticed that on my phone, when cutting the internet connection while syncing, the assistant downloaded existing files into placeholder files, and then continued actually downloading files when the network connection was restored. + + +"""]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_6058a22b733cb02126286af950074ed4._comment b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_6058a22b733cb02126286af950074ed4._comment new file mode 100644 index 000000000..33e85c772 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_5_6058a22b733cb02126286af950074ed4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 5" + date="2013-11-03T01:17:39Z" + content=""" +I don't understand what you mean by \"The assistant autorecovered my work repo before I noticed\". What repo is the work repo, and how could the assistant \"autorecover\" it, and what did it do? + +At this point, I am completely in the dark about whether you're reporting a problem, and what the problem is. +"""]] diff --git a/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_6_593a49669e2fadfb91773f8c84fbb031._comment b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_6_593a49669e2fadfb91773f8c84fbb031._comment new file mode 100644 index 000000000..af31edcf8 --- /dev/null +++ b/doc/bugs/Corrupted_drive:_Assistant_seems_consider_files_deleted_and_deletes_them_elsewhere_too/comment_6_593a49669e2fadfb91773f8c84fbb031._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="comment 6" + date="2013-10-31T10:03:01Z" + content=""" +Of course, the autorecovery wouldn't affect the daemon.log from the work machine... so here they are: http://capocasa.name/work-desktop-ubuntu-12.04-daemonlog.tgz +"""]] diff --git a/doc/bugs/Could_not_read_from_remote_repository.mdwn b/doc/bugs/Could_not_read_from_remote_repository.mdwn new file mode 100644 index 000000000..e4f7b9c43 --- /dev/null +++ b/doc/bugs/Could_not_read_from_remote_repository.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. + +I've been using git-annex for a few weeks now, and everything was working fine until today. Now, when git-annex goes to sync my files, it will hang for a while, and then display a red box on the left side, saying `! Synced with adam.liter`. So, basically, it doesn't really sync. The logs say that it cannot read from the remote repository, which is set up on box.com and was working just fine until today. + +I've tried reconfiguring my jabber account on all my devices with git-annex as well as deleting and remaking the box.com repository, and none of these steps have solved the problem. + +### What steps will reproduce the problem? + +Making changes to any file located in the repository. + +### What version of git-annex are you using? On what operating system? + +Mac OS X 10.8.4 and git-annex version 4.20130801-gc88bbc4. + +### Please provide any additional information below. + +[[!format sh """ +[2013-09-09 01:33:03 EDT] XMPPSendPack: Syncing with adam.liter +Already up-to-date. +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. +"""]] diff --git a/doc/bugs/Could_not_read_from_remote_repository/comment_1_da842a9d146bcd5c7773b58364c25597._comment b/doc/bugs/Could_not_read_from_remote_repository/comment_1_da842a9d146bcd5c7773b58364c25597._comment new file mode 100644 index 000000000..c236beacd --- /dev/null +++ b/doc/bugs/Could_not_read_from_remote_repository/comment_1_da842a9d146bcd5c7773b58364c25597._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T06:01:18Z" + content=""" +From the small bit of log posted, it seems to be failing to sync over XMPP. Perhaps the XMPP server is down or it cannot connect? You can turn on debugging to get a lot more debugging about XMPP sync attempts. +"""]] diff --git a/doc/bugs/Could_not_read_from_remote_repository/comment_2_82746a0cf989d884cd0fd796db092b3c._comment b/doc/bugs/Could_not_read_from_remote_repository/comment_2_82746a0cf989d884cd0fd796db092b3c._comment new file mode 100644 index 000000000..8312bb3a3 --- /dev/null +++ b/doc/bugs/Could_not_read_from_remote_repository/comment_2_82746a0cf989d884cd0fd796db092b3c._comment @@ -0,0 +1,36 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U" + nickname="Adam" + subject="comment 2" + date="2013-09-09T06:12:44Z" + content=""" +This is what is in the logs after I turned on debugging: + + [2013-09-09 02:04:22 EDT] XMPPSendPack: finished running push Pushing \"a29\" (PushRequest (UUID \"c96c8493-b702-4ca0-9a88-f8a38dd6c3f5\")) True + [2013-09-09 02:04:22 EDT] XMPPSendPack: started running push Pushing \"a29\" (PushRequest (UUID \"c96c8493-b702-4ca0-9a88-f8a38dd6c3f5\")) + [2013-09-09 02:04:22 EDT] read: git [\"--git-dir=/Users/adamliter/Library/texmf/.git\",\"--work-tree=/Users/adamliter/Library/texmf\",\"symbolic-ref\",\"HEAD\"] + [2013-09-09 02:04:22 EDT] read: git [\"--git-dir=/Users/adamliter/Library/texmf/.git\",\"--work-tree=/Users/adamliter/Library/texmf\",\"show-ref\",\"refs/heads/master\"] + [2013-09-09 02:04:22 EDT] call: git [\"--git-dir=/Users/adamliter/Library/texmf/.git\",\"--work-tree=/Users/adamliter/Library/texmf\",\"branch\",\"-f\",\"synced/master\"] + [2013-09-09 02:04:22 EDT] XMPPSendPack: Syncing with adam.liter + [2013-09-09 02:04:22 EDT] call: git [\"--git-dir=/Users/adamliter/Library/texmf/.git\",\"--work-tree=/Users/adamliter/Library/texmf\",\"push\",\"adam.liter\",\"git-annex:refs/synced/6258750b-9b0d-4f05-b443-61f4fb0a3f66/YWRhbS5saXRlckBnbWFpbC5jb20=/git-annex\",\"refs/heads/master:refs/synced/6258750b-9b0d-4f05-b443-61f4fb0a3f66/YWRhbS5saXRlckBnbWFpbC5jb20=/master\"] + [2013-09-09 02:04:22 EDT] XMPPClient: sending: Pushing \"a29\" (StartingPush (UUID \"6258750b-9b0d-4f05-b443-61f4fb0a3f66\")) + [2013-09-09 02:04:22 EDT] XMPPClient: to client: a10/F4E99F98 + [2013-09-09 02:04:23 EDT] XMPPReceivePack: timeout waiting for git send-pack output via XMPP + fatal: The remote end hung up unexpectedly + [2013-09-09 02:04:23 EDT] XMPPReceivePack: finished running push Pushing \"a29\" (StartingPush (UUID \"c96c8493-b702-4ca0-9a88-f8a38dd6c3f5\")) True + [2013-09-09 02:04:23 EDT] XMPPClient: sending: Pushing \"a29\" (ReceivePackDone (ExitFailure 128)) + [2013-09-09 02:04:23 EDT] XMPPReceivePack: started running push Pushing \"a29\" (StartingPush (UUID \"c96c8493-b702-4ca0-9a88-f8a38dd6c3f5\")) + [2013-09-09 02:04:23 EDT] XMPPClient: to client: a10/F4E99F98 + [2013-09-09 02:04:23 EDT] XMPPReceivePack: Syncing with adam.liter + [2013-09-09 02:04:23 EDT] chat: git [\"receive-pack\",\"/Users/adamliter/Library/texmf\"] + [2013-09-09 02:04:23 EDT] XMPPClient: sending: Pushing \"a29\" (ReceivePackOutput 1 \"<elided>\") + [2013-09-09 02:04:23 EDT] XMPPClient: to client: a10/F4E99F98 + [2013-09-09 02:04:23 EDT] XMPPClient: sending: Pushing \"a29\" (ReceivePackOutput 2 \"<elided>\") + [2013-09-09 02:04:23 EDT] XMPPClient: to client: a10/F4E99F98 + [2013-09-09 02:04:23 EDT] XMPPClient: received: [\"Pushing \\"a29\\" (StartingPush (UUID \\"c96c8493-b702-4ca0-9a88-f8a38dd6c3f5\\"))\"] + [2013-09-09 02:04:23 EDT] XMPPClient: received: [\"Unknown message\"] + + + + +"""]] 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 new file mode 100644 index 000000000..28b74bd98 --- /dev/null +++ b/doc/bugs/Creating_second_repository_leads_to_wrong_ip___40__using_git-annex_webapp_--listen__41__.mdwn @@ -0,0 +1,35 @@ +### 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/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn b/doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn new file mode 100644 index 000000000..8e836e345 --- /dev/null +++ b/doc/bugs/Discrepancy_between_git_annex_add_and_git_annex_watch.mdwn @@ -0,0 +1,33 @@ +### Please describe the problem. + +`git annex add` does not add dotfiles (as per the man page) while `git annex watch` does (nothing on the man page). It's not a bug, but rather a surprise (at least to me). + +### What steps will reproduce the problem? + +[[!format sh """ +git init dotfiles +cd dotfiles +git annex init "my dotfiles" +echo test > test.txt +echo dottest > .dotest.txt +git annex add +git commit -a -m "initial dots" +git annex whereis .dotest.txt # no answer, as expected +git annex watch +git annex whereis .dotest.txt # answers that .dotest.txt is here +"""]] + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20131101, ubuntu 12.04 with all updates. + +### 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. +"""]] + +> Improved documentation. [[done]] --[[Joey]] diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn new file mode 100644 index 000000000..d011e4416 --- /dev/null +++ b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder.mdwn @@ -0,0 +1,3747 @@ +### Please describe the problem. +Two repositories A and B. B carries the full data, A only carries a subset of the data by excluding a couple of directories with a preferred content expression. Both repos in direct mode. A was modified quite heavily (thousands of files moved, deleted) with git-annex assistant running but without a possibility to synchronise with B. + +During synchronisation (by starting the webapp on A and git-annex assistant on B) suddenly former top-level folders, e.g. + + ./201207 + +appear in + + ./incoming/5d/201207 + +in both repositories. + +Then deleting + + ./incoming/5d/201207 + +in repo A unfortunately removes the top-level directory + + ./201207 + +as well and removes them in both repositories. + +### What steps will reproduce the problem? +I don't know how to reproduce apart from the description above. + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20131002, +Debian jessie, A: amd64, B: armhf + +### Please provide any additional information below. + +A paste of .git/annex/daemon.log of repoA below, as I haven't realised the problem immediatly I cannot tell whether this is the relevant log or not. If more is needed, I can provide additional logs. + +[[!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-27 18:35:52 CET] main: Syncing with repoB +From repoB:/media/srv/img + d1e3763..5eba12c git-annex -> repoB/git-annex + 611e4f5..a7b9fd7 master -> repoB/master + 714ed67..a7b9fd7 synced/master -> repoB/synced/master +Auto packing the repository for optimum performance. You may also +run "git gc" manually. See "git help gc" for more information. +Updating 714ed67..a7b9fd7 +Fast-forward + 201109/jmg_7250.cr2 | 1 - + 201109/jmg_7250.jpg | 1 - + 201109/jmg_7251.cr2 | 1 - + 201109/jmg_7251.jpg | 1 - + 201109/jmg_7253.cr2 | 1 - + 201109/jmg_7253.jpg | 1 - + 201109/jmg_7256_raw.jpg | 1 - + 201109/jmg_7259.cr2 | 1 - + 201109/jmg_7259.jpg | 1 - + 201109/jmg_7261.cr2 | 1 - + 201109/jmg_7261.jpg | 1 - + 201109/jmg_7265.cr2 | 1 - + 201109/jmg_7265.jpg | 1 - + 201109/jmg_7272.jpg | 1 - + 201109/jmg_7274.jpg | 1 - + 201109/jmg_7275.jpg | 1 - + 201109/jmg_7276.jpg | 1 - + 201109/jmg_7280.jpg | 1 - + 201109/jmg_7284.jpg | 1 - + 201109/jmg_7286.jpg | 1 - + 201109/jmg_7288.jpg | 1 - + 201109/jmg_7289.jpg | 1 - + 201109/jmg_7292.jpg | 1 - + 201109/jmg_7293.jpg | 1 - + 201109/jmg_7295.cr2 | 1 - + 201109/jmg_7295.jpg | 1 - + 201109/jmg_7296.cr2 | 1 - + 201109/jmg_7296.jpg | 1 - + 201109/jmg_7299.cr2 | 1 - + 201109/jmg_7299.jpg | 1 - + 201109/jmg_7300.cr2 | 1 - + 201109/jmg_7300.jpg | 1 - + 201109/jmg_7304.jpg | 1 - + 201109/jmg_7305_raw.jpg | 1 - + 201109/jmg_7307_raw.jpg | 1 - + 201202/jmg_8528.jpg | 1 - + 201202/jmg_8529.jpg | 1 - + 201202/jmg_8595.jpg | 1 - + 201202/jmg_8596.jpg | 1 - + 201202/jmg_8597.jpg | 1 - + 201202/jmg_8601.jpg | 1 - + 201202/jmg_8602.cr2 | 1 - + 201202/jmg_8602.jpg | 1 - + 201202/jmg_8603.cr2 | 1 - + 201202/jmg_8603.jpg | 1 - + 201202/jmg_8604.jpg | 1 - + 201202/jmg_8605.jpg | 1 - + 201202/jmg_8606.jpg | 1 - + 201202/jmg_8607.jpg | 1 - + 201202/jmg_8608.jpg | 1 - + 201202/jmg_8609.jpg | 1 - + 201202/jmg_8610.jpg | 1 - + 201202/jmg_8611.jpg | 1 - + 201202/jmg_8612.cr2 | 1 - + 201202/jmg_8612.jpg | 1 - + 201202/jmg_8613.jpg | 1 - + 201202/jmg_8614.jpg | 1 - + 201202/jmg_8615.jpg | 1 - + 201202/jmg_8616_raw.jpg | 1 - + 201202/jmg_8617.jpg | 1 - + 201202/jmg_8618.jpg | 1 - + 201202/jmg_8619.jpg | 1 - + 201202/jmg_8620.jpg | 1 - + 201202/jmg_8621.jpg | 1 - + 201202/jmg_8622.jpg | 1 - + 201202/jmg_8624.jpg | 1 - + 201202/jmg_8625.cr2 | 1 - + 201202/jmg_8625.jpg | 1 - + 201202/jmg_8626.jpg | 1 - + 201202/jmg_8627.jpg | 1 - + 201202/jmg_8628.jpg | 1 - + 201202/jmg_8629.jpg | 1 - + 201202/jmg_8630.jpg | 1 - + 201202/jmg_8631.jpg | 1 - + 201202/jmg_8632.jpg | 1 - + 201202/jmg_8633.cr2 | 1 - + 201202/jmg_8633.jpg | 1 - + 201202/jmg_8634.jpg | 1 - + 201202/jmg_8637.jpg | 1 - + 201202/jmg_8639.jpg | 1 - + 201202/jmg_8640.jpg | 1 - + 201202/jmg_8641.jpg | 1 - + 201202/jmg_8642_raw.jpg | 1 - + 201202/jmg_8643.jpg | 1 - + 201202/jmg_8644.jpg | 1 - + 201202/jmg_8647.jpg | 1 - + 201202/jmg_8648.jpg | 1 - + 201202/jmg_8651.cr2 | 1 - + 201202/jmg_8651.jpg | 1 - + 201202/jmg_8652.jpg | 1 - + 201202/jmg_8653.jpg | 1 - + 201202/jmg_8654.jpg | 1 - + 201202/jmg_8655.jpg | 1 - + 201202/jmg_8657.jpg | 1 - + 201202/jmg_8665.jpg | 1 - + 201202/jmg_8670.jpg | 1 - + 201202/jmg_8671.jpg | 1 - + 201202/jmg_8673.cr2 | 1 - + 201202/jmg_8673.jpg | 1 - + 201202/jmg_8674.jpg | 1 - + 201202/jmg_8675.jpg | 1 - + 201202/jmg_8676.jpg | 1 - + 201202/jmg_8677.jpg | 1 - + 201202/jmg_8678.jpg | 1 - + 201202/jmg_8679.jpg | 1 - + 201202/jmg_8680.jpg | 1 - + 201202/jmg_8681.jpg | 1 - + 201203/jmg_8701.cr2 | 1 - + 201203/jmg_8702.jpg | 1 - + 201203/jmg_8705.jpg | 1 - + 201203/jmg_8711.jpg | 1 - + 201203/jmg_8717.jpg | 1 - + 201203/jmg_8718.jpg | 1 - + 201203/jmg_8719.jpg | 1 - + 201203/jmg_8721.jpg | 1 - + 201203/jmg_8725.jpg | 1 - + 201203/jmg_8726.jpg | 1 - + 201203/jmg_8731.jpg | 1 - + 201203/jmg_8739.jpg | 1 - + 201203/jmg_8745.jpg | 1 - + 201203/jmg_8747_raw.jpg | 1 - + 201203/jmg_8750.cr2 | 1 - + 201203/jmg_8750.jpg | 1 - + 201204/jmg_8751.jpg | 1 - + 201204/jmg_8752.jpg | 1 - + 201204/jmg_8755.jpg | 1 - + 201204/jmg_8756.jpg | 1 - + 201204/jmg_8757.jpg | 1 - + 201204/jmg_8759.jpg | 1 - + 201204/jmg_8760.jpg | 1 - + 201204/jmg_8761.jpg | 1 - + 201204/jmg_8762.jpg | 1 - + 201204/jmg_8763.cr2 | 1 - + 201204/jmg_8763.jpg | 1 - + 201204/jmg_8766.jpg | 1 - + 201204/jmg_8767.cr2 | 1 - + 201204/jmg_8767.jpg | 1 - + 201204/jmg_8768.jpg | 1 - + 201204/jmg_8769.jpg | 1 - + 201204/jmg_8770.jpg | 1 - + 201204/jmg_8771.jpg | 1 - + 201204/jmg_8772.jpg | 1 - + 201204/jmg_8773.jpg | 1 - + 201205/jmg_8822.jpg | 1 - + 201205/jmg_8823.jpg | 1 - + 201205/jmg_8824.jpg | 1 - + 201205/jmg_8826.jpg | 1 - + 201205/jmg_8831.jpg | 1 - + 201205/jmg_8834.jpg | 1 - + 201205/jmg_8835.jpg | 1 - + 201205/jmg_8835_raw.jpg | 1 - + 201205/jmg_8837.jpg | 1 - + 201205/jmg_8839.cr2 | 1 - + 201205/jmg_8839.jpg | 1 - + 201205/jmg_8839_raw.jpg | 1 - + 201205/jmg_8840.cr2 | 1 - + 201205/jmg_8840.jpg | 1 - + 201205/jmg_8840_raw.jpg | 1 - + 201205/jmg_8841.jpg | 1 - + 201205/jmg_8842.jpg | 1 - + 201205/jmg_8844.cr2 | 1 - + 201205/jmg_8844.jpg | 1 - + 201205/jmg_8844_raw.jpg | 1 - + 201205/jmg_8845.jpg | 1 - + 201205/jmg_8846.jpg | 1 - + 201205/jmg_8847.cr2 | 1 - + 201205/jmg_8847.jpg | 1 - + 201205/jmg_8847_raw.jpg | 1 - + 201205/jmg_8848.jpg | 1 - + 201205/jmg_8849.jpg | 1 - + 201205/jmg_8851.cr2 | 1 - + 201205/jmg_8851.jpg | 1 - + 201205/jmg_8851_raw.jpg | 1 - + 201205/jmg_8856.cr2 | 1 - + 201205/jmg_8856.jpg | 1 - + 201205/jmg_8856_raw.jpg | 1 - + 201205/jmg_8857.jpg | 1 - + 201205/jmg_8858.jpg | 1 - + 201205/jmg_8859.jpg | 1 - + 201205/jmg_8861.jpg | 1 - + 201205/jmg_8862.jpg | 1 - + 201205/jmg_8863.jpg | 1 - + 201205/jmg_8871.cr2 | 1 - + 201205/jmg_8871.jpg | 1 - + 201205/jmg_8872.jpg | 1 - + 201205/jmg_8873.jpg | 1 - + 201205/jmg_8875.jpg | 1 - + 201205/jmg_8876.cr2 | 1 - + 201205/jmg_8876.jpg | 1 - + 201205/jmg_8878.cr2 | 1 - + 201205/jmg_8878.jpg | 1 - + 201205/jmg_8879.cr2 | 1 - + 201205/jmg_8879.jpg | 1 - + 201205/jmg_8880.cr2 | 1 - + 201205/jmg_8880.jpg | 1 - + 201205/jmg_8881.cr2 | 1 - + 201205/jmg_8881.jpg | 1 - + 201205/jmg_8892.cr2 | 1 - + 201205/jmg_8892.jpg | 1 - + 201205/jmg_8893.cr2 | 1 - + 201205/jmg_8893.jpg | 1 - + 201205/jmg_8894.cr2 | 1 - + 201205/jmg_8894.jpg | 1 - + 201206/jmg_8989.cr2 | 1 - + 201206/jmg_8989.jpg | 1 - + 201206/jmg_8990.cr2 | 1 - + 201206/jmg_8990.jpg | 1 - + 201206/jmg_8995.jpg | 1 - + 201206/jmg_8996.jpg | 1 - + 201206/jmg_8998.jpg | 1 - + 201206/jmg_9001.jpg | 1 - + 201206/jmg_9003.jpg | 1 - + 201206/jmg_9006.jpg | 1 - + 201206/jmg_9007.jpg | 1 - + 201206/jmg_9011.jpg | 1 - + 201206/jmg_9014.jpg | 1 - + 201206/jmg_9014_raw.jpg | 1 - + 201206/jmg_9015.jpg | 1 - + 201206/jmg_9016.cr2 | 1 - + 201206/jmg_9016.jpg | 1 - + 201206/jmg_9017.cr2 | 1 - + 201206/jmg_9017.jpg | 1 - + 201206/jmg_9018.cr2 | 1 - + 201206/jmg_9018.jpg | 1 - + 201206/jmg_9019.cr2 | 1 - + 201206/jmg_9019.jpg | 1 - + 201206/jmg_9023.cr2 | 1 - + 201206/jmg_9023.jpg | 1 - + 201206/jmg_9024.cr2 | 1 - + 201206/jmg_9024.jpg | 1 - + 201206/jmg_9025.cr2 | 1 - + 201206/jmg_9025.jpg | 1 - + 201206/jmg_9028.jpg | 1 - + 201206/jmg_9029.jpg | 1 - + 201206/jmg_9030.jpg | 1 - + 201206/jmg_9031.jpg | 1 - + 201206/jmg_9032_raw.jpg | 1 - + 201206/jmg_9033.jpg | 1 - + 201206/jmg_9033_raw.jpg | 1 - + 201206/jmg_9034.jpg | 1 - + 201206/jmg_9035.jpg | 1 - + 201206/jmg_9035_raw.jpg | 1 - + 201206/jmg_9036.jpg | 1 - + 201206/jmg_9039.cr2 | 1 - + 201206/jmg_9039.jpg | 1 - + 201206/jmg_9040.cr2 | 1 - + 201206/jmg_9040.jpg | 1 - + 201206/jmg_9043.cr2 | 1 - + 201206/jmg_9043.jpg | 1 - + 201206/jmg_9047.cr2 | 1 - + 201206/jmg_9047.jpg | 1 - + 201207/jmg_9048.jpg | 1 - + 201207/jmg_9053.jpg | 1 - + 201207/jmg_9054.jpg | 1 - + 201207/jmg_9069.cr2 | 1 - + 201207/jmg_9069.jpg | 1 - + 201207/jmg_9070.cr2 | 1 - + 201207/jmg_9070.jpg | 1 - + 201207/jmg_9072.cr2 | 1 - + 201207/jmg_9072.jpg | 1 - + 201207/jmg_9076.cr2 | 1 - + 201207/jmg_9076.jpg | 1 - + 201208/jmg_9077.jpg | 1 - + 201208/jmg_9302_raw.jpg | 1 - + 201208/jmg_9303.jpg | 1 - + 201208/jmg_9304.cr2 | 1 - + 201208/jmg_9304.jpg | 1 - + 201208/jmg_9305.cr2 | 1 - + 201208/jmg_9305.jpg | 1 - + 201208/jmg_9306_raw.jpg | 1 - + 201208/jmg_9307.cr2 | 1 - + 201208/jmg_9307.jpg | 1 - + 201208/jmg_9308_raw.jpg | 1 - + 201208/jmg_9309_raw.jpg | 1 - + 201208/jmg_9310.cr2 | 1 - + 201208/jmg_9310.jpg | 1 - + 201208/jmg_9310_bw.jpg | 1 - + 201208/jmg_9310_raw.jpg | 1 - + 201208/jmg_9312.jpg | 1 - + 201208/jmg_9313.jpg | 1 - + 201208/jmg_9314.jpg | 1 - + 201208/jmg_9315.jpg | 1 - + 201208/jmg_9319.jpg | 1 - + 201208/jmg_9523.jpg | 1 - + 201208/jmg_9524.jpg | 1 - + 201208/jmg_9525.jpg | 1 - + 201208/jmg_9526.jpg | 1 - + 201208/jmg_9527.jpg | 1 - + 201208/jmg_9527_raw.jpg | 1 - + 201208/jmg_9528.jpg | 1 - + 201208/jmg_9529.jpg | 1 - + 201208/jmg_9530.jpg | 1 - + 201208/jmg_9531.jpg | 1 - + 201208/jmg_9532.jpg | 1 - + 201208/jmg_9533.cr2 | 1 - + 201208/jmg_9533.jpg | 1 - + 201208/jmg_9534.cr2 | 1 - + 201208/jmg_9534.jpg | 1 - + 201208/jmg_9535.jpg | 1 - + 201208/jmg_9536.jpg | 1 - + 201208/jmg_9537.cr2 | 1 - + 201208/jmg_9537.jpg | 1 - + 201208/jmg_9538.jpg | 1 - + 201208/jmg_9539.jpg | 1 - + 201208/jmg_9540.jpg | 1 - + 201208/jmg_9541.cr2 | 1 - + 201208/jmg_9542.jpg | 1 - + 201208/jmg_9543.cr2 | 1 - + 201208/jmg_9543.jpg | 1 - + 201208/jmg_9544.cr2 | 1 - + 201208/jmg_9544.jpg | 1 - + 201208/jmg_9545.jpg | 1 - + 201209/jmg_9547.jpg | 1 - + 201209/jmg_9548.jpg | 1 - + 201209/jmg_9549.jpg | 1 - + 201209/jmg_9550.jpg | 1 - + 201209/jmg_9551.jpg | 1 - + 201209/jmg_9552.jpg | 1 - + 201209/jmg_9553.jpg | 1 - + 201209/jmg_9555.jpg | 1 - + 201209/jmg_9556.jpg | 1 - + 201209/jmg_9558.jpg | 1 - + 201209/jmg_9559.cr2 | 1 - + 201209/jmg_9559.jpg | 1 - + 201209/jmg_9560.cr2 | 1 - + 201209/jmg_9560.jpg | 1 - + 201209/jmg_9561.jpg | 1 - + 201209/jmg_9562.jpg | 1 - + 201209/jmg_9568.jpg | 1 - + 201210/jmg_0001.jpg | 1 - + 201210/jmg_0021.jpg | 1 - + 201210/jmg_0022.cr2 | 1 - + 201210/jmg_0022.jpg | 1 - + 201210/jmg_0025.jpg | 1 - + 201210/jmg_0026.jpg | 1 - + 201210/jmg_0027.jpg | 1 - + 201210/jmg_0028.jpg | 1 - + 201210/jmg_0029.jpg | 1 - + 201210/jmg_0030.jpg | 1 - + 201210/jmg_0032.jpg | 1 - + 201210/jmg_0034.jpg | 1 - + 201210/jmg_0035.jpg | 1 - + 201210/jmg_0036.jpg | 1 - + 201210/jmg_0037.jpg | 1 - + 201210/jmg_0039.cr2 | 1 - + 201210/jmg_0039.jpg | 1 - + 201210/jmg_0040.jpg | 1 - + 201210/jmg_9572.jpg | 1 - + 201210/jmg_9573.jpg | 1 - + 201210/jmg_9574.jpg | 1 - + 201210/jmg_9575.jpg | 1 - + 201210/jmg_9576.jpg | 1 - + 201210/jmg_9578.jpg | 1 - + 201210/jmg_9580.jpg | 1 - + 201210/jmg_9581.jpg | 1 - + 201210/jmg_9582.cr2 | 1 - + 201210/jmg_9582.jpg | 1 - + 201210/jmg_9585.cr2 | 1 - + 201210/jmg_9585.jpg | 1 - + 201210/jmg_9587.cr2 | 1 - + 201210/jmg_9587.jpg | 1 - + 201210/jmg_9588.jpg | 1 - + 201210/jmg_9589.jpg | 1 - + 201210/jmg_9590.jpg | 1 - + 201210/jmg_9591.jpg | 1 - + 201210/jmg_9594.jpg | 1 - + 201210/jmg_9595.jpg | 1 - + 201210/jmg_9596.jpg | 1 - + 201210/jmg_9597.cr2 | 1 - + 201210/jmg_9597.jpg | 1 - + 201210/jmg_9598.cr2 | 1 - + 201210/jmg_9598.jpg | 1 - + 201210/jmg_9599.cr2 | 1 - + 201210/jmg_9599.jpg | 1 - + 201210/jmg_9600.jpg | 1 - + 201210/jmg_9602.jpg | 1 - + 201210/jmg_9603.jpg | 1 - + 201210/jmg_9604.jpg | 1 - + 201210/jmg_9605.cr2 | 1 - + 201210/jmg_9605.jpg | 1 - + 201210/jmg_9606.jpg | 1 - + 201210/jmg_9608.jpg | 1 - + 201210/jmg_9609.jpg | 1 - + 201210/jmg_9610.jpg | 1 - + 201210/jmg_9611.jpg | 1 - + 201210/jmg_9612.jpg | 1 - + 201210/jmg_9613.jpg | 1 - + 201210/jmg_9614.jpg | 1 - + 201210/jmg_9616.cr2 | 1 - + 201210/jmg_9616.jpg | 1 - + 201210/jmg_9617.jpg | 1 - + 201210/jmg_9619.jpg | 1 - + 201210/jmg_9620.jpg | 1 - + 201210/jmg_9621.jpg | 1 - + 201210/jmg_9622.jpg | 1 - + 201210/jmg_9623.cr2 | 1 - + 201210/jmg_9623.jpg | 1 - + 201210/jmg_9624.cr2 | 1 - + 201210/jmg_9624.jpg | 1 - + 201210/jmg_9736_raw.jpg | 1 - + 201210/jmg_9738_raw.jpg | 1 - + 201210/jmg_9740.cr2 | 1 - + 201210/jmg_9740.jpg | 1 - + 201210/jmg_9743.jpg | 1 - + 201210/jmg_9744.jpg | 1 - + 201210/jmg_9745.cr2 | 1 - + 201210/jmg_9745.jpg | 1 - + 201210/jmg_9746.cr2 | 1 - + 201210/jmg_9746.jpg | 1 - + 201210/jmg_9748.jpg | 1 - + 201210/jmg_9749_raw.jpg | 1 - + 201210/jmg_9751.jpg | 1 - + 201210/jmg_9752.jpg | 1 - + 201210/jmg_9754.jpg | 1 - + 201210/jmg_9755.jpg | 1 - + 201210/jmg_9756.jpg | 1 - + 201210/jmg_9760.cr2 | 1 - + 201210/jmg_9760.jpg | 1 - + 201210/jmg_9761.cr2 | 1 - + 201210/jmg_9761.jpg | 1 - + 201210/jmg_9763.jpg | 1 - + 201210/jmg_9764.jpg | 1 - + 201210/jmg_9766.jpg | 1 - + 201210/jmg_9767.cr2 | 1 - + 201210/jmg_9767.jpg | 1 - + 201210/jmg_9768.jpg | 1 - + 201210/jmg_9771.jpg | 1 - + 201210/jmg_9772.jpg | 1 - + 201210/jmg_9791.jpg | 1 - + 201210/jmg_9792.jpg | 1 - + 201210/jmg_9793.jpg | 1 - + 201210/jmg_9794.jpg | 1 - + 201210/jmg_9796.jpg | 1 - + 201210/jmg_9797.jpg | 1 - + 201210/jmg_9799.jpg | 1 - + 201210/jmg_9800.jpg | 1 - + 201210/jmg_9801.jpg | 1 - + 201210/jmg_9803.jpg | 1 - + 201210/jmg_9807.jpg | 1 - + 201210/jmg_9808.jpg | 1 - + 201210/jmg_9809.jpg | 1 - + 201210/jmg_9810.jpg | 1 - + 201210/jmg_9811.jpg | 1 - + 201210/jmg_9812.jpg | 1 - + 201210/jmg_9813.jpg | 1 - + 201210/jmg_9815.jpg | 1 - + 201210/jmg_9818.jpg | 1 - + 201210/jmg_9819.jpg | 1 - + 201210/jmg_9820.jpg | 1 - + 201210/jmg_9821.jpg | 1 - + 201210/jmg_9822.jpg | 1 - + 201210/jmg_9823.jpg | 1 - + 201210/jmg_9825.jpg | 1 - + 201210/jmg_9826.jpg | 1 - + 201210/jmg_9827.jpg | 1 - + 201210/jmg_9828.jpg | 1 - + 201210/jmg_9829.jpg | 1 - + 201210/jmg_9830.cr2 | 1 - + 201210/jmg_9830.jpg | 1 - + 201210/jmg_9832.cr2 | 1 - + 201210/jmg_9832.jpg | 1 - + 201210/jmg_9834.jpg | 1 - + 201210/jmg_9836.jpg | 1 - + 201210/jmg_9838.jpg | 1 - + 201210/jmg_9839.jpg | 1 - + 201210/jmg_9841.jpg | 1 - + 201210/jmg_9843.jpg | 1 - + 201210/jmg_9845.jpg | 1 - + 201210/jmg_9846.jpg | 1 - + 201210/jmg_9848.jpg | 1 - + 201210/jmg_9849.jpg | 1 - + 201210/jmg_9852.jpg | 1 - + 201210/jmg_9853.jpg | 1 - + 201210/jmg_9854.jpg | 1 - + 201210/jmg_9855.jpg | 1 - + 201210/jmg_9856.jpg | 1 - + 201210/jmg_9857.cr2 | 1 - + 201210/jmg_9857.jpg | 1 - + 201210/jmg_9858.cr2 | 1 - + 201210/jmg_9858.jpg | 1 - + 201210/jmg_9859.jpg | 1 - + 201210/jmg_9860.jpg | 1 - + 201210/jmg_9915.jpg | 1 - + 201210/jmg_9917.jpg | 1 - + 201210/jmg_9918.jpg | 1 - + 201210/jmg_9919.jpg | 1 - + 201210/jmg_9922.jpg | 1 - + 201210/jmg_9923.jpg | 1 - + 201210/jmg_9925.jpg | 1 - + 201210/jmg_9926.cr2 | 1 - + 201210/jmg_9926.jpg | 1 - + 201210/jmg_9928.jpg | 1 - + 201210/jmg_9975.cr2 | 1 - + 201210/jmg_9975.jpg | 1 - + 201210/jmg_9976.cr2 | 1 - + 201210/jmg_9976.jpg | 1 - + 201210/jmg_9978.jpg | 1 - + 201210/jmg_9986.jpg | 1 - + 201210/jmg_9987.jpg | 1 - + 201210/jmg_9988.jpg | 1 - + 201210/jmg_9989.jpg | 1 - + 201210/jmg_9991.jpg | 1 - + 201210/jmg_9993.jpg | 1 - + 201210/jmg_9994.cr2 | 1 - + 201210/jmg_9994.jpg | 1 - + 201210/jmg_9997.jpg | 1 - + 201210/jmg_9998.jpg | 1 - + 201210/jmg_9999.jpg | 1 - + 201212/jmg_0131.jpg | 1 - + 201212/jmg_0134.jpg | 1 - + 201212/jmg_0135.jpg | 1 - + 201212/jmg_0152.jpg | 1 - + 201212/jmg_0155.jpg | 1 - + 201212/jmg_0156.jpg | 1 - + 201212/jmg_0162.jpg | 1 - + 201212/jmg_0163.jpg | 1 - + 201212/jmg_0165.jpg | 1 - + 201212/jmg_0176.cr2 | 1 - + 201212/jmg_0176.jpg | 1 - + 201212/jmg_0177.cr2 | 1 - + 201212/jmg_0177.jpg | 1 - + 201212/jmg_0178.jpg | 1 - + 201212/jmg_0179.jpg | 1 - + 201212/jmg_0180.jpg | 1 - + 201212/jmg_0184.jpg | 1 - + 201212/jmg_0185.jpg | 1 - + 201212/jmg_0186.jpg | 1 - + 201212/jmg_0187.jpg | 1 - + 201212/jmg_0306.jpg | 1 - + 201212/jmg_0307.jpg | 1 - + 201212/jmg_0308.jpg | 1 - + 201212/jmg_0310.jpg | 1 - + 201212/jmg_0311.jpg | 1 - + 201212/jmg_0312.jpg | 1 - + 201212/jmg_0313.jpg | 1 - + 201212/jmg_0314.jpg | 1 - + 201212/jmg_0315.jpg | 1 - + 201212/jmg_0316.jpg | 1 - + 201212/jmg_0317.jpg | 1 - + 201212/jmg_0321.jpg | 1 - + 201212/jmg_0326.jpg | 1 - + 201212/jmg_0328.jpg | 1 - + 201212/jmg_0330.jpg | 1 - + 201212/jmg_0333.jpg | 1 - + 201212/jmg_0336.jpg | 1 - + 201212/jmg_0340.jpg | 1 - + 201212/jmg_0343.jpg | 1 - + 201212/jmg_0345.jpg | 1 - + 201212/jmg_0360.jpg | 1 - + 201212/jmg_0362.jpg | 1 - + 201212/jmg_0363.jpg | 1 - + 201212/jmg_0364.jpg | 1 - + 201212/jmg_0366.jpg | 1 - + 201212/jmg_0367.jpg | 1 - + 201212/jmg_0368.jpg | 1 - + 201212/jmg_0369.jpg | 1 - + 201212/jmg_0370.jpg | 1 - + 201212/jmg_0372.jpg | 1 - + 201212/jmg_0382.jpg | 1 - + 201212/jmg_0383.jpg | 1 - + 201212/jmg_0384.jpg | 1 - + 201212/jmg_0385.jpg | 1 - + 201212/jmg_0387.jpg | 1 - + 201212/jmg_0388.jpg | 1 - + 201212/jmg_0389.jpg | 1 - + 201212/jmg_0390.jpg | 1 - + 201212/jmg_0392.jpg | 1 - + 201212/jmg_0396.jpg | 1 - + 201212/jmg_0397.jpg | 1 - + 201212/jmg_0398.jpg | 1 - + 201212/jmg_0399.jpg | 1 - + 201212/jmg_0402.jpg | 1 - + 201212/jmg_0404.jpg | 1 - + 201212/jmg_0405.jpg | 1 - + 201212/jmg_0406.jpg | 1 - + 201212/jmg_0407.jpg | 1 - + 201212/jmg_0408.jpg | 1 - + 201212/jmg_0410.jpg | 1 - + 201212/jmg_0411.jpg | 1 - + 201212/jmg_0412.jpg | 1 - + 201212/jmg_0415.jpg | 1 - + 201212/jmg_0417.jpg | 1 - + 201212/jmg_0418.jpg | 1 - + 201302/jmg_0502.cr2 | 1 - + 201302/jmg_0502.jpg | 1 - + 201302/jmg_0503.jpg | 1 - + 201302/jmg_0507.jpg | 1 - + 201302/jmg_0510.jpg | 1 - + 201302/jmg_0512.jpg | 1 - + 201302/jmg_0513.jpg | 1 - + 201302/jmg_0514.jpg | 1 - + 201302/jmg_0516.jpg | 1 - + 201302/jmg_0517.jpg | 1 - + 201302/jmg_0518.jpg | 1 - + 201302/jmg_0521.jpg | 1 - + 201302/jmg_0522.jpg | 1 - + 201302/jmg_0523.jpg | 1 - + 201302/jmg_0524.jpg | 1 - + 201302/jmg_0526.jpg | 1 - + 201302/jmg_0527.jpg | 1 - + 201302/jmg_0528.jpg | 1 - + 201302/jmg_0532.cr2 | 1 - + 201302/jmg_0532.jpg | 1 - + 201302/jmg_0534.jpg | 1 - + 201302/jmg_0535.jpg | 1 - + 201302/jmg_0537.jpg | 1 - + 201302/jmg_0539.jpg | 1 - + 201302/jmg_0541.jpg | 1 - + 201302/jmg_0543.jpg | 1 - + 201304/bruecke_saeckingen.tif | 1 - + 201304/jmg_0685.cr2 | 1 - + 201304/jmg_0685.jpg | 1 - + 201304/jmg_0687.cr2 | 1 - + 201304/jmg_0687.jpg | 1 - + 201304/jmg_0699.jpg | 1 - + 201304/jmg_0700.jpg | 1 - + 201304/jmg_0726.jpg | 1 - + 201304/jmg_0727.jpg | 1 - + 201304/jmg_0728.jpg | 1 - + 201304/jmg_0729.cr2 | 1 - + 201304/jmg_0729.jpg | 1 - + 201304/jmg_0730.jpg | 1 - + 201304/jmg_0731.jpg | 1 - + 201304/jmg_0733.cr2 | 1 - + 201304/jmg_0733.jpg | 1 - + 201304/jmg_0734.cr2 | 1 - + 201304/jmg_0734.jpg | 1 - + 201304/jmg_0736.cr2 | 1 - + 201304/jmg_0736.jpg | 1 - + 201304/jmg_0737.cr2 | 1 - + 201304/jmg_0737.jpg | 1 - + 201304/jmg_0738.jpg | 1 - + 201304/jmg_0739.jpg | 1 - + 201304/jmg_0740.jpg | 1 - + 201304/jmg_0741.jpg | 1 - + 201304/jmg_0742.jpg | 1 - + 201304/jmg_0744.cr2 | 1 - + 201304/jmg_0744.jpg | 1 - + 201304/jmg_0749.jpg | 1 - + 201304/jmg_0750.jpg | 1 - + 201304/jmg_0751.jpg | 1 - + 201304/jmg_0752.jpg | 1 - + 201304/jmg_0753.jpg | 1 - + 201304/jmg_0755.cr2 | 1 - + 201304/jmg_0755.jpg | 1 - + 201304/jmg_0757.cr2 | 1 - + 201304/jmg_0757.jpg | 1 - + 201304/jmg_0758.jpg | 1 - + 201304/jmg_0759.jpg | 1 - + 201304/jmg_0760.cr2 | 1 - + 201304/jmg_0760.jpg | 1 - + 201304/jmg_0762.cr2 | 1 - + 201304/jmg_0762.jpg | 1 - + 201304/jmg_0763.jpg | 1 - + 201304/jmg_0764.jpg | 1 - + 201304/jmg_0765.jpg | 1 - + 201304/jmg_0766.jpg | 1 - + 201304/jmg_0769.jpg | 1 - + 201304/jmg_0770.jpg | 1 - + 201304/jmg_0771.jpg | 1 - + 201304/jmg_0785.cr2 | 1 - + 201304/jmg_0785.jpg | 1 - + 201304/jmg_0786.cr2 | 1 - + 201304/jmg_0786.jpg | 1 - + 201304/jmg_0787.cr2 | 1 - + 201304/jmg_0787.jpg | 1 - + 201304/jmg_0789.jpg | 1 - + 201304/jmg_0790.jpg | 1 - + 201304/jmg_0791.jpg | 1 - + 201304/jmg_0800.jpg | 1 - + 201304/jmg_0801.jpg | 1 - + 201304/jmg_0802.jpg | 1 - + 201304/jmg_0803.jpg | 1 - + 201304/jmg_0809.jpg | 1 - + 201304/jmg_0810.jpg | 1 - + 201304/jmg_0812.jpg | 1 - + 201304/jmg_0813.jpg | 1 - + 201304/jmg_0824.jpg | 1 - + 201304/jmg_0825.jpg | 1 - + 201304/jmg_0827.jpg | 1 - + 201304/jmg_0831.jpg | 1 - + 201304/jmg_0833.jpg | 1 - + 201304/jmg_0834.jpg | 1 - + 201304/jmg_0836.jpg | 1 - + 201304/jmg_0837.jpg | 1 - + 201304/jmg_0845.jpg | 1 - + 201304/jmg_0846.jpg | 1 - + 201304/jmg_0847.jpg | 1 - + 201304/jmg_0848.jpg | 1 - + 201304/jmg_0849.jpg | 1 - + 201304/jmg_0850.jpg | 1 - + 201304/jmg_0851.jpg | 1 - + 201304/jmg_0857.jpg | 1 - + 201304/jmg_0858.jpg | 1 - + 201304/jmg_0860.jpg | 1 - + 201304/jmg_0861.jpg | 1 - + 201304/jmg_0862.jpg | 1 - + 201304/jmg_0863.jpg | 1 - + 201304/jmg_0864.jpg | 1 - + 201304/jmg_0866.jpg | 1 - + 201304/jmg_0867.jpg | 1 - + 201304/jmg_0868.cr2 | 1 - + 201304/jmg_0868.jpg | 1 - + 201304/jmg_0869.cr2 | 1 - + 201304/jmg_0869.jpg | 1 - + 201304/jmg_0872.cr2 | 1 - + 201304/jmg_0872.jpg | 1 - + 201304/jmg_0874.cr2 | 1 - + 201304/jmg_0874.jpg | 1 - + 201304/jmg_0875.jpg | 1 - + 201304/jmg_0875_raw.jpg | 1 - + 201304/jmg_0876.jpg | 1 - + 201304/jmg_0877.jpg | 1 - + 201304/jmg_0878.jpg | 1 - + 201304/jmg_0880.jpg | 1 - + 201304/jmg_0881.jpg | 1 - + 201304/jmg_0882.jpg | 1 - + 201304/jmg_0884.jpg | 1 - + 201304/jmg_0885.jpg | 1 - + 201304/jmg_0886.jpg | 1 - + 201304/jmg_0888.jpg | 1 - + 201304/jmg_0889.jpg | 1 - + 201304/jmg_0890.jpg | 1 - + 201304/jmg_0891.jpg | 1 - + 201304/jmg_0892.jpg | 1 - + 201304/jmg_0893.cr2 | 1 - + 201304/jmg_0893.jpg | 1 - + 201304/jmg_0894.jpg | 1 - + 201304/jmg_0896.jpg | 1 - + 201304/jmg_0897.jpg | 1 - + 201304/jmg_0898.jpg | 1 - + 201304/jmg_0899.jpg | 1 - + 201304/jmg_0900.jpg | 1 - + 201304/jmg_0902.jpg | 1 - + 201304/jmg_0905.jpg | 1 - + 201304/jmg_0921.jpg | 1 - + 201304/jmg_0922.jpg | 1 - + 201304/jmg_0932.jpg | 1 - + 201304/jmg_0935.jpg | 1 - + 201304/jmg_0936.jpg | 1 - + 201304/jmg_0937.jpg | 1 - + 201304/jmg_0938.jpg | 1 - + 201304/jmg_0942.jpg | 1 - + 201304/jmg_0944.jpg | 1 - + 201304/jmg_0946.jpg | 1 - + 201304/jmg_0947.jpg | 1 - + 201304/jmg_0948.jpg | 1 - + 201304/jmg_0949.jpg | 1 - + 201304/jmg_0950.jpg | 1 - + 201304/jmg_0951.jpg | 1 - + 201304/jmg_0952.jpg | 1 - + 201304/jmg_0953.jpg | 1 - + 201304/jmg_0954.jpg | 1 - + 201304/jmg_0958.jpg | 1 - + 201304/jmg_0959.jpg | 1 - + 201304/jmg_0960.jpg | 1 - + 201304/jmg_0961.jpg | 1 - + 201304/jmg_0962.jpg | 1 - + 201304/jmg_0963.jpg | 1 - + 201304/jmg_0964.jpg | 1 - + 201304/jmg_0965.jpg | 1 - + 201304/jmg_0966.jpg | 1 - + 201304/jmg_0967.jpg | 1 - + 201304/jmg_0968.jpg | 1 - + 201304/jmg_0969.jpg | 1 - + 201304/jmg_0976.cr2 | 1 - + 201304/jmg_0976.jpg | 1 - + 201304/jmg_0978.jpg | 1 - + 201304/jmg_0979.jpg | 1 - + 201304/jmg_0980.jpg | 1 - + 201304/jmg_0981.cr2 | 1 - + 201304/jmg_0981.jpg | 1 - + 201304/jmg_0982.jpg | 1 - + 201304/jmg_0984.cr2 | 1 - + 201304/jmg_0984.jpg | 1 - + 201304/jmg_0987.jpg | 1 - + 201304/jmg_0988.jpg | 1 - + 201304/jmg_0989.jpg | 1 - + 201304/jmg_0990.jpg | 1 - + 201304/jmg_0991.jpg | 1 - + 201304/jmg_0992.jpg | 1 - + 201304/jmg_1206.jpg | 1 - + 201304/jmg_1207.jpg | 1 - + 201304/jmg_1208.jpg | 1 - + 201304/jmg_1209.jpg | 1 - + 201304/jmg_1210.cr2 | 1 - + 201304/jmg_1210.jpg | 1 - + 201304/jmg_1211.jpg | 1 - + 201304/jmg_1212.jpg | 1 - + 201304/jmg_1213.jpg | 1 - + 201304/jmg_1214.cr2 | 1 - + 201304/jmg_1214.jpg | 1 - + 201304/jmg_1215.jpg | 1 - + 201304/jmg_1216.cr2 | 1 - + 201304/jmg_1216.jpg | 1 - + 201304/jmg_1217.cr2 | 1 - + 201304/jmg_1217.jpg | 1 - + 201304/jmg_1220.cr2 | 1 - + 201304/jmg_1220.jpg | 1 - + 201304/jmg_1222.cr2 | 1 - + 201304/jmg_1222.jpg | 1 - + 201304/jmg_1223.jpg | 1 - + 201306/jmg_1465.jpg | 1 - + 201306/jmg_1466.jpg | 1 - + 201306/jmg_1467.jpg | 1 - + 201306/jmg_1468.jpg | 1 - + 201306/jmg_1469.jpg | 1 - + 201306/jmg_1470.jpg | 1 - + 201306/jmg_1471.jpg | 1 - + 201306/jmg_1472.jpg | 1 - + 201306/jmg_1473.jpg | 1 - + 201306/jmg_1475.jpg | 1 - + 201306/jmg_1476.jpg | 1 - + 201306/jmg_1477.jpg | 1 - + 201306/jmg_1478.jpg | 1 - + 201306/jmg_1479.jpg | 1 - + 201306/jmg_1480.jpg | 1 - + 201306/jmg_1481.jpg | 1 - + 201306/jmg_1482.jpg | 1 - + 201306/jmg_1483.jpg | 1 - + 201306/jmg_1484.jpg | 1 - + 201306/jmg_1485.jpg | 1 - + 201306/jmg_1486.jpg | 1 - + 201306/jmg_1487.jpg | 1 - + 201306/jmg_1488.jpg | 1 - + 201306/jmg_1489.jpg | 1 - + 201306/jmg_1490.jpg | 1 - + 201306/jmg_1491.jpg | 1 - + 201306/jmg_1492.jpg | 1 - + 201306/jmg_1495.jpg | 1 - + 201306/jmg_1496.jpg | 1 - + 201306/jmg_1498.jpg | 1 - + 201306/jmg_1499.jpg | 1 - + 201306/jmg_1500.jpg | 1 - + 201306/jmg_1501.jpg | 1 - + 201306/jmg_1502.jpg | 1 - + 201306/jmg_1504.jpg | 1 - + 201306/jmg_1506.jpg | 1 - + 201306/jmg_1510.jpg | 1 - + 201306/jmg_1512.jpg | 1 - + 201306/jmg_1513.jpg | 1 - + 201306/jmg_1514.jpg | 1 - + 201306/jmg_1515.jpg | 1 - + 201306/jmg_1517.jpg | 1 - + 201306/jmg_1520.jpg | 1 - + 201306/jmg_1521.jpg | 1 - + 201306/jmg_1526.jpg | 1 - + 201306/jmg_1533.jpg | 1 - + 201306/jmg_1540.jpg | 1 - + 201306/jmg_1546.jpg | 1 - + 201306/jmg_1547.jpg | 1 - + 201306/jmg_1549.jpg | 1 - + 201306/jmg_1550.jpg | 1 - + 201306/jmg_1551.jpg | 1 - + 201306/jmg_1552.jpg | 1 - + 201306/jmg_1553.jpg | 1 - + 201306/jmg_1555.jpg | 1 - + 201306/jmg_1556.jpg | 1 - + 201306/jmg_1557.jpg | 1 - + 201306/jmg_1558.jpg | 1 - + 201306/jmg_1559.jpg | 1 - + 201306/jmg_1560.jpg | 1 - + 201306/jmg_1562.jpg | 1 - + 201306/jmg_1566.jpg | 1 - + 201306/jmg_1568.jpg | 1 - + 201306/jmg_1570.jpg | 1 - + 201306/jmg_1571.jpg | 1 - + 201306/jmg_1572.jpg | 1 - + 201306/jmg_1574.jpg | 1 - + 201306/jmg_1575.jpg | 1 - + 201306/jmg_1576.jpg | 1 - + 201306/jmg_1577.jpg | 1 - + 201306/jmg_1578.jpg | 1 - + 201306/jmg_1579.jpg | 1 - + 201306/jmg_1579_raw.jpg | 1 - + 201306/jmg_1581.jpg | 1 - + 201306/jmg_1583.jpg | 1 - + 201306/jmg_1583_cut.jpg | 1 - + 201306/jmg_1583_raw.jpg | 1 - + 201306/jmg_1584.jpg | 1 - + 201306/jmg_1586.jpg | 1 - + 201306/jmg_1587.jpg | 1 - + 201306/jmg_1588.jpg | 1 - + 201306/jmg_1589.jpg | 1 - + 201306/jmg_1591.jpg | 1 - + 201306/jmg_1592.jpg | 1 - + 201306/jmg_1593.jpg | 1 - + 201306/jmg_1593_raw.jpg | 1 - + 201306/jmg_1594.jpg | 1 - + 201306/jmg_1594_raw.jpg | 1 - + 201306/jmg_1595.jpg | 1 - + 201306/jmg_1596.jpg | 1 - + 201306/jmg_1597.jpg | 1 - + 201306/jmg_1599.jpg | 1 - + 201306/jmg_1626.jpg | 1 - + 201306/jmg_1628.jpg | 1 - + 201306/jmg_1629.jpg | 1 - + 201306/jmg_1630.jpg | 1 - + 201306/jmg_1631.jpg | 1 - + 201306/jmg_1633.jpg | 1 - + 201306/jmg_1635.jpg | 1 - + 201306/jmg_1636.jpg | 1 - + 201306/jmg_1637.jpg | 1 - + 201306/jmg_1638.jpg | 1 - + 201306/jmg_1640.jpg | 1 - + 201306/jmg_1642.jpg | 1 - + 201306/jmg_1643.jpg | 1 - + 201306/jmg_1644.jpg | 1 - + 201306/jmg_1647.jpg | 1 - + 201306/jmg_1649.jpg | 1 - + 201306/jmg_1650.jpg | 1 - + 201306/jmg_1651.jpg | 1 - + 201306/jmg_1652.jpg | 1 - + 201306/jmg_1653.jpg | 1 - + 201306/jmg_1655.jpg | 1 - + 201306/jmg_1656.jpg | 1 - + 201306/jmg_1660.jpg | 1 - + 201306/jmg_1667.jpg | 1 - + 201306/jmg_1682.jpg | 1 - + 201306/jmg_1688.jpg | 1 - + 201306/jmg_1689.jpg | 1 - + 201306/jmg_1701.jpg | 1 - + 201306/jmg_1702.jpg | 1 - + 201306/jmg_1703.jpg | 1 - + 201306/jmg_1710.jpg | 1 - + 201306/jmg_1710_raw.jpg | 1 - + 201306/jmg_1715.jpg | 1 - + 201306/jmg_1716.jpg | 1 - + 201306/jmg_1719.jpg | 1 - + 201306/jmg_1722.jpg | 1 - + 201306/jmg_1723.jpg | 1 - + 201306/jmg_1729.cr2 | 1 - + 201308/jmg_2038.jpg | 1 - + 201308/jmg_2039.jpg | 1 - + 201308/jmg_2040.jpg | 1 - + 201308/jmg_2041.jpg | 1 - + 201308/jmg_2042.jpg | 1 - + 201308/jmg_2043.jpg | 1 - + 201308/jmg_2045.jpg | 1 - + 201308/jmg_2047.jpg | 1 - + 201308/jmg_2048.jpg | 1 - + 201308/jmg_2049.jpg | 1 - + 201308/jmg_2050.jpg | 1 - + 201308/jmg_2051.jpg | 1 - + 201308/jmg_2052.jpg | 1 - + 201308/jmg_2053.jpg | 1 - + 201308/jmg_2054.jpg | 1 - + 201308/jmg_2055.jpg | 1 - + 201308/jmg_2056.jpg | 1 - + 201308/jmg_2057.jpg | 1 - + 201308/jmg_2058.jpg | 1 - + 201308/jmg_2059.jpg | 1 - + 201308/jmg_2060.jpg | 1 - + 201308/jmg_2061.jpg | 1 - + 201308/jmg_2062.jpg | 1 - + 201308/jmg_2089.cr2 | 1 - + 201308/jmg_2089.jpg | 1 - + 201308/jmg_2089_raw.jpg | 1 - + 201308/jmg_2090.jpg | 1 - + 201308/jmg_2091.jpg | 1 - + 201308/jmg_2092.jpg | 1 - + 201308/jmg_2093.jpg | 1 - + 201308/jmg_2096.jpg | 1 - + 201308/jmg_2097.jpg | 1 - + 201308/jmg_2098.jpg | 1 - + 201308/jmg_2099.cr2 | 1 - + 201308/jmg_2099.jpg | 1 - + 201308/jmg_2099_raw.jpg | 1 - + 201308/jmg_2100.cr2 | 1 - + 201308/jmg_2100.jpg | 1 - + 201308/jmg_2100_raw.jpg | 1 - + 201308/jmg_2102.jpg | 1 - + 201308/jmg_2103.jpg | 1 - + 201308/jmg_2104.jpg | 1 - + 201308/jmg_2105.jpg | 1 - + 201308/jmg_2106.jpg | 1 - + 201308/jmg_2107.jpg | 1 - + 201308/jmg_2108.jpg | 1 - + 201308/jmg_2109.jpg | 1 - + 201308/jmg_2110.jpg | 1 - + 201308/jmg_2111.jpg | 1 - + 201308/jmg_2112.jpg | 1 - + 201308/jmg_2113.jpg | 1 - + 201308/jmg_2114.jpg | 1 - + 201308/jmg_2115.jpg | 1 - + 201308/jmg_2117.jpg | 1 - + 201308/jmg_2118.jpg | 1 - + 201308/jmg_2119.jpg | 1 - + 201308/jmg_2120.jpg | 1 - + 201308/jmg_2122.jpg | 1 - + 201308/jmg_2125.jpg | 1 - + 201308/jmg_2127.jpg | 1 - + 201308/jmg_2129.jpg | 1 - + 201308/jmg_2130.jpg | 1 - + 201308/jmg_2132.jpg | 1 - + 201308/jmg_2134.jpg | 1 - + 201308/jmg_2135.jpg | 1 - + 201308/jmg_2136.jpg | 1 - + 201308/jmg_2137.jpg | 1 - + 201308/jmg_2138.jpg | 1 - + 201308/jmg_2148.jpg | 1 - + 201308/jmg_2150.jpg | 1 - + 201308/jmg_2151.jpg | 1 - + 201308/jmg_2156.jpg | 1 - + 201308/jmg_2158.cr2 | 1 - + 201308/jmg_2158.jpg | 1 - + 201308/jmg_2159.jpg | 1 - + 201308/jmg_2160.jpg | 1 - + 201308/jmg_2161.jpg | 1 - + 201308/jmg_2162.jpg | 1 - + 201308/jmg_2165.jpg | 1 - + 201308/jmg_2166.jpg | 1 - + 201308/jmg_2168.jpg | 1 - + 201308/jmg_2169.jpg | 1 - + 201308/jmg_2171.jpg | 1 - + 201308/jmg_2173.jpg | 1 - + 201308/jmg_2174.jpg | 1 - + 201308/jmg_2175.jpg | 1 - + 201308/jmg_2177.jpg | 1 - + 201308/jmg_2178.jpg | 1 - + 201308/jmg_2180.jpg | 1 - + 201308/jmg_2181.jpg | 1 - + 201308/jmg_2182.jpg | 1 - + 201308/jmg_2183.jpg | 1 - + 201308/jmg_2184.jpg | 1 - + 201308/jmg_2187.jpg | 1 - + 201308/jmg_2188.jpg | 1 - + 201308/jmg_2189.jpg | 1 - + 201308/jmg_2191.cr2 | 1 - + 201308/jmg_2191.jpg | 1 - + 201308/jmg_2193.cr2 | 1 - + 201308/jmg_2193.jpg | 1 - + 201308/jmg_2194.cr2 | 1 - + 201308/jmg_2194.jpg | 1 - + 201308/jmg_2197.cr2 | 1 - + 201308/jmg_2197.jpg | 1 - + 201308/jmg_2200.cr2 | 1 - + 201308/jmg_2200.jpg | 1 - + 201308/jmg_2201.cr2 | 1 - + 201308/jmg_2201.jpg | 1 - + 201308/jmg_2202.cr2 | 1 - + 201308/jmg_2202.jpg | 1 - + 201308/jmg_2209.jpg | 1 - + 201308/jmg_2210.jpg | 1 - + 201308/jmg_2215.jpg | 1 - + 201308/jmg_2216.jpg | 1 - + 201308/jmg_2217.cr2 | 1 - + 201308/jmg_2217.jpg | 1 - + 201308/jmg_2219.cr2 | 1 - + 201308/jmg_2219.jpg | 1 - + 201308/jmg_2223.jpg | 1 - + 201308/jmg_2224.jpg | 1 - + 201308/jmg_2225.cr2 | 1 - + 201308/jmg_2225.jpg | 1 - + 201308/jmg_2227.jpg | 1 - + 201308/jmg_2228.jpg | 1 - + 201308/jmg_2235.jpg | 1 - + 201308/jmg_2237.jpg | 1 - + 201308/jmg_2238.jpg | 1 - + 201308/jmg_2239.cr2 | 1 - + 201308/jmg_2239.jpg | 1 - + 201308/jmg_2239_raw.jpg | 1 - + 201308/jmg_2240.jpg | 1 - + 201308/jmg_2243.jpg | 1 - + 201308/jmg_2244.jpg | 1 - + 201308/jmg_2245.jpg | 1 - + 201308/jmg_2247.cr2 | 1 - + 201308/jmg_2247.jpg | 1 - + 201308/jmg_2249.jpg | 1 - + 201308/jmg_2250.cr2 | 1 - + 201308/jmg_2250.jpg | 1 - + 201308/jmg_2252.jpg | 1 - + 201308/jmg_2253.jpg | 1 - + 201308/jmg_2254.jpg | 1 - + incoming/5d/201203/jmg_8701.cr2 | 1 + + incoming/5d/201203/jmg_8702.jpg | 1 + + incoming/5d/201203/jmg_8705.jpg | 1 + + incoming/5d/201203/jmg_8711.jpg | 1 + + incoming/5d/201203/jmg_8717.jpg | 1 + + incoming/5d/201203/jmg_8718.jpg | 1 + + incoming/5d/201203/jmg_8719.jpg | 1 + + incoming/5d/201203/jmg_8721.jpg | 1 + + incoming/5d/201203/jmg_8725.jpg | 1 + + incoming/5d/201203/jmg_8726.jpg | 1 + + incoming/5d/201203/jmg_8731.jpg | 1 + + incoming/5d/201203/jmg_8745.jpg | 1 + + incoming/5d/201203/jmg_8747_raw.jpg | 1 + + incoming/5d/201203/jmg_8750.cr2 | 1 + + incoming/5d/201203/jmg_8750.jpg | 1 + + incoming/5d/201207/jmg_9048.jpg | 1 + + incoming/5d/201207/jmg_9053.jpg | 1 + + incoming/5d/201207/jmg_9054.jpg | 1 + + incoming/5d/201207/jmg_9069.cr2 | 1 + + incoming/5d/201207/jmg_9069.jpg | 1 + + incoming/5d/201207/jmg_9070.cr2 | 1 + + incoming/5d/201207/jmg_9070.jpg | 1 + + incoming/5d/201207/jmg_9072.cr2 | 1 + + incoming/5d/201207/jmg_9072.jpg | 1 + + incoming/5d/201207/jmg_9076.cr2 | 1 + + incoming/5d/201207/jmg_9076.jpg | 1 + + incoming/5d/201302/jmg_0502.cr2 | 1 + + incoming/5d/201302/jmg_0502.jpg | 1 + + incoming/5d/201302/jmg_0503.jpg | 1 + + incoming/5d/201302/jmg_0507.jpg | 1 + + incoming/5d/201302/jmg_0510.jpg | 1 + + incoming/5d/201302/jmg_0512.jpg | 1 + + incoming/5d/201302/jmg_0513.jpg | 1 + + incoming/5d/201302/jmg_0514.jpg | 1 + + incoming/5d/201302/jmg_0516.jpg | 1 + + incoming/5d/201302/jmg_0517.jpg | 1 + + incoming/5d/201302/jmg_0518.jpg | 1 + + incoming/5d/201302/jmg_0521.jpg | 1 + + incoming/5d/201302/jmg_0522.jpg | 1 + + incoming/5d/201302/jmg_0523.jpg | 1 + + incoming/5d/201302/jmg_0524.jpg | 1 + + incoming/5d/201302/jmg_0526.jpg | 1 + + incoming/5d/201302/jmg_0527.jpg | 1 + + incoming/5d/201302/jmg_0528.jpg | 1 + + incoming/5d/201302/jmg_0532.cr2 | 1 + + incoming/5d/201302/jmg_0532.jpg | 1 + + incoming/5d/201302/jmg_0534.jpg | 1 + + incoming/5d/201302/jmg_0535.jpg | 1 + + incoming/5d/201302/jmg_0537.jpg | 1 + + incoming/5d/201302/jmg_0539.jpg | 1 + + incoming/5d/201302/jmg_0541.jpg | 1 + + incoming/5d/201302/jmg_0543.jpg | 1 + + incoming/5d/jmg_0021.jpg | 1 + + incoming/5d/jmg_0025.jpg | 1 + + incoming/5d/jmg_0026.jpg | 1 + + incoming/5d/jmg_0027.jpg | 1 + + incoming/5d/jmg_0034.jpg | 1 + + incoming/5d/jmg_0035.jpg | 1 + + incoming/5d/jmg_0036.jpg | 1 + + incoming/5d/jmg_0130.jpg | 1 + + incoming/5d/jmg_0131.jpg | 1 + + incoming/5d/jmg_0133.jpg | 1 + + incoming/5d/jmg_0155.jpg | 1 + + incoming/5d/jmg_0156.jpg | 1 + + incoming/5d/jmg_0158.cr2 | 1 + + incoming/5d/jmg_0165.cr2 | 1 + + incoming/5d/jmg_0166.cr2 | 1 + + incoming/5d/jmg_0178.cr2 | 1 + + incoming/5d/jmg_0179.jpg | 1 + + incoming/5d/jmg_0180.cr2 | 1 + + incoming/5d/jmg_0184.jpg | 1 + + incoming/5d/jmg_0185.cr2 | 1 + + incoming/5d/jmg_0187.cr2 | 1 + + incoming/5d/jmg_0310.jpg | 1 + + incoming/5d/jmg_0312.jpg | 1 + + incoming/5d/jmg_0315.jpg | 1 + + incoming/5d/jmg_0340.jpg | 1 + + incoming/5d/jmg_0357.jpg | 1 + + incoming/5d/jmg_0364.jpg | 1 + + incoming/5d/jmg_0365.jpg | 1 + + incoming/5d/jmg_0368.jpg | 1 + + incoming/5d/jmg_0374.jpg | 1 + + incoming/5d/jmg_0375.jpg | 1 + + incoming/5d/jmg_0386.jpg | 1 + + incoming/5d/jmg_0399.jpg | 1 + + incoming/5d/jmg_0411.jpg | 1 + + incoming/5d/jmg_0418.jpg | 1 + + incoming/5d/jmg_0476.cr2 | 1 + + incoming/5d/jmg_0476.jpg | 1 + + incoming/5d/jmg_0503.jpg | 1 + + incoming/5d/jmg_0507.cr2 | 1 + + incoming/5d/jmg_0513.cr2 | 1 + + incoming/5d/jmg_0513.jpg | 1 + + incoming/5d/jmg_0516.cr2 | 1 + + incoming/5d/jmg_0517.cr2 | 1 + + incoming/5d/jmg_0518.jpg | 1 + + incoming/5d/jmg_0522.cr2 | 1 + + incoming/5d/jmg_0524.cr2 | 1 + + incoming/5d/jmg_0524.jpg | 1 + + incoming/5d/jmg_0530.jpg | 1 + + incoming/5d/jmg_0541.cr2 | 1 + + incoming/5d/jmg_0550.jpg | 1 + + incoming/5d/jmg_0554.jpg | 1 + + incoming/5d/jmg_0555.jpg | 1 + + incoming/5d/jmg_0558.jpg | 1 + + incoming/5d/jmg_0563.jpg | 1 + + incoming/5d/jmg_0573.jpg | 1 + + incoming/5d/jmg_0575.cr2 | 1 + + incoming/5d/jmg_0578.cr2 | 1 + + incoming/5d/jmg_0579.cr2 | 1 + + incoming/5d/jmg_0582.jpg | 1 + + incoming/5d/jmg_0593.cr2 | 1 + + incoming/5d/jmg_0594.cr2 | 1 + + incoming/5d/jmg_0594.jpg | 1 + + incoming/5d/jmg_0595.cr2 | 1 + + incoming/5d/jmg_0600.jpg | 1 + + incoming/5d/jmg_0606.cr2 | 1 + + incoming/5d/jmg_0607.jpg | 1 + + incoming/5d/jmg_0610.cr2 | 1 + + incoming/5d/jmg_0610.jpg | 1 + + incoming/5d/jmg_0612.jpg | 1 + + incoming/5d/jmg_0613.cr2 | 1 + + incoming/5d/jmg_0614.jpg | 1 + + incoming/5d/jmg_0619.cr2 | 1 + + incoming/5d/jmg_0623.jpg | 1 + + incoming/5d/jmg_0628.cr2 | 1 + + incoming/5d/jmg_0628.jpg | 1 + + incoming/5d/jmg_0639.jpg | 1 + + incoming/5d/jmg_0645.cr2 | 1 + + incoming/5d/jmg_0646.jpg | 1 + + incoming/5d/jmg_0647.cr2 | 1 + + incoming/5d/jmg_0648.jpg | 1 + + incoming/5d/jmg_0649.jpg | 1 + + incoming/5d/jmg_0655.jpg | 1 + + incoming/5d/jmg_0667.jpg | 1 + + incoming/5d/jmg_0670.jpg | 1 + + incoming/5d/jmg_0673.jpg | 1 + + incoming/5d/jmg_0679.jpg | 1 + + incoming/5d/jmg_0685.jpg | 1 + + incoming/5d/jmg_0699.cr2 | 1 + + incoming/5d/jmg_0700.cr2 | 1 + + incoming/5d/jmg_0701.cr2 | 1 + + incoming/5d/jmg_0708.jpg | 1 + + incoming/5d/jmg_0718.jpg | 1 + + incoming/5d/jmg_0726.cr2 | 1 + + incoming/5d/jmg_0728.jpg | 1 + + incoming/5d/jmg_0730.jpg | 1 + + incoming/5d/jmg_0734.jpg | 1 + + incoming/5d/jmg_0740.jpg | 1 + + incoming/5d/jmg_0743.cr2 | 1 + + incoming/5d/jmg_0744.cr2 | 1 + + incoming/5d/jmg_0745.cr2 | 1 + + incoming/5d/jmg_0747.jpg | 1 + + incoming/5d/jmg_0750.cr2 | 1 + + incoming/5d/jmg_0755.cr2 | 1 + + incoming/5d/jmg_0759.cr2 | 1 + + incoming/5d/jmg_0760.cr2 | 1 + + incoming/5d/jmg_0761.jpg | 1 + + incoming/5d/jmg_0765.jpg | 1 + + incoming/5d/jmg_0768.jpg | 1 + + incoming/5d/jmg_0771.jpg | 1 + + incoming/5d/jmg_0778.jpg | 1 + + incoming/5d/jmg_0780.jpg | 1 + + incoming/5d/jmg_0782.cr2 | 1 + + incoming/5d/jmg_0786.cr2 | 1 + + incoming/5d/jmg_0787.cr2 | 1 + + incoming/5d/jmg_0788.cr2 | 1 + + incoming/5d/jmg_0794.jpg | 1 + + incoming/5d/jmg_0796.jpg | 1 + + incoming/5d/jmg_0801.cr2 | 1 + + incoming/5d/jmg_0803.cr2 | 1 + + incoming/5d/jmg_0804.cr2 | 1 + + incoming/5d/jmg_0812.jpg | 1 + + incoming/5d/jmg_0819.jpg | 1 + + incoming/5d/jmg_0827.jpg | 1 + + incoming/5d/jmg_0830.jpg | 1 + + incoming/5d/jmg_0842.jpg | 1 + + incoming/5d/jmg_0846.jpg | 1 + + incoming/5d/jmg_0857.cr2 | 1 + + incoming/5d/jmg_0863.jpg | 1 + + incoming/5d/jmg_0866.cr2 | 1 + + incoming/5d/jmg_0868.cr2 | 1 + + incoming/5d/jmg_0868.jpg | 1 + + incoming/5d/jmg_0870.jpg | 1 + + incoming/5d/jmg_0877.jpg | 1 + + incoming/5d/jmg_0882.cr2 | 1 + + incoming/5d/jmg_0883.jpg | 1 + + incoming/5d/jmg_0888.jpg | 1 + + incoming/5d/jmg_0891.jpg | 1 + + incoming/5d/jmg_0894.cr2 | 1 + + incoming/5d/jmg_0896.cr2 | 1 + + incoming/5d/jmg_0897.cr2 | 1 + + incoming/5d/jmg_0898.jpg | 1 + + incoming/5d/jmg_0899.cr2 | 1 + + incoming/5d/jmg_0900.jpg | 1 + + incoming/5d/jmg_0905.jpg | 1 + + incoming/5d/jmg_0908.jpg | 1 + + incoming/5d/jmg_0914.jpg | 1 + + incoming/5d/jmg_0915.jpg | 1 + + incoming/5d/jmg_0916.jpg | 1 + + incoming/5d/jmg_0923.jpg | 1 + + incoming/5d/jmg_0924.jpg | 1 + + incoming/5d/jmg_0926.jpg | 1 + + incoming/5d/jmg_0928.jpg | 1 + + incoming/5d/jmg_0929.jpg | 1 + + incoming/5d/jmg_0936.jpg | 1 + + incoming/5d/jmg_0942.jpg | 1 + + incoming/5d/jmg_0944.jpg | 1 + + incoming/5d/jmg_0948.jpg | 1 + + incoming/5d/jmg_0960.jpg | 1 + + incoming/5d/jmg_0966.jpg | 1 + + incoming/5d/jmg_0970.cr2 | 1 + + incoming/5d/jmg_0970.jpg | 1 + + incoming/5d/jmg_0972.jpg | 1 + + incoming/5d/jmg_0976.jpg | 1 + + incoming/5d/jmg_0983.cr2 | 1 + + incoming/5d/jmg_0985.cr2 | 1 + + incoming/5d/jmg_0985.jpg | 1 + + incoming/5d/jmg_0994.jpg | 1 + + incoming/5d/jmg_1005.jpg | 2 +- + incoming/5d/jmg_1009.jpg | 2 +- + incoming/5d/jmg_1012.jpg | 2 +- + incoming/5d/jmg_1020.jpg | 2 +- + incoming/5d/jmg_1021.jpg | 2 +- + incoming/5d/jmg_1032.jpg | 2 +- + incoming/5d/jmg_1033.jpg | 2 +- + incoming/5d/jmg_1037.jpg | 2 +- + incoming/5d/jmg_1039.jpg | 2 +- + incoming/5d/jmg_1048.jpg | 2 +- + incoming/5d/jmg_1051.jpg | 2 +- + incoming/5d/jmg_1063.jpg | 2 +- + incoming/5d/jmg_1064.jpg | 2 +- + incoming/5d/jmg_1067.jpg | 2 +- + incoming/5d/jmg_1116.jpg | 2 +- + incoming/5d/jmg_1118.jpg | 2 +- + incoming/5d/jmg_1125.jpg | 2 +- + incoming/5d/jmg_1126.jpg | 2 +- + incoming/5d/jmg_1129.jpg | 2 +- + incoming/5d/jmg_1133.jpg | 2 +- + incoming/5d/jmg_1138.jpg | 2 +- + incoming/5d/jmg_1139.jpg | 2 +- + incoming/5d/jmg_1143.jpg | 2 +- + incoming/5d/jmg_1149.jpg | 2 +- + incoming/5d/jmg_1150.jpg | 2 +- + incoming/5d/jmg_1155.jpg | 2 +- + incoming/5d/jmg_1160.jpg | 2 +- + incoming/5d/jmg_1168.jpg | 2 +- + incoming/5d/jmg_1173.jpg | 2 +- + incoming/5d/jmg_1175.jpg | 2 +- + incoming/5d/jmg_1177.jpg | 2 +- + incoming/5d/jmg_1179.jpg | 2 +- + incoming/5d/jmg_1183.jpg | 2 +- + incoming/5d/jmg_1185.jpg | 2 +- + incoming/5d/jmg_1189.jpg | 2 +- + incoming/5d/jmg_1192.jpg | 2 +- + incoming/5d/jmg_1199.jpg | 2 +- + incoming/5d/jmg_1205.jpg | 2 +- + incoming/5d/jmg_1209.cr2 | 1 + + incoming/5d/jmg_1209.jpg | 1 + + incoming/5d/jmg_1211.cr2 | 1 + + incoming/5d/jmg_1211.jpg | 1 + + incoming/5d/jmg_1217.cr2 | 1 + + incoming/5d/jmg_1467.cr2 | 1 + + incoming/5d/jmg_1469.jpg | 1 + + incoming/5d/jmg_1470.cr2 | 1 + + incoming/5d/jmg_1471.cr2 | 1 + + incoming/5d/jmg_1472.cr2 | 1 + + incoming/5d/jmg_1477.cr2 | 1 + + incoming/5d/jmg_1477.jpg | 1 + + incoming/5d/jmg_1481.cr2 | 1 + + incoming/5d/jmg_1483.cr2 | 1 + + incoming/5d/jmg_1485.jpg | 1 + + incoming/5d/jmg_1488.jpg | 1 + + incoming/5d/jmg_1491.jpg | 1 + + incoming/5d/jmg_1496.cr2 | 1 + + incoming/5d/jmg_1502.jpg | 1 + + incoming/5d/jmg_1503.cr2 | 1 + + incoming/5d/jmg_1504.jpg | 1 + + incoming/5d/jmg_1507.jpg | 1 + + incoming/5d/jmg_1515.jpg | 1 + + incoming/5d/jmg_1520.jpg | 1 + + incoming/5d/jmg_1523.jpg | 1 + + incoming/5d/jmg_1525.jpg | 1 + + incoming/5d/jmg_1539.jpg | 1 + + incoming/5d/jmg_1542.jpg | 1 + + incoming/5d/jmg_1546.jpg | 1 + + incoming/5d/jmg_1547.cr2 | 1 + + incoming/5d/jmg_1549.jpg | 1 + + incoming/5d/jmg_1552.jpg | 1 + + incoming/5d/jmg_1554.cr2 | 1 + + incoming/5d/jmg_1555.cr2 | 1 + + incoming/5d/jmg_1556.cr2 | 1 + + incoming/5d/jmg_1559.cr2 | 1 + + incoming/5d/jmg_1560.cr2 | 1 + + incoming/5d/jmg_1561.cr2 | 1 + + incoming/5d/jmg_1562.cr2 | 1 + + incoming/5d/jmg_1565.cr2 | 1 + + incoming/5d/jmg_1567.cr2 | 1 + + incoming/5d/jmg_1572.cr2 | 1 + + incoming/5d/jmg_1577.cr2 | 1 + + incoming/5d/jmg_1578.jpg | 1 + + incoming/5d/jmg_1583_cut.jpg | 1 + + incoming/5d/jmg_1583_raw.jpg | 1 + + incoming/5d/jmg_1592.cr2 | 1 + + incoming/5d/jmg_1593.jpg | 1 + + incoming/5d/jmg_1626.cr2 | 1 + + incoming/5d/jmg_1627.jpg | 1 + + incoming/5d/jmg_1628.cr2 | 1 + + incoming/5d/jmg_1629.jpg | 1 + + incoming/5d/jmg_1630.cr2 | 1 + + incoming/5d/jmg_1631.cr2 | 1 + + incoming/5d/jmg_1633.cr2 | 1 + + incoming/5d/jmg_1638.jpg | 1 + + incoming/5d/jmg_1639.cr2 | 1 + + incoming/5d/jmg_1646.cr2 | 1 + + incoming/5d/jmg_1646.jpg | 1 + + incoming/5d/jmg_1650.jpg | 1 + + incoming/5d/jmg_1651.cr2 | 1 + + incoming/5d/jmg_1654.cr2 | 1 + + incoming/5d/jmg_1656.jpg | 1 + + incoming/5d/jmg_1677.jpg | 1 + + incoming/5d/jmg_1689.jpg | 1 + + incoming/5d/jmg_1701.jpg | 1 + + incoming/5d/jmg_1703.jpg | 1 + + incoming/5d/jmg_1723.jpg | 1 + + incoming/5d/jmg_2039.jpg | 1 + + incoming/5d/jmg_2041.jpg | 1 + + incoming/5d/jmg_2048.cr2 | 1 + + incoming/5d/jmg_2052.jpg | 1 + + incoming/5d/jmg_2061.jpg | 1 + + incoming/5d/jmg_2064_raw.jpg | 1 - + incoming/5d/jmg_2065_mo.jpg | 1 - + incoming/5d/jmg_2065_raw.jpg | 1 - + incoming/5d/jmg_2066_mo.jpg | 1 - + incoming/5d/jmg_2066_raw.jpg | 1 - + incoming/5d/jmg_2090.jpg | 1 + + incoming/5d/jmg_2093.jpg | 1 + + incoming/5d/jmg_2100.cr2 | 1 + + incoming/5d/jmg_2103.jpg | 1 + + incoming/5d/jmg_2107.jpg | 1 + + incoming/5d/jmg_2108.jpg | 1 + + incoming/5d/jmg_2112.jpg | 1 + + incoming/5d/jmg_2118.jpg | 1 + + incoming/5d/jmg_2119.jpg | 1 + + incoming/5d/jmg_2122.jpg | 1 + + incoming/5d/jmg_2125.jpg | 1 + + incoming/5d/jmg_2137.jpg | 1 + + incoming/5d/jmg_2149.jpg | 1 + + incoming/5d/jmg_2150.jpg | 1 + + incoming/5d/jmg_2158.cr2 | 1 + + incoming/5d/jmg_2160.jpg | 1 + + incoming/5d/jmg_2165.jpg | 1 + + incoming/5d/jmg_2188.jpg | 1 + + incoming/5d/jmg_2189.jpg | 1 + + incoming/5d/jmg_2193.jpg | 1 + + incoming/5d/jmg_2194.cr2 | 1 + + incoming/5d/jmg_2200.jpg | 1 + + incoming/5d/jmg_2201.cr2 | 1 + + incoming/5d/jmg_2201.jpg | 1 + + incoming/5d/jmg_2210.jpg | 1 + + incoming/5d/jmg_2215.cr2 | 1 + + incoming/5d/jmg_2216.cr2 | 1 + + incoming/5d/jmg_2216.jpg | 1 + + incoming/5d/jmg_2224.jpg | 1 + + incoming/5d/jmg_2235.jpg | 1 + + incoming/5d/jmg_2238.jpg | 1 + + incoming/5d/jmg_2239.cr2 | 1 + + incoming/5d/jmg_2239.jpg | 1 + + incoming/5d/jmg_2240.jpg | 1 + + incoming/5d/jmg_2244.jpg | 1 + + incoming/5d/jmg_2247.jpg | 1 + + incoming/5d/jmg_7250.cr2 | 1 + + incoming/5d/jmg_7250.jpg | 1 + + incoming/5d/jmg_7256.jpg | 1 + + incoming/5d/jmg_7257.cr2 | 1 + + incoming/5d/jmg_7259.cr2 | 1 + + incoming/5d/jmg_7263.jpg | 1 + + incoming/5d/jmg_7265.cr2 | 1 + + incoming/5d/jmg_7269.cr2 | 1 + + incoming/5d/jmg_7270.cr2 | 1 + + incoming/5d/jmg_7279.cr2 | 1 + + incoming/5d/jmg_7286.cr2 | 1 + + incoming/5d/jmg_7286.jpg | 1 + + incoming/5d/jmg_7290.cr2 | 1 + + incoming/5d/jmg_7290.jpg | 1 + + incoming/5d/jmg_7293.cr2 | 1 + + incoming/5d/jmg_7296.cr2 | 1 + + incoming/5d/jmg_7299.jpg | 1 + + incoming/5d/jmg_7300.cr2 | 1 + + incoming/5d/jmg_7300.jpg | 1 + + incoming/5d/jmg_7305_raw.jpg | 1 + + incoming/5d/jmg_8532.cr2 | 1 + + incoming/5d/jmg_8533.cr2 | 1 + + incoming/5d/jmg_8534.cr2 | 1 + + incoming/5d/jmg_8536.jpg | 1 + + incoming/5d/jmg_8538.cr2 | 1 + + incoming/5d/jmg_8549.cr2 | 1 + + incoming/5d/jmg_8549.jpg | 1 + + incoming/5d/jmg_8552.cr2 | 1 + + incoming/5d/jmg_8557.cr2 | 1 + + incoming/5d/jmg_8560.cr2 | 1 + + incoming/5d/jmg_8565.cr2 | 1 + + incoming/5d/jmg_8566.cr2 | 1 + + incoming/5d/jmg_8569.jpg | 1 + + incoming/5d/jmg_8575.jpg | 1 + + incoming/5d/jmg_8576.jpg | 1 + + incoming/5d/jmg_8578.cr2 | 1 + + incoming/5d/jmg_8579.cr2 | 1 + + incoming/5d/jmg_8580.jpg | 1 + + incoming/5d/jmg_8583.cr2 | 1 + + incoming/5d/jmg_8588.cr2 | 1 + + incoming/5d/jmg_8589.cr2 | 1 + + incoming/5d/jmg_8595.jpg | 1 + + incoming/5d/jmg_8597.jpg | 1 + + incoming/5d/jmg_8599.jpg | 1 + + incoming/5d/jmg_8602.cr2 | 1 + + incoming/5d/jmg_8603.cr2 | 1 + + incoming/5d/jmg_8606.cr2 | 1 + + incoming/5d/jmg_8606.jpg | 1 + + incoming/5d/jmg_8609.jpg | 1 + + incoming/5d/jmg_8613.jpg | 1 + + incoming/5d/jmg_8615.cr2 | 1 + + incoming/5d/jmg_8617.jpg | 1 + + incoming/5d/jmg_8619.cr2 | 1 + + incoming/5d/jmg_8620.jpg | 1 + + incoming/5d/jmg_8625.jpg | 1 + + incoming/5d/jmg_8627.jpg | 1 + + incoming/5d/jmg_8628.jpg | 1 + + incoming/5d/jmg_8632.cr2 | 1 + + incoming/5d/jmg_8636.cr2 | 1 + + incoming/5d/jmg_8636.jpg | 1 + + incoming/5d/jmg_8637.cr2 | 1 + + incoming/5d/jmg_8639.jpg | 1 + + incoming/5d/jmg_8640.cr2 | 1 + + incoming/5d/jmg_8655.jpg | 1 + + incoming/5d/jmg_8657.jpg | 1 + + incoming/5d/jmg_8670.cr2 | 1 + + incoming/5d/jmg_8673.jpg | 1 + + incoming/5d/jmg_8674.cr2 | 1 + + incoming/5d/jmg_8676.cr2 | 1 + + incoming/5d/jmg_8676.jpg | 1 + + incoming/5d/jmg_8677.cr2 | 1 + + incoming/5d/jmg_8681.jpg | 1 + + incoming/5d/jmg_8682.cr2 | 1 + + incoming/5d/jmg_8702.cr2 | 1 + + incoming/5d/jmg_8702.jpg | 1 + + incoming/5d/jmg_8707.jpg | 1 + + incoming/5d/jmg_8714.jpg | 1 + + incoming/5d/jmg_8716.jpg | 1 + + incoming/5d/jmg_8717.cr2 | 1 + + incoming/5d/jmg_8719.jpg | 1 + + incoming/5d/jmg_8721.jpg | 1 + + incoming/5d/jmg_8727.cr2 | 1 + + incoming/5d/jmg_8730.jpg | 1 + + incoming/5d/jmg_8736.cr2 | 1 + + incoming/5d/jmg_8737.cr2 | 1 + + incoming/5d/jmg_8742.cr2 | 1 + + incoming/5d/jmg_8742.jpg | 1 + + incoming/5d/jmg_8745.jpg | 1 + + incoming/5d/jmg_8748.cr2 | 1 + + incoming/5d/jmg_8748.jpg | 1 + + incoming/5d/jmg_8751.cr2 | 1 + + incoming/5d/jmg_8755.cr2 | 1 + + incoming/5d/jmg_8757.cr2 | 1 + + incoming/5d/jmg_8760.cr2 | 1 + + incoming/5d/jmg_8760.jpg | 1 + + incoming/5d/jmg_8765.cr2 | 1 + + incoming/5d/jmg_8771.jpg | 1 + + incoming/5d/jmg_8801.jpg | 1 + + incoming/5d/jmg_8803.cr2 | 1 + + incoming/5d/jmg_8803.jpg | 1 + + incoming/5d/jmg_8804.jpg | 1 + + incoming/5d/jmg_8805.jpg | 1 + + incoming/5d/jmg_8813.jpg | 1 + + incoming/5d/jmg_8816.cr2 | 1 + + incoming/5d/jmg_8823.jpg | 1 + + incoming/5d/jmg_8827.cr2 | 1 + + incoming/5d/jmg_8829.cr2 | 1 + + incoming/5d/jmg_8832.jpg | 1 + + incoming/5d/jmg_8833.cr2 | 1 + + incoming/5d/jmg_8837.cr2 | 1 + + incoming/5d/jmg_8838.jpg | 1 + + incoming/5d/jmg_8840.jpg | 1 + + incoming/5d/jmg_8842.jpg | 1 + + incoming/5d/jmg_8844.cr2 | 1 + + incoming/5d/jmg_8850.cr2 | 1 + + incoming/5d/jmg_8850.jpg | 1 + + incoming/5d/jmg_8852.cr2 | 1 + + incoming/5d/jmg_8853.cr2 | 1 + + incoming/5d/jmg_8853.jpg | 1 + + incoming/5d/jmg_8856.cr2 | 1 + + incoming/5d/jmg_8859.jpg | 1 + + incoming/5d/jmg_8863.jpg | 1 + + incoming/5d/jmg_8870.jpg | 1 + + incoming/5d/jmg_8871.cr2 | 1 + + incoming/5d/jmg_8871.jpg | 1 + + incoming/5d/jmg_8881.jpg | 1 + + incoming/5d/jmg_8883.jpg | 1 + + incoming/5d/jmg_8886.jpg | 1 + + incoming/5d/jmg_8887.cr2 | 1 + + incoming/5d/jmg_8889.cr2 | 1 + + incoming/5d/jmg_8894.cr2 | 1 + + incoming/5d/jmg_8897.cr2 | 1 + + incoming/5d/jmg_8898.cr2 | 1 + + incoming/5d/jmg_8900.jpg | 1 + + incoming/5d/jmg_8901.cr2 | 1 + + incoming/5d/jmg_8902.cr2 | 1 + + incoming/5d/jmg_8904.cr2 | 1 + + incoming/5d/jmg_8906.jpg | 1 + + incoming/5d/jmg_8908.cr2 | 1 + + incoming/5d/jmg_8920.cr2 | 1 + + incoming/5d/jmg_8920.jpg | 1 + + incoming/5d/jmg_8922.cr2 | 1 + + incoming/5d/jmg_8922.jpg | 1 + + incoming/5d/jmg_8923.cr2 | 1 + + incoming/5d/jmg_8924.jpg | 1 + + incoming/5d/jmg_8925.cr2 | 1 + + incoming/5d/jmg_8929.jpg | 1 + + incoming/5d/jmg_8930.jpg | 1 + + incoming/5d/jmg_8937.cr2 | 1 + + incoming/5d/jmg_8939.cr2 | 1 + + incoming/5d/jmg_8940.jpg | 1 + + incoming/5d/jmg_8941.jpg | 1 + + incoming/5d/jmg_8943.cr2 | 1 + + incoming/5d/jmg_8944.jpg | 1 + + incoming/5d/jmg_8950.cr2 | 1 + + incoming/5d/jmg_8951.jpg | 1 + + incoming/5d/jmg_8955.jpg | 1 + + incoming/5d/jmg_8959.cr2 | 1 + + incoming/5d/jmg_8960.jpg | 1 + + incoming/5d/jmg_8962.cr2 | 1 + + incoming/5d/jmg_8964.cr2 | 1 + + incoming/5d/jmg_8965.jpg | 1 + + incoming/5d/jmg_8966.jpg | 1 + + incoming/5d/jmg_8971.jpg | 1 + + incoming/5d/jmg_8976.jpg | 1 + + incoming/5d/jmg_8978.cr2 | 1 + + incoming/5d/jmg_8981.jpg | 1 + + incoming/5d/jmg_8982.jpg | 1 + + incoming/5d/jmg_8985.jpg | 1 + + incoming/5d/jmg_8988.cr2 | 1 + + incoming/5d/jmg_8988.jpg | 1 + + incoming/5d/jmg_8992.cr2 | 1 + + incoming/5d/jmg_8995.jpg | 1 + + incoming/5d/jmg_8996.cr2 | 1 + + incoming/5d/jmg_8997.cr2 | 1 + + incoming/5d/jmg_8999.cr2 | 1 + + incoming/5d/jmg_9000.cr2 | 1 + + incoming/5d/jmg_9015.cr2 | 1 + + incoming/5d/jmg_9017.cr2 | 1 + + incoming/5d/jmg_9019.cr2 | 1 + + incoming/5d/jmg_9021.cr2 | 1 + + incoming/5d/jmg_9021.jpg | 1 + + incoming/5d/jmg_9022.cr2 | 1 + + incoming/5d/jmg_9027.cr2 | 1 + + incoming/5d/jmg_9028.jpg | 1 + + incoming/5d/jmg_9031.cr2 | 1 + + incoming/5d/jmg_9035.cr2 | 1 + + incoming/5d/jmg_9043.jpg | 1 + + incoming/5d/jmg_9057.cr2 | 1 + + incoming/5d/jmg_9064.cr2 | 1 + + incoming/5d/jmg_9077.jpg | 1 + + incoming/5d/jmg_9078.jpg | 1 + + incoming/5d/jmg_9081.jpg | 1 + + incoming/5d/jmg_9082.cr2 | 1 + + incoming/5d/jmg_9083.jpg | 1 + + incoming/5d/jmg_9086.cr2 | 1 + + incoming/5d/jmg_9088.jpg | 1 + + incoming/5d/jmg_9308.jpg | 1 + + incoming/5d/jmg_9312.cr2 | 1 + + incoming/5d/jmg_9313.jpg | 1 + + incoming/5d/jmg_9319.jpg | 1 + + incoming/5d/jmg_9521.cr2 | 1 + + incoming/5d/jmg_9522.cr2 | 1 + + incoming/5d/jmg_9533.jpg | 1 + + incoming/5d/jmg_9534.jpg | 1 + + incoming/5d/jmg_9535.cr2 | 1 + + incoming/5d/jmg_9538.cr2 | 1 + + incoming/5d/jmg_9538.jpg | 1 + + incoming/5d/jmg_9540.jpg | 1 + + incoming/5d/jmg_9542.cr2 | 1 + + incoming/5d/jmg_9545.jpg | 1 + + incoming/5d/jmg_9554.jpg | 1 + + incoming/5d/jmg_9555.jpg | 1 + + incoming/5d/jmg_9558.jpg | 1 + + incoming/5d/jmg_9561.cr2 | 1 + + incoming/5d/jmg_9585.cr2 | 1 + + incoming/5d/jmg_9587.jpg | 1 + + incoming/5d/jmg_9591.jpg | 1 + + incoming/5d/jmg_9595.jpg | 1 + + incoming/5d/jmg_9598.cr2 | 1 + + incoming/5d/jmg_9600.jpg | 1 + + incoming/5d/jmg_9604.jpg | 1 + + incoming/5d/jmg_9610.jpg | 1 + + incoming/5d/jmg_9613.cr2 | 1 + + incoming/5d/jmg_9613.jpg | 1 + + incoming/5d/jmg_9614.cr2 | 1 + + incoming/5d/jmg_9618.jpg | 1 + + incoming/5d/jmg_9619.jpg | 1 + + incoming/5d/jmg_9620.jpg | 1 + + incoming/5d/jmg_9621.jpg | 1 + + incoming/5d/jmg_9623.cr2 | 1 + + incoming/5d/jmg_9746.jpg | 1 + + incoming/5d/jmg_9763.cr2 | 1 + + incoming/5d/jmg_9763.jpg | 1 + + incoming/5d/jmg_9764.cr2 | 1 + + incoming/5d/jmg_9772.jpg | 1 + + incoming/5d/jmg_9773.jpg | 1 + + incoming/5d/jmg_9781.jpg | 1 + + incoming/5d/jmg_9790.jpg | 1 + + incoming/5d/jmg_9800.jpg | 1 + + incoming/5d/jmg_9808.jpg | 1 + + incoming/5d/jmg_9830.jpg | 1 + + incoming/5d/jmg_9834.cr2 | 1 + + incoming/5d/jmg_9843.jpg | 1 + + incoming/5d/jmg_9848.jpg | 1 + + incoming/5d/jmg_9849.jpg | 1 + + incoming/5d/jmg_9853.cr2 | 1 + + incoming/5d/jmg_9856.jpg | 1 + + incoming/5d/jmg_9857.cr2 | 1 + + incoming/5d/jmg_9859.cr2 | 1 + + incoming/5d/jmg_9860.jpg | 1 + + incoming/5d/jmg_9917.jpg | 1 + + incoming/5d/jmg_9923.jpg | 1 + + incoming/5d/jmg_9926.jpg | 1 + + incoming/5d/jmg_9975.cr2 | 1 + + incoming/5d/jmg_9976.cr2 | 1 + + incoming/5d/jmg_9978.jpg | 1 + + incoming/5d/jmg_9988.jpg | 1 + + incoming/5d/jmg_9997.cr2 | 1 + + incoming/5d/jmg_9998.jpg | 1 + + incoming/5d/jmg_9999.jpg | 1 + + list_5d_repoB | 1 - + only_on_repoB | 1 + + dir/2012/dir2/jmg_0128.cr2 | 1 - + dir/2012/dir2/jmg_0128.jpg | 1 - + dir/2012/dir2/jmg_0129.cr2 | 1 - + dir/2012/dir2/jmg_0129.jpg | 1 - + dir/2012/dir2/jmg_0353.jpg | 1 - + dir/2012/dir2/jmg_0354.jpg | 1 - + dir/2012/dir2/jmg_0375.jpg | 1 - + dir/2012/dir2/jmg_0376.jpg | 1 - + dir/2012/dir2/jmg_0378.jpg | 1 - + dir/2012/dir2/jmg_8707.cr2 | 1 - + dir/2012/dir2/jmg_8707.jpg | 1 - + dir/2012/dir2/jmg_8727.cr2 | 1 - + dir/2012/dir2/jmg_8727.jpg | 1 - + dir/2012/dir2/jmg_8728.cr2 | 1 - + dir/2012/dir2/jmg_8728.jpg | 1 - + dir/2012/dir2/jmg_8729.cr2 | 1 - + dir/2012/dir2/jmg_8729.jpg | 1 - + dir/2012/dir2/jmg_8740.cr2 | 1 - + dir/2012/dir2/jmg_8740.jpg | 1 - + dir/2012/dir2/jmg_8742.cr2 | 1 - + dir/2012/dir2/jmg_8742.jpg | 1 - + dir/2012/dir2/jmg_8825.cr2 | 1 - + dir/2012/dir2/jmg_8825.jpg | 1 - + dir/2012/dir2/jmg_8991.cr2 | 1 - + dir/2012/dir2/jmg_8991.jpg | 1 - + dir/2012/dir2/jmg_8992.cr2 | 1 - + dir/2012/dir2/jmg_8992.jpg | 1 - + dir/2012/dir2/jmg_8993.cr2 | 1 - + dir/2012/dir2/jmg_8993.jpg | 1 - + dir/2012/dir2/jmg_9059.cr2 | 1 - + dir/2012/dir2/jmg_9059.jpg | 1 - + dir/2012/dir2/jmg_9060.cr2 | 1 - + dir/2012/dir2/jmg_9060.jpg | 1 - + dir/2012/dir2/jmg_9064.cr2 | 1 - + dir/2012/dir2/jmg_9064.jpg | 1 - + dir/2012/dir2/jmg_9065.cr2 | 1 - + dir/2012/dir2/jmg_9065.jpg | 1 - + dir/2012/dir2/jmg_9081.cr2 | 1 - + dir/2012/dir2/jmg_9081.jpg | 1 - + dir/2012/dir2/jmg_9082.cr2 | 1 - + dir/2012/dir2/jmg_9082.jpg | 1 - + dir/2012/dir2/jmg_9083.cr2 | 1 - + dir/2012/dir2/jmg_9083.jpg | 1 - + dir/2012/dir1/jmg_0132.cr2 | 1 - + dir/2012/dir1/jmg_0132.jpg | 1 - + dir/2012/dir1/jmg_0133.cr2 | 1 - + dir/2012/dir1/jmg_0133.jpg | 1 - + dir/2012/dir1/jmg_0347.jpg | 1 - + dir/2012/dir1/jmg_0351.jpg | 1 - + dir/2012/dir1/jmg_0352.jpg | 1 - + dir/2012/dir1/jmg_0374.jpg | 1 - + dir/2012/dir1/jmg_8714.cr2 | 1 - + dir/2012/dir1/jmg_8714.jpg | 1 - + dir/2012/dir1/jmg_8716.cr2 | 1 - + dir/2012/dir1/jmg_8716.jpg | 1 - + dir/2012/dir1/jmg_8734.cr2 | 1 - + dir/2012/dir1/jmg_8734.jpg | 1 - + dir/2012/dir1/jmg_8735.cr2 | 1 - + dir/2012/dir1/jmg_8735.jpg | 1 - + dir/2012/dir1/jmg_8736.cr2 | 1 - + dir/2012/dir1/jmg_8736.jpg | 1 - + dir/2012/dir1/jmg_8743.cr2 | 1 - + dir/2012/dir1/jmg_8743.jpg | 1 - + dir/2012/dir1/jmg_8746.cr2 | 1 - + dir/2012/dir1/jmg_8746.jpg | 1 - + dir/2012/dir1/jmg_8828.cr2 | 1 - + dir/2012/dir1/jmg_8828.jpg | 1 - + dir/2012/dir1/jmg_8984.cr2 | 1 - + dir/2012/dir1/jmg_8984.jpg | 1 - + dir/2012/dir1/jmg_8985.cr2 | 1 - + dir/2012/dir1/jmg_8985.jpg | 1 - + dir/2012/dir1/jmg_8986.cr2 | 1 - + dir/2012/dir1/jmg_8986.jpg | 1 - + dir/2012/dir1/jmg_8988.cr2 | 1 - + dir/2012/dir1/jmg_8988.jpg | 1 - + dir/2012/dir1/jmg_9057.cr2 | 1 - + dir/2012/dir1/jmg_9057.jpg | 1 - + dir/2012/dir1/jmg_9058.cr2 | 1 - + dir/2012/dir1/jmg_9058.jpg | 1 - + dir/2012/dir1/jmg_9086.cr2 | 1 - + dir/2012/dir1/jmg_9086.jpg | 1 - + dir/2012/dir1/jmg_9087.cr2 | 1 - + dir/2012/dir1/jmg_9087.jpg | 1 - + dir/2013/dir2/jmg_0477.cr2 | 1 - + dir/2013/dir2/jmg_0477.jpg | 1 - + dir/2013/dir2/jmg_0478.cr2 | 1 - + dir/2013/dir2/jmg_0478.jpg | 1 - + dir/2013/dir2/jmg_0479.cr2 | 1 - + dir/2013/dir2/jmg_0479.jpg | 1 - + dir/2013/dir2/jmg_0604.cr2 | 1 - + dir/2013/dir2/jmg_0604.jpg | 1 - + dir/2013/dir2/jmg_0605.cr2 | 1 - + dir/2013/dir2/jmg_0605.jpg | 1 - + dir/2013/dir2/jmg_0606.cr2 | 1 - + dir/2013/dir2/jmg_0606.jpg | 1 - + dir/2013/dir2/jmg_0607.cr2 | 1 - + dir/2013/dir2/jmg_0607.jpg | 1 - + dir/2013/dir2/jmg_0608.cr2 | 1 - + dir/2013/dir2/jmg_0608.jpg | 1 - + dir/2013/dir2/jmg_0708.cr2 | 1 - + dir/2013/dir2/jmg_0708.jpg | 1 - + dir/2013/dir2/jmg_0709.cr2 | 1 - + dir/2013/dir2/jmg_0709.jpg | 1 - + dir/2013/dir2/jmg_0710.cr2 | 1 - + dir/2013/dir2/jmg_0710.jpg | 1 - + dir/2013/dir1/jmg_0475.cr2 | 1 - + dir/2013/dir1/jmg_0475.jpg | 1 - + dir/2013/dir1/jmg_0476.cr2 | 1 - + dir/2013/dir1/jmg_0476.jpg | 1 - + dir/2013/dir1/jmg_0718.cr2 | 1 - + dir/2013/dir1/jmg_0718.jpg | 1 - + dir/2013/dir1/jmg_0719.cr2 | 1 - + dir/2013/dir1/jmg_0719.jpg | 1 - + 1821 files changed, 628 insertions(+), 1231 deletions(-) + delete mode 120000 201109/jmg_7250.cr2 + delete mode 120000 201109/jmg_7250.jpg + delete mode 120000 201109/jmg_7251.cr2 + delete mode 120000 201109/jmg_7251.jpg + delete mode 120000 201109/jmg_7253.cr2 + delete mode 120000 201109/jmg_7253.jpg + delete mode 120000 201109/jmg_7256_raw.jpg + delete mode 120000 201109/jmg_7259.cr2 + delete mode 120000 201109/jmg_7259.jpg + delete mode 120000 201109/jmg_7261.cr2 + delete mode 120000 201109/jmg_7261.jpg + delete mode 120000 201109/jmg_7265.cr2 + delete mode 120000 201109/jmg_7265.jpg + delete mode 120000 201109/jmg_7272.jpg + delete mode 120000 201109/jmg_7274.jpg + delete mode 120000 201109/jmg_7275.jpg + delete mode 120000 201109/jmg_7276.jpg + delete mode 120000 201109/jmg_7280.jpg + delete mode 120000 201109/jmg_7284.jpg + delete mode 120000 201109/jmg_7286.jpg + delete mode 120000 201109/jmg_7288.jpg + delete mode 120000 201109/jmg_7289.jpg + delete mode 120000 201109/jmg_7292.jpg + delete mode 120000 201109/jmg_7293.jpg + delete mode 120000 201109/jmg_7295.cr2 + delete mode 120000 201109/jmg_7295.jpg + delete mode 120000 201109/jmg_7296.cr2 + delete mode 120000 201109/jmg_7296.jpg + delete mode 120000 201109/jmg_7299.cr2 + delete mode 120000 201109/jmg_7299.jpg + delete mode 120000 201109/jmg_7300.cr2 + delete mode 120000 201109/jmg_7300.jpg + delete mode 120000 201109/jmg_7304.jpg + delete mode 120000 201109/jmg_7305_raw.jpg + delete mode 120000 201109/jmg_7307_raw.jpg + delete mode 120000 201202/jmg_8528.jpg + delete mode 120000 201202/jmg_8529.jpg + delete mode 120000 201202/jmg_8595.jpg + delete mode 120000 201202/jmg_8596.jpg + delete mode 120000 201202/jmg_8597.jpg + delete mode 120000 201202/jmg_8601.jpg + delete mode 120000 201202/jmg_8602.cr2 + delete mode 120000 201202/jmg_8602.jpg + delete mode 120000 201202/jmg_8603.cr2 + delete mode 120000 201202/jmg_8603.jpg + delete mode 120000 201202/jmg_8604.jpg + delete mode 120000 201202/jmg_8605.jpg + delete mode 120000 201202/jmg_8606.jpg + delete mode 120000 201202/jmg_8607.jpg + delete mode 120000 201202/jmg_8608.jpg + delete mode 120000 201202/jmg_8609.jpg + delete mode 120000 201202/jmg_8610.jpg + delete mode 120000 201202/jmg_8611.jpg + delete mode 120000 201202/jmg_8612.cr2 + delete mode 120000 201202/jmg_8612.jpg + delete mode 120000 201202/jmg_8613.jpg + delete mode 120000 201202/jmg_8614.jpg + delete mode 120000 201202/jmg_8615.jpg + delete mode 120000 201202/jmg_8616_raw.jpg + delete mode 120000 201202/jmg_8617.jpg + delete mode 120000 201202/jmg_8618.jpg + delete mode 120000 201202/jmg_8619.jpg + delete mode 120000 201202/jmg_8620.jpg + delete mode 120000 201202/jmg_8621.jpg + delete mode 120000 201202/jmg_8622.jpg + delete mode 120000 201202/jmg_8624.jpg + delete mode 120000 201202/jmg_8625.cr2 + delete mode 120000 201202/jmg_8625.jpg + delete mode 120000 201202/jmg_8626.jpg + delete mode 120000 201202/jmg_8627.jpg + delete mode 120000 201202/jmg_8628.jpg + delete mode 120000 201202/jmg_8629.jpg + delete mode 120000 201202/jmg_8630.jpg + delete mode 120000 201202/jmg_8631.jpg + delete mode 120000 201202/jmg_8632.jpg + delete mode 120000 201202/jmg_8633.cr2 + delete mode 120000 201202/jmg_8633.jpg + delete mode 120000 201202/jmg_8634.jpg + delete mode 120000 201202/jmg_8637.jpg + delete mode 120000 201202/jmg_8639.jpg + delete mode 120000 201202/jmg_8640.jpg + delete mode 120000 201202/jmg_8641.jpg + delete mode 120000 201202/jmg_8642_raw.jpg + delete mode 120000 201202/jmg_8643.jpg + delete mode 120000 201202/jmg_8644.jpg + delete mode 120000 201202/jmg_8647.jpg + delete mode 120000 201202/jmg_8648.jpg + delete mode 120000 201202/jmg_8651.cr2 + delete mode 120000 201202/jmg_8651.jpg + delete mode 120000 201202/jmg_8652.jpg + delete mode 120000 201202/jmg_8653.jpg + delete mode 120000 201202/jmg_8654.jpg + delete mode 120000 201202/jmg_8655.jpg + delete mode 120000 201202/jmg_8657.jpg + delete mode 120000 201202/jmg_8665.jpg + delete mode 120000 201202/jmg_8670.jpg + delete mode 120000 201202/jmg_8671.jpg + delete mode 120000 201202/jmg_8673.cr2 + delete mode 120000 201202/jmg_8673.jpg + delete mode 120000 201202/jmg_8674.jpg + delete mode 120000 201202/jmg_8675.jpg + delete mode 120000 201202/jmg_8676.jpg + delete mode 120000 201202/jmg_8677.jpg + delete mode 120000 201202/jmg_8678.jpg + delete mode 120000 201202/jmg_8679.jpg + delete mode 120000 201202/jmg_8680.jpg + delete mode 120000 201202/jmg_8681.jpg + delete mode 120000 201203/jmg_8701.cr2 + delete mode 120000 201203/jmg_8702.jpg + delete mode 120000 201203/jmg_8705.jpg + delete mode 120000 201203/jmg_8711.jpg + delete mode 120000 201203/jmg_8717.jpg + delete mode 120000 201203/jmg_8718.jpg + delete mode 120000 201203/jmg_8719.jpg + delete mode 120000 201203/jmg_8721.jpg + delete mode 120000 201203/jmg_8725.jpg + delete mode 120000 201203/jmg_8726.jpg + delete mode 120000 201203/jmg_8731.jpg + delete mode 120000 201203/jmg_8739.jpg + delete mode 120000 201203/jmg_8745.jpg + delete mode 120000 201203/jmg_8747_raw.jpg + delete mode 120000 201203/jmg_8750.cr2 + delete mode 120000 201203/jmg_8750.jpg + delete mode 120000 201204/jmg_8751.jpg + delete mode 120000 201204/jmg_8752.jpg + delete mode 120000 201204/jmg_8755.jpg + delete mode 120000 201204/jmg_8756.jpg + delete mode 120000 201204/jmg_8757.jpg + delete mode 120000 201204/jmg_8759.jpg + delete mode 120000 201204/jmg_8760.jpg + delete mode 120000 201204/jmg_8761.jpg + delete mode 120000 201204/jmg_8762.jpg + delete mode 120000 201204/jmg_8763.cr2 + delete mode 120000 201204/jmg_8763.jpg + delete mode 120000 201204/jmg_8766.jpg + delete mode 120000 201204/jmg_8767.cr2 + delete mode 120000 201204/jmg_8767.jpg + delete mode 120000 201204/jmg_8768.jpg + delete mode 120000 201204/jmg_8769.jpg + delete mode 120000 201204/jmg_8770.jpg + delete mode 120000 201204/jmg_8771.jpg + delete mode 120000 201204/jmg_8772.jpg + delete mode 120000 201204/jmg_8773.jpg + delete mode 120000 201205/jmg_8822.jpg + delete mode 120000 201205/jmg_8823.jpg + delete mode 120000 201205/jmg_8824.jpg + delete mode 120000 201205/jmg_8826.jpg + delete mode 120000 201205/jmg_8831.jpg + delete mode 120000 201205/jmg_8834.jpg + delete mode 120000 201205/jmg_8835.jpg + delete mode 120000 201205/jmg_8835_raw.jpg + delete mode 120000 201205/jmg_8837.jpg + delete mode 120000 201205/jmg_8839.cr2 + delete mode 120000 201205/jmg_8839.jpg + delete mode 120000 201205/jmg_8839_raw.jpg + delete mode 120000 201205/jmg_8840.cr2 + delete mode 120000 201205/jmg_8840.jpg + delete mode 120000 201205/jmg_8840_raw.jpg + delete mode 120000 201205/jmg_8841.jpg + delete mode 120000 201205/jmg_8842.jpg + delete mode 120000 201205/jmg_8844.cr2 + delete mode 120000 201205/jmg_8844.jpg + delete mode 120000 201205/jmg_8844_raw.jpg + delete mode 120000 201205/jmg_8845.jpg + delete mode 120000 201205/jmg_8846.jpg + delete mode 120000 201205/jmg_8847.cr2 + delete mode 120000 201205/jmg_8847.jpg + delete mode 120000 201205/jmg_8847_raw.jpg + delete mode 120000 201205/jmg_8848.jpg + delete mode 120000 201205/jmg_8849.jpg + delete mode 120000 201205/jmg_8851.cr2 + delete mode 120000 201205/jmg_8851.jpg + delete mode 120000 201205/jmg_8851_raw.jpg + delete mode 120000 201205/jmg_8856.cr2 + delete mode 120000 201205/jmg_8856.jpg + delete mode 120000 201205/jmg_8856_raw.jpg + delete mode 120000 201205/jmg_8857.jpg + delete mode 120000 201205/jmg_8858.jpg + delete mode 120000 201205/jmg_8859.jpg + delete mode 120000 201205/jmg_8861.jpg + delete mode 120000 201205/jmg_8862.jpg + delete mode 120000 201205/jmg_8863.jpg + delete mode 120000 201205/jmg_8871.cr2 + delete mode 120000 201205/jmg_8871.jpg + delete mode 120000 201205/jmg_8872.jpg + delete mode 120000 201205/jmg_8873.jpg + delete mode 120000 201205/jmg_8875.jpg + delete mode 120000 201205/jmg_8876.cr2 + delete mode 120000 201205/jmg_8876.jpg + delete mode 120000 201205/jmg_8878.cr2 + delete mode 120000 201205/jmg_8878.jpg + delete mode 120000 201205/jmg_8879.cr2 + delete mode 120000 201205/jmg_8879.jpg + delete mode 120000 201205/jmg_8880.cr2 + delete mode 120000 201205/jmg_8880.jpg + delete mode 120000 201205/jmg_8881.cr2 + delete mode 120000 201205/jmg_8881.jpg + delete mode 120000 201205/jmg_8892.cr2 + delete mode 120000 201205/jmg_8892.jpg + delete mode 120000 201205/jmg_8893.cr2 + delete mode 120000 201205/jmg_8893.jpg + delete mode 120000 201205/jmg_8894.cr2 + delete mode 120000 201205/jmg_8894.jpg + delete mode 120000 201206/jmg_8989.cr2 + delete mode 120000 201206/jmg_8989.jpg + delete mode 120000 201206/jmg_8990.cr2 + delete mode 120000 201206/jmg_8990.jpg + delete mode 120000 201206/jmg_8995.jpg + delete mode 120000 201206/jmg_8996.jpg + delete mode 120000 201206/jmg_8998.jpg + delete mode 120000 201206/jmg_9001.jpg + delete mode 120000 201206/jmg_9003.jpg + delete mode 120000 201206/jmg_9006.jpg + delete mode 120000 201206/jmg_9007.jpg + delete mode 120000 201206/jmg_9011.jpg + delete mode 120000 201206/jmg_9014.jpg + delete mode 120000 201206/jmg_9014_raw.jpg + delete mode 120000 201206/jmg_9015.jpg + delete mode 120000 201206/jmg_9016.cr2 + delete mode 120000 201206/jmg_9016.jpg + delete mode 120000 201206/jmg_9017.cr2 + delete mode 120000 201206/jmg_9017.jpg + delete mode 120000 201206/jmg_9018.cr2 + delete mode 120000 201206/jmg_9018.jpg + delete mode 120000 201206/jmg_9019.cr2 + delete mode 120000 201206/jmg_9019.jpg + delete mode 120000 201206/jmg_9023.cr2 + delete mode 120000 201206/jmg_9023.jpg + delete mode 120000 201206/jmg_9024.cr2 + delete mode 120000 201206/jmg_9024.jpg + delete mode 120000 201206/jmg_9025.cr2 + delete mode 120000 201206/jmg_9025.jpg + delete mode 120000 201206/jmg_9028.jpg + delete mode 120000 201206/jmg_9029.jpg + delete mode 120000 201206/jmg_9030.jpg + delete mode 120000 201206/jmg_9031.jpg + delete mode 120000 201206/jmg_9032_raw.jpg + delete mode 120000 201206/jmg_9033.jpg + delete mode 120000 201206/jmg_9033_raw.jpg + delete mode 120000 201206/jmg_9034.jpg + delete mode 120000 201206/jmg_9035.jpg + delete mode 120000 201206/jmg_9035_raw.jpg + delete mode 120000 201206/jmg_9036.jpg + delete mode 120000 201206/jmg_9039.cr2 + delete mode 120000 201206/jmg_9039.jpg + delete mode 120000 201206/jmg_9040.cr2 + delete mode 120000 201206/jmg_9040.jpg + delete mode 120000 201206/jmg_9043.cr2 + delete mode 120000 201206/jmg_9043.jpg + delete mode 120000 201206/jmg_9047.cr2 + delete mode 120000 201206/jmg_9047.jpg + delete mode 120000 201207/jmg_9048.jpg + delete mode 120000 201207/jmg_9053.jpg + delete mode 120000 201207/jmg_9054.jpg + delete mode 120000 201207/jmg_9069.cr2 + delete mode 120000 201207/jmg_9069.jpg + delete mode 120000 201207/jmg_9070.cr2 + delete mode 120000 201207/jmg_9070.jpg + delete mode 120000 201207/jmg_9072.cr2 + delete mode 120000 201207/jmg_9072.jpg + delete mode 120000 201207/jmg_9076.cr2 + delete mode 120000 201207/jmg_9076.jpg + delete mode 120000 201208/jmg_9077.jpg + delete mode 120000 201208/jmg_9302_raw.jpg + delete mode 120000 201208/jmg_9303.jpg + delete mode 120000 201208/jmg_9304.cr2 + delete mode 120000 201208/jmg_9304.jpg + delete mode 120000 201208/jmg_9305.cr2 + delete mode 120000 201208/jmg_9305.jpg + delete mode 120000 201208/jmg_9306_raw.jpg + delete mode 120000 201208/jmg_9307.cr2 + delete mode 120000 201208/jmg_9307.jpg + delete mode 120000 201208/jmg_9308_raw.jpg + delete mode 120000 201208/jmg_9309_raw.jpg + delete mode 120000 201208/jmg_9310.cr2 + delete mode 120000 201208/jmg_9310.jpg + delete mode 120000 201208/jmg_9310_bw.jpg + delete mode 120000 201208/jmg_9310_raw.jpg + delete mode 120000 201208/jmg_9312.jpg + delete mode 120000 201208/jmg_9313.jpg + delete mode 120000 201208/jmg_9314.jpg + delete mode 120000 201208/jmg_9315.jpg + delete mode 120000 201208/jmg_9319.jpg + delete mode 120000 201208/jmg_9523.jpg + delete mode 120000 201208/jmg_9524.jpg + delete mode 120000 201208/jmg_9525.jpg + delete mode 120000 201208/jmg_9526.jpg + delete mode 120000 201208/jmg_9527.jpg + delete mode 120000 201208/jmg_9527_raw.jpg + delete mode 120000 201208/jmg_9528.jpg + delete mode 120000 201208/jmg_9529.jpg + delete mode 120000 201208/jmg_9530.jpg + delete mode 120000 201208/jmg_9531.jpg + delete mode 120000 201208/jmg_9532.jpg + delete mode 120000 201208/jmg_9533.cr2 + delete mode 120000 201208/jmg_9533.jpg + delete mode 120000 201208/jmg_9534.cr2 + delete mode 120000 201208/jmg_9534.jpg + delete mode 120000 201208/jmg_9535.jpg + delete mode 120000 201208/jmg_9536.jpg + delete mode 120000 201208/jmg_9537.cr2 + delete mode 120000 201208/jmg_9537.jpg + delete mode 120000 201208/jmg_9538.jpg + delete mode 120000 201208/jmg_9539.jpg + delete mode 120000 201208/jmg_9540.jpg + delete mode 120000 201208/jmg_9541.cr2 + delete mode 120000 201208/jmg_9542.jpg + delete mode 120000 201208/jmg_9543.cr2 + delete mode 120000 201208/jmg_9543.jpg + delete mode 120000 201208/jmg_9544.cr2 + delete mode 120000 201208/jmg_9544.jpg + delete mode 120000 201208/jmg_9545.jpg + delete mode 120000 201209/jmg_9547.jpg + delete mode 120000 201209/jmg_9548.jpg + delete mode 120000 201209/jmg_9549.jpg + delete mode 120000 201209/jmg_9550.jpg + delete mode 120000 201209/jmg_9551.jpg + delete mode 120000 201209/jmg_9552.jpg + delete mode 120000 201209/jmg_9553.jpg + delete mode 120000 201209/jmg_9555.jpg + delete mode 120000 201209/jmg_9556.jpg + delete mode 120000 201209/jmg_9558.jpg + delete mode 120000 201209/jmg_9559.cr2 + delete mode 120000 201209/jmg_9559.jpg + delete mode 120000 201209/jmg_9560.cr2 + delete mode 120000 201209/jmg_9560.jpg + delete mode 120000 201209/jmg_9561.jpg + delete mode 120000 201209/jmg_9562.jpg + delete mode 120000 201209/jmg_9568.jpg + delete mode 120000 201210/jmg_0001.jpg + delete mode 120000 201210/jmg_0021.jpg + delete mode 120000 201210/jmg_0022.cr2 + delete mode 120000 201210/jmg_0022.jpg + delete mode 120000 201210/jmg_0025.jpg + delete mode 120000 201210/jmg_0026.jpg + delete mode 120000 201210/jmg_0027.jpg + delete mode 120000 201210/jmg_0028.jpg + delete mode 120000 201210/jmg_0029.jpg + delete mode 120000 201210/jmg_0030.jpg + delete mode 120000 201210/jmg_0032.jpg + delete mode 120000 201210/jmg_0034.jpg + delete mode 120000 201210/jmg_0035.jpg + delete mode 120000 201210/jmg_0036.jpg + delete mode 120000 201210/jmg_0037.jpg + delete mode 120000 201210/jmg_0039.cr2 + delete mode 120000 201210/jmg_0039.jpg + delete mode 120000 201210/jmg_0040.jpg + delete mode 120000 201210/jmg_9572.jpg + delete mode 120000 201210/jmg_9573.jpg + delete mode 120000 201210/jmg_9574.jpg + delete mode 120000 201210/jmg_9575.jpg + delete mode 120000 201210/jmg_9576.jpg + delete mode 120000 201210/jmg_9578.jpg + delete mode 120000 201210/jmg_9580.jpg + delete mode 120000 201210/jmg_9581.jpg + delete mode 120000 201210/jmg_9582.cr2 + delete mode 120000 201210/jmg_9582.jpg + delete mode 120000 201210/jmg_9585.cr2 + delete mode 120000 201210/jmg_9585.jpg + delete mode 120000 201210/jmg_9587.cr2 + delete mode 120000 201210/jmg_9587.jpg + delete mode 120000 201210/jmg_9588.jpg + delete mode 120000 201210/jmg_9589.jpg + delete mode 120000 201210/jmg_9590.jpg + delete mode 120000 201210/jmg_9591.jpg + delete mode 120000 201210/jmg_9594.jpg + delete mode 120000 201210/jmg_9595.jpg + delete mode 120000 201210/jmg_9596.jpg + delete mode 120000 201210/jmg_9597.cr2 + delete mode 120000 201210/jmg_9597.jpg + delete mode 120000 201210/jmg_9598.cr2 + delete mode 120000 201210/jmg_9598.jpg + delete mode 120000 201210/jmg_9599.cr2 + delete mode 120000 201210/jmg_9599.jpg + delete mode 120000 201210/jmg_9600.jpg + delete mode 120000 201210/jmg_9602.jpg + delete mode 120000 201210/jmg_9603.jpg + delete mode 120000 201210/jmg_9604.jpg + delete mode 120000 201210/jmg_9605.cr2 + delete mode 120000 201210/jmg_9605.jpg + delete mode 120000 201210/jmg_9606.jpg + delete mode 120000 201210/jmg_9608.jpg + delete mode 120000 201210/jmg_9609.jpg + delete mode 120000 201210/jmg_9610.jpg + delete mode 120000 201210/jmg_9611.jpg + delete mode 120000 201210/jmg_9612.jpg + delete mode 120000 201210/jmg_9613.jpg + delete mode 120000 201210/jmg_9614.jpg + delete mode 120000 201210/jmg_9616.cr2 + delete mode 120000 201210/jmg_9616.jpg + delete mode 120000 201210/jmg_9617.jpg + delete mode 120000 201210/jmg_9619.jpg + delete mode 120000 201210/jmg_9620.jpg + delete mode 120000 201210/jmg_9621.jpg + delete mode 120000 201210/jmg_9622.jpg + delete mode 120000 201210/jmg_9623.cr2 + delete mode 120000 201210/jmg_9623.jpg + delete mode 120000 201210/jmg_9624.cr2 + delete mode 120000 201210/jmg_9624.jpg + delete mode 120000 201210/jmg_9736_raw.jpg + delete mode 120000 201210/jmg_9738_raw.jpg + delete mode 120000 201210/jmg_9740.cr2 + delete mode 120000 201210/jmg_9740.jpg + delete mode 120000 201210/jmg_9743.jpg + delete mode 120000 201210/jmg_9744.jpg + delete mode 120000 201210/jmg_9745.cr2 + delete mode 120000 201210/jmg_9745.jpg + delete mode 120000 201210/jmg_9746.cr2 + delete mode 120000 201210/jmg_9746.jpg + delete mode 120000 201210/jmg_9748.jpg + delete mode 120000 201210/jmg_9749_raw.jpg + delete mode 120000 201210/jmg_9751.jpg + delete mode 120000 201210/jmg_9752.jpg + delete mode 120000 201210/jmg_9754.jpg + delete mode 120000 201210/jmg_9755.jpg + delete mode 120000 201210/jmg_9756.jpg + delete mode 120000 201210/jmg_9760.cr2 + delete mode 120000 201210/jmg_9760.jpg + delete mode 120000 201210/jmg_9761.cr2 + delete mode 120000 201210/jmg_9761.jpg + delete mode 120000 201210/jmg_9763.jpg + delete mode 120000 201210/jmg_9764.jpg + delete mode 120000 201210/jmg_9766.jpg + delete mode 120000 201210/jmg_9767.cr2 + delete mode 120000 201210/jmg_9767.jpg + delete mode 120000 201210/jmg_9768.jpg + delete mode 120000 201210/jmg_9771.jpg + delete mode 120000 201210/jmg_9772.jpg + delete mode 120000 201210/jmg_9791.jpg + delete mode 120000 201210/jmg_9792.jpg + delete mode 120000 201210/jmg_9793.jpg + delete mode 120000 201210/jmg_9794.jpg + delete mode 120000 201210/jmg_9796.jpg + delete mode 120000 201210/jmg_9797.jpg + delete mode 120000 201210/jmg_9799.jpg + delete mode 120000 201210/jmg_9800.jpg + delete mode 120000 201210/jmg_9801.jpg + delete mode 120000 201210/jmg_9803.jpg + delete mode 120000 201210/jmg_9807.jpg + delete mode 120000 201210/jmg_9808.jpg + delete mode 120000 201210/jmg_9809.jpg + delete mode 120000 201210/jmg_9810.jpg + delete mode 120000 201210/jmg_9811.jpg + delete mode 120000 201210/jmg_9812.jpg + delete mode 120000 201210/jmg_9813.jpg + delete mode 120000 201210/jmg_9815.jpg + delete mode 120000 201210/jmg_9818.jpg + delete mode 120000 201210/jmg_9819.jpg + delete mode 120000 201210/jmg_9820.jpg + delete mode 120000 201210/jmg_9821.jpg + delete mode 120000 201210/jmg_9822.jpg + delete mode 120000 201210/jmg_9823.jpg + delete mode 120000 201210/jmg_9825.jpg + delete mode 120000 201210/jmg_9826.jpg + delete mode 120000 201210/jmg_9827.jpg + delete mode 120000 201210/jmg_9828.jpg + delete mode 120000 201210/jmg_9829.jpg + delete mode 120000 201210/jmg_9830.cr2 + delete mode 120000 201210/jmg_9830.jpg + delete mode 120000 201210/jmg_9832.cr2 + delete mode 120000 201210/jmg_9832.jpg + delete mode 120000 201210/jmg_9834.jpg + delete mode 120000 201210/jmg_9836.jpg + delete mode 120000 201210/jmg_9838.jpg + delete mode 120000 201210/jmg_9839.jpg + delete mode 120000 201210/jmg_9841.jpg + delete mode 120000 201210/jmg_9843.jpg + delete mode 120000 201210/jmg_9845.jpg + delete mode 120000 201210/jmg_9846.jpg + delete mode 120000 201210/jmg_9848.jpg + delete mode 120000 201210/jmg_9849.jpg + delete mode 120000 201210/jmg_9852.jpg + delete mode 120000 201210/jmg_9853.jpg + delete mode 120000 201210/jmg_9854.jpg + delete mode 120000 201210/jmg_9855.jpg + delete mode 120000 201210/jmg_9856.jpg + delete mode 120000 201210/jmg_9857.cr2 + delete mode 120000 201210/jmg_9857.jpg + delete mode 120000 201210/jmg_9858.cr2 + delete mode 120000 201210/jmg_9858.jpg + delete mode 120000 201210/jmg_9859.jpg + delete mode 120000 201210/jmg_9860.jpg + delete mode 120000 201210/jmg_9915.jpg + delete mode 120000 201210/jmg_9917.jpg + delete mode 120000 201210/jmg_9918.jpg + delete mode 120000 201210/jmg_9919.jpg + delete mode 120000 201210/jmg_9922.jpg + delete mode 120000 201210/jmg_9923.jpg + delete mode 120000 201210/jmg_9925.jpg + delete mode 120000 201210/jmg_9926.cr2 + delete mode 120000 201210/jmg_9926.jpg + delete mode 120000 201210/jmg_9928.jpg + delete mode 120000 201210/jmg_9975.cr2 + delete mode 120000 201210/jmg_9975.jpg + delete mode 120000 201210/jmg_9976.cr2 + delete mode 120000 201210/jmg_9976.jpg + delete mode 120000 201210/jmg_9978.jpg + delete mode 120000 201210/jmg_9986.jpg + delete mode 120000 201210/jmg_9987.jpg + delete mode 120000 201210/jmg_9988.jpg + delete mode 120000 201210/jmg_9989.jpg + delete mode 120000 201210/jmg_9991.jpg + delete mode 120000 201210/jmg_9993.jpg + delete mode 120000 201210/jmg_9994.cr2 + delete mode 120000 201210/jmg_9994.jpg + delete mode 120000 201210/jmg_9997.jpg + delete mode 120000 201210/jmg_9998.jpg + delete mode 120000 201210/jmg_9999.jpg + delete mode 120000 201212/jmg_0131.jpg + delete mode 120000 201212/jmg_0134.jpg + delete mode 120000 201212/jmg_0135.jpg + delete mode 120000 201212/jmg_0152.jpg + delete mode 120000 201212/jmg_0155.jpg + delete mode 120000 201212/jmg_0156.jpg + delete mode 120000 201212/jmg_0162.jpg + delete mode 120000 201212/jmg_0163.jpg + delete mode 120000 201212/jmg_0165.jpg + delete mode 120000 201212/jmg_0176.cr2 + delete mode 120000 201212/jmg_0176.jpg + delete mode 120000 201212/jmg_0177.cr2 + delete mode 120000 201212/jmg_0177.jpg + delete mode 120000 201212/jmg_0178.jpg + delete mode 120000 201212/jmg_0179.jpg + delete mode 120000 201212/jmg_0180.jpg + delete mode 120000 201212/jmg_0184.jpg + delete mode 120000 201212/jmg_0185.jpg + delete mode 120000 201212/jmg_0186.jpg + delete mode 120000 201212/jmg_0187.jpg + delete mode 120000 201212/jmg_0306.jpg + delete mode 120000 201212/jmg_0307.jpg + delete mode 120000 201212/jmg_0308.jpg + delete mode 120000 201212/jmg_0310.jpg + delete mode 120000 201212/jmg_0311.jpg + delete mode 120000 201212/jmg_0312.jpg + delete mode 120000 201212/jmg_0313.jpg + delete mode 120000 201212/jmg_0314.jpg + delete mode 120000 201212/jmg_0315.jpg + delete mode 120000 201212/jmg_0316.jpg + delete mode 120000 201212/jmg_0317.jpg + delete mode 120000 201212/jmg_0321.jpg + delete mode 120000 201212/jmg_0326.jpg + delete mode 120000 201212/jmg_0328.jpg + delete mode 120000 201212/jmg_0330.jpg + delete mode 120000 201212/jmg_0333.jpg + delete mode 120000 201212/jmg_0336.jpg + delete mode 120000 201212/jmg_0340.jpg + delete mode 120000 201212/jmg_0343.jpg + delete mode 120000 201212/jmg_0345.jpg + delete mode 120000 201212/jmg_0360.jpg + delete mode 120000 201212/jmg_0362.jpg + delete mode 120000 201212/jmg_0363.jpg + delete mode 120000 201212/jmg_0364.jpg + delete mode 120000 201212/jmg_0366.jpg + delete mode 120000 201212/jmg_0367.jpg + delete mode 120000 201212/jmg_0368.jpg + delete mode 120000 201212/jmg_0369.jpg + delete mode 120000 201212/jmg_0370.jpg + delete mode 120000 201212/jmg_0372.jpg + delete mode 120000 201212/jmg_0382.jpg + delete mode 120000 201212/jmg_0383.jpg + delete mode 120000 201212/jmg_0384.jpg + delete mode 120000 201212/jmg_0385.jpg + delete mode 120000 201212/jmg_0387.jpg + delete mode 120000 201212/jmg_0388.jpg + delete mode 120000 201212/jmg_0389.jpg + delete mode 120000 201212/jmg_0390.jpg + delete mode 120000 201212/jmg_0392.jpg + delete mode 120000 201212/jmg_0396.jpg + delete mode 120000 201212/jmg_0397.jpg + delete mode 120000 201212/jmg_0398.jpg + delete mode 120000 201212/jmg_0399.jpg + delete mode 120000 201212/jmg_0402.jpg + delete mode 120000 201212/jmg_0404.jpg + delete mode 120000 201212/jmg_0405.jpg + delete mode 120000 201212/jmg_0406.jpg + delete mode 120000 201212/jmg_0407.jpg + delete mode 120000 201212/jmg_0408.jpg + delete mode 120000 201212/jmg_0410.jpg + delete mode 120000 201212/jmg_0411.jpg + delete mode 120000 201212/jmg_0412.jpg + delete mode 120000 201212/jmg_0415.jpg + delete mode 120000 201212/jmg_0417.jpg + delete mode 120000 201212/jmg_0418.jpg + delete mode 120000 201302/jmg_0502.cr2 + delete mode 120000 201302/jmg_0502.jpg + delete mode 120000 201302/jmg_0503.jpg + delete mode 120000 201302/jmg_0507.jpg + delete mode 120000 201302/jmg_0510.jpg + delete mode 120000 201302/jmg_0512.jpg + delete mode 120000 201302/jmg_0513.jpg + delete mode 120000 201302/jmg_0514.jpg + delete mode 120000 201302/jmg_0516.jpg + delete mode 120000 201302/jmg_0517.jpg + delete mode 120000 201302/jmg_0518.jpg + delete mode 120000 201302/jmg_0521.jpg + delete mode 120000 201302/jmg_0522.jpg + delete mode 120000 201302/jmg_0523.jpg + delete mode 120000 201302/jmg_0524.jpg + delete mode 120000 201302/jmg_0526.jpg + delete mode 120000 201302/jmg_0527.jpg + delete mode 120000 201302/jmg_0528.jpg + delete mode 120000 201302/jmg_0532.cr2 + delete mode 120000 201302/jmg_0532.jpg + delete mode 120000 201302/jmg_0534.jpg + delete mode 120000 201302/jmg_0535.jpg + delete mode 120000 201302/jmg_0537.jpg + delete mode 120000 201302/jmg_0539.jpg + delete mode 120000 201302/jmg_0541.jpg + delete mode 120000 201302/jmg_0543.jpg + delete mode 120000 201304/bruecke_saeckingen.tif + delete mode 120000 201304/jmg_0685.cr2 + delete mode 120000 201304/jmg_0685.jpg + delete mode 120000 201304/jmg_0687.cr2 + delete mode 120000 201304/jmg_0687.jpg + delete mode 120000 201304/jmg_0699.jpg + delete mode 120000 201304/jmg_0700.jpg + delete mode 120000 201304/jmg_0726.jpg + delete mode 120000 201304/jmg_0727.jpg + delete mode 120000 201304/jmg_0728.jpg + delete mode 120000 201304/jmg_0729.cr2 + delete mode 120000 201304/jmg_0729.jpg + delete mode 120000 201304/jmg_0730.jpg + delete mode 120000 201304/jmg_0731.jpg + delete mode 120000 201304/jmg_0733.cr2 + delete mode 120000 201304/jmg_0733.jpg + delete mode 120000 201304/jmg_0734.cr2 + delete mode 120000 201304/jmg_0734.jpg + delete mode 120000 201304/jmg_0736.cr2 + delete mode 120000 201304/jmg_0736.jpg + delete mode 120000 201304/jmg_0737.cr2 + delete mode 120000 201304/jmg_0737.jpg + delete mode 120000 201304/jmg_0738.jpg + delete mode 120000 201304/jmg_0739.jpg + delete mode 120000 201304/jmg_0740.jpg + delete mode 120000 201304/jmg_0741.jpg + delete mode 120000 201304/jmg_0742.jpg + delete mode 120000 201304/jmg_0744.cr2 + delete mode 120000 201304/jmg_0744.jpg + delete mode 120000 201304/jmg_0749.jpg + delete mode 120000 201304/jmg_0750.jpg + delete mode 120000 201304/jmg_0751.jpg + delete mode 120000 201304/jmg_0752.jpg + delete mode 120000 201304/jmg_0753.jpg + delete mode 120000 201304/jmg_0755.cr2 + delete mode 120000 201304/jmg_0755.jpg + delete mode 120000 201304/jmg_0757.cr2 + delete mode 120000 201304/jmg_0757.jpg + delete mode 120000 201304/jmg_0758.jpg + delete mode 120000 201304/jmg_0759.jpg + delete mode 120000 201304/jmg_0760.cr2 + delete mode 120000 201304/jmg_0760.jpg + delete mode 120000 201304/jmg_0762.cr2 + delete mode 120000 201304/jmg_0762.jpg + delete mode 120000 201304/jmg_0763.jpg + delete mode 120000 201304/jmg_0764.jpg + delete mode 120000 201304/jmg_0765.jpg + delete mode 120000 201304/jmg_0766.jpg + delete mode 120000 201304/jmg_0769.jpg + delete mode 120000 201304/jmg_0770.jpg + delete mode 120000 201304/jmg_0771.jpg + delete mode 120000 201304/jmg_0785.cr2 + delete mode 120000 201304/jmg_0785.jpg + delete mode 120000 201304/jmg_0786.cr2 + delete mode 120000 201304/jmg_0786.jpg + delete mode 120000 201304/jmg_0787.cr2 + delete mode 120000 201304/jmg_0787.jpg + delete mode 120000 201304/jmg_0789.jpg + delete mode 120000 201304/jmg_0790.jpg + delete mode 120000 201304/jmg_0791.jpg + delete mode 120000 201304/jmg_0800.jpg + delete mode 120000 201304/jmg_0801.jpg + delete mode 120000 201304/jmg_0802.jpg + delete mode 120000 201304/jmg_0803.jpg + delete mode 120000 201304/jmg_0809.jpg + delete mode 120000 201304/jmg_0810.jpg + delete mode 120000 201304/jmg_0812.jpg + delete mode 120000 201304/jmg_0813.jpg + delete mode 120000 201304/jmg_0824.jpg + delete mode 120000 201304/jmg_0825.jpg + delete mode 120000 201304/jmg_0827.jpg + delete mode 120000 201304/jmg_0831.jpg + delete mode 120000 201304/jmg_0833.jpg + delete mode 120000 201304/jmg_0834.jpg + delete mode 120000 201304/jmg_0836.jpg + delete mode 120000 201304/jmg_0837.jpg + delete mode 120000 201304/jmg_0845.jpg + delete mode 120000 201304/jmg_0846.jpg + delete mode 120000 201304/jmg_0847.jpg + delete mode 120000 201304/jmg_0848.jpg + delete mode 120000 201304/jmg_0849.jpg + delete mode 120000 201304/jmg_0850.jpg + delete mode 120000 201304/jmg_0851.jpg + delete mode 120000 201304/jmg_0857.jpg + delete mode 120000 201304/jmg_0858.jpg + delete mode 120000 201304/jmg_0860.jpg + delete mode 120000 201304/jmg_0861.jpg + delete mode 120000 201304/jmg_0862.jpg + delete mode 120000 201304/jmg_0863.jpg + delete mode 120000 201304/jmg_0864.jpg + delete mode 120000 201304/jmg_0866.jpg + delete mode 120000 201304/jmg_0867.jpg + delete mode 120000 201304/jmg_0868.cr2 + delete mode 120000 201304/jmg_0868.jpg + delete mode 120000 201304/jmg_0869.cr2 + delete mode 120000 201304/jmg_0869.jpg + delete mode 120000 201304/jmg_0872.cr2 + delete mode 120000 201304/jmg_0872.jpg + delete mode 120000 201304/jmg_0874.cr2 + delete mode 120000 201304/jmg_0874.jpg + delete mode 120000 201304/jmg_0875.jpg + delete mode 120000 201304/jmg_0875_raw.jpg + delete mode 120000 201304/jmg_0876.jpg + delete mode 120000 201304/jmg_0877.jpg + delete mode 120000 201304/jmg_0878.jpg + delete mode 120000 201304/jmg_0880.jpg + delete mode 120000 201304/jmg_0881.jpg + delete mode 120000 201304/jmg_0882.jpg + delete mode 120000 201304/jmg_0884.jpg + delete mode 120000 201304/jmg_0885.jpg + delete mode 120000 201304/jmg_0886.jpg + delete mode 120000 201304/jmg_0888.jpg + delete mode 120000 201304/jmg_0889.jpg + delete mode 120000 201304/jmg_0890.jpg + delete mode 120000 201304/jmg_0891.jpg + delete mode 120000 201304/jmg_0892.jpg + delete mode 120000 201304/jmg_0893.cr2 + delete mode 120000 201304/jmg_0893.jpg + delete mode 120000 201304/jmg_0894.jpg + delete mode 120000 201304/jmg_0896.jpg + delete mode 120000 201304/jmg_0897.jpg + delete mode 120000 201304/jmg_0898.jpg + delete mode 120000 201304/jmg_0899.jpg + delete mode 120000 201304/jmg_0900.jpg + delete mode 120000 201304/jmg_0902.jpg + delete mode 120000 201304/jmg_0905.jpg + delete mode 120000 201304/jmg_0921.jpg + delete mode 120000 201304/jmg_0922.jpg + delete mode 120000 201304/jmg_0932.jpg + delete mode 120000 201304/jmg_0935.jpg + delete mode 120000 201304/jmg_0936.jpg + delete mode 120000 201304/jmg_0937.jpg + delete mode 120000 201304/jmg_0938.jpg + delete mode 120000 201304/jmg_0942.jpg + delete mode 120000 201304/jmg_0944.jpg + delete mode 120000 201304/jmg_0946.jpg + delete mode 120000 201304/jmg_0947.jpg + delete mode 120000 201304/jmg_0948.jpg + delete mode 120000 201304/jmg_0949.jpg + delete mode 120000 201304/jmg_0950.jpg + delete mode 120000 201304/jmg_0951.jpg + delete mode 120000 201304/jmg_0952.jpg + delete mode 120000 201304/jmg_0953.jpg + delete mode 120000 201304/jmg_0954.jpg + delete mode 120000 201304/jmg_0958.jpg + delete mode 120000 201304/jmg_0959.jpg + delete mode 120000 201304/jmg_0960.jpg + delete mode 120000 201304/jmg_0961.jpg + delete mode 120000 201304/jmg_0962.jpg + delete mode 120000 201304/jmg_0963.jpg + delete mode 120000 201304/jmg_0964.jpg + delete mode 120000 201304/jmg_0965.jpg + delete mode 120000 201304/jmg_0966.jpg + delete mode 120000 201304/jmg_0967.jpg + delete mode 120000 201304/jmg_0968.jpg + delete mode 120000 201304/jmg_0969.jpg + delete mode 120000 201304/jmg_0976.cr2 + delete mode 120000 201304/jmg_0976.jpg + delete mode 120000 201304/jmg_0978.jpg + delete mode 120000 201304/jmg_0979.jpg + delete mode 120000 201304/jmg_0980.jpg + delete mode 120000 201304/jmg_0981.cr2 + delete mode 120000 201304/jmg_0981.jpg + delete mode 120000 201304/jmg_0982.jpg + delete mode 120000 201304/jmg_0984.cr2 + delete mode 120000 201304/jmg_0984.jpg + delete mode 120000 201304/jmg_0987.jpg + delete mode 120000 201304/jmg_0988.jpg + delete mode 120000 201304/jmg_0989.jpg + delete mode 120000 201304/jmg_0990.jpg + delete mode 120000 201304/jmg_0991.jpg + delete mode 120000 201304/jmg_0992.jpg + delete mode 120000 201304/jmg_1206.jpg + delete mode 120000 201304/jmg_1207.jpg + delete mode 120000 201304/jmg_1208.jpg + delete mode 120000 201304/jmg_1209.jpg + delete mode 120000 201304/jmg_1210.cr2 + delete mode 120000 201304/jmg_1210.jpg + delete mode 120000 201304/jmg_1211.jpg + delete mode 120000 201304/jmg_1212.jpg + delete mode 120000 201304/jmg_1213.jpg + delete mode 120000 201304/jmg_1214.cr2 + delete mode 120000 201304/jmg_1214.jpg + delete mode 120000 201304/jmg_1215.jpg + delete mode 120000 201304/jmg_1216.cr2 + delete mode 120000 201304/jmg_1216.jpg + delete mode 120000 201304/jmg_1217.cr2 + delete mode 120000 201304/jmg_1217.jpg + delete mode 120000 201304/jmg_1220.cr2 + delete mode 120000 201304/jmg_1220.jpg + delete mode 120000 201304/jmg_1222.cr2 + delete mode 120000 201304/jmg_1222.jpg + delete mode 120000 201304/jmg_1223.jpg + delete mode 120000 201306/jmg_1465.jpg + delete mode 120000 201306/jmg_1466.jpg + delete mode 120000 201306/jmg_1467.jpg + delete mode 120000 201306/jmg_1468.jpg + delete mode 120000 201306/jmg_1469.jpg + delete mode 120000 201306/jmg_1470.jpg + delete mode 120000 201306/jmg_1471.jpg + delete mode 120000 201306/jmg_1472.jpg + delete mode 120000 201306/jmg_1473.jpg + delete mode 120000 201306/jmg_1475.jpg + delete mode 120000 201306/jmg_1476.jpg + delete mode 120000 201306/jmg_1477.jpg + delete mode 120000 201306/jmg_1478.jpg + delete mode 120000 201306/jmg_1479.jpg + delete mode 120000 201306/jmg_1480.jpg + delete mode 120000 201306/jmg_1481.jpg + delete mode 120000 201306/jmg_1482.jpg + delete mode 120000 201306/jmg_1483.jpg + delete mode 120000 201306/jmg_1484.jpg + delete mode 120000 201306/jmg_1485.jpg + delete mode 120000 201306/jmg_1486.jpg + delete mode 120000 201306/jmg_1487.jpg + delete mode 120000 201306/jmg_1488.jpg + delete mode 120000 201306/jmg_1489.jpg + delete mode 120000 201306/jmg_1490.jpg + delete mode 120000 201306/jmg_1491.jpg + delete mode 120000 201306/jmg_1492.jpg + delete mode 120000 201306/jmg_1495.jpg + delete mode 120000 201306/jmg_1496.jpg + delete mode 120000 201306/jmg_1498.jpg + delete mode 120000 201306/jmg_1499.jpg + delete mode 120000 201306/jmg_1500.jpg + delete mode 120000 201306/jmg_1501.jpg + delete mode 120000 201306/jmg_1502.jpg + delete mode 120000 201306/jmg_1504.jpg + delete mode 120000 201306/jmg_1506.jpg + delete mode 120000 201306/jmg_1510.jpg + delete mode 120000 201306/jmg_1512.jpg + delete mode 120000 201306/jmg_1513.jpg + delete mode 120000 201306/jmg_1514.jpg + delete mode 120000 201306/jmg_1515.jpg + delete mode 120000 201306/jmg_1517.jpg + delete mode 120000 201306/jmg_1520.jpg + delete mode 120000 201306/jmg_1521.jpg + delete mode 120000 201306/jmg_1526.jpg + delete mode 120000 201306/jmg_1533.jpg + delete mode 120000 201306/jmg_1540.jpg + delete mode 120000 201306/jmg_1546.jpg + delete mode 120000 201306/jmg_1547.jpg + delete mode 120000 201306/jmg_1549.jpg + delete mode 120000 201306/jmg_1550.jpg + delete mode 120000 201306/jmg_1551.jpg + delete mode 120000 201306/jmg_1552.jpg + delete mode 120000 201306/jmg_1553.jpg + delete mode 120000 201306/jmg_1555.jpg + delete mode 120000 201306/jmg_1556.jpg + delete mode 120000 201306/jmg_1557.jpg + delete mode 120000 201306/jmg_1558.jpg + delete mode 120000 201306/jmg_1559.jpg + delete mode 120000 201306/jmg_1560.jpg + delete mode 120000 201306/jmg_1562.jpg + delete mode 120000 201306/jmg_1566.jpg + delete mode 120000 201306/jmg_1568.jpg + delete mode 120000 201306/jmg_1570.jpg + delete mode 120000 201306/jmg_1571.jpg + delete mode 120000 201306/jmg_1572.jpg + delete mode 120000 201306/jmg_1574.jpg + delete mode 120000 201306/jmg_1575.jpg + delete mode 120000 201306/jmg_1576.jpg + delete mode 120000 201306/jmg_1577.jpg + delete mode 120000 201306/jmg_1578.jpg + delete mode 120000 201306/jmg_1579.jpg + delete mode 120000 201306/jmg_1579_raw.jpg + delete mode 120000 201306/jmg_1581.jpg + delete mode 120000 201306/jmg_1583.jpg + delete mode 120000 201306/jmg_1583_cut.jpg + delete mode 120000 201306/jmg_1583_raw.jpg + delete mode 120000 201306/jmg_1584.jpg + delete mode 120000 201306/jmg_1586.jpg + delete mode 120000 201306/jmg_1587.jpg + delete mode 120000 201306/jmg_1588.jpg + delete mode 120000 201306/jmg_1589.jpg + delete mode 120000 201306/jmg_1591.jpg + delete mode 120000 201306/jmg_1592.jpg + delete mode 120000 201306/jmg_1593.jpg + delete mode 120000 201306/jmg_1593_raw.jpg + delete mode 120000 201306/jmg_1594.jpg + delete mode 120000 201306/jmg_1594_raw.jpg + delete mode 120000 201306/jmg_1595.jpg + delete mode 120000 201306/jmg_1596.jpg + delete mode 120000 201306/jmg_1597.jpg + delete mode 120000 201306/jmg_1599.jpg + delete mode 120000 201306/jmg_1626.jpg + delete mode 120000 201306/jmg_1628.jpg + delete mode 120000 201306/jmg_1629.jpg + delete mode 120000 201306/jmg_1630.jpg + delete mode 120000 201306/jmg_1631.jpg + delete mode 120000 201306/jmg_1633.jpg + delete mode 120000 201306/jmg_1635.jpg + delete mode 120000 201306/jmg_1636.jpg + delete mode 120000 201306/jmg_1637.jpg + delete mode 120000 201306/jmg_1638.jpg + delete mode 120000 201306/jmg_1640.jpg + delete mode 120000 201306/jmg_1642.jpg + delete mode 120000 201306/jmg_1643.jpg + delete mode 120000 201306/jmg_1644.jpg + delete mode 120000 201306/jmg_1647.jpg + delete mode 120000 201306/jmg_1649.jpg + delete mode 120000 201306/jmg_1650.jpg + delete mode 120000 201306/jmg_1651.jpg + delete mode 120000 201306/jmg_1652.jpg + delete mode 120000 201306/jmg_1653.jpg + delete mode 120000 201306/jmg_1655.jpg + delete mode 120000 201306/jmg_1656.jpg + delete mode 120000 201306/jmg_1660.jpg + delete mode 120000 201306/jmg_1667.jpg + delete mode 120000 201306/jmg_1682.jpg + delete mode 120000 201306/jmg_1688.jpg + delete mode 120000 201306/jmg_1689.jpg + delete mode 120000 201306/jmg_1701.jpg + delete mode 120000 201306/jmg_1702.jpg + delete mode 120000 201306/jmg_1703.jpg + delete mode 120000 201306/jmg_1710.jpg + delete mode 120000 201306/jmg_1710_raw.jpg + delete mode 120000 201306/jmg_1715.jpg + delete mode 120000 201306/jmg_1716.jpg + delete mode 120000 201306/jmg_1719.jpg + delete mode 120000 201306/jmg_1722.jpg + delete mode 120000 201306/jmg_1723.jpg + delete mode 120000 201306/jmg_1729.cr2 + delete mode 120000 201308/jmg_2038.jpg + delete mode 120000 201308/jmg_2039.jpg + delete mode 120000 201308/jmg_2040.jpg + delete mode 120000 201308/jmg_2041.jpg + delete mode 120000 201308/jmg_2042.jpg + delete mode 120000 201308/jmg_2043.jpg + delete mode 120000 201308/jmg_2045.jpg + delete mode 120000 201308/jmg_2047.jpg + delete mode 120000 201308/jmg_2048.jpg + delete mode 120000 201308/jmg_2049.jpg + delete mode 120000 201308/jmg_2050.jpg + delete mode 120000 201308/jmg_2051.jpg + delete mode 120000 201308/jmg_2052.jpg + delete mode 120000 201308/jmg_2053.jpg + delete mode 120000 201308/jmg_2054.jpg + delete mode 120000 201308/jmg_2055.jpg + delete mode 120000 201308/jmg_2056.jpg + delete mode 120000 201308/jmg_2057.jpg + delete mode 120000 201308/jmg_2058.jpg + delete mode 120000 201308/jmg_2059.jpg + delete mode 120000 201308/jmg_2060.jpg + delete mode 120000 201308/jmg_2061.jpg + delete mode 120000 201308/jmg_2062.jpg + delete mode 120000 201308/jmg_2089.cr2 + delete mode 120000 201308/jmg_2089.jpg + delete mode 120000 201308/jmg_2089_raw.jpg + delete mode 120000 201308/jmg_2090.jpg + delete mode 120000 201308/jmg_2091.jpg + delete mode 120000 201308/jmg_2092.jpg + delete mode 120000 201308/jmg_2093.jpg + delete mode 120000 201308/jmg_2096.jpg + delete mode 120000 201308/jmg_2097.jpg + delete mode 120000 201308/jmg_2098.jpg + delete mode 120000 201308/jmg_2099.cr2 + delete mode 120000 201308/jmg_2099.jpg + delete mode 120000 201308/jmg_2099_raw.jpg + delete mode 120000 201308/jmg_2100.cr2 + delete mode 120000 201308/jmg_2100.jpg + delete mode 120000 201308/jmg_2100_raw.jpg + delete mode 120000 201308/jmg_2102.jpg + delete mode 120000 201308/jmg_2103.jpg + delete mode 120000 201308/jmg_2104.jpg + delete mode 120000 201308/jmg_2105.jpg + delete mode 120000 201308/jmg_2106.jpg + delete mode 120000 201308/jmg_2107.jpg + delete mode 120000 201308/jmg_2108.jpg + delete mode 120000 201308/jmg_2109.jpg + delete mode 120000 201308/jmg_2110.jpg + delete mode 120000 201308/jmg_2111.jpg + delete mode 120000 201308/jmg_2112.jpg + delete mode 120000 201308/jmg_2113.jpg + delete mode 120000 201308/jmg_2114.jpg + delete mode 120000 201308/jmg_2115.jpg + delete mode 120000 201308/jmg_2117.jpg + delete mode 120000 201308/jmg_2118.jpg + delete mode 120000 201308/jmg_2119.jpg + delete mode 120000 201308/jmg_2120.jpg + delete mode 120000 201308/jmg_2122.jpg + delete mode 120000 201308/jmg_2125.jpg + delete mode 120000 201308/jmg_2127.jpg + delete mode 120000 201308/jmg_2129.jpg + delete mode 120000 201308/jmg_2130.jpg + delete mode 120000 201308/jmg_2132.jpg + delete mode 120000 201308/jmg_2134.jpg + delete mode 120000 201308/jmg_2135.jpg + delete mode 120000 201308/jmg_2136.jpg + delete mode 120000 201308/jmg_2137.jpg + delete mode 120000 201308/jmg_2138.jpg + delete mode 120000 201308/jmg_2148.jpg + delete mode 120000 201308/jmg_2150.jpg + delete mode 120000 201308/jmg_2151.jpg + delete mode 120000 201308/jmg_2156.jpg + delete mode 120000 201308/jmg_2158.cr2 + delete mode 120000 201308/jmg_2158.jpg + delete mode 120000 201308/jmg_2159.jpg + delete mode 120000 201308/jmg_2160.jpg + delete mode 120000 201308/jmg_2161.jpg + delete mode 120000 201308/jmg_2162.jpg + delete mode 120000 201308/jmg_2165.jpg + delete mode 120000 201308/jmg_2166.jpg + delete mode 120000 201308/jmg_2168.jpg + delete mode 120000 201308/jmg_2169.jpg + delete mode 120000 201308/jmg_2171.jpg + delete mode 120000 201308/jmg_2173.jpg + delete mode 120000 201308/jmg_2174.jpg + delete mode 120000 201308/jmg_2175.jpg + delete mode 120000 201308/jmg_2177.jpg + delete mode 120000 201308/jmg_2178.jpg + delete mode 120000 201308/jmg_2180.jpg + delete mode 120000 201308/jmg_2181.jpg + delete mode 120000 201308/jmg_2182.jpg + delete mode 120000 201308/jmg_2183.jpg + delete mode 120000 201308/jmg_2184.jpg + delete mode 120000 201308/jmg_2187.jpg + delete mode 120000 201308/jmg_2188.jpg + delete mode 120000 201308/jmg_2189.jpg + delete mode 120000 201308/jmg_2191.cr2 + delete mode 120000 201308/jmg_2191.jpg + delete mode 120000 201308/jmg_2193.cr2 + delete mode 120000 201308/jmg_2193.jpg + delete mode 120000 201308/jmg_2194.cr2 + delete mode 120000 201308/jmg_2194.jpg + delete mode 120000 201308/jmg_2197.cr2 + delete mode 120000 201308/jmg_2197.jpg + delete mode 120000 201308/jmg_2200.cr2 + delete mode 120000 201308/jmg_2200.jpg + delete mode 120000 201308/jmg_2201.cr2 + delete mode 120000 201308/jmg_2201.jpg + delete mode 120000 201308/jmg_2202.cr2 + delete mode 120000 201308/jmg_2202.jpg + delete mode 120000 201308/jmg_2209.jpg + delete mode 120000 201308/jmg_2210.jpg + delete mode 120000 201308/jmg_2215.jpg + delete mode 120000 201308/jmg_2216.jpg + delete mode 120000 201308/jmg_2217.cr2 + delete mode 120000 201308/jmg_2217.jpg + delete mode 120000 201308/jmg_2219.cr2 + delete mode 120000 201308/jmg_2219.jpg + delete mode 120000 201308/jmg_2223.jpg + delete mode 120000 201308/jmg_2224.jpg + delete mode 120000 201308/jmg_2225.cr2 + delete mode 120000 201308/jmg_2225.jpg + delete mode 120000 201308/jmg_2227.jpg + delete mode 120000 201308/jmg_2228.jpg + delete mode 120000 201308/jmg_2235.jpg + delete mode 120000 201308/jmg_2237.jpg + delete mode 120000 201308/jmg_2238.jpg + delete mode 120000 201308/jmg_2239.cr2 + delete mode 120000 201308/jmg_2239.jpg + delete mode 120000 201308/jmg_2239_raw.jpg + delete mode 120000 201308/jmg_2240.jpg + delete mode 120000 201308/jmg_2243.jpg + delete mode 120000 201308/jmg_2244.jpg + delete mode 120000 201308/jmg_2245.jpg + delete mode 120000 201308/jmg_2247.cr2 + delete mode 120000 201308/jmg_2247.jpg + delete mode 120000 201308/jmg_2249.jpg + delete mode 120000 201308/jmg_2250.cr2 + delete mode 120000 201308/jmg_2250.jpg + delete mode 120000 201308/jmg_2252.jpg + delete mode 120000 201308/jmg_2253.jpg + delete mode 120000 201308/jmg_2254.jpg + create mode 120000 incoming/5d/201203/jmg_8701.cr2 + create mode 120000 incoming/5d/201203/jmg_8702.jpg + create mode 120000 incoming/5d/201203/jmg_8705.jpg + create mode 120000 incoming/5d/201203/jmg_8711.jpg + create mode 120000 incoming/5d/201203/jmg_8717.jpg + create mode 120000 incoming/5d/201203/jmg_8718.jpg + create mode 120000 incoming/5d/201203/jmg_8719.jpg + create mode 120000 incoming/5d/201203/jmg_8721.jpg + create mode 120000 incoming/5d/201203/jmg_8725.jpg + create mode 120000 incoming/5d/201203/jmg_8726.jpg + create mode 120000 incoming/5d/201203/jmg_8731.jpg + create mode 120000 incoming/5d/201203/jmg_8745.jpg + create mode 120000 incoming/5d/201203/jmg_8747_raw.jpg + create mode 120000 incoming/5d/201203/jmg_8750.cr2 + create mode 120000 incoming/5d/201203/jmg_8750.jpg + create mode 120000 incoming/5d/201207/jmg_9048.jpg + create mode 120000 incoming/5d/201207/jmg_9053.jpg + create mode 120000 incoming/5d/201207/jmg_9054.jpg + create mode 120000 incoming/5d/201207/jmg_9069.cr2 + create mode 120000 incoming/5d/201207/jmg_9069.jpg + create mode 120000 incoming/5d/201207/jmg_9070.cr2 + create mode 120000 incoming/5d/201207/jmg_9070.jpg + create mode 120000 incoming/5d/201207/jmg_9072.cr2 + create mode 120000 incoming/5d/201207/jmg_9072.jpg + create mode 120000 incoming/5d/201207/jmg_9076.cr2 + create mode 120000 incoming/5d/201207/jmg_9076.jpg + create mode 120000 incoming/5d/201302/jmg_0502.cr2 + create mode 120000 incoming/5d/201302/jmg_0502.jpg + create mode 120000 incoming/5d/201302/jmg_0503.jpg + create mode 120000 incoming/5d/201302/jmg_0507.jpg + create mode 120000 incoming/5d/201302/jmg_0510.jpg + create mode 120000 incoming/5d/201302/jmg_0512.jpg + create mode 120000 incoming/5d/201302/jmg_0513.jpg + create mode 120000 incoming/5d/201302/jmg_0514.jpg + create mode 120000 incoming/5d/201302/jmg_0516.jpg + create mode 120000 incoming/5d/201302/jmg_0517.jpg + create mode 120000 incoming/5d/201302/jmg_0518.jpg + create mode 120000 incoming/5d/201302/jmg_0521.jpg + create mode 120000 incoming/5d/201302/jmg_0522.jpg + create mode 120000 incoming/5d/201302/jmg_0523.jpg + create mode 120000 incoming/5d/201302/jmg_0524.jpg + create mode 120000 incoming/5d/201302/jmg_0526.jpg + create mode 120000 incoming/5d/201302/jmg_0527.jpg + create mode 120000 incoming/5d/201302/jmg_0528.jpg + create mode 120000 incoming/5d/201302/jmg_0532.cr2 + create mode 120000 incoming/5d/201302/jmg_0532.jpg + create mode 120000 incoming/5d/201302/jmg_0534.jpg + create mode 120000 incoming/5d/201302/jmg_0535.jpg + create mode 120000 incoming/5d/201302/jmg_0537.jpg + create mode 120000 incoming/5d/201302/jmg_0539.jpg + create mode 120000 incoming/5d/201302/jmg_0541.jpg + create mode 120000 incoming/5d/201302/jmg_0543.jpg + create mode 120000 incoming/5d/jmg_0021.jpg + create mode 120000 incoming/5d/jmg_0025.jpg + create mode 120000 incoming/5d/jmg_0026.jpg + create mode 120000 incoming/5d/jmg_0027.jpg + create mode 120000 incoming/5d/jmg_0034.jpg + create mode 120000 incoming/5d/jmg_0035.jpg + create mode 120000 incoming/5d/jmg_0036.jpg + create mode 120000 incoming/5d/jmg_0130.jpg + create mode 120000 incoming/5d/jmg_0131.jpg + create mode 120000 incoming/5d/jmg_0133.jpg + create mode 120000 incoming/5d/jmg_0155.jpg + create mode 120000 incoming/5d/jmg_0156.jpg + create mode 120000 incoming/5d/jmg_0158.cr2 + create mode 120000 incoming/5d/jmg_0165.cr2 + create mode 120000 incoming/5d/jmg_0166.cr2 + create mode 120000 incoming/5d/jmg_0178.cr2 + create mode 120000 incoming/5d/jmg_0179.jpg + create mode 120000 incoming/5d/jmg_0180.cr2 + create mode 120000 incoming/5d/jmg_0184.jpg + create mode 120000 incoming/5d/jmg_0185.cr2 + create mode 120000 incoming/5d/jmg_0187.cr2 + create mode 120000 incoming/5d/jmg_0310.jpg + create mode 120000 incoming/5d/jmg_0312.jpg + create mode 120000 incoming/5d/jmg_0315.jpg + create mode 120000 incoming/5d/jmg_0340.jpg + create mode 120000 incoming/5d/jmg_0357.jpg + create mode 120000 incoming/5d/jmg_0364.jpg + create mode 120000 incoming/5d/jmg_0365.jpg + create mode 120000 incoming/5d/jmg_0368.jpg + create mode 120000 incoming/5d/jmg_0374.jpg + create mode 120000 incoming/5d/jmg_0375.jpg + create mode 120000 incoming/5d/jmg_0386.jpg + create mode 120000 incoming/5d/jmg_0399.jpg + create mode 120000 incoming/5d/jmg_0411.jpg + create mode 120000 incoming/5d/jmg_0418.jpg + create mode 120000 incoming/5d/jmg_0476.cr2 + create mode 120000 incoming/5d/jmg_0476.jpg + create mode 120000 incoming/5d/jmg_0503.jpg + create mode 120000 incoming/5d/jmg_0507.cr2 + create mode 120000 incoming/5d/jmg_0513.cr2 + create mode 120000 incoming/5d/jmg_0513.jpg + create mode 120000 incoming/5d/jmg_0516.cr2 + create mode 120000 incoming/5d/jmg_0517.cr2 + create mode 120000 incoming/5d/jmg_0518.jpg + create mode 120000 incoming/5d/jmg_0522.cr2 + create mode 120000 incoming/5d/jmg_0524.cr2 + create mode 120000 incoming/5d/jmg_0524.jpg + create mode 120000 incoming/5d/jmg_0530.jpg + create mode 120000 incoming/5d/jmg_0541.cr2 + create mode 120000 incoming/5d/jmg_0550.jpg + create mode 120000 incoming/5d/jmg_0554.jpg + create mode 120000 incoming/5d/jmg_0555.jpg + create mode 120000 incoming/5d/jmg_0558.jpg + create mode 120000 incoming/5d/jmg_0563.jpg + create mode 120000 incoming/5d/jmg_0573.jpg + create mode 120000 incoming/5d/jmg_0575.cr2 + create mode 120000 incoming/5d/jmg_0578.cr2 + create mode 120000 incoming/5d/jmg_0579.cr2 + create mode 120000 incoming/5d/jmg_0582.jpg + create mode 120000 incoming/5d/jmg_0593.cr2 + create mode 120000 incoming/5d/jmg_0594.cr2 + create mode 120000 incoming/5d/jmg_0594.jpg + create mode 120000 incoming/5d/jmg_0595.cr2 + create mode 120000 incoming/5d/jmg_0600.jpg + create mode 120000 incoming/5d/jmg_0606.cr2 + create mode 120000 incoming/5d/jmg_0607.jpg + create mode 120000 incoming/5d/jmg_0610.cr2 + create mode 120000 incoming/5d/jmg_0610.jpg + create mode 120000 incoming/5d/jmg_0612.jpg + create mode 120000 incoming/5d/jmg_0613.cr2 + create mode 120000 incoming/5d/jmg_0614.jpg + create mode 120000 incoming/5d/jmg_0619.cr2 + create mode 120000 incoming/5d/jmg_0623.jpg + create mode 120000 incoming/5d/jmg_0628.cr2 + create mode 120000 incoming/5d/jmg_0628.jpg + create mode 120000 incoming/5d/jmg_0639.jpg + create mode 120000 incoming/5d/jmg_0645.cr2 + create mode 120000 incoming/5d/jmg_0646.jpg + create mode 120000 incoming/5d/jmg_0647.cr2 + create mode 120000 incoming/5d/jmg_0648.jpg + create mode 120000 incoming/5d/jmg_0649.jpg + create mode 120000 incoming/5d/jmg_0655.jpg + create mode 120000 incoming/5d/jmg_0667.jpg + create mode 120000 incoming/5d/jmg_0670.jpg + create mode 120000 incoming/5d/jmg_0673.jpg + create mode 120000 incoming/5d/jmg_0679.jpg + create mode 120000 incoming/5d/jmg_0685.jpg + create mode 120000 incoming/5d/jmg_0699.cr2 + create mode 120000 incoming/5d/jmg_0700.cr2 + create mode 120000 incoming/5d/jmg_0701.cr2 + create mode 120000 incoming/5d/jmg_0708.jpg + create mode 120000 incoming/5d/jmg_0718.jpg + create mode 120000 incoming/5d/jmg_0726.cr2 + create mode 120000 incoming/5d/jmg_0728.jpg + create mode 120000 incoming/5d/jmg_0730.jpg + create mode 120000 incoming/5d/jmg_0734.jpg + create mode 120000 incoming/5d/jmg_0740.jpg + create mode 120000 incoming/5d/jmg_0743.cr2 + create mode 120000 incoming/5d/jmg_0744.cr2 + create mode 120000 incoming/5d/jmg_0745.cr2 + create mode 120000 incoming/5d/jmg_0747.jpg + create mode 120000 incoming/5d/jmg_0750.cr2 + create mode 120000 incoming/5d/jmg_0755.cr2 + create mode 120000 incoming/5d/jmg_0759.cr2 + create mode 120000 incoming/5d/jmg_0760.cr2 + create mode 120000 incoming/5d/jmg_0761.jpg + create mode 120000 incoming/5d/jmg_0765.jpg + create mode 120000 incoming/5d/jmg_0768.jpg + create mode 120000 incoming/5d/jmg_0771.jpg + create mode 120000 incoming/5d/jmg_0778.jpg + create mode 120000 incoming/5d/jmg_0780.jpg + create mode 120000 incoming/5d/jmg_0782.cr2 + create mode 120000 incoming/5d/jmg_0786.cr2 + create mode 120000 incoming/5d/jmg_0787.cr2 + create mode 120000 incoming/5d/jmg_0788.cr2 + create mode 120000 incoming/5d/jmg_0794.jpg + create mode 120000 incoming/5d/jmg_0796.jpg + create mode 120000 incoming/5d/jmg_0801.cr2 + create mode 120000 incoming/5d/jmg_0803.cr2 + create mode 120000 incoming/5d/jmg_0804.cr2 + create mode 120000 incoming/5d/jmg_0812.jpg + create mode 120000 incoming/5d/jmg_0819.jpg + create mode 120000 incoming/5d/jmg_0827.jpg + create mode 120000 incoming/5d/jmg_0830.jpg + create mode 120000 incoming/5d/jmg_0842.jpg + create mode 120000 incoming/5d/jmg_0846.jpg + create mode 120000 incoming/5d/jmg_0857.cr2 + create mode 120000 incoming/5d/jmg_0863.jpg + create mode 120000 incoming/5d/jmg_0866.cr2 + create mode 120000 incoming/5d/jmg_0868.cr2 + create mode 120000 incoming/5d/jmg_0868.jpg + create mode 120000 incoming/5d/jmg_0870.jpg + create mode 120000 incoming/5d/jmg_0877.jpg + create mode 120000 incoming/5d/jmg_0882.cr2 + create mode 120000 incoming/5d/jmg_0883.jpg + create mode 120000 incoming/5d/jmg_0888.jpg + create mode 120000 incoming/5d/jmg_0891.jpg + create mode 120000 incoming/5d/jmg_0894.cr2 + create mode 120000 incoming/5d/jmg_0896.cr2 + create mode 120000 incoming/5d/jmg_0897.cr2 + create mode 120000 incoming/5d/jmg_0898.jpg + create mode 120000 incoming/5d/jmg_0899.cr2 + create mode 120000 incoming/5d/jmg_0900.jpg + create mode 120000 incoming/5d/jmg_0905.jpg + create mode 120000 incoming/5d/jmg_0908.jpg + create mode 120000 incoming/5d/jmg_0914.jpg + create mode 120000 incoming/5d/jmg_0915.jpg + create mode 120000 incoming/5d/jmg_0916.jpg + create mode 120000 incoming/5d/jmg_0923.jpg + create mode 120000 incoming/5d/jmg_0924.jpg + create mode 120000 incoming/5d/jmg_0926.jpg + create mode 120000 incoming/5d/jmg_0928.jpg + create mode 120000 incoming/5d/jmg_0929.jpg + create mode 120000 incoming/5d/jmg_0936.jpg + create mode 120000 incoming/5d/jmg_0942.jpg + create mode 120000 incoming/5d/jmg_0944.jpg + create mode 120000 incoming/5d/jmg_0948.jpg + create mode 120000 incoming/5d/jmg_0960.jpg + create mode 120000 incoming/5d/jmg_0966.jpg + create mode 120000 incoming/5d/jmg_0970.cr2 + create mode 120000 incoming/5d/jmg_0970.jpg + create mode 120000 incoming/5d/jmg_0972.jpg + create mode 120000 incoming/5d/jmg_0976.jpg + create mode 120000 incoming/5d/jmg_0983.cr2 + create mode 120000 incoming/5d/jmg_0985.cr2 + create mode 120000 incoming/5d/jmg_0985.jpg + create mode 120000 incoming/5d/jmg_0994.jpg + create mode 120000 incoming/5d/jmg_1209.cr2 + create mode 120000 incoming/5d/jmg_1209.jpg + create mode 120000 incoming/5d/jmg_1211.cr2 + create mode 120000 incoming/5d/jmg_1211.jpg + create mode 120000 incoming/5d/jmg_1217.cr2 + create mode 120000 incoming/5d/jmg_1467.cr2 + create mode 120000 incoming/5d/jmg_1469.jpg + create mode 120000 incoming/5d/jmg_1470.cr2 + create mode 120000 incoming/5d/jmg_1471.cr2 + create mode 120000 incoming/5d/jmg_1472.cr2 + create mode 120000 incoming/5d/jmg_1477.cr2 + create mode 120000 incoming/5d/jmg_1477.jpg + create mode 120000 incoming/5d/jmg_1481.cr2 + create mode 120000 incoming/5d/jmg_1483.cr2 + create mode 120000 incoming/5d/jmg_1485.jpg + create mode 120000 incoming/5d/jmg_1488.jpg + create mode 120000 incoming/5d/jmg_1491.jpg + create mode 120000 incoming/5d/jmg_1496.cr2 + create mode 120000 incoming/5d/jmg_1502.jpg + create mode 120000 incoming/5d/jmg_1503.cr2 + create mode 120000 incoming/5d/jmg_1504.jpg + create mode 120000 incoming/5d/jmg_1507.jpg + create mode 120000 incoming/5d/jmg_1515.jpg + create mode 120000 incoming/5d/jmg_1520.jpg + create mode 120000 incoming/5d/jmg_1523.jpg + create mode 120000 incoming/5d/jmg_1525.jpg + create mode 120000 incoming/5d/jmg_1539.jpg + create mode 120000 incoming/5d/jmg_1542.jpg + create mode 120000 incoming/5d/jmg_1546.jpg + create mode 120000 incoming/5d/jmg_1547.cr2 + create mode 120000 incoming/5d/jmg_1549.jpg + create mode 120000 incoming/5d/jmg_1552.jpg + create mode 120000 incoming/5d/jmg_1554.cr2 + create mode 120000 incoming/5d/jmg_1555.cr2 + create mode 120000 incoming/5d/jmg_1556.cr2 + create mode 120000 incoming/5d/jmg_1559.cr2 + create mode 120000 incoming/5d/jmg_1560.cr2 + create mode 120000 incoming/5d/jmg_1561.cr2 + create mode 120000 incoming/5d/jmg_1562.cr2 + create mode 120000 incoming/5d/jmg_1565.cr2 + create mode 120000 incoming/5d/jmg_1567.cr2 + create mode 120000 incoming/5d/jmg_1572.cr2 + create mode 120000 incoming/5d/jmg_1577.cr2 + create mode 120000 incoming/5d/jmg_1578.jpg + create mode 120000 incoming/5d/jmg_1583_cut.jpg + create mode 120000 incoming/5d/jmg_1583_raw.jpg + create mode 120000 incoming/5d/jmg_1592.cr2 + create mode 120000 incoming/5d/jmg_1593.jpg + create mode 120000 incoming/5d/jmg_1626.cr2 + create mode 120000 incoming/5d/jmg_1627.jpg + create mode 120000 incoming/5d/jmg_1628.cr2 + create mode 120000 incoming/5d/jmg_1629.jpg + create mode 120000 incoming/5d/jmg_1630.cr2 + create mode 120000 incoming/5d/jmg_1631.cr2 + create mode 120000 incoming/5d/jmg_1633.cr2 + create mode 120000 incoming/5d/jmg_1638.jpg + create mode 120000 incoming/5d/jmg_1639.cr2 + create mode 120000 incoming/5d/jmg_1646.cr2 + create mode 120000 incoming/5d/jmg_1646.jpg + create mode 120000 incoming/5d/jmg_1650.jpg + create mode 120000 incoming/5d/jmg_1651.cr2 + create mode 120000 incoming/5d/jmg_1654.cr2 + create mode 120000 incoming/5d/jmg_1656.jpg + create mode 120000 incoming/5d/jmg_1677.jpg + create mode 120000 incoming/5d/jmg_1689.jpg + create mode 120000 incoming/5d/jmg_1701.jpg + create mode 120000 incoming/5d/jmg_1703.jpg + create mode 120000 incoming/5d/jmg_1723.jpg + create mode 120000 incoming/5d/jmg_2039.jpg + create mode 120000 incoming/5d/jmg_2041.jpg + create mode 120000 incoming/5d/jmg_2048.cr2 + create mode 120000 incoming/5d/jmg_2052.jpg + create mode 120000 incoming/5d/jmg_2061.jpg + delete mode 120000 incoming/5d/jmg_2064_raw.jpg + delete mode 120000 incoming/5d/jmg_2065_mo.jpg + delete mode 120000 incoming/5d/jmg_2065_raw.jpg + delete mode 120000 incoming/5d/jmg_2066_mo.jpg + delete mode 120000 incoming/5d/jmg_2066_raw.jpg + create mode 120000 incoming/5d/jmg_2090.jpg + create mode 120000 incoming/5d/jmg_2093.jpg + create mode 120000 incoming/5d/jmg_2100.cr2 + create mode 120000 incoming/5d/jmg_2103.jpg + create mode 120000 incoming/5d/jmg_2107.jpg + create mode 120000 incoming/5d/jmg_2108.jpg + create mode 120000 incoming/5d/jmg_2112.jpg + create mode 120000 incoming/5d/jmg_2118.jpg + create mode 120000 incoming/5d/jmg_2119.jpg + create mode 120000 incoming/5d/jmg_2122.jpg + create mode 120000 incoming/5d/jmg_2125.jpg + create mode 120000 incoming/5d/jmg_2137.jpg + create mode 120000 incoming/5d/jmg_2149.jpg + create mode 120000 incoming/5d/jmg_2150.jpg + create mode 120000 incoming/5d/jmg_2158.cr2 + create mode 120000 incoming/5d/jmg_2160.jpg + create mode 120000 incoming/5d/jmg_2165.jpg + create mode 120000 incoming/5d/jmg_2188.jpg + create mode 120000 incoming/5d/jmg_2189.jpg + create mode 120000 incoming/5d/jmg_2193.jpg + create mode 120000 incoming/5d/jmg_2194.cr2 + create mode 120000 incoming/5d/jmg_2200.jpg + create mode 120000 incoming/5d/jmg_2201.cr2 + create mode 120000 incoming/5d/jmg_2201.jpg + create mode 120000 incoming/5d/jmg_2210.jpg + create mode 120000 incoming/5d/jmg_2215.cr2 + create mode 120000 incoming/5d/jmg_2216.cr2 + create mode 120000 incoming/5d/jmg_2216.jpg + create mode 120000 incoming/5d/jmg_2224.jpg + create mode 120000 incoming/5d/jmg_2235.jpg + create mode 120000 incoming/5d/jmg_2238.jpg + create mode 120000 incoming/5d/jmg_2239.cr2 + create mode 120000 incoming/5d/jmg_2239.jpg + create mode 120000 incoming/5d/jmg_2240.jpg + create mode 120000 incoming/5d/jmg_2244.jpg + create mode 120000 incoming/5d/jmg_2247.jpg + create mode 120000 incoming/5d/jmg_7250.cr2 + create mode 120000 incoming/5d/jmg_7250.jpg + create mode 120000 incoming/5d/jmg_7256.jpg + create mode 120000 incoming/5d/jmg_7257.cr2 + create mode 120000 incoming/5d/jmg_7259.cr2 + create mode 120000 incoming/5d/jmg_7263.jpg + create mode 120000 incoming/5d/jmg_7265.cr2 + create mode 120000 incoming/5d/jmg_7269.cr2 + create mode 120000 incoming/5d/jmg_7270.cr2 + create mode 120000 incoming/5d/jmg_7279.cr2 + create mode 120000 incoming/5d/jmg_7286.cr2 + create mode 120000 incoming/5d/jmg_7286.jpg + create mode 120000 incoming/5d/jmg_7290.cr2 + create mode 120000 incoming/5d/jmg_7290.jpg + create mode 120000 incoming/5d/jmg_7293.cr2 + create mode 120000 incoming/5d/jmg_7296.cr2 + create mode 120000 incoming/5d/jmg_7299.jpg + create mode 120000 incoming/5d/jmg_7300.cr2 + create mode 120000 incoming/5d/jmg_7300.jpg + create mode 120000 incoming/5d/jmg_7305_raw.jpg + create mode 120000 incoming/5d/jmg_8532.cr2 + create mode 120000 incoming/5d/jmg_8533.cr2 + create mode 120000 incoming/5d/jmg_8534.cr2 + create mode 120000 incoming/5d/jmg_8536.jpg + create mode 120000 incoming/5d/jmg_8538.cr2 + create mode 120000 incoming/5d/jmg_8549.cr2 + create mode 120000 incoming/5d/jmg_8549.jpg + create mode 120000 incoming/5d/jmg_8552.cr2 + create mode 120000 incoming/5d/jmg_8557.cr2 + create mode 120000 incoming/5d/jmg_8560.cr2 + create mode 120000 incoming/5d/jmg_8565.cr2 + create mode 120000 incoming/5d/jmg_8566.cr2 + create mode 120000 incoming/5d/jmg_8569.jpg + create mode 120000 incoming/5d/jmg_8575.jpg + create mode 120000 incoming/5d/jmg_8576.jpg + create mode 120000 incoming/5d/jmg_8578.cr2 + create mode 120000 incoming/5d/jmg_8579.cr2 + create mode 120000 incoming/5d/jmg_8580.jpg + create mode 120000 incoming/5d/jmg_8583.cr2 + create mode 120000 incoming/5d/jmg_8588.cr2 + create mode 120000 incoming/5d/jmg_8589.cr2 + create mode 120000 incoming/5d/jmg_8595.jpg + create mode 120000 incoming/5d/jmg_8597.jpg + create mode 120000 incoming/5d/jmg_8599.jpg + create mode 120000 incoming/5d/jmg_8602.cr2 + create mode 120000 incoming/5d/jmg_8603.cr2 + create mode 120000 incoming/5d/jmg_8606.cr2 + create mode 120000 incoming/5d/jmg_8606.jpg + create mode 120000 incoming/5d/jmg_8609.jpg + create mode 120000 incoming/5d/jmg_8613.jpg + create mode 120000 incoming/5d/jmg_8615.cr2 + create mode 120000 incoming/5d/jmg_8617.jpg + create mode 120000 incoming/5d/jmg_8619.cr2 + create mode 120000 incoming/5d/jmg_8620.jpg + create mode 120000 incoming/5d/jmg_8625.jpg + create mode 120000 incoming/5d/jmg_8627.jpg + create mode 120000 incoming/5d/jmg_8628.jpg + create mode 120000 incoming/5d/jmg_8632.cr2 + create mode 120000 incoming/5d/jmg_8636.cr2 + create mode 120000 incoming/5d/jmg_8636.jpg + create mode 120000 incoming/5d/jmg_8637.cr2 + create mode 120000 incoming/5d/jmg_8639.jpg + create mode 120000 incoming/5d/jmg_8640.cr2 + create mode 120000 incoming/5d/jmg_8655.jpg + create mode 120000 incoming/5d/jmg_8657.jpg + create mode 120000 incoming/5d/jmg_8670.cr2 + create mode 120000 incoming/5d/jmg_8673.jpg + create mode 120000 incoming/5d/jmg_8674.cr2 + create mode 120000 incoming/5d/jmg_8676.cr2 + create mode 120000 incoming/5d/jmg_8676.jpg + create mode 120000 incoming/5d/jmg_8677.cr2 + create mode 120000 incoming/5d/jmg_8681.jpg + create mode 120000 incoming/5d/jmg_8682.cr2 + create mode 120000 incoming/5d/jmg_8702.cr2 + create mode 120000 incoming/5d/jmg_8702.jpg + create mode 120000 incoming/5d/jmg_8707.jpg + create mode 120000 incoming/5d/jmg_8714.jpg + create mode 120000 incoming/5d/jmg_8716.jpg + create mode 120000 incoming/5d/jmg_8717.cr2 + create mode 120000 incoming/5d/jmg_8719.jpg + create mode 120000 incoming/5d/jmg_8721.jpg + create mode 120000 incoming/5d/jmg_8727.cr2 + create mode 120000 incoming/5d/jmg_8730.jpg + create mode 120000 incoming/5d/jmg_8736.cr2 + create mode 120000 incoming/5d/jmg_8737.cr2 + create mode 120000 incoming/5d/jmg_8742.cr2 + create mode 120000 incoming/5d/jmg_8742.jpg + create mode 120000 incoming/5d/jmg_8745.jpg + create mode 120000 incoming/5d/jmg_8748.cr2 + create mode 120000 incoming/5d/jmg_8748.jpg + create mode 120000 incoming/5d/jmg_8751.cr2 + create mode 120000 incoming/5d/jmg_8755.cr2 + create mode 120000 incoming/5d/jmg_8757.cr2 + create mode 120000 incoming/5d/jmg_8760.cr2 + create mode 120000 incoming/5d/jmg_8760.jpg + create mode 120000 incoming/5d/jmg_8765.cr2 + create mode 120000 incoming/5d/jmg_8771.jpg + create mode 120000 incoming/5d/jmg_8801.jpg + create mode 120000 incoming/5d/jmg_8803.cr2 + create mode 120000 incoming/5d/jmg_8803.jpg + create mode 120000 incoming/5d/jmg_8804.jpg + create mode 120000 incoming/5d/jmg_8805.jpg + create mode 120000 incoming/5d/jmg_8813.jpg + create mode 120000 incoming/5d/jmg_8816.cr2 + create mode 120000 incoming/5d/jmg_8823.jpg + create mode 120000 incoming/5d/jmg_8827.cr2 + create mode 120000 incoming/5d/jmg_8829.cr2 + create mode 120000 incoming/5d/jmg_8832.jpg + create mode 120000 incoming/5d/jmg_8833.cr2 + create mode 120000 incoming/5d/jmg_8837.cr2 + create mode 120000 incoming/5d/jmg_8838.jpg + create mode 120000 incoming/5d/jmg_8840.jpg + create mode 120000 incoming/5d/jmg_8842.jpg + create mode 120000 incoming/5d/jmg_8844.cr2 + create mode 120000 incoming/5d/jmg_8850.cr2 + create mode 120000 incoming/5d/jmg_8850.jpg + create mode 120000 incoming/5d/jmg_8852.cr2 + create mode 120000 incoming/5d/jmg_8853.cr2 + create mode 120000 incoming/5d/jmg_8853.jpg + create mode 120000 incoming/5d/jmg_8856.cr2 + create mode 120000 incoming/5d/jmg_8859.jpg + create mode 120000 incoming/5d/jmg_8863.jpg + create mode 120000 incoming/5d/jmg_8870.jpg + create mode 120000 incoming/5d/jmg_8871.cr2 + create mode 120000 incoming/5d/jmg_8871.jpg + create mode 120000 incoming/5d/jmg_8881.jpg + create mode 120000 incoming/5d/jmg_8883.jpg + create mode 120000 incoming/5d/jmg_8886.jpg + create mode 120000 incoming/5d/jmg_8887.cr2 + create mode 120000 incoming/5d/jmg_8889.cr2 + create mode 120000 incoming/5d/jmg_8894.cr2 + create mode 120000 incoming/5d/jmg_8897.cr2 + create mode 120000 incoming/5d/jmg_8898.cr2 + create mode 120000 incoming/5d/jmg_8900.jpg + create mode 120000 incoming/5d/jmg_8901.cr2 + create mode 120000 incoming/5d/jmg_8902.cr2 + create mode 120000 incoming/5d/jmg_8904.cr2 + create mode 120000 incoming/5d/jmg_8906.jpg + create mode 120000 incoming/5d/jmg_8908.cr2 + create mode 120000 incoming/5d/jmg_8920.cr2 + create mode 120000 incoming/5d/jmg_8920.jpg + create mode 120000 incoming/5d/jmg_8922.cr2 + create mode 120000 incoming/5d/jmg_8922.jpg + create mode 120000 incoming/5d/jmg_8923.cr2 + create mode 120000 incoming/5d/jmg_8924.jpg + create mode 120000 incoming/5d/jmg_8925.cr2 + create mode 120000 incoming/5d/jmg_8929.jpg + create mode 120000 incoming/5d/jmg_8930.jpg + create mode 120000 incoming/5d/jmg_8937.cr2 + create mode 120000 incoming/5d/jmg_8939.cr2 + create mode 120000 incoming/5d/jmg_8940.jpg + create mode 120000 incoming/5d/jmg_8941.jpg + create mode 120000 incoming/5d/jmg_8943.cr2 + create mode 120000 incoming/5d/jmg_8944.jpg + create mode 120000 incoming/5d/jmg_8950.cr2 + create mode 120000 incoming/5d/jmg_8951.jpg + create mode 120000 incoming/5d/jmg_8955.jpg + create mode 120000 incoming/5d/jmg_8959.cr2 + create mode 120000 incoming/5d/jmg_8960.jpg + create mode 120000 incoming/5d/jmg_8962.cr2 + create mode 120000 incoming/5d/jmg_8964.cr2 + create mode 120000 incoming/5d/jmg_8965.jpg + create mode 120000 incoming/5d/jmg_8966.jpg + create mode 120000 incoming/5d/jmg_8971.jpg + create mode 120000 incoming/5d/jmg_8976.jpg + create mode 120000 incoming/5d/jmg_8978.cr2 + create mode 120000 incoming/5d/jmg_8981.jpg + create mode 120000 incoming/5d/jmg_8982.jpg + create mode 120000 incoming/5d/jmg_8985.jpg + create mode 120000 incoming/5d/jmg_8988.cr2 + create mode 120000 incoming/5d/jmg_8988.jpg + create mode 120000 incoming/5d/jmg_8992.cr2 + create mode 120000 incoming/5d/jmg_8995.jpg + create mode 120000 incoming/5d/jmg_8996.cr2 + create mode 120000 incoming/5d/jmg_8997.cr2 + create mode 120000 incoming/5d/jmg_8999.cr2 + create mode 120000 incoming/5d/jmg_9000.cr2 + create mode 120000 incoming/5d/jmg_9015.cr2 + create mode 120000 incoming/5d/jmg_9017.cr2 + create mode 120000 incoming/5d/jmg_9019.cr2 + create mode 120000 incoming/5d/jmg_9021.cr2 + create mode 120000 incoming/5d/jmg_9021.jpg + create mode 120000 incoming/5d/jmg_9022.cr2 + create mode 120000 incoming/5d/jmg_9027.cr2 + create mode 120000 incoming/5d/jmg_9028.jpg + create mode 120000 incoming/5d/jmg_9031.cr2 + create mode 120000 incoming/5d/jmg_9035.cr2 + create mode 120000 incoming/5d/jmg_9043.jpg + create mode 120000 incoming/5d/jmg_9057.cr2 + create mode 120000 incoming/5d/jmg_9064.cr2 + create mode 120000 incoming/5d/jmg_9077.jpg + create mode 120000 incoming/5d/jmg_9078.jpg + create mode 120000 incoming/5d/jmg_9081.jpg + create mode 120000 incoming/5d/jmg_9082.cr2 + create mode 120000 incoming/5d/jmg_9083.jpg + create mode 120000 incoming/5d/jmg_9086.cr2 + create mode 120000 incoming/5d/jmg_9088.jpg + create mode 120000 incoming/5d/jmg_9308.jpg + create mode 120000 incoming/5d/jmg_9312.cr2 + create mode 120000 incoming/5d/jmg_9313.jpg + create mode 120000 incoming/5d/jmg_9319.jpg + create mode 120000 incoming/5d/jmg_9521.cr2 + create mode 120000 incoming/5d/jmg_9522.cr2 + create mode 120000 incoming/5d/jmg_9533.jpg + create mode 120000 incoming/5d/jmg_9534.jpg + create mode 120000 incoming/5d/jmg_9535.cr2 + create mode 120000 incoming/5d/jmg_9538.cr2 + create mode 120000 incoming/5d/jmg_9538.jpg + create mode 120000 incoming/5d/jmg_9540.jpg + create mode 120000 incoming/5d/jmg_9542.cr2 + create mode 120000 incoming/5d/jmg_9545.jpg + create mode 120000 incoming/5d/jmg_9554.jpg + create mode 120000 incoming/5d/jmg_9555.jpg + create mode 120000 incoming/5d/jmg_9558.jpg + create mode 120000 incoming/5d/jmg_9561.cr2 + create mode 120000 incoming/5d/jmg_9585.cr2 + create mode 120000 incoming/5d/jmg_9587.jpg + create mode 120000 incoming/5d/jmg_9591.jpg + create mode 120000 incoming/5d/jmg_9595.jpg + create mode 120000 incoming/5d/jmg_9598.cr2 + create mode 120000 incoming/5d/jmg_9600.jpg + create mode 120000 incoming/5d/jmg_9604.jpg + create mode 120000 incoming/5d/jmg_9610.jpg + create mode 120000 incoming/5d/jmg_9613.cr2 + create mode 120000 incoming/5d/jmg_9613.jpg + create mode 120000 incoming/5d/jmg_9614.cr2 + create mode 120000 incoming/5d/jmg_9618.jpg + create mode 120000 incoming/5d/jmg_9619.jpg + create mode 120000 incoming/5d/jmg_9620.jpg + create mode 120000 incoming/5d/jmg_9621.jpg + create mode 120000 incoming/5d/jmg_9623.cr2 + create mode 120000 incoming/5d/jmg_9746.jpg + create mode 120000 incoming/5d/jmg_9763.cr2 + create mode 120000 incoming/5d/jmg_9763.jpg + create mode 120000 incoming/5d/jmg_9764.cr2 + create mode 120000 incoming/5d/jmg_9772.jpg + create mode 120000 incoming/5d/jmg_9773.jpg + create mode 120000 incoming/5d/jmg_9781.jpg + create mode 120000 incoming/5d/jmg_9790.jpg + create mode 120000 incoming/5d/jmg_9800.jpg + create mode 120000 incoming/5d/jmg_9808.jpg + create mode 120000 incoming/5d/jmg_9830.jpg + create mode 120000 incoming/5d/jmg_9834.cr2 + create mode 120000 incoming/5d/jmg_9843.jpg + create mode 120000 incoming/5d/jmg_9848.jpg + create mode 120000 incoming/5d/jmg_9849.jpg + create mode 120000 incoming/5d/jmg_9853.cr2 + create mode 120000 incoming/5d/jmg_9856.jpg + create mode 120000 incoming/5d/jmg_9857.cr2 + create mode 120000 incoming/5d/jmg_9859.cr2 + create mode 120000 incoming/5d/jmg_9860.jpg + create mode 120000 incoming/5d/jmg_9917.jpg + create mode 120000 incoming/5d/jmg_9923.jpg + create mode 120000 incoming/5d/jmg_9926.jpg + create mode 120000 incoming/5d/jmg_9975.cr2 + create mode 120000 incoming/5d/jmg_9976.cr2 + create mode 120000 incoming/5d/jmg_9978.jpg + create mode 120000 incoming/5d/jmg_9988.jpg + create mode 120000 incoming/5d/jmg_9997.cr2 + create mode 120000 incoming/5d/jmg_9998.jpg + create mode 120000 incoming/5d/jmg_9999.jpg + delete mode 120000 list_5d_repoB + create mode 120000 only_on_repoB + delete mode 120000 dir/2012/dir2/jmg_0128.cr2 + delete mode 120000 dir/2012/dir2/jmg_0128.jpg + delete mode 120000 dir/2012/dir2/jmg_0129.cr2 + delete mode 120000 dir/2012/dir2/jmg_0129.jpg + delete mode 120000 dir/2012/dir2/jmg_0353.jpg + delete mode 120000 dir/2012/dir2/jmg_0354.jpg + delete mode 120000 dir/2012/dir2/jmg_0375.jpg + delete mode 120000 dir/2012/dir2/jmg_0376.jpg + delete mode 120000 dir/2012/dir2/jmg_0378.jpg + delete mode 120000 dir/2012/dir2/jmg_8707.cr2 + delete mode 120000 dir/2012/dir2/jmg_8707.jpg + delete mode 120000 dir/2012/dir2/jmg_8727.cr2 + delete mode 120000 dir/2012/dir2/jmg_8727.jpg + delete mode 120000 dir/2012/dir2/jmg_8728.cr2 + delete mode 120000 dir/2012/dir2/jmg_8728.jpg + delete mode 120000 dir/2012/dir2/jmg_8729.cr2 + delete mode 120000 dir/2012/dir2/jmg_8729.jpg + delete mode 120000 dir/2012/dir2/jmg_8740.cr2 + delete mode 120000 dir/2012/dir2/jmg_8740.jpg + delete mode 120000 dir/2012/dir2/jmg_8742.cr2 + delete mode 120000 dir/2012/dir2/jmg_8742.jpg + delete mode 120000 dir/2012/dir2/jmg_8825.cr2 + delete mode 120000 dir/2012/dir2/jmg_8825.jpg + delete mode 120000 dir/2012/dir2/jmg_8991.cr2 + delete mode 120000 dir/2012/dir2/jmg_8991.jpg + delete mode 120000 dir/2012/dir2/jmg_8992.cr2 + delete mode 120000 dir/2012/dir2/jmg_8992.jpg + delete mode 120000 dir/2012/dir2/jmg_8993.cr2 + delete mode 120000 dir/2012/dir2/jmg_8993.jpg + delete mode 120000 dir/2012/dir2/jmg_9059.cr2 + delete mode 120000 dir/2012/dir2/jmg_9059.jpg + delete mode 120000 dir/2012/dir2/jmg_9060.cr2 + delete mode 120000 dir/2012/dir2/jmg_9060.jpg + delete mode 120000 dir/2012/dir2/jmg_9064.cr2 + delete mode 120000 dir/2012/dir2/jmg_9064.jpg + delete mode 120000 dir/2012/dir2/jmg_9065.cr2 + delete mode 120000 dir/2012/dir2/jmg_9065.jpg + delete mode 120000 dir/2012/dir2/jmg_9081.cr2 + delete mode 120000 dir/2012/dir2/jmg_9081.jpg + delete mode 120000 dir/2012/dir2/jmg_9082.cr2 + delete mode 120000 dir/2012/dir2/jmg_9082.jpg + delete mode 120000 dir/2012/dir2/jmg_9083.cr2 + delete mode 120000 dir/2012/dir2/jmg_9083.jpg + delete mode 120000 dir/2012/dir1/jmg_0132.cr2 + delete mode 120000 dir/2012/dir1/jmg_0132.jpg + delete mode 120000 dir/2012/dir1/jmg_0133.cr2 + delete mode 120000 dir/2012/dir1/jmg_0133.jpg + delete mode 120000 dir/2012/dir1/jmg_0347.jpg + delete mode 120000 dir/2012/dir1/jmg_0351.jpg + delete mode 120000 dir/2012/dir1/jmg_0352.jpg + delete mode 120000 dir/2012/dir1/jmg_0374.jpg + delete mode 120000 dir/2012/dir1/jmg_8714.cr2 + delete mode 120000 dir/2012/dir1/jmg_8714.jpg + delete mode 120000 dir/2012/dir1/jmg_8716.cr2 + delete mode 120000 dir/2012/dir1/jmg_8716.jpg + delete mode 120000 dir/2012/dir1/jmg_8734.cr2 + delete mode 120000 dir/2012/dir1/jmg_8734.jpg + delete mode 120000 dir/2012/dir1/jmg_8735.cr2 + delete mode 120000 dir/2012/dir1/jmg_8735.jpg + delete mode 120000 dir/2012/dir1/jmg_8736.cr2 + delete mode 120000 dir/2012/dir1/jmg_8736.jpg + delete mode 120000 dir/2012/dir1/jmg_8743.cr2 + delete mode 120000 dir/2012/dir1/jmg_8743.jpg + delete mode 120000 dir/2012/dir1/jmg_8746.cr2 + delete mode 120000 dir/2012/dir1/jmg_8746.jpg + delete mode 120000 dir/2012/dir1/jmg_8828.cr2 + delete mode 120000 dir/2012/dir1/jmg_8828.jpg + delete mode 120000 dir/2012/dir1/jmg_8984.cr2 + delete mode 120000 dir/2012/dir1/jmg_8984.jpg + delete mode 120000 dir/2012/dir1/jmg_8985.cr2 + delete mode 120000 dir/2012/dir1/jmg_8985.jpg + delete mode 120000 dir/2012/dir1/jmg_8986.cr2 + delete mode 120000 dir/2012/dir1/jmg_8986.jpg + delete mode 120000 dir/2012/dir1/jmg_8988.cr2 + delete mode 120000 dir/2012/dir1/jmg_8988.jpg + delete mode 120000 dir/2012/dir1/jmg_9057.cr2 + delete mode 120000 dir/2012/dir1/jmg_9057.jpg + delete mode 120000 dir/2012/dir1/jmg_9058.cr2 + delete mode 120000 dir/2012/dir1/jmg_9058.jpg + delete mode 120000 dir/2012/dir1/jmg_9086.cr2 + delete mode 120000 dir/2012/dir1/jmg_9086.jpg + delete mode 120000 dir/2012/dir1/jmg_9087.cr2 + delete mode 120000 dir/2012/dir1/jmg_9087.jpg + delete mode 120000 dir/2013/dir2/jmg_0477.cr2 + delete mode 120000 dir/2013/dir2/jmg_0477.jpg + delete mode 120000 dir/2013/dir2/jmg_0478.cr2 + delete mode 120000 dir/2013/dir2/jmg_0478.jpg + delete mode 120000 dir/2013/dir2/jmg_0479.cr2 + delete mode 120000 dir/2013/dir2/jmg_0479.jpg + delete mode 120000 dir/2013/dir2/jmg_0604.cr2 + delete mode 120000 dir/2013/dir2/jmg_0604.jpg + delete mode 120000 dir/2013/dir2/jmg_0605.cr2 + delete mode 120000 dir/2013/dir2/jmg_0605.jpg + delete mode 120000 dir/2013/dir2/jmg_0606.cr2 + delete mode 120000 dir/2013/dir2/jmg_0606.jpg + delete mode 120000 dir/2013/dir2/jmg_0607.cr2 + delete mode 120000 dir/2013/dir2/jmg_0607.jpg + delete mode 120000 dir/2013/dir2/jmg_0608.cr2 + delete mode 120000 dir/2013/dir2/jmg_0608.jpg + delete mode 120000 dir/2013/dir2/jmg_0708.cr2 + delete mode 120000 dir/2013/dir2/jmg_0708.jpg + delete mode 120000 dir/2013/dir2/jmg_0709.cr2 + delete mode 120000 dir/2013/dir2/jmg_0709.jpg + delete mode 120000 dir/2013/dir2/jmg_0710.cr2 + delete mode 120000 dir/2013/dir2/jmg_0710.jpg + delete mode 120000 dir/2013/dir1/jmg_0475.cr2 + delete mode 120000 dir/2013/dir1/jmg_0475.jpg + delete mode 120000 dir/2013/dir1/jmg_0476.cr2 + delete mode 120000 dir/2013/dir1/jmg_0476.jpg + delete mode 120000 dir/2013/dir1/jmg_0718.cr2 + delete mode 120000 dir/2013/dir1/jmg_0718.jpg + delete mode 120000 dir/2013/dir1/jmg_0719.cr2 + delete mode 120000 dir/2013/dir1/jmg_0719.jpg +Already up-to-date. +[2013-10-27 18:36:44 CET] Committer: Committing changes to git +[2013-10-27 18:36:44 CET] Pusher: Syncing with repoB +Already up-to-date. +fatal: Unable to create '/media/srv/img/.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 +From repoB:/media/srv/img + 276f659..5eba12c synced/git-annex -> repoB/synced/git-annex +Everything up-to-date +[2013-10-27 18:36:50 CET] Committer: Committing changes to git +[2013-10-27 18:36:51 CET] Pusher: Syncing with repoB +[2013-10-27 18:36:52 CET] Transferrer: Downloaded only_on_repoB +[2013-10-27 18:36:53 CET] Transferrer: Downloaded jmg_9077.jpg +[2013-10-27 18:36:58 CET] Committer: Committing changes to git +[2013-10-27 18:36:58 CET] Transferrer: Downloaded jmg_8676.cr2 +[2013-10-27 18:36:59 CET] Committer: Committing changes to git +[2013-10-27 18:37:02 CET] Transferrer: Downloaded jmg_0021.jpg +[2013-10-27 18:37:02 CET] Committer: Committing changes to git +[2013-10-27 18:37:04 CET] Transferrer: Downloaded jmg_0025.jpg +[2013-10-27 18:37:04 CET] Committer: Committing changes to git +[2013-10-27 18:37:06 CET] Transferrer: Downloaded jmg_0026.jpg +[2013-10-27 18:37:06 CET] Committer: Committing changes to git +[2013-10-27 18:37:07 CET] Transferrer: Downloaded jmg_0027.jpg +[2013-10-27 18:37:07 CET] Committer: Committing changes to git +[2013-10-27 18:37:10 CET] Transferrer: Downloaded jmg_0034.jpg +[2013-10-27 18:37:10 CET] Committer: Committing changes to git +[2013-10-27 18:37:12 CET] Transferrer: Downloaded jmg_0035.jpg +[2013-10-27 18:37:12 CET] Committer: Committing changes to git +[2013-10-27 18:37:15 CET] Transferrer: Downloaded jmg_0036.jpg +[2013-10-27 18:37:15 CET] Committer: Committing changes to git +[2013-10-27 18:37:17 CET] Transferrer: Downloaded jmg_0130.jpg +[2013-10-27 18:37:17 CET] Committer: Committing changes to git +[2013-10-27 18:37:18 CET] Transferrer: Downloaded jmg_0131.jpg +[2013-10-27 18:37:18 CET] Committer: Committing changes to git +[2013-10-27 18:37:20 CET] Transferrer: Downloaded jmg_0155.jpg +[2013-10-27 18:37:20 CET] Committer: Committing changes to git +[2013-10-27 18:37:23 CET] Transferrer: Downloaded jmg_0156.jpg +[2013-10-27 18:37:23 CET] Committer: Committing changes to git +[2013-10-27 18:37:27 CET] Transferrer: Downloaded jmg_0158.cr2 +[2013-10-27 18:37:27 CET] Committer: Committing changes to git +[2013-10-27 18:37:32 CET] Transferrer: Downloaded jmg_0165.cr2 +[2013-10-27 18:37:32 CET] Committer: Committing changes to git +[2013-10-27 18:37:37 CET] Transferrer: Downloaded jmg_0166.cr2 +[2013-10-27 18:37:37 CET] Committer: Committing changes to git +To repoB:/media/srv/img/ + 276f659..5eba12c git-annex -> synced/git-annex +To repoB:/media/srv/img/ + 5eba12c..f00ee07 git-annex -> synced/git-annex +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(merging repoB/git-annex into git-annex...) + + +(Recording state in git...) + +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +# End of transcript or log. +"""]] + +> [[done]], seems this was caused by the bug I alread fixed. --[[Joey]] diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment new file mode 100644 index 000000000..88b293284 --- /dev/null +++ b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_1_ae4a13ff121d27f78904eee9bf5e716b._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-10-28T22:02:30Z" + content=""" +So this sounds like [[bugs/direct_mode_assistant_in_subdir_confusion]], which was fixed in 4.20131024. Is there a possibility that you started the git-annex assistant (or webapp) from within `incoming/5d` ? + +I'm not sure if the bug could also cause the removal of directories to happen in the wrong location. + + +---- + +It should be possible to revert these changes and get your files back. + +1. `git annex indirect` +2. `git log --stat` (find the commit that deleted files) +3. `git revert $commit` +4. `git annex direct` +"""]] diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment new file mode 100644 index 000000000..1a7e4e16c --- /dev/null +++ b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_2_32e360cd7b100ddb9a526e7833fc55e1._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnh6wz0pMA3NLPFg2j_I3S5JeinaOVqnng" + nickname="Felix" + subject="comment 2" + date="2013-10-30T22:55:36Z" + content=""" +It's quite possible that I have started the assistant (on the armhf machine) or the webapp (on the amd64 machine) in one of the subfolders, so yes it looks like that specific bug hit me. + +Having looked at the logs, I'm pretty sure that the removal of the original directory was caused by removing the suddenly occuring \"mirror\" folders in a subdirectory. +*** +Reverting proves to be difficult. I created a full copy of the git-annex repo and switched to indirect mode. There are around 500 commits that need to be reverted and about 6 of them are merges which I haven't been able to revert. I have only reverted the non-merge commits and after going back to direct mode there are now around 200 broken symlinks. I'm now assuming that those 200 are the ones that are lost and I need to restore from a backup. Can I rely on that? It's extremely difficult for me to do a full check. +*** +How should I proceed to get this repo (after further repairs) again in sync with the second repo and have the second repo adopt the \"repaired\" state? + +"""]] diff --git a/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment new file mode 100644 index 000000000..4e7d6491c --- /dev/null +++ b/doc/bugs/During_synchronisation_top-level_folder_suddenly_appear_in_sub-sub-folder/comment_3_650dc9ede4e16ef668d96840f63dad47._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 3" + date="2013-11-02T20:03:33Z" + content=""" +I don't understand why there are so many commits that need to be reverted. I'd have thought that it would have only made one bad commit due to the bug, and reverting that would do. Or even just adding back any symlinks removed by any of the bad commits, without an explicit revert would accomplish the same. + +You should be able to check with `git annex whereis --not --in .` what git-annex thinks about the 200 broken symlinks. Clearly their content is not in the local repisitory; it may be present elsewhere, or you might have to restore those files from backup. + +Once you have the git tree of the repository back in good shape, assuming you did it by committing changes, and possibly committing git reverts, you should be able to just use normal git annex syncing to sync those changes to the second repo. Ie, `git annex sync` in both, or running the assistant. +"""]] diff --git a/doc/bugs/Endless_SSH_password_prompts.mdwn b/doc/bugs/Endless_SSH_password_prompts.mdwn new file mode 100644 index 000000000..26def613f --- /dev/null +++ b/doc/bugs/Endless_SSH_password_prompts.mdwn @@ -0,0 +1,15 @@ +### 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 diff --git a/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment b/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment new file mode 100644 index 000000000..b1ea71526 --- /dev/null +++ b/doc/bugs/Endless_SSH_password_prompts/comment_1_b3a32d7a53c30478f409a47f856282ab._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..fec729ddb --- /dev/null +++ b/doc/bugs/Endless_SSH_password_prompts/comment_2_0a1fc4b4580d8be4c37064e0a16de99b._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..aacf1cc01 --- /dev/null +++ b/doc/bugs/Endless_SSH_password_prompts/comment_3_46210f7745b8c7c237fc8b08309390fe._comment @@ -0,0 +1,11 @@ +[[!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/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn new file mode 100644 index 000000000..a44ecc82e --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. +When I try to add a box.com cloud repository with the encryption option selected, I get an error that says "internal server error". + +### What steps will reproduce the problem? +Anytime I try to set up a cloud repository with box.com (and presumably others, since this seems to be a problem with gpg (see log)) that is encrypted, I get this error. + + +### What version of git-annex are you using? On what operating system? +The operating system is Mac OS X 10.8.4, and the version of git-annex is 4.20130801-gc88bbc4. + + +### 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 + +(encryption setup) gpg: /Users/adamliter/.gnupg/gpg.conf:233: invalid auto-key-locate list +30/Aug/2013:02:27:11 -0400 [Error#yesod-core] user error (gpg ["--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. +"""]] + +[[!meta title="OSX bundled gpg does not work with gpg.conf created by MacGPG"]] + +> [[done]]; I have updated the gpg to version 1.4.14 which +> manages to build with the missing features. +> --[[Joey]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment new file mode 100644 index 000000000..ec0234c2d --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_1_9be1b577fa4d5fe9754845073fdf5d32._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 1" + date="2013-08-30T11:39:51Z" + content=""" +gpg complains about an invalid parameter for the `auto-key-locate` option, which is not passed by git-annex but found in your gpg.conf. + +What is on line 233 of `/Users/adamliter/.gnupg/gpg.conf`? +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment new file mode 100644 index 000000000..c8a1db228 --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_2_0da0d68b646f2b38be6ecf7c0fe13743._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U" + nickname="Adam" + subject="comment 2" + date="2013-08-30T15:39:16Z" + content=""" +\"auto-key-locate cert pka ldap hkp://keys.gnupg.net\" is on line 233 +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment new file mode 100644 index 000000000..3cfa9a829 --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_3_09c56f5574931f2ebe903069f0731160._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 3" + date="2013-08-30T16:09:58Z" + content=""" +Hmm, it looks like a perfectly valid list. Interesting. +But regardless, gpg doesn't seem to like that line; what gpg version +are you using? Also, does it work directly on the command-line +(`gpg -a --gen-random 1 1`)? + +Have you tried to setup the remote without that line in the gpg.conf? Of +course it wouldn't solve the core of the issue, but it's irrelevant for +random data generation anyway (the same goes for `--trust-model`); +perhaps this very command should be run with `--no-options`. +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment new file mode 100644 index 000000000..6d2bb451a --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_4_0c127396e682ca6ced43aec7deeb0335._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U" + nickname="Adam" + subject="comment 4" + date="2013-08-30T21:39:26Z" + content=""" +`gpg -a --gen-random 1 1` on the command line seems to work. At least, when I just ran it it returned `Xg==`. I'm not super familiar with running gpg on the command line, so I'm not sure if that is the desired result when running that. + +The version of gpg is GnuPG/MacGPG2 version 2.0.20. + +I just tried deleting that line from the config file, and now it worked. Would I be able to replace the line after setting up the repository, or is that going to create problems? I'm not entirely sure what that line does, and I'm a little wary about messing with it in case it breaks the functionality of any of the other things that I use gpg for, like email encryption. +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment new file mode 100644 index 000000000..998d67055 --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_5_6bc3eadefde4750eec67a55de6651b2d._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 5" + date="2013-08-30T22:51:56Z" + content=""" +OK (you just generated 1 byte of base64-encoded random data). +No, I'm afraid git-annex will croak for each operation using gpg on your remote (which includes get, push, fsck, ...). + +This lines specifies how gpg automatically retrieves public keys when you get a signed message for instance. If you don't want to mix configurations, it is easy to create a git-annex-specific GnuPG home directory, but it requires you to point the `GNUPGHOME` to this alternative directory before starting git-annex. + +That said, other MacOSX users have encountered the same problem, and it was [[reported_to_be_solved_recently|/bugs/internal_server_error_when_choosing_encrypted_rsync_repo_option/]]. +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment new file mode 100644 index 000000000..65e6275da --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_6_263ab9c1483438b1717c8061ac81a2fa._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.140" + subject="comment 6" + date="2013-09-05T16:30:52Z" + content=""" +I have verified the gpg build I am currently using on OSX fails with that line. MacGPG doesn't but I had problems including it in the build before. +If you remove the \"cert\" and the \"pkg\" from the line it will work. It seems I need to update the gpg build to support these DNS based key finding methods. +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment new file mode 100644 index 000000000..35d9c71e8 --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_7_eccc10990dff37584f8e60cd481a7140._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.140" + subject="comment 7" + date="2013-09-05T16:54:36Z" + content=""" +./configure says: + +<pre> +checking whether the resolver is usable... no +checking whether I can make the resolver usable with BIND_8_COMPAT... no + +configure:7918: gcc -o conftest -g -O2 conftest.c >&5 +Undefined symbols for architecture x86_64: + \"_res_9_dn_expand\", referenced from: + _main in ccsJFrZc.o + \"_res_9_dn_skipname\", referenced from: + _main in ccsJFrZc.o + \"_res_9_query\", referenced from: + _main in ccsJFrZc.o +ld: symbol(s) not found for architecture x86_64 +collect2: ld returned 1 exit status +</pre> + +So no DNS stuff until I can find a way to build a gpg for OSX that supports it. +"""]] diff --git a/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment new file mode 100644 index 000000000..741c5342f --- /dev/null +++ b/doc/bugs/Error_creating_encrypted_cloud_repository:___34__internal_server_error__34__/comment_8_f897d20cbe5e0f3f58ce1a0bacad3d71._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkgH7oNEqNbh3g-N1-UHXuqleXaRYDgj1U" + nickname="Adam" + subject="comment 8" + date="2013-09-05T17:30:07Z" + content=""" +Hmm, thanks for looking into it. I appreciate it. +"""]] diff --git a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn index c25f6b3ba..634f3e501 100644 --- a/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn +++ b/doc/bugs/Failed_to_make_repository___40__calling_nonexistant_shell__41__.mdwn @@ -24,3 +24,5 @@ Ubuntu 10.04 on both desktop and server. ### Please provide any additional information below. The problem seems to be runshell trying to call /home/annex/sh, which does not exist. Why would it do that? + +> [[done]] diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn b/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn new file mode 100644 index 000000000..950aad0fc --- /dev/null +++ b/doc/bugs/Feature_request:___34__quvi__34___flag.mdwn @@ -0,0 +1,14 @@ +### Please describe the problem. +git-annex v4.20130827 can't be built on ARM. Technically it's vector that can't be built due to a lack of Template Haskell compilers for this architecture. Vector is a dependency of aeson, which is a dependency of git-annex, which therefore fails to compile. + +The only functionality that relies on aeson is, to my knowledge, quvi. Thus my feature request: If you were to introduce a flag to switch quvi support on or off, ARM users like me could circumvent the aeson dependency at build time. In this case we weren't stuck with 4.20130815 (the latest version to not depend on aeson) and could use current and future versions of git-annex. I would appreciate it. + + +### What steps will reproduce the problem? +See above. + + +### What version of git-annex are you using? On what operating system? +I'm running Raspbian Wheezy on a Raspberry Pi. The git-annex version to be built is 4.20130827. + +> [[done]] --[[Joey]] diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment new file mode 100644 index 000000000..a5668f664 --- /dev/null +++ b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_1_908c38024fd252328566034608c2dec3._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T05:25:39Z" + content=""" +Sorry, I didn't consider this dependency chain. + +FWIW, it is possible to build aeson without TH. See `standalone/android/haskell-patches/aeson_0.6.1.0_0001-disable-TH.patch` in the git-annex source tree. + +However, I will add a flag. +"""]] diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment new file mode 100644 index 000000000..ab4494c19 --- /dev/null +++ b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_2_4b6822fe91aa865f2ac1297a3daa3fca._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 2" + date="2013-09-09T05:44:48Z" + content=""" +Also, note that libghc-aeson-dev is available for arm in Debian. +"""]] diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment new file mode 100644 index 000000000..bbbd5b597 --- /dev/null +++ b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_3_c72ef77e76b1c99b5e0c78d0742080e7._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="91.213.8.236" + subject="comment 3" + date="2013-09-09T05:52:48Z" + content=""" +Thanks for the quick answer, I will give these two options a try. A flag will be even better, though. +"""]] diff --git a/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment new file mode 100644 index 000000000..10a84afda --- /dev/null +++ b/doc/bugs/Feature_request:___34__quvi__34___flag/comment_4_6092695d6afb1608447afe6f86e6fb83._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="96.44.189.102" + subject="comment 4" + date="2013-09-09T19:31:44Z" + content=""" +That was fast! +"""]] diff --git a/doc/bugs/Finding_an_Unused_file.mdwn b/doc/bugs/Finding_an_Unused_file.mdwn new file mode 100644 index 000000000..211755829 --- /dev/null +++ b/doc/bugs/Finding_an_Unused_file.mdwn @@ -0,0 +1,152 @@ +### Please describe the problem. + +SHA256E makes it difficult or impossible to find the original filename + +### What steps will reproduce the problem? + +I have these unused files: + + $ git annex unused + unused . (checking for unused data...) (checking master...) (checking backupbook/HEAD...) (checking b + aster...) (checking lang/a-...) (checking lang/master...) + Some annexed data is no longer used by any files: + NUMBER KEY + 1 SHA256-s9107031--2611c08c9822179c443f001f0bd7ecadf29adcd28edfa4cd1d8938d289cd3950 + 2 SHA256E-s31131336--58c48adad8e5f091981549dfbb2d9ec1003c8c46d1a660673fabefe722358f9b.flac + 3 SHA256-s9941549--db12950459ba039e6e6f6102a0811213c11a717d140d6e2f169049b958a5e047 + 4 SHA256-s11544438--174514684e03035cc741fa397a1b46f925899bd29189a98173f8f2a136d95ace + 5 SHA256E-s23445007--4659fae3eda6db7c528af6439fafab1496c740d02bdb67892450a8a2208fb29b.flac + 6 SHA256E-s47080709--7d331788ae7fee16bccce060c62cafa3cdafc9e0a2b387c0843cfe5871f51fa6.flac + 7 SHA256E-s33262563--3280607d6d397f84a02542c5ab2e5a9c44d60256b330e3d075078694f0c7f709.flac + 8 SHA256-s6522640--a1fa374afd62e8c85a115f18f78e679722f63980191c1e11ef84a49ae86f5b4f + 9 SHA256E-s29266138--27e792d64b6d4a4d44bdafe6867ca25ba79480d1b650cf385e67ff28a1fc5c31.flac + 10 SHA256-s14568326--023eb9fcefc063ee3ea495f4d382a8feac795d0e1a81c585781f5d369db2e00c + 11 SHA256-s11907175--73b66220bdbf0ca92209605b93d95d5f9e8247745f9c4367ff20cb53e11c24ac + 12 SHA256-s9193267--e159038b78c1b239d4cb8eeb892c7acf0e7b82feac7f5b5808dad477605e8478 + 13 SHA256E-s39329047--880ffab99c4b4c48224f409acb0cd797737e4ee70eacdba9bc7d7628ba3d05d7.flac + 14 SHA256E-s31400468--17ad7b13757d4e4d6e5d193d8295a30f566e00eea82bc19f50dc14b2bbf79ef3.flac + 15 SHA256E-s51514687--f83eb092ddcdf35e7f729bfa2cc0914b404de60f0b42f69f207cf01766061f16.flac + 16 SHA256E-s36235648--54e3f893b498b205b0b96bd87d5f14c71712e891c518070a0e1c730d92b3b0ac.flac + 17 SHA256-s10001177--35afb0b91c8b9f711b2d3b0fe7433ecc3bb13aece78c6170a47323c94233133d + 18 SHA256-s11830142--3dabe97ccbb68045d9ea82036ddf7211a3925a1bf682e05a32bcdf9b07bec676 + 19 SHA256E-s23102994--f848ed216e6ba17e6b539f31caa5af36266c367ed55dcff243445848b01fbeef.flac + 20 SHA256E-s38505547--967763ddd42daf782afa9299e67cb5c834153cb20242b50115dda566b24a68c4.flac + 21 SHA256-s11874975--14774a404526c4b68ede146f527202c59a4bee88376707c93df7da3bdb5345f2 + 22 SHA256-s10188700--18fd4ee62c2b3b1d8944eae528b59de2a45d493a291440edc9b30881ba10ece3 + 23 SHA256E-s53024109--eba924a26f7c602b60a83f208b2204ef3b570fd92ff39fbc067eeaec7c443ab6.flac + 24 SHA256-s11315225--0a8d2165166995e819e8c78302c45b1eeca9b79a5d77a3574885cbf8e18f265a + 25 SHA256-s12249573--79b9e551051232079f24902078e1fe5b7daed684e8acaa7cf29c191404a7c3c7 + 26 SHA256E-s47991289--79cfd8db5b3cbe7f50c335bfe0d148c38ff36dbc97b17ea3aff23d642bd5d167.flac + 27 SHA256E-s76961343--80e91f73e2f3ae6790d752d380118b3fadc223f9f1449354daa0095b5713986c.flac + 28 SHA256E-s44706648--ce782096aa5c0d58a12f7cbd6dbfe032fa7b0b4810219e23f906bd7fa0d96336.flac + 29 SHA256-s9393784--1e0e0190030352b3583ce515cd6dfb0db9f2ae39809a462099482947193bfd0f + 30 SHA256E-s11534608--bfcc0fdcb1ed112b1737d4fe7d2aa88511187d4c1c132bf1b7ab2cda9a7d90ad.flac + 31 SHA256E-s27916580--1f196e1b6312421f9d9bcd227a3885a5dec299fc47748cd34d5e59fe26374187.flac + 32 SHA256-s12099941--0a33af0293acb7cffa1727cc04efa4d7abb29a39e8f2165bfd565e2b18879430 + 33 SHA256E-s35578262--01d6f6022161bcaa825cb353012f85bacf3dcb930337ba506fc94b663b0d8043.flac + 34 SHA256E-s38880984--fa326bd0db5c9e400a4256e77acd488fede23ec714aeab7deb6952091a09e318.flac + 35 SHA256E-s27784704--a426f885d79d88d8b42b8a23ce267fb1c1855e8f7ff6833ec9ea61860b3c6819.flac + 36 SHA256-s11827390--17c1e84815805ea7e01555fdfa038a643a97621b84073679d5c649c020750652 + 37 SHA256E-s16632423--9735e37261624360f6a54fd1bc8a893cb5344afdc910e6b9e00c5791036759b0.flac + 38 SHA256-s10809006--7dd7ff078bdf4571bee6ab06213df970f427a8a2af476d4511a9c08ed0fb814d + 39 SHA256E-s33043364--3603942143fa4b1c0082ab7ba1db9b536621402eea3ac94e08ef0197062a2ef6.flac + 40 SHA256E-s33278052--62e1038e26894c6c014af4e77d2d9f79074ff4fc1ca9ca8c16fcc98eee5277c7.flac + 41 SHA256E-s47299134--0b604bff3ce12d077691d6e6428648da879c021537c094c72633209d5302fd97.flac + 42 SHA256E-s14882445--16c6aa4aaf8e60da617701281dfdfa372cb049636ae0f10f5aefcd8ce6c472af.flac + 43 SHA256E-s18168736--dfd7bfe9a433daef89f6f0015dfddaf7ac3611dd31813b0aed049171ac008323.flac + 44 SHA256-s10060170--9e3b638c4f397d8dbaa2fa9fc2bfacf6f9e93f00c80ee1fdd26971d25aff86ce + 45 SHA256E-s25630107--26fedc816dee58cb999cd2be8a58f3e8726ff056ba9c2abfbb9d149e7a92a230.flac + 46 SHA256-s9148609--3f29a2ae1ebd2e4857bb5c92aefb2f50f39a5a984e14645f658d15795a7c72a5 + 47 SHA256-s10576861--7d95469441ef205616ed795012d8a4c59acc00be00aca66bcacd8b041c2499c5 + 48 SHA256E-s23806802--8725d04f04925f4cd456bdb2108a48682cf51a498d97af9f71c58a412b8db9ab.flac + 49 SHA256E-s43187837--e83648296fa4553556596464efd4ab313529c0062071c9a40113fecede7a5de6.flac + 50 SHA256-s10384945--055a01b7e06f3165dddd10beb3e98ba4ca47b35abf9d5b2f26187bf07b9aa401 + 51 SHA256E-s54253300--b011eea8ec7ea51f22e0fe09645ffe83183e9589a9784ebc2d6dd0c559f07322.flac + 52 SHA256-s10335583--008c17c1a994884c6b9c52e10d17373b9160136ffab940992ef0f9d08eac45c1 + 53 SHA256-s9769970--b36fcb01d9df7627106e3a3c283944457f3e282ab62878c186162d465530cfbc + 54 SHA256-s10329964--dc4d82e085af3ade48d33cf828f8e7eecc27d4c33c448965e1b8bb59832ec473 + 55 SHA256-s10625243--2494e2ef2c64fc77dcb063f7b58079ad668cf46862b7f11eb28943d45f21b8dd + 56 SHA256E-s44585111--e35b0774729ccf547cd62e652425579781e3cbd76b33a17a0127bdbedb90606a.flac + 57 SHA256E-s42060728--9e0a533e640086fadefad7167d37d5b3c5de899e1ac5890bfd7a88524701ff14.flac + 58 SHA256E-s30013479--ae34a897e2f0e1124f04396e75dd41749511ce9930a2891ae3a066597ad518c5.flac + 59 SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137.flac + 60 SHA256-s13044938--8714a1db8781daa9f3993128dcda5a5ca904e075723cf38a11bc5e3695cf126f + 61 SHA256-s8814622--ba374e92c53ddb83605e2b500647117a00e4c6c463653cb0dd0311b76627c2ec + 62 SHA256E-s14900839--e94089b89629561ebf771543236f31439af1e6fcdce7ff56b9a183041e95e7ea.flac + 63 SHA256E-s27370218--a4717cf0615cda099ea5740194da8b4e349f2f38f6ebbf5f6111ced7f56d1736.flac + 64 SHA256E-s57686070--6d02689ccf91317bdfa4d8694ccbf7a9ccf00a7e00b92733769194908b4087d9.flac + 65 SHA256-s8707306--7f05e3e3dc4336eb7012d5bbb6d3d65047552901858ee4967e4a70d100fd1deb + 66 SHA256E-s42482194--bb7a968ec9bc0a8813974af9173c38cb39a43aa7d0c2aec203ddb358119e1f25.flac + 67 SHA256E-s31951334--b19789a9bbb98cb25df7b8a1b6d8856256bc2851cd892c91dddba7cf736542c5.flac + 68 SHA256E-s35901187--8eae2684aa3566b632a1797bd09d112dd5f438c98b649c000d71640983a549f2.flac + 69 SHA256E-s40659631--f6ca3227b14c7c050877ce4cc1218fea7582426649cd68fc82a74cae5d6962b4.flac + 70 SHA256E-s41415180--9c6f0000da119bd70422fe9529c41efb3103ca943697bdfb685f119f6b5ae6fd.flac + 71 SHA256E-s52313976--e4a59c65e05bd9450ef595b3c08365810205731952e45a68ee0c89bc76fbd9fc.flac + 72 SHA256E-s44925214--eabc5f7172d5c2e094ff84a5ecce784c172b175c8eeca861aa3996749668ea42.flac + (To see where data was previously used, try: git log --stat -S'KEY') + + To remove unwanted data: git-annex dropunused NUMBER + + ok + +And running: + + $ git log --stat -S'SHA256-s13044938--8714a1db8781daa9f3993128dcda5a5ca904e075723cf38a11bc5e3695cf126f' + commit 767a63a54784139f13d69d12fcfbee8f6ca3df41 + Author: Matthew Forrester <matt@keyboardwritescode.com> + Date: Fri Aug 23 21:38:31 2013 +0100 + + Remove Roger Shah - Openminded! as there is another copy in Unsorted with correct? filenames + + Amazon/Roger Shah/Openminded!/1114 - Shine (Album Mix).mp3 | 1 - + 1 file changed, 1 deletion(-) + + commit 6b04002c03287fb8918bdcdeaae393e862bebd4e + Author: Matthew Forrester <matt@keyboardwritescode.com> + Date: Thu Aug 8 21:30:14 2013 +0100 + + Initial checkin + + Amazon/Roger Shah/Openminded!/1114 - Shine (Album Mix).mp3 | 1 + + 1 file changed, 1 insertion(+) + +Works but I cannot find out how to get the `.flac` files working: + + +`$ git log --stat -S'SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137.flac'` + +`$ git log --stat -S'SHA256E-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137'` + +`$ git log --stat -S'SHA256-s38896704--ca6211442c33d9c44b997bef8f1079f07cdd2eb0e9e3c1de1eda9ae8a705f137'` + + +None of which give answers. I don't know if I'm doing it wrong (though I __think__ I'm doing what the instructions say), but I can't make it work. + + +### What version of git-annex are you using? On what operating system? + +$ uname -a +Linux fozz-desktop 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 19:56:49 UTC 2013 i686 i686 i686 GNU/Linux + +$ git annex version +git-annex version: 3.20121112ubuntu2 +local repository version: 3 +default repository version: 3 +supported repository versions: 3 +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 + + +# End of transcript or log. +"""]] + +> If `git log -S` does not find the key, then it was not used for any +> commit currently in the git repository. Which is certianly possible; +> for example `git annex add file; git rm file`. +> +> This is a dup of [[todo/wishlist: option to print more info with 'unused']]; [[done]] --[[Joey]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__.mdwn b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__.mdwn new file mode 100644 index 000000000..d66196acd --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__.mdwn @@ -0,0 +1,44 @@ +### Please describe the problem. +Using the webapp to generate a new (local) repository instantly takes it to the following state: +[[!format sh """ +user@local:~/Annex$ git status +# On branch master +# Changes to be committed: +# (use "git reset HEAD <file>..." to unstage) +# +# deleted: uuid.log +# +user@local:~/Annex$ git branch + git-annex +* master +user@local:~/Annex$ git log +commit 90bfcaf17b0576d8ecdc48ae44dda22d41464acc +Author: local <user> +Date: Sun Nov 3 15:30:17 2013 +0100 + + created repository +user@local:~/Annex$ git show HEAD +commit 90bfcaf17b0576d8ecdc48ae44dda22d41464acc +Author: local <user> +Date: Sun Nov 3 15:30:17 2013 +0100 + + created repository + +diff --git a/uuid.log b/uuid.log +new file mode 100644 +index 0000000..9df3670 +--- /dev/null ++++ b/uuid.log +@@ -0,0 +1 @@ ++987e7b9a-aa9d-41db-ae92-23fcae7f6187 user@local:~/Annex timestamp=1383489017.181 +user@local:~/Annex$ +"""]] + +I'm new to git-annex, so I'm not quite sure, but looking at [[internals]] this file should only exist in the git-annex branch, not in master. Furthermore, from this state it seems impossible to get "sync with your other devices" to work, because of a merge conflict on this change. + +Perhaps some sort of a race-condition with the annex-assistant picking up the uuid.log file while the repository is being initialized? + +### What version of git-annex are you using? On what operating system? +Ubuntu 13.10 with git-annex 4.20130815 + +> [[fixed|done]]; see comments. (This fix needs to be backported to Ubuntu.) --[[Joey]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_1_6441dd04adc158df22589c81746108a9._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_1_6441dd04adc158df22589c81746108a9._comment new file mode 100644 index 000000000..6080e88e4 --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_1_6441dd04adc158df22589c81746108a9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-11-03T16:48:25Z" + content=""" +I can't reproduce this at all. What version of git do you have installed? Did you install git-annex from ubuntu's repository? Does the same thing happen if you install the standalone linux tarball and use it to make a new repository? + +git-annex never creates a file named uuid.log on disk, so it's quite strange that it shows up in the initial commit to the master branch. It sort of looks like somehow git-annex's normal use of a separate index file to stage the uuid.log to the git-annex branch is failing. Since I have never seen any problem with that, I have to suspect that the ubuntu build is somehow badly broken. Or that the git in Ubuntu is for some reason ignoring `GIT_INDEX_FILE`. +"""]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_2_d1c5d7642284a375f9c455dbf76efa5c._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_2_d1c5d7642284a375f9c455dbf76efa5c._comment new file mode 100644 index 000000000..50bff5f41 --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_2_d1c5d7642284a375f9c455dbf76efa5c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 2" + date="2013-11-03T17:02:47Z" + content=""" +I made an Ubuntu saucy chroot, apt-get installed git-annex from universe, and ran the webapp in there. I did not reproduce this problem. + +The cause of the problem, it seems, must be something local to your system. Perhaps you have an environment variable set that is messing up git. Or perhaps you have a different, broken version of git installed. + +Can you \"git show git-annex\" in the repository? It should show a commit made to the git-annex branch that adds the uuid.log there. +"""]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_3_4b863da1c8ba73ad54da20f7d2ec6e5c._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_3_4b863da1c8ba73ad54da20f7d2ec6e5c._comment new file mode 100644 index 000000000..7acab1c37 --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_3_4b863da1c8ba73ad54da20f7d2ec6e5c._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="tanen" + ip="83.128.159.25" + subject="comment 3" + date="2013-11-03T17:35:00Z" + content=""" +Very strange: this is on a machine that I wiped and reinstalled just a few hours ago, it's a completely fresh Ubuntu 13.10 install with barely anything installed but the defaults. Git version is 1.8.3.2-1 + +I initially just pulled git-annex from the Ubuntu repo. After that I grabbed a more recent version from https://launchpad.net/ubuntu/+source/git-annex/4.20131101/+build/5189754 which is showing the same behavior. + +\"git show git-annex\" indeed shows the commit creating the uuid.log file on the git-annex branch. master has just one commit, with description \"created repository\" and creates a \"uuid.log\" file. The contents of the master uuid.log are identical to the one in the git-annex branch. + +I'm currently in the middle of trying out a git-annex setup so I can't switch versions again right now, but given the above I imagine a fresh 13.10 VM should show the same behavior. +"""]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_4_8e0f489305ce30ad578b9f8526e86416._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_4_8e0f489305ce30ad578b9f8526e86416._comment new file mode 100644 index 000000000..c020fc3a8 --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_4_8e0f489305ce30ad578b9f8526e86416._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 4" + date="2013-11-06T15:09:19Z" + content=""" +Intriguing -- I was able to reproduce this bug after installing the Ubuntu server ISO in a VM. + +Which is really strange, the only difference between this and my debootstrapped chroot should be the kernel.. +"""]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_5_c699034c8e02b2354516414d0ab73aab._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_5_c699034c8e02b2354516414d0ab73aab._comment new file mode 100644 index 000000000..e8a5f8cdd --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_5_c699034c8e02b2354516414d0ab73aab._comment @@ -0,0 +1,53 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 5" + date="2013-11-06T16:27:49Z" + content=""" +Running the prebuilt tarball build of git-annex, the bug does not occur. + +However, if I remove the git shipped with the prebuilt tarball, so it uses the system git, I do see the bug. So, it's apparently git version dependent. + +Also, I was able to reproduce it in a amd64 chroot. My other chroot was i386. Somehow architecture specific bug? + +--- + +Instrumenting all calls to git to be logged with the full environment and command, I found this: + +<pre> +GIT_INDEX_FILE='/home/foo/annex/.git/annex/index' +--git-dir=/home/foo/annex/.git --work-tree=/home/foo/annex commit --quiet --allow-empty -m created repository +</pre> + +This certianly looks like the index file setting for the git-annex branch is somehow leaking out past the branch commit operations. It continued setting that while setting up `gc.auto`; the next call to git after that stopped setting the index file. + +The only way I can see offhand this could possibly happen is due to an exception. It may be that on ubuntu an exception is thrown by code that runs a git command with the index file set, for whatever reason, and this causes the code that normally resets it back to not run. + +---- + +Ok, found it! + +<pre> +\"withIndex entered\" + +*** Please tell me who you are. + +Run + + git config --global user.email \"you@example.com\" + git config --global user.name \"Your Name\" + +to set your account's default identity. +Omit --global to set the identity only in this repository. + +fatal: unable to auto-detect email address (got 'foo@darkstar.(none)') +\"withIndex entered\" +\"withIndex cleaned up\" +</pre> + +Note lack of clean up after the first withIndex call. Thus leaving the environment passed to git polluted for further calls. + +This also explains why it's only happening on some systems, or with some versions of git. git's got all kinds of complexity around its username and email handling code. + +I have fixed this in git. +"""]] diff --git a/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_6_786cb7e643811dfd2496ceeff8f34f44._comment b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_6_786cb7e643811dfd2496ceeff8f34f44._comment new file mode 100644 index 000000000..ea3e97e8e --- /dev/null +++ b/doc/bugs/Freshly_initialized_repo_has_staged_change___34__deleted:_uuid.log__34__/comment_6_786cb7e643811dfd2496ceeff8f34f44._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 6" + date="2013-11-06T16:40:57Z" + content=""" +Ubuntu bug report about this: <https://bugs.launchpad.net/ubuntu/+source/git-annex/+bug/1248623> + +It should be pretty easy to backport the fix to the version in Ubuntu. The relevant git commits are ee23be55fd3e7e202bc721c124f78b79d1aba6df and 81117e8a9d19d4739d3773d0515006e1ea41c266 +"""]] diff --git a/doc/bugs/GPG_can__39__t_handle_some_files.mdwn b/doc/bugs/GPG_can__39__t_handle_some_files.mdwn new file mode 100644 index 000000000..6c29a95b8 --- /dev/null +++ b/doc/bugs/GPG_can__39__t_handle_some_files.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. + +It looks like GPG is being used in text mode, or at least isn't overriding the GPG config. + +### What steps will reproduce the problem? + +Have a binary file with long lines, and attempt to copy it into git-annex. + +This will happen: + + $ git-annex copy 09\ Into\ The\ Dissonance.mp3 -t rsync.net_annex + copy 09 Into The Dissonance.mp3 (gpg) (checking rsync.net_annex...) (to rsync.net_annex...) gpg: can't handle text lines longer than 19995 characters + failed + git-annex: copy: 1 failed + +A workaround is to remove "textmode" from your gpg.conf, but git-annex should force this. + +### What version of git-annex are you using? On what operating system? + +7ae625363bcb6e1fc8b3733c1d7814aca05a2368 on Ubuntu 13.04 x86_64 + +> The sheer number of ways gpg offers of shooting yourself in the foot.. +> Ok [[done]] --[[Joey]] diff --git a/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment b/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment new file mode 100644 index 000000000..60c363fd9 --- /dev/null +++ b/doc/bugs/GPG_can__39__t_handle_some_files/comment_1_4388c971e991dbc0326e69c49994df1e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://launchpad.net/~eythian" + nickname="eythian" + subject="comment 1" + date="2013-09-06T23:37:10Z" + content=""" +I also had a huge bunch of files come across corrupted, but the one that came after I made this change wasn't. This might be a sign that GPG is corrupting things on the way past. +"""]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn new file mode 100644 index 000000000..bf68208da --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android.mdwn @@ -0,0 +1,280 @@ +### Please describe the problem. +git add hangs. +Maybe because of encrypted sdcard? + + + + + +### What steps will reproduce the problem? + + app_30@android:/sdcard $ mkdir annex;cd annex + app_30@android:/sdcard/annex $ git init + Initialized empty Git repository in /mnt/sdcard/annex/.git/ + app_30@android:/sdcard/annex $ git annex init + init + Detected a crippled filesystem. + + Enabling direct mode. + + Detected a filesystem without fifo support. + + Disabling ssh connection caching. + ok + (Recording state in git...) + app_30@android:/sdcard/annex $ touch lala + git annex add lala --debug < + [2013-10-13 22:05:17 CEST] read: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","ls-files","--others","--exclude-standard","-z","--","lala"] + [2013-10-13 22:05:17 CEST] read: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","ls-files","--modified","-z","--","lala"] + [2013-10-13 22:05:17 CEST] chat: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","cat-file","--batch"] + add lala [2013-10-13 22:05:17 CEST] chat: git ["--git-dir=/mnt/sdcard/annex/.git","--work-tree=/mnt/sdcard/annex","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"] + ** HANGS ** + + + +The same will happen when just running and asking assistant to create annex for camera. + +ps aux | grep -i git: + + app_30 9870 8950 2512 464 c009cd2c 400456a4 S git + app_30 9871 9870 64900 7552 ffffffff 40108a38 S git-annex + app_30 9876 9871 0 0 ffffffff 00000000 Z git + app_30 9877 9871 0 0 ffffffff 00000000 Z git + app_30 9878 9871 2512 608 c0114a4c 400b2878 S git + app_30 9879 9871 2512 556 c0114a4c 40074878 S git + +lsof | grep git: + + 1|app_30@android:/sdcard $ lsof | grep git + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/__properties__ (deleted) + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-res.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/framework/com.htc.resources.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-htc-res.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework.jar + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/etc/system_fonts.xml + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/etc/fallback_fonts.xml + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/Roboto-Regular.ttf + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/framework/core.jar + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/urandom + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/tasks + 9870 /data/data/ga.androidterm/lib/lib.git.so socket:[1172354] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/bg_non_interactive/tasks + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9870 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9870 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/app/Aluminum.apk + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172380] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172381] + 9870 /data/data/ga.androidterm/lib/lib.git.so /data/data/ga.androidterm/fifo + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172382] + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9870 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/DroidSansMono.ttf + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9870 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9870 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177783] + 9870 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177784] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/pts/2 + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/pts/2 + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/pts/2 + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/main + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/radio + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/events + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/system + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so anon_inode:[eventpoll] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184035] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/__properties__ (deleted) + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184035] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so anon_inode:[eventfd] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184036] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184036] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so anon_inode:[eventfd] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184039] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184043] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184044] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184046] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1184047] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/framework/framework-res.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/framework/com.htc.resources.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/framework/framework-htc-res.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/framework/framework.jar + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/etc/system_fonts.xml + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/etc/fallback_fonts.xml + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/fonts/Roboto-Regular.ttf + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/framework/core.jar + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/urandom + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/main + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/radio + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/events + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/log/system + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/cpuctl/tasks + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so socket:[1172354] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172355] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172355] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/cpuctl/bg_non_interactive/tasks + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172358] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172358] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so anon_inode:[eventpoll] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/ashmem + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/ashmem + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /data/app/ga.androidterm-1.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /data/app/ga.androidterm-1.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/app/Aluminum.apk + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172380] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172381] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /data/data/ga.androidterm/fifo + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172382] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/pts/2 + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /system/fonts/DroidSansMono.ttf + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172407] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1172407] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so anon_inode:[eventpoll] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so /dev/ashmem + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1177783] + 9871 /data/data/ga.androidterm/lib/lib.git-annex.so pipe:[1177784] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1184043] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1184044] + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/__properties__ (deleted) + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-res.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/framework/com.htc.resources.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-htc-res.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework.jar + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/etc/system_fonts.xml + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/etc/fallback_fonts.xml + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/Roboto-Regular.ttf + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/framework/core.jar + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/urandom + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/tasks + 9878 /data/data/ga.androidterm/lib/lib.git.so socket:[1172354] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/bg_non_interactive/tasks + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9878 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9878 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/app/Aluminum.apk + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172380] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172381] + 9878 /data/data/ga.androidterm/lib/lib.git.so /data/data/ga.androidterm/fifo + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172382] + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9878 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/DroidSansMono.ttf + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9878 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9878 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177783] + 9878 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177784] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1184046] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1184047] + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/__properties__ (deleted) + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-res.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/framework/com.htc.resources.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework-htc-res.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/framework/framework.jar + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/etc/system_fonts.xml + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/etc/fallback_fonts.xml + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/Roboto-Regular.ttf + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/framework/core.jar + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/urandom + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/main + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/radio + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/events + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/log/system + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/tasks + 9879 /data/data/ga.androidterm/lib/lib.git.so socket:[1172354] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172355] + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/cpuctl/bg_non_interactive/tasks + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172358] + 9879 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9879 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so /data/app/ga.androidterm-1.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/app/Aluminum.apk + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172380] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172381] + 9879 /data/data/ga.androidterm/lib/lib.git.so /data/data/ga.androidterm/fifo + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172382] + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/pts/2 + 9879 /data/data/ga.androidterm/lib/lib.git.so /system/fonts/DroidSansMono.ttf + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1172407] + 9879 /data/data/ga.androidterm/lib/lib.git.so anon_inode:[eventpoll] + 9879 /data/data/ga.androidterm/lib/lib.git.so /dev/ashmem + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177783] + 9879 /data/data/ga.androidterm/lib/lib.git.so pipe:[1177784] + + +vfat/sdcard entry: + /dev/block/dm-2 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702, \ + allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 + tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 + + + +### What version of git-annex are you using? On what operating system? +Version from git annex version: +2a8136b6bd60a17d687eb800594ec7c37b872b3d + +I tried both daily build and most recent 'stable' with the same effect. + +Android 4.0.3 (Htc One V) + +The same happens on my another android device; Samsung tablet with... also 4.0.3. +Tried to gather strace information on git, but couldn't. If anything more is necessary, +please let me know. + +The same happens when I git annex add in /data/data/ga.androidterm/anntmp - so it's not sdcard nor vfat. + +### 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 have updated git-annex to work with the new git, which will be 1.8.5. +> This fix should appear in the android autobuild within an hour if you +> want to try it. [[done]] --[[Joey]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment new file mode 100644 index 000000000..19b8ae1a6 --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_1_2fc435d1c741f9fc422401f682e7c8b7._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="I can reproduce this! (with 4.20130923-g78e9013)" + date="2013-10-15T19:57:19Z" + content=""" +Comparing straces from Android and Linux, it seems to be due to git check-attr outputting something different: + +<pre> +read(16, \"andro\0annex.backend\0unspecified\0\"..., 8096) = 66 +read(10, \"linux: annex.backend: unspecifie\"..., 8096) = 70 +</pre> + +So, this is not actually Android specific, thankfully. It's just a breakage caused by a change in a newish version of git! I think it's not yet released, just Android is building from git head right now. + +I have reverted the Android stable build to the last version I think won't be affected by this. +"""]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment new file mode 100644 index 000000000..12b0f9f6e --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_2_b73fb99a75aef912f8286626c5bde66d._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="bla" + ip="91.121.95.205" + subject="Testing" + date="2013-10-15T21:24:35Z" + content=""" +Last autobuild (installed by replacing existing) +annex 89345b7 with git 1.8.4.474.g128a96c - also hangs on add in the same manner (in previously created tmp git in /data/data/ga.androidterm/anntmp). Not sure if I did something wrong. + +Current stable release - works just fine (deinstalled, installed again - replace failed somehow) + + + +"""]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment new file mode 100644 index 000000000..eb3c993a8 --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_3_b7115f2c658439ff59a029f500697fc1._comment @@ -0,0 +1,57 @@ +[[!comment format=mdwn + username="bla" + ip="91.121.95.205" + subject="More info on latest autobuild" + date="2013-10-15T21:42:52Z" + content=""" +Using adb shell, su app_30, runshell: + + app_30@android:/data/data/ga.androidterm/anntmp $ head -n 3 /sdcard/git-annex.> + Installation starting to /data/data/ga.androidterm + 89345b7108f5c18eba0845f84780a26d069d011d + installing busybox + + app_30@android:/data/data/ga.androidterm/anntmp $ git version + git version 1.8.4.474.g128a96c + app_30@android:/data/data/ga.androidterm/anntmp $ git annex version + git-annex version: 4.20131015-g89345b7 + build flags: Assistant Webapp Testsuite S3 WebDAV Inotify 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: 3 + default repository version: 3 + supported repository versions: 3 4 + upgrade supported from repository versions: 0 1 2 + + git init; git annex init; touch lala + 130|app_30@android:/data/data/ga.androidterm/anntmp $ git annex add lala --deb> + [2013-10-15 23:37:20 CEST] read: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"ls-files\",\"--others\",\"--exclude-standard\",\"-z\",\"--\",\"lala\"] + [2013-10-15 23:37:20 CEST] read: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"diff\",\"--name-only\",\"--diff-filter=T\",\"-z\",\"--\",\"lala\"] + add lala [2013-10-15 23:37:20 CEST] chat: git [\"--git-dir=/data/data/ga.androidterm/anntmp/.git\",\"--work-tree=/data/data/ga.androidterm/anntmp\",\"check-attr\",\"-z\",\"--stdin\",\"annex.backend\",\"annex.numcopies\",\"--\"] + *hangs* + + + + echo lala | git check-attr -z --stdin annex.backend annex.numcopies | hexdump -C + 00000000 6c 61 6c 61 0a 00 61 6e 6e 65 78 2e 62 61 63 6b |lala..annex.back| + 00000010 65 6e 64 00 75 6e 73 70 65 63 69 66 69 65 64 00 |end.unspecified.| + 00000020 6c 61 6c 61 0a 00 61 6e 6e 65 78 2e 6e 75 6d 63 |lala..annex.numc| + 00000030 6f 70 69 65 73 00 75 6e 73 70 65 63 69 66 69 65 |opies.unspecifie| + 00000040 64 00 |d.| + 00000042 + +While on my laptop (git 1.8.4.rc3) + + feather annex % echo lala | git check-attr -z --stdin annex.backend annex.numcopies | hexdump -C + 00000000 22 6c 61 6c 61 5c 6e 22 3a 20 61 6e 6e 65 78 2e |\"lala\n\": annex.| + 00000010 62 61 63 6b 65 6e 64 3a 20 75 6e 73 70 65 63 69 |backend: unspeci| + 00000020 66 69 65 64 0a 22 6c 61 6c 61 5c 6e 22 3a 20 61 |fied.\"lala\n\": a| + 00000030 6e 6e 65 78 2e 6e 75 6d 63 6f 70 69 65 73 3a 20 |nnex.numcopies: | + 00000040 75 6e 73 70 65 63 69 66 69 65 64 0a |unspecified.| + 0000004c + +So in fact very different indeed. + + +Hope it helps - assuming i didn't do some weird mistake. I'll happily use stable version for now. GREAT THANKS! +"""]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment new file mode 100644 index 000000000..4456e2cef --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_4_67de7a56ddb06fc0e31cc011d281c633._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 4" + date="2013-10-16T16:16:02Z" + content=""" +Thanks for testing that. I had a fencepost error, which I've fixed, and actually tested with problimatic git version now. +"""]] diff --git a/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment new file mode 100644 index 000000000..7bbef0fdd --- /dev/null +++ b/doc/bugs/Git_annex_hangs_after_git_annex_add_on_vfat__47__sdcard__47__android/comment_5_58fdb2a00f1737746cdbc804f831a0e7._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://adamspiers.myopenid.com/" + nickname="Adam" + subject="any chance of a new release?" + date="2013-10-22T13:33:57Z" + content=""" +I just upgraded via cabal install to 4.20131002, which (unsurprisingly, I guess) still exhibits this issue. Would be great if a new release could be cut for this ... +"""]] 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 new file mode 100644 index 000000000..3f58bd889 --- /dev/null +++ b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path.mdwn @@ -0,0 +1,63 @@ +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. 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 new file mode 100644 index 000000000..8ff232159 --- /dev/null +++ b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_1_b3197993dbdfaf2db5e4651ac54a896e._comment @@ -0,0 +1,12 @@ +[[!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 new file mode 100644 index 000000000..b7aa61f17 --- /dev/null +++ b/doc/bugs/Git_annexed_files_symlink_are_wrong_when_submodule_is_not_in_the_same_path/comment_2_1fbbd02e61ef524597dafd69460b00b4._comment @@ -0,0 +1,10 @@ +[[!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/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment b/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment new file mode 100644 index 000000000..55d7efa1c --- /dev/null +++ b/doc/bugs/Hangs_on_creating_repository_when_using_--listen/comment_2_dc128eeddeaaf3f84e71aca0fb7d341f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 2" + date="2013-08-24T18:52:11Z" + content=""" +This also affects creating a second repository in the webapp, not just the repository creation at first startup. +"""]] diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn new file mode 100644 index 000000000..69b0c4116 --- /dev/null +++ b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__.mdwn @@ -0,0 +1,295 @@ +### Please describe the problem. + +I use both the assistant and the command line. Unfortunately I often end up +in a state where I cannot do a "git annex sync" (it fails as described below) +and I have to use the assistant to synchronize things to make the sync work. I +would like to know how to do the same thing using only the command line. + +### What steps will reproduce the problem? + +This problem involves two repos: a local, indirect mode, manual group, repo, and +a ssh remote archive group bare repo (with full git annex available +remotely). The local repo is "top" and the remote one is "mini_archive". + +I start with the assistant not running, and the two repos in sync. Note that the +remote server cannot directly contact the local repo. + +local: + + schmitta@top ~/D/annex (master)> git annex sync + commit + ok + pull mini_archive + ok + +remote: + + schmitta@mini ~/a/archive> git annex sync + commit + ok + +I then add a file locally and try to sync, getting a problem on mini_archive: + + schmitta@top ~/D/annex (master)> git annex add videos/Minecraft/Icy\ and\ FlowerChild\ Play\ -\ Better\ Than\ Wolves\ 3-qg6LVTcDl4Y.mp4 + add videos/Minecraft/Icy and FlowerChild Play - Better Than Wolves 3-qg6LVTcDl4Y.mp4 (checksum...) ok + (Recording state in git...) + schmitta@top ~/D/annex (master)> git annex sync + commit + ok + pull mini_archive + ok + push mini_archive + Counting objects: 15, done. + Delta compression using up to 4 threads. + Compressing objects: 100% (10/10), done. + Writing objects: 100% (10/10), 1.01 KiB | 0 bytes/s, done. + Total 10 (delta 4), reused 0 (delta 0) + remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first) + To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + a5b002b..dde2626 master -> synced/master + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) + error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' + failed + git-annex: sync: 1 failed + +I try to merge and sync on the remote (I assume sync also does merge, but I'm +not sure). + + schmitta@mini ~/a/archive> git annex merge + merge git-annex ok + schmitta@mini ~/a/archive> git annex sync + commit + ok + +Back on the local machine, I still have the conflict. + + schmitta@top ~/D/annex (master) [1]> git annex sync + commit + ok + pull mini_archive + ok + push mini_archive + Counting objects: 7, done. + Delta compression using up to 4 threads. + Compressing objects: 100% (5/5), done. + Writing objects: 100% (5/5), 513 bytes | 0 bytes/s, done. + Total 5 (delta 1), reused 0 (delta 0) + remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first) + To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) + error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' + failed + git-annex: sync: 1 failed + +From this state, the only way to resolve things is to launch the web app. It +tells me "synced with mini_archive" (and it starts uploading the new file). Then +on the server there is something to merge. (I haven't waited for the file to +finish uploading in this case.) + + schmitta@mini ~/a/archive> git annex merge + merge git-annex (merging refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex into git-annex...) + ok + schmitta@mini ~/a/archive> git annex sync + commit + ok + +and I can then sync on the local repo: + + schmitta@top ~/D/annex (master) [1]> git annex sync + commit + ok + pull mini_archive + From ssh://git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive + 8f39d4c..cb7f6c3 git-annex -> mini_archive/git-annex + ok + +Note that I need to do the remote merge for things to work. After the file has +finished uploading, I get back in a conflict: + + schmitta@top ~/D/annex (master)> git annex sync + commit + ok + pull mini_archive + ok + push mini_archive + Total 0 (delta 0), reused 0 (delta 0) + remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first) + To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) + error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' + failed + git-annex: sync: 1 failed + +If I disable and re-enable the sync on the server (forcing a sync), I still have +a conflict locally: + + schmitta@top ~/D/annex (master) [1]> git annex sync + commit + ok + pull mini_archive + ok + push mini_archive + Total 0 (delta 0), reused 0 (delta 0) + remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first) + To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) + error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' + failed + git-annex: sync: 1 failed + +It only get solved by doing a merge on the server: + + schmitta@mini ~/a/archive> git annex merge + merge git-annex (merging refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex into git-annex...) + (Recording state in git...) + ok + + schmitta@top ~/D/annex (master) [1]> git annex sync + commit + ok + pull mini_archive + remote: Counting objects: 13, done. + remote: Compressing objects: 100% (5/5), done. + remote: Total 5 (delta 3), reused 0 (delta 0) + Unpacking objects: 100% (5/5), done. + From ssh://git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive + cb7f6c3..d177e1a git-annex -> mini_archive/git-annex + ok + (merging mini_archive/git-annex into git-annex...) + + +### What version of git-annex are you using? On what operating system? + +Current version available on cabal: + + schmitta@top ~/D/annex (master)> git annex version + git-annex version: 4.20131002 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi + 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: 3 + default repository version: 3 + supported repository versions: 3 4 + upgrade supported from repository versions: 0 1 2 + + schmitta@mini ~/a/archive> git annex version + git-annex version: 4.20131002 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi + 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: 3 + default repository version: 3 + supported repository versions: 3 4 + upgrade supported from repository versions: 0 1 2 + + +### Please provide any additional information below. + +Here is daemon.log. It mentions another repo which is an external +hard drive not plugged it at the moment. I'm skipping the file transmission +(...). + +[[!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-23 14:02:05 CEST] main: starting assistant version 4.20131002 +[2013-10-23 14:02:05 CEST] TransferScanner: Syncing with hole, mini_archive +Already up-to-date. +fatal: '/Volumes/hole/annex/' does not appear to be a git repository +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. + +(scanning...) [2013-10-23 14:02:06 CEST] Watcher: Performing startup scan +Already up-to-date. +Already up-to-date. +fatal: '/Volumes/hole/annex/' does not appear to be a git repository +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +fatal: '/Volumes/hole/annex/' does not appear to be a git repository +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. +fatal: '/Volumes/hole/annex/' does not appear to be a git repository +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +fatal: '/Volumes/hole/annex/' does not appear to be a git repository +fatal: Could not read from remote repository. + +Please make sure you have the correct access rights +and the repository exists. +[2013-10-23 14:02:10 CEST] Committer: Committing changes to git +[2013-10-23 14:02:10 CEST] Pusher: Syncing with mini_archive + + +(Recording state in git...) +(started...) To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + 8f39d4c..cb7f6c3 git-annex -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex + a5b002b..dde2626 master -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/master +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +Everything up-to-date +(gpg) + + +SHA256E-s608232213--d4d6e02e651b1d265ff1c041ee8e8c23db9d880140816d62b8cc82cee4db3a54.mp4 + +... + +sent 608306626 bytes received 42 bytes 5133389.60 bytes/sec +total size is 608232213 speedup is 1.00 +[2013-10-23 14:04:13 CEST] Transferrer: Uploaded Icy and F..cDl4Y.mp4 +[2013-10-23 14:04:13 CEST] Pusher: Syncing with mini_archive +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + cb7f6c3..927cc1c git-annex -> refs/synced/1cdfb490-0660-41fb-b7ce-74b89abb9aac/git-annex +[2013-10-23 14:05:35 CEST] main: Syncing with mini_archive +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +remote: error: denying non-fast-forward refs/heads/synced/git-annex (you should pull first)[K +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +error: failed to push some refs to 'ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/' +Everything up-to-date + + +# End of transcript or log. +"""]] + +> So, receive.denyNonFastforwards was the problem. It turns out that +> `git init --bare --shared` sets that by default, and the webapp +> uses that to create repositories on ssh server. I have made the webapp +> unset receive.denyNonFastforwards when setting up such a repository. +> +> Also added something to the assistant release notes about this +> to handle existing repositories. [[done]] --[[Joey]] diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment new file mode 100644 index 000000000..ef2399d81 --- /dev/null +++ b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 1" + date="2013-10-23T15:21:34Z" + content=""" +<pre> +To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ + ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) +</pre> + +Since version 4.20130909, git-annex is supposed to have avoided this problem by forcing the push of the git-annex branch. If you run `git annex sync --debug`, you should see: + +[2013-10-23 11:12:54 EDT] call: git [\"--git-dir=annex/.git\",\"--work-tree=annex\",\"push\",\"foo\",\"+git-annex:synced/git-annex\",\"master:synced/master\"] + +The \"+\" flag before the branch name forces git push to update the remote branch even if it's not a fast-forward. + +You should be able to verify if git-annex is doing that, and run the same git push command manually to investigate why it might not be working. I have not seen this problem since putting in that fix, and I saw it before. Perhaps your server has an old or broken version of git that ignores this flag, or some git configuration setting I am not aware of that prevents it from working. +"""]] diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment new file mode 100644 index 000000000..44ccfe00b --- /dev/null +++ b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="http://alan.petitepomme.net/" + nickname="Alan Schmitt" + subject="comment 2" + date="2013-10-23T16:21:30Z" + content=""" +I think I found the problem, after much googling. + +The command line you suggest is indeed tried, and rejected by the server. + +The answer came from [here](http://stackoverflow.com/questions/253055/how-do-i-push-amended-commit-to-the-remote-git-repo) where it says (speaking of a forced push) + +> Even this may not work as git allows remote repositories to refuse non-fastforward pushes at the far end by using the config variable 'receive.denynonfastforwards'. + +Indeed this is set in my annex repository. Note that this is a local setting, and that repository was created by the assistant. + +I removed this setting, and I can now push. Could the setting of this bit be a bug in the assistant? + +In any case, thanks a lot for indicating where to look at. +"""]] 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 index fcb9fead9..07d6f3eb3 100644 --- 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 @@ -1,5 +1,7 @@ ### 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? @@ -59,3 +61,9 @@ 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_3_a07105226ef3488b97731db004651976._comment b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_3_a07105226ef3488b97731db004651976._comment new file mode 100644 index 000000000..e4795e5a8 --- /dev/null +++ b/doc/bugs/Huge_annex_out_of_memory_on_switch_to_indirect_mode_and_status/comment_3_a07105226ef3488b97731db004651976._comment @@ -0,0 +1,10 @@ +[[!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/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp.mdwn b/doc/bugs/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp.mdwn new file mode 100644 index 000000000..4a8006f06 --- /dev/null +++ b/doc/bugs/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp.mdwn @@ -0,0 +1,21 @@ +### Please describe the problem. +As described earlier in [[tips/fully_encrypted_git_repositories_with_gcrypt]] + +### What steps will reproduce the problem? +- A: use the webapp to create a new repository +- A: add a remote server to the repository using the 'gcrypt' method +- A: add a jabber account + +- B: use the webapp to create a new repository +- B: add the jabber account +- B: see the previously created 'cloud repository' with status 'not enabled' +- B: click enable, see that the stored credentials are correct, and press "verify this server" +- B: enter the ssh password twice +- B: get redirected to a blank screen (on the url /config/repository/enable/gcrypt/UUID "x"?auth=y) + +The assistent logfiles show nothing after the "Your public key has been saved in", the server shows that no public key for B was added to the account. + +This is with git-annex installed on the remote server; without it the process gets stuck after clicking "encrypt repository" in step 2, it will just indefinitely keep prompting for the SSH password. + +### What version of git-annex are you using? On what operating system? +Latest nightly build on ubuntu 13.10 diff --git a/doc/bugs/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp/comment_1_17814787e333d15da3ab4e57c7d31d4b._comment b/doc/bugs/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp/comment_1_17814787e333d15da3ab4e57c7d31d4b._comment new file mode 100644 index 000000000..5bd45d686 --- /dev/null +++ b/doc/bugs/Impossible_to_enable_an_existing_gcrypt_repo_in_the_webapp/comment_1_17814787e333d15da3ab4e57c7d31d4b._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.246" + subject="comment 1" + date="2013-11-13T16:51:40Z" + content=""" +I've tried to reproduce this, and cannot; it enabled the repository without trouble. + +Also, I have never seen the webapp fail with a blank screen, so that's strange. + +I think you need to show your `~/annex/.git/annex/daemon.log` from B. +"""]] 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 new file mode 100644 index 000000000..46a07ee6a --- /dev/null +++ b/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__.mdwn @@ -0,0 +1,42 @@ +### 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 +"""]] 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 new file mode 100644 index 000000000..53c9f7915 --- /dev/null +++ b/doc/bugs/Incorrect_merge__44___direct_repos___40__2__41__/comment_1_15c354c4841d364e78882d2b46a0a764._comment @@ -0,0 +1,66 @@ +[[!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___40__a_special_case__41__.mdwn b/doc/bugs/Incorrect_merge___40__a_special_case__41__.mdwn new file mode 100644 index 000000000..5b817e214 --- /dev/null +++ b/doc/bugs/Incorrect_merge___40__a_special_case__41__.mdwn @@ -0,0 +1,45 @@ +### 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 +"""]] 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 new file mode 100644 index 000000000..0594ddabe --- /dev/null +++ b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_1_c80418d76b501c688e3a9fb4831520fd._comment @@ -0,0 +1,41 @@ +[[!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 new file mode 100644 index 000000000..39bb90877 --- /dev/null +++ b/doc/bugs/Incorrect_merge___40__a_special_case__41__/comment_2_8b2a188696f46819f6e3f0e9660362d2._comment @@ -0,0 +1,45 @@ +[[!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/Internal_Server_Error:_Unknown_UUID/comment_9_ced3516c3e7161e4d7e599232f62a511._comment b/doc/bugs/Internal_Server_Error:_Unknown_UUID/comment_9_ced3516c3e7161e4d7e599232f62a511._comment new file mode 100644 index 000000000..4a99ee3ad --- /dev/null +++ b/doc/bugs/Internal_Server_Error:_Unknown_UUID/comment_9_ced3516c3e7161e4d7e599232f62a511._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="Tilde did it for me" + date="2013-10-06T21:59:43Z" + content=""" +I had exactly the same error message, \"Internal Server Error: Unknown UUID\", when I used a path starting with a tilde. Absolute path for home directory worked. +"""]] diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn index 630db722b..2629a7d56 100644 --- a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn +++ b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss.mdwn @@ -48,3 +48,10 @@ For this reason, it seems likely this is due to some sort of race condition. This is on Ubuntu 12.04 with git-annex revision a1e2bc4. +> There was no good soluton to this, so I picked a bad one that +> will not have users complainging git-annex ate their data. +> They will complain that `git annex unannex` is slow since it now copies +> the file, and perhaps instead use --fast, and hopefully avoid destroying +> their own data by editing the resulting hard links. +> +> [[done]] --[[Joey]] diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment new file mode 100644 index 000000000..c0b286a2b --- /dev/null +++ b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_10_52364dc5b1b43b51748453d1896e35c6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmVV_nBwlsyCv53BXoJt8YpCX_wZPfzpyo" + nickname="Peter" + subject="Progress" + date="2013-10-10T01:17:08Z" + content=""" +Is there any type of script / tool / patch which does the --fast but with a copy instead of only a hard link? Can someone point me towards how I'm supposed to do this? I'm a technical user, however I don't really fancy having try to go learn the source code of git-annex to fix this really bad flaw :-/ +"""]] diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment new file mode 100644 index 000000000..4e55bd020 --- /dev/null +++ b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_11_99b4db1841f8630a9c5efd08910e87a3._comment @@ -0,0 +1,104 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmVV_nBwlsyCv53BXoJt8YpCX_wZPfzpyo" + nickname="Peter" + subject="Productive Annoyance" + date="2013-10-10T04:30:47Z" + content=""" +Ok, so I'm annoyed by this enough (and desperate enough to want to get my data back) that I wrote up a few scripts to help with this. I make no claims regarding how well these will work, but they seem to work with some minimal testing on a Fedora 17 machine. + +READ THROUGH THESE SCRIPTS BEFORE RUNNING THEM TO MAKE SURE YOU ARE OK WITH WHAT THEY ARE DOING!!! + +First, a script to create a bad git-annex: one with missing files (with a few corner case names) after a git unannex. Specify the directory you'd like to make the annex at the top of the file. ALL CONTENTS OF THIS DIRECTORY WILL BE REMOVED!!! + + #!/bin/bash + + #This is the folder you'd like to create and unannex + FOLDERTOUNANNEX='/tmp/badAnnex' + + pushd . + + if [ ! -d \"$FOLDERTOUNANNEX\" ] ; then + mkdir \"$FOLDERTOUNANNEX\" + fi + + cd \"$FOLDERTOUNANNEX\" + + rm -rf * + + mkdir subdir + echo \"hi\" > 1one.txt + echo \"hi\" > 2two.txt + echo \"hi\" > \"3thr re ee.boo\" + echo \"hi\" > \"4f o u r.boo\" + echo \"hi\" > 5 + echo \"hi\" > \"6\" + echo \"hi\" > \"subdir/7\" + echo \"hi\" > \"subdir/8.cat\" + echo \"hi\" > \"subdir/9.cat\" + + echo \"* annex.backend=SHA512E\" > .gitattributes + + chmod g-r 5 6 + chmod o-r 6 + + ls -la + + git init + git annex init \"stupid\" + git annex add * + ls -la + git annex unannex * + ls -la + + popd + + +Then, a script to recover the files left missing by the above script. Note this might be very slow as it has to generate SHA512 hashes for all the files in your annex. Again, change the paths at the top of this file to work in your environment: + + #!/bin/bash + + #Set this to some place outside your annex, where we can store our hashes while we search for them + #It will be fastest if this is on a different physical disk than the annexed folder + #You can manually delete the file afterwards + HASHFILE='/backup3/tmp.sha' + #This is the folder you'd like to unannex + FOLDERTOUNANNEX='/tmp/badAnnex' + + + + + HASHLEN=128 + + pushd . + cd \"$FOLDERTOUNANNEX\" + + find \"$FOLDERTOUNANNEX\" ! -path '*.git*' -exec sha512sum \{\} \; > \"$HASHFILE\" + + find -L \"$FOLDERTOUNANNEX\" -type l | while read BROKENFILE; do + POINTSTO=`file \"$BROKENFILE\" | sed -r 's/^.*broken symbolic link to .(.*).$/\1/g'` + + HASH=`echo \"$POINTSTO\" | sed -r \"s/^.*--([^-\/.]{$HASHLEN}).*$/\1/g\"` + + EXT=`echo \"$POINTSTO\" | sed -r \"s/^.*--[^-\/.]{$HASHLEN}(.[^.]+)?$/\1/g\"` + + echo \"-\" + echo \"FILE:$BROKENFILE\" + echo \"POINTSTO:$POINTSTO\" + echo \"HASH:$HASH\" + echo \"EXT:$EXT\" + + SOURCEFILE=`grep $HASH $HASHFILE | grep -m 1 \"$EXT\" | sed -r \"s/^.{$HASHLEN} (.*)$/\1/g\"` + + echo \"SOURCEFILE:$SOURCEFILE\" + if [ -f \"$SOURCEFILE\" ]; + then + cp --backup --suffix=\"~GIT_ANNEX_IS_DANGEROUS~\" -a \"$SOURCEFILE\" \"$BROKENFILE\" + else + echo \"ERROR: Cant find sourcefile\" + fi + done; + + popd + +I have not yet run this repair script on my rather large broken annex. I cannot seem to figure out how to restore file ownership and permissions which seem to have been lost when the second file is just linked to the matching previously annexed file (note: this is visible after \"fixing\" the bad annex created by the first script above in that after \"fixing\" file \"6\" is readable by other, whereas originally he was NOT readable by other. The permissions of 6 have been copied from 5.) Any thoughts or improvements on this are appreciated. +"""]] diff --git a/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment new file mode 100644 index 000000000..74aaa1e56 --- /dev/null +++ b/doc/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/comment_9_e53148a9efa061a825f668a9492182f7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 9" + date="2013-08-30T05:59:28Z" + content=""" +I'll chime in and say that the non-fast behavior being the default seems wrong, and making hard-link invisibly seems wrong. What Joey proposed -- copying a file if there are multiple hard-links -- seems like the right solution. + +Just recently I tried to unannex a large repository and was bitten by now-dangling symlinks to files that I couldn't locate anymore. The fact is that the current unannex operation is too dangerous to be useful. +"""]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn new file mode 100644 index 000000000..63f423e2c --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn @@ -0,0 +1,39 @@ +### Please describe the problem. +Pairing over my local network doesn't work. The pairing process never finishes. The log shows that the same PairMsg messages are repeated endlessly. + +### What steps will reproduce the problem? + + +### What version of git-annex are you using? On what operating system? +I'm on Ubuntu Raring 13.04. I installed git-annex 4.20131024 from the Precise PPA. It is working fine with a remote ssh repo, just not local pairing. + +### 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-11-01 16:55:21 CDT] main: Pairing in progress +[2013-11-01 16:55:55 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})" +[2013-11-01 16:55:56 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})" +[2013-11-01 16:55:57 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})" +[2013-11-01 16:55:58 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})" +[2013-11-01 16:55:59 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})" +[2013-11-01 16:56:00 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"kubbie\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvBEWT+AiAmehOFyTQWlSdwDs7DDbkw7rfZ4W/IeG5awZjMgT5BefIv9cmar8vGIIEFMZLpf8cL3xIargDz0xE2wuqj5CLkdz+DKp5f2FGs11Ax/62DZr+eCiVtPnwijFw0Cz0wMRzkN93uedrvzP/KkNRcczgWh3aZqn8WxlkCia1fyykm/pP3W80MNkiJYX5vXpu1NCV5KLu+UXQzKhM2njOauJ3W5wsMvSl8faZIpEmKVCD3BMDDruxTIxggA3kt9GCGvIbPawy+fGOpp/j6pHqnX3GB2kkT47RIZKYEv99HuLyvea+oY5R11FsC2yYY3ujIdUU0fXnV8pvrqSv me@kubbie\\n\", pairUUID = UUID \"fd6a6858-76c9-4eea-b733-9359c7313e72\"},IPv4Addr 1879091392), verifiableDigest = \"cbd8197c3d78c8c68bb30f63aa974cd88dd0fb13\"})" +[2013-11-01 16:56:01 CDT] PairListener: received "PairMsg (Verifiable {verifiableVal = (PairReq,PairData {remoteHostName = Just \"Onyx\", remoteUserName = \"me\", remoteDirectory = \"~/annex\", remoteSshPubKey = \"ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBT0Y6TTzTg8nWwonmgUPPwJmPIaJzfEoJl8DbuylpgXqGCQ4doJXuvBODHIehPfyMr1xCWqNlNNLkcWg/a/eHFceyt3IlcD9XaZ1aKPzPmpjYKKf5amiYd6mAssw8zFaZUvwaXkNuHZpXVZyg6C6TkT6kdfln+6fOJZpSGQzksy0jka/Rzx0KXjsp3oqO4tQJbC7AX0nvmD0zvLtyCURzfGV+n2IqQxpPf2nP75Evt8jamcuqm6pWoe+hj9zjGytIXpSKe35wzRwUAUrjgmZ9NweuWfi2uMPJlDv8/n+Q3HyjygA+GzixBGuYXDt1CD8ISZvuoygS+9+jeY9uYH8b me@Onyx\\n\", pairUUID = UUID \"834b4f39-ca66-4baf-9323-57ef7058d7d0\"},IPv4Addr 2281744576), verifiableDigest = \"8d5d380542f7377f09a4584a38b0dbcea9ea215c\"})" +...and so on and so on... +# End of transcript or log. +"""]] + +> I was able to reproduce something very like this by starting +> pairing separately on both computers under poor network conditions (ie, +> weak wifi on my front porch). +> +> So, I've made a new PairReq message that has not been seen before +> always make the alert pop up, even if the assistant thinks it is +> in the middle of its own pairing process (or even another pairing process +> with a different box on the LAN). +> +> (This shouldn't cause a rogue PairAck to disrupt a pairing process part +> way through.) +> +> [[done]] --[[Joey]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment new file mode 100644 index 000000000..39587ee90 --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_1_b8c485bafd98be8c21595597af361255._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 1" + date="2013-11-01T23:10:12Z" + content=""" +Also, when I initiate the pairing process on one computer only, I can see the PairMsg being constantly received in the other computer's log, but the prompt to finish pairing never appears. +"""]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment new file mode 100644 index 000000000..f10b16f3c --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_2_bc63489334f44a423645021415ffe196._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 2" + date="2013-11-01T23:27:24Z" + content=""" +Well I installed the 1 Nov release from the tarball and then it picked up the pair request from the other system. I don't know if it was a bug in the previous version or something to do with the PPA. It's weird that the assistant just wasn't doing anything about the pair request it received. + +Thanks for your work on git-annex assistant. +"""]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment new file mode 100644 index 000000000..a7eff6744 --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_3_6345b174d04b6613c2c55a6ec9e50c21._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 3" + date="2013-11-02T19:02:55Z" + content=""" +There is something a little strange in the logs. It shows both Onyx and kubbie are sending PairReqs. Probably one of those is the local computer, logging its own broadcast messages which loop back to it. But normally in pairing, one side starts the pairing process with a PairReq, and the other side pops up an alert and continues the process with a PairAck. It's not normal for both sides to request that pairing start. + +Is it possible that you started pairing on both computers separately? + +I tried doing that with gnu and darkstar. First I started pairing on gnu. darkstar saw the pair request, but I ignored the alert message about that, and went and started a separate pairing process on darkstar. gnu never showed an alert message for that; it ignored darkstar's PairReqs since it was sending its own. + +It's unlikely you'd ignore the alert, but the same thing could happen if the two computers were not able to communicate over the network initially, and pairing were started on both separately. So neither gets a chance to see the other's PairReq and show the alert. Even when they came into communication, they'd each ignore the other's PairReq. + +So, that seems like a bug.. +"""]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment new file mode 100644 index 000000000..cacbad03f --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_4_f39ec6c3d5a016b3c5260162c0b42177._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 4" + date="2013-11-02T22:52:31Z" + content=""" +I did indeed try to pair from both systems. What happened was, after I started the pair request, I went to the other system, and there was no pair request listed. So I misunderstood the directions and thought I was supposed to go ahead and enter the same password into the other system. (It says that pairing will complete as soon as the password is entered on the other system, so it seems reasonable to try that.) Then both systems were constantly issuing pair requests, but neither system was responding to the requests, even though it was receiving them. + +Both systems were always on the network and always able to communicate over it. The bug went away when I upgraded to the 1 Nov release...but then I had some very confusing issues with partially-paired repos from different git-annex versions...I ended up having to start git-annex over from scratch on both systems with the 1 Nov build. + +So I'm not sure where to go from here with this bug. Thanks for your help. +"""]] diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment new file mode 100644 index 000000000..413ca952e --- /dev/null +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop/comment_5_ca0c5ef6e6a6d2c4b64430ac68370b6a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 5" + date="2013-11-02T22:55:42Z" + content=""" +Oh, now I see your comment up there that you fixed it. Awesome. :) +"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo.mdwn b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo.mdwn new file mode 100644 index 000000000..b217b0a3e --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo.mdwn @@ -0,0 +1,20 @@ +### 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) +"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment new file mode 100644 index 000000000..34d8d94b1 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_1_0b4dcedc58e5071733e1239490aed2ea._comment @@ -0,0 +1,10 @@ +[[!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/comment_2_1cb1ef0292a3357874b461a77c13373e._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_2_1cb1ef0292a3357874b461a77c13373e._comment new file mode 100644 index 000000000..83e0b2317 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_2_1cb1ef0292a3357874b461a77c13373e._comment @@ -0,0 +1,8 @@ +[[!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/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment new file mode 100644 index 000000000..0b3a804b9 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_erro_when_creating_USB_repo/comment_3_e5ec1e3ab304d738e3b0847287a47af4._comment @@ -0,0 +1,10 @@ +[[!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.mdwn b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo.mdwn new file mode 100644 index 000000000..a08737040 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo.mdwn @@ -0,0 +1,25 @@ +### 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) + +"""]] diff --git a/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment new file mode 100644 index 000000000..0f1e34e31 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_1_d95accb43bd18cc9acbbf1d4069f86b3._comment @@ -0,0 +1,8 @@ +[[!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/comment_2_452a3c524974832f0742efb00df4d576._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_2_452a3c524974832f0742efb00df4d576._comment new file mode 100644 index 000000000..6b3ca2a0b --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_2_452a3c524974832f0742efb00df4d576._comment @@ -0,0 +1,13 @@ +[[!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/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment new file mode 100644 index 000000000..e2ae9c3dc --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_3_f8f6d1e0065e5ba56cd405b1c021ca09._comment @@ -0,0 +1,10 @@ +[[!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/comment_4_b524649cee751532d20a4894d71c5cf3._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_4_b524649cee751532d20a4894d71c5cf3._comment new file mode 100644 index 000000000..8c7450ca6 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_4_b524649cee751532d20a4894d71c5cf3._comment @@ -0,0 +1,8 @@ +[[!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/comment_5_8312ba868ef616ec00563446c9c3464f._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_5_8312ba868ef616ec00563446c9c3464f._comment new file mode 100644 index 000000000..f94f2d9c8 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_5_8312ba868ef616ec00563446c9c3464f._comment @@ -0,0 +1,12 @@ +[[!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/comment_6_1af75c691d27c97397f1901f7c2483b0._comment b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_6_1af75c691d27c97397f1901f7c2483b0._comment new file mode 100644 index 000000000..19313d9a7 --- /dev/null +++ b/doc/bugs/Mac_OS_10.9_GPG_error_adding_S3_repo/comment_6_1af75c691d27c97397f1901f7c2483b0._comment @@ -0,0 +1,8 @@ +[[!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/OSX_app_issues/comment_13_cb12d419459e5cac766022ee0697fedc._comment b/doc/bugs/OSX_app_issues/comment_13_cb12d419459e5cac766022ee0697fedc._comment new file mode 100644 index 000000000..c9e199961 --- /dev/null +++ b/doc/bugs/OSX_app_issues/comment_13_cb12d419459e5cac766022ee0697fedc._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="John" + ip="109.242.130.160" + subject="runshell typo prevents execution" + date="2013-09-22T00:24:10Z" + content=""" +Using the latest Mountain Lion build available. + +>$ /Applications/git-annex.app/Contents/MacOS/git-annex + +>/Applications/git-annex.app/Contents/MacOS/runshell: line 25: syntax error near unexpected token `&' + +Line 25: +>echo \"** runshell loop detected!\"> &2 + +Fix (obvious but for the sake of completeness): +>echo \"** runshell loop detected!\" >&2 +"""]] diff --git a/doc/bugs/OSX_app_issues/comment_14_c966fa549bc73c52034ac9abc49de52a._comment b/doc/bugs/OSX_app_issues/comment_14_c966fa549bc73c52034ac9abc49de52a._comment new file mode 100644 index 000000000..df45eb601 --- /dev/null +++ b/doc/bugs/OSX_app_issues/comment_14_c966fa549bc73c52034ac9abc49de52a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.1.250" + subject="comment 14" + date="2013-09-22T14:15:28Z" + content=""" +I have fixed the runshell typo and updated the builds. +"""]] diff --git a/doc/bugs/OSX_app_issues/comment_15_10f1df95266f1a8c9ef933183190f6e2._comment b/doc/bugs/OSX_app_issues/comment_15_10f1df95266f1a8c9ef933183190f6e2._comment new file mode 100644 index 000000000..bdb0b55fa --- /dev/null +++ b/doc/bugs/OSX_app_issues/comment_15_10f1df95266f1a8c9ef933183190f6e2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="gueux" + ip="2a01:240:fe6d:0:8947:cf55:f955:49b9" + subject="same typo on Lion build" + date="2013-10-23T09:17:58Z" + content=""" +Could you please fix this typo on the Lion build? +"""]] diff --git a/doc/bugs/OSX_app_issues/comment_16_064e151da121f9c2ef13c19ecb4e7458._comment b/doc/bugs/OSX_app_issues/comment_16_064e151da121f9c2ef13c19ecb4e7458._comment new file mode 100644 index 000000000..8569bda7c --- /dev/null +++ b/doc/bugs/OSX_app_issues/comment_16_064e151da121f9c2ef13c19ecb4e7458._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="Remy" + ip="83.87.21.84" + subject="Crashes on OSX 10.9" + date="2013-10-23T20:30:12Z" + content=""" +I just installed OSX Mavericks. I also took the latest autobuild and copied it over the old git-annex.app to be sure it doesn't work. +When I execute \"git-annex status\" I get the following message + + +> dyld: 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 +> [1] 1361 trace trap git-annex status +"""]] diff --git a/doc/bugs/OSX_app_issues/comment_17_0e6ac5e0a54ce78bdc56c62e6fb92846._comment b/doc/bugs/OSX_app_issues/comment_17_0e6ac5e0a54ce78bdc56c62e6fb92846._comment new file mode 100644 index 000000000..5d5c0237e --- /dev/null +++ b/doc/bugs/OSX_app_issues/comment_17_0e6ac5e0a54ce78bdc56c62e6fb92846._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="calmyournerves" + ip="85.3.250.239" + subject="comment 17" + date="2013-10-24T21:43:37Z" + content=""" +For 10.9 Mavericks see http://git-annex.branchable.com/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/#comments +"""]] 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 new file mode 100644 index 000000000..3860456d2 --- /dev/null +++ b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex.mdwn @@ -0,0 +1,54 @@ +### 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 new file mode 100644 index 000000000..ca3ad1229 --- /dev/null +++ b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_2_f7149b684a97070cff051b780c73be48._comment @@ -0,0 +1,15 @@ +[[!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/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn index 96d73f0f4..46ae06f6d 100644 --- a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn +++ b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple.mdwn @@ -59,4 +59,6 @@ My .gitconfig is as follows: """]] > Closing this because all autobuilders have been upgraded -> to a more recent version of git. [[done]] --[[Joey]] +> to a more recent version of git. done --[[Joey]] +>> Reopened, because the Linux autobuilds have been downgraded to Debian +>> stable and have this problem again. --[[Joey]] diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment new file mode 100644 index 000000000..bee277aa6 --- /dev/null +++ b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_3_eaed9b5532e30e401f50193a72b98310._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmTNrhkVQ26GBLaLD5-zNuEiR8syTj4mI8" + nickname="Juan" + subject="Still happening in the linux autobuild (08/22/2013)" + date="2013-08-23T02:04:42Z" + content=""" +I've seen that git-annex for linux is still coming with git 1.7, which causes problems with my installed git (1.8.1.2). +Wasn't that corrected in autobuilds? +Thanks in advance. +Keep up the good work. +Regards, + Juan +"""]] diff --git a/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment new file mode 100644 index 000000000..2c9c33c8e --- /dev/null +++ b/doc/bugs/Older_version_of_git_causes_Internal_Server_Error_when_push.default___61___simple/comment_4_1fab407f3823ce8cec87f5df55e49f8c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 4" + date="2013-08-23T17:41:32Z" + content=""" +It was done for the autobuilds, but then I switched them to build using Debian stable, which still has git 1.7, and there is not currently a backport of a newer git to stable for me to use. +"""]] diff --git a/doc/bugs/On_Windows__44___can__39__t_use_a_USB_disk_annex_created_on_Linux.mdwn b/doc/bugs/On_Windows__44___can__39__t_use_a_USB_disk_annex_created_on_Linux.mdwn index ea36ac561..b997a8c72 100644 --- a/doc/bugs/On_Windows__44___can__39__t_use_a_USB_disk_annex_created_on_Linux.mdwn +++ b/doc/bugs/On_Windows__44___can__39__t_use_a_USB_disk_annex_created_on_Linux.mdwn @@ -14,3 +14,5 @@ On Windows, git-annex is unable to 'annex get' from a repository hosted on an ex Windows 7: 4.20140627-g8a36ec5 (from the git-annex download page) Debian Linux: 3.20120629 (from the package manager) + +[[!tag moreinfo]] diff --git a/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured.mdwn b/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured.mdwn index 07f8fa84c..92de1dce3 100644 --- a/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured.mdwn +++ b/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured.mdwn @@ -18,3 +18,5 @@ Debian Linux: 3.20120629 (from the package manager) I experienced this bug several times with a plain git-annex install, and the only workaround was removing the unix-style remotes from remote repos. After other hackery to get git-annex working on Windows, I can't currently reproduce the issue. + +[[!tag moreinfo]] diff --git a/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured/comment_1_95655915ff6ba9fb5d873358ff047496._comment b/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured/comment_1_95655915ff6ba9fb5d873358ff047496._comment new file mode 100644 index 000000000..d727bcafc --- /dev/null +++ b/doc/bugs/On_Windows__44___can__39__t_use_repository_that_has_a_unix-style_local_remote_configured/comment_1_95655915ff6ba9fb5d873358ff047496._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 1" + date="2013-09-13T19:14:55Z" + content=""" +I don't understand what is meant by a \"unix-style\" remote. + +Generally it helps to provide some commands I can run on Windows to replicate the problem. +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn new file mode 100644 index 000000000..e01310336 --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone..mdwn @@ -0,0 +1,230 @@ +### Please describe the problem. + +I had set up git-annex on a mac; I had created an initial repository at ~/annex; I had created a second repository on an external drive, at /Volumes/Biblio/annex; I had paired with three other machines on the same network, (two linux, one other mac) and set up a remote server as a backup-type repository. All seemed well. It had finally finished syncing everything to the remote server (my upload speeds are slow). + +I closed the firefox window showing the dashboard. I wanted to reopen it, so I ran the git-annex.app again, presuming on a running instance that that just opens the browser back at the webapp. Firefox window opened, but the only repository was the second one I'd made on the external drive. + +I restarted, as best as I could work out: git-annex assistant --stop, then because that left behind a process, killall git-annex. Then restarted the app. + +Firefox opened on the webapp. I had two repositories: The one on the external drive (now the "Here" repo) and the one on ~/annex but only as if it was paired from a different machine. + +ie: I see only "celestia.local (rachel@celestia.local~/annex)". This machine *is* celestia.local. + +That's it. Startup scan took a couple of minutes but didn't add anything. Then it decided to sync to celestia.local, which it took a little time over but didn't apparently do anything. + +If I drop files into ~/annex they are not synced anywhere. ~/annex still has a .git directory, populated with git files, it looks intact. It's just not being seen. + +Is it possible because the user is prompted to create their initial repo at ~/Desktop/annex it will by default only look there, then start looking in external drives for it? So the fact I didn't want it on my desktop, but put it directly in home, meant it got lost on restart? + +git-annex vicfg in ~/annex shows me this: + +[[!format sh """ +# git-annex configuration +# +# Changes saved to this file will be recorded in the git-annex branch. +# +# Lines in this file have the format: +# setting uuid = value + +# Repository trust configuration +# (Valid trust levels: trusted semitrusted untrusted dead) +# (for web) +#trust 00000000-0000-0000-0000-000000000001 = semitrusted +# (for rachel@octavia:~/annex) +#trust 161dec38-e8be-43b8-86c5-555d35ce3416 = semitrusted +# (for rachel@celestia.local:~/annex) +#trust 179fcddf-e247-4577-804b-267feed8abb1 = semitrusted +# (for 192.168.1.103_annex (rachel@rainbow.local:~/annex)) +#trust 256d5762-150d-4d5d-9340-517de298c874 = semitrusted +# (for twilight.local_annex (rachel@twilight:~/annex)) +#trust aeef7490-ce27-4255-b800-1947706c4a06 = semitrusted +# (for rachel@octavia:~/annex) +#trust c469fbce-f3b4-4e27-a54f-0b747797a7d5 = semitrusted +# (for annex (Biblio's Copy)) +#trust c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = semitrusted +# (for luna.strangenoises.org_annex) +#trust f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = semitrusted +# (for octavia.local_annex (rachel@octavia:~/annex)) +#trust f748a5ed-d870-48fb-b3ec-811488eb2faa = semitrusted +# (for rachel@twilight:~/annex) +#trust fcaba03e-1ba5-11e3-90f1-57fe1467e006 = semitrusted + +# Repository groups +# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) +# (Separate group names with spaces) +# (for rachel@octavia:~/annex) +group 161dec38-e8be-43b8-86c5-555d35ce3416 = client +# (for rachel@celestia.local:~/annex) +group 179fcddf-e247-4577-804b-267feed8abb1 = client +# (for 192.168.1.103_annex (rachel@rainbow.local:~/annex)) +group 256d5762-150d-4d5d-9340-517de298c874 = client +# (for twilight.local_annex (rachel@twilight:~/annex)) +group aeef7490-ce27-4255-b800-1947706c4a06 = client +# (for rachel@octavia:~/annex) +group c469fbce-f3b4-4e27-a54f-0b747797a7d5 = client +# (for annex (Biblio's Copy)) +group c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = client +# (for octavia.local_annex (rachel@octavia:~/annex)) +group f748a5ed-d870-48fb-b3ec-811488eb2faa = client +# (for rachel@twilight:~/annex) +group fcaba03e-1ba5-11e3-90f1-57fe1467e006 = client +# (for luna.strangenoises.org_annex) +group f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = transfer +# (for web) +#group 00000000-0000-0000-0000-000000000001 = + +# Repository preferred contents +# (for rachel@octavia:~/annex) +content 161dec38-e8be-43b8-86c5-555d35ce3416 = standard +# (for rachel@celestia.local:~/annex) +content 179fcddf-e247-4577-804b-267feed8abb1 = standard +# (for 192.168.1.103_annex (rachel@rainbow.local:~/annex)) +content 256d5762-150d-4d5d-9340-517de298c874 = standard +# (for twilight.local_annex (rachel@twilight:~/annex)) +content aeef7490-ce27-4255-b800-1947706c4a06 = standard +# (for rachel@octavia:~/annex) +content c469fbce-f3b4-4e27-a54f-0b747797a7d5 = standard +# (for annex (Biblio's Copy)) +content c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = standard +# (for luna.strangenoises.org_annex) +content f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = standard +# (for octavia.local_annex (rachel@octavia:~/annex)) +content f748a5ed-d870-48fb-b3ec-811488eb2faa = standard +# (for rachel@twilight:~/annex) +content fcaba03e-1ba5-11e3-90f1-57fe1467e006 = standard +# (for web) +#content 00000000-0000-0000-0000-000000000001 = +"""]] + +while the same command in /Volumes/Biblio/annex gives: + +[[!format sh """ +# git-annex configuration +# +# Changes saved to this file will be recorded in the git-annex branch. +# +# Lines in this file have the format: +# setting uuid = value + +# Repository trust configuration +# (Valid trust levels: trusted semitrusted untrusted dead) +# (for web) +#trust 00000000-0000-0000-0000-000000000001 = semitrusted +# (for rachel@octavia:~/annex) +#trust 161dec38-e8be-43b8-86c5-555d35ce3416 = semitrusted +# (for celestia.local (rachel@celestia.local:~/annex)) +#trust 179fcddf-e247-4577-804b-267feed8abb1 = semitrusted +# (for rachel@rainbow.local:~/annex) +#trust 256d5762-150d-4d5d-9340-517de298c874 = semitrusted +# (for rachel@twilight:~/annex) +#trust aeef7490-ce27-4255-b800-1947706c4a06 = semitrusted +# (for rachel@octavia:~/annex) +#trust c469fbce-f3b4-4e27-a54f-0b747797a7d5 = semitrusted +# (for Biblio's Copy) +#trust c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = semitrusted +# (for ) +#trust f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = semitrusted +# (for rachel@octavia:~/annex) +#trust f748a5ed-d870-48fb-b3ec-811488eb2faa = semitrusted +# (for rachel@twilight:~/annex) +#trust fcaba03e-1ba5-11e3-90f1-57fe1467e006 = semitrusted + +# Repository groups +# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted) +# (Separate group names with spaces) +# (for rachel@octavia:~/annex) +group 161dec38-e8be-43b8-86c5-555d35ce3416 = client +# (for celestia.local (rachel@celestia.local:~/annex)) +group 179fcddf-e247-4577-804b-267feed8abb1 = client +# (for rachel@rainbow.local:~/annex) +group 256d5762-150d-4d5d-9340-517de298c874 = client +# (for rachel@twilight:~/annex) +group aeef7490-ce27-4255-b800-1947706c4a06 = client +# (for rachel@octavia:~/annex) +group c469fbce-f3b4-4e27-a54f-0b747797a7d5 = client +# (for Biblio's Copy) +group c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = client +# (for rachel@octavia:~/annex) +group f748a5ed-d870-48fb-b3ec-811488eb2faa = client +# (for rachel@twilight:~/annex) +group fcaba03e-1ba5-11e3-90f1-57fe1467e006 = client +# (for ) +group f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = transfer +# (for web) +#group 00000000-0000-0000-0000-000000000001 = + +# Repository preferred contents +# (for rachel@octavia:~/annex) +content 161dec38-e8be-43b8-86c5-555d35ce3416 = standard +# (for celestia.local (rachel@celestia.local:~/annex)) +content 179fcddf-e247-4577-804b-267feed8abb1 = standard +# (for rachel@rainbow.local:~/annex) +content 256d5762-150d-4d5d-9340-517de298c874 = standard +# (for rachel@twilight:~/annex) +content aeef7490-ce27-4255-b800-1947706c4a06 = standard +# (for rachel@octavia:~/annex) +content c469fbce-f3b4-4e27-a54f-0b747797a7d5 = standard +# (for Biblio's Copy) +content c9e307e2-1189-47ed-8ad4-03b5c1b64e36 = standard +# (for ) +content f36dbdf8-1bba-11e3-9dbe-f33cfb0e2bed = standard +# (for rachel@octavia:~/annex) +content f748a5ed-d870-48fb-b3ec-811488eb2faa = standard +# (for rachel@twilight:~/annex) +content fcaba03e-1ba5-11e3-90f1-57fe1467e006 = standard +# (for web) +#content 00000000-0000-0000-0000-000000000001 = +"""]] + +### What steps will reproduce the problem? + +As above. I have no idea what just happened, but apart from git-annex assistant --stop and having to mop up leftover processes, I didn't use the git-annex commandline for anything. + +### What version of git-annex are you using? On what operating system? + +Mac OS X 10.8.4 + + Version: 4.20130909-ga29f960 + Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi + +### Please provide any additional information below. + +The log on ~/annex/.git/annex/daemon.log is huge and full of transfers of files with my personal filenames. I'd rather not. It appears to end normally. + +Now there is a short log in /Volumes/Biblio/annex/.git/annex/daemon.log from, I guess, the time I tried to restart. For some reason therefore, after the successful session finished, on restart it only looks here. This log is appended. + +[[!format sh """ +[2013-09-12 21:35:39 BST] main: starting assistant version 4.20130909-ga29f960 + +[2013-09-12 21:35:39 BST] TransferScanner: Syncing with celestia.local +Already up-to-date. + +(scanning...) [2013-09-12 21:35:39 BST] Watcher: Performing startup scan +From /Users/rachel/annex + * [new branch] git-annex -> celestia.local/git-annex + * [new branch] master -> celestia.local/master + * [new branch] synced/git-annex -> celestia.local/synced/git-annex + * [new branch] synced/master -> celestia.local/synced/master +Updating 4f974a8..74770d9 +Fast-forward +Already up-to-date. +Already up-to-date. +Already up-to-date. +[2013-09-12 21:36:39 BST] Pusher: Syncing with celestia.local +(merging celestia.local/git-annex celestia.local/synced/git-annex into git-annex...) +(Recording state in git...) + + + + +(started...) error: Ref refs/heads/synced/git-annex is at 5b4ed9b3098e936d60b61a1d3915fa29e8c823d0 but expected 792d2a5c14b0b6327d2089e174063c474ba5a764 +remote: error: failed to lock refs/heads/synced/git-annex +To /Users/rachel/annex + 792d2a5..5b4ed9b git-annex -> synced/git-annex +To /Users/rachel/annex + ! [remote rejected] git-annex -> synced/git-annex (failed to lock) +error: failed to push some refs to '/Users/rachel/annex' +Everything up-to-date +"""]] + +Well, I see that thing about "failed to lock". I can imagine that my 'killall git-annex' to kill a leftover process that was hanging around after I'd done git-annex assistant --stop might have left stale lock files, somewhere... but of course I only got as far as doing that because I was already encountering problems, just trying to return to the webapp. diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_1_3a3891c9d7ee808f6a71780cb628f23d._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_1_3a3891c9d7ee808f6a71780cb628f23d._comment new file mode 100644 index 000000000..a26db0870 --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_1_3a3891c9d7ee808f6a71780cb628f23d._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 1" + date="2013-09-12T21:29:39Z" + content=""" +The git-annex webapp displays a view from \"inside\" one git repsitory at a time. It seems to me that you have two or more local git repositories; one in ~/annex and one on a removable drive. The webapp is coming up viewing from inside your removable drive's repository. You can change the repository that the webapp views by going to the Repository menu in the upper-right corner and selecting Switch repository. The webapp will remember which repository it viewed last, and come back up showing that same repository. + +It's BTW an unusual configuration to have the git-annex assistant directly running on a removable drive as you seem to have done. You must have previously went to the Repository menu and selected \"Add another local repository\", and then added the removable drive, and then connected that repository up to your ~/annex repository. Which would explain why the webapp was last showing the repository on the removable drive. The more usual way to add a removable drive is to use the \"Add another repository\" button and select \"Removable drive\". + +I think, but am not sure, that the error \"Ref refs/heads/synced/git-annex is at 5b4ed9b3098e936d60b61a1d3915fa29e8c823d0 but expected 792d2a5c14b0b6327d2089e174063c474ba5a764\" is due to having two git-annex assistants running in these two different repositories and both updating them both at the same time. You might want to stop all git-annex processes, edit `~/.config/git-annex/autostart` and remove the removable drive repository from that list, leaving only `~/annex` in the list. +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_2_2bc6efb1d9e872cc5d4fbfbaaf5cc10e._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_2_2bc6efb1d9e872cc5d4fbfbaaf5cc10e._comment new file mode 100644 index 000000000..10fad2252 --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_2_2bc6efb1d9e872cc5d4fbfbaaf5cc10e._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="I don't know whether I've fixed it or confused things further" + date="2013-09-12T21:30:44Z" + content=""" +I shut down the daemon that was running from the webapp itself. + +Instead of launching by using the app, I did: + +[[!format txt \"\"\" +celestia:~ rachel$ cd annex/ +celestia:annex rachel$ git-annex assistant +(merging synced/git-annex into git-annex...) +celestia:annex rachel$ git-annex webapp +Launching web browser on file:///Users/rachel/annex/.git/annex/webapp.html +celestia:annex rachel$ +\"\"\"]] + +It opened the webapp. I could see all the repos back again. + +It also seems to be syncing to everything else, sending the files all over again, even though they haven't changed. + +It's just about possible it's completing the job, as I'm not sure I saw the files syncing now, being synced earlier. But... in that earlier session it had run the queue dry, *it* thought it had completed syncing. + +What's going on? +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_3_fff1e778a6334258c173a96e6bf7ef6a._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_3_fff1e778a6334258c173a96e6bf7ef6a._comment new file mode 100644 index 000000000..4d44aaf5c --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_3_fff1e778a6334258c173a96e6bf7ef6a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 3" + date="2013-09-12T21:33:18Z" + content=""" +See my explanation above. By manually starting the webapp inside your ~/annex repository you forced it to view that repository. + +It's not unusual for the webapp to display it syncing some files that have been synced before. This repository may not be up-to-date on which files have been sent where, and it will quickly notice the file has already been transferred and skip doing anything for that file. +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_4_2a86da97a89e28f0a0f5e160d4932ae6._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_4_2a86da97a89e28f0a0f5e160d4932ae6._comment new file mode 100644 index 000000000..16a5a351f --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_4_2a86da97a89e28f0a0f5e160d4932ae6._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="Last night's comment" + date="2013-09-13T10:28:02Z" + content=""" +> It's BTW an unusual configuration to have the git-annex assistant directly running on a removable drive as you seem to have done. You must have previously went to the Repository menu and selected \"Add another local repository\", and then added the removable drive, and then connected that repository up to your ~/annex repository. Which would explain why the webapp was last showing the repository on the removable drive. The more usual way to add a removable drive is to use the \"Add another repository\" button and select \"Removable drive\". + +That is exactly how I'd added that repository, yes. I didn't notice the dedicated \"removable drive\" option until later. :-) I thought it possibly appropriate to leave it that way because, while Biblio is an external drive and remov*able*, in practice I never remove it; it's a permanent fixture. + +After all, this is a mac mini server, originally (no longer running Server) so it has a second *internal* drive. It would have been even more logical for me to have added a second repo on there in the same manner, as it's most definitely not removable without extreme effort; but it still mounts inside /Volumes, and presumably if I'd added it as a non-removable repo, I'd have had the same problem? + +> It's not unusual for the webapp to display it syncing some files that have been synced before. This repository may not be up-to-date on which files have been sent where, and it will quickly notice the file has already been transferred and skip doing anything for that file. + +Yes, that's probably what happened. It finished pretty quickly, about a minute after sending my previous comment. + +Going to bed now, but tomorrow I'll follow the remaining suggestions; basically I'll remove the repo on the external drive then, if I still want it there, I'll add it back in the other way, so it thinks of it as removable. + +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_5_41b8e8e58025cc8c8f12efb9a51acd29._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_5_41b8e8e58025cc8c8f12efb9a51acd29._comment new file mode 100644 index 000000000..685d1b024 --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_5_41b8e8e58025cc8c8f12efb9a51acd29._comment @@ -0,0 +1,50 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="And this morning..." + date="2013-09-13T10:38:35Z" + content=""" +I tried removing the second repo, by deleting it, it seemed to begin normally. Then it just hung, and hung. + +Looking at logs, it seemed to be hung on dropping one file - a very small file in fact, but it was probably the most recent file to be added. So the end of the log just looked like: + +[[!format txt \"\"\" +drop annex old stuff/renegade/issue7back.pdf ok +drop annex old stuff/renegade/issue7fiction.pdf ok +drop annex postgresql 9.0->9.1 upgrade process +\"\"\"]] + +After a while I started getting problems in other terminal shells where I was doing stuff unrelated to git annex. eg: on trying to open a new terminal window, it would open, then shut immediately, or it would open with just: + +[[!format txt \"\"\" +forkpty: Resource temporarily unavailable +Could not create a new process and open a pseudo-tty. +\"\"\"]] + +Various other commands that would have resulted in a fork were failing too. In the end I shut down git annex (using the shutdown daemon open in the menu in the webapp), and everything went back to normal. + +This is the end of the daemon.log from this morning. I don't want to paste the whole thing, as essentially it lists all my private filenames, and there's a lot. In fact I wonder if the quantity of files may be a factor: + +[[!format txt \"\"\" +drop annex old stuff/renegade/index.html ok +drop annex old stuff/renegade/issue1.pdf ok +drop annex old stuff/renegade/issue2.pdf ok +drop annex old stuff/renegade/issue3.pdf ok +drop annex old stuff/renegade/issue4.pdf ok +drop annex old stuff/renegade/issue4coverpic.pdf ok +drop annex old stuff/renegade/issue6articles.pdf ok +drop annex old stuff/renegade/issue6cover.pdf ok +drop annex old stuff/renegade/issue6fiction.pdf ok +drop annex old stuff/renegade/issue7articles.pdf ok +drop annex old stuff/renegade/issue7back.pdf ok +drop annex old stuff/renegade/issue7fiction.pdf ok +drop annex postgresql 9.0->9.1 upgrade process [2013-09-13 11:25:07 BST] NetWatcherFallback: Syncing with twilight.local_annex, octavia.local_annex, 192.168.1.103_annex, luna.strangenoises.org_annex +NetWatcherFallback crashed: git: createProcess: resource exhausted (Resource temporarily unavailable) +[2013-09-13 11:25:07 BST] NetWatcherFallback: warning NetWatcherFallback crashed: git: createProcess: resource exhausted (Resource temporarily unavailable) +recv: resource vanisrhreeecdcv v:(: C rorenesnsoeoucurtrciceoe n v varanenisiseshthe edbd y ( (CpCoeonennrne)ec +cttiioonn rreesseett bbyy ppeeeerr)) + +[2013-09-13 11:26:32 BST] main: warning git-annex has been shut down +\"\"\"]] + +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_6_38afcd8e7fb278ca0ee2e9e0c9f6883e._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_6_38afcd8e7fb278ca0ee2e9e0c9f6883e._comment new file mode 100644 index 000000000..c0923b22a --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_6_38afcd8e7fb278ca0ee2e9e0c9f6883e._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="comment 6" + date="2013-09-13T10:52:07Z" + content=""" +FYI, if there's any relevance to the number of files in the annex, there are 1899 files in the annex at the moment, so that many in the one being deleted. The one it hung on, \"postgresql 9.0->9.1 upgrade process\" was indeed the last one that comes up in a find command, which I think means the most recently added to this dir. + +Creating too many threads? +"""]] diff --git a/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_7_06de36dcde4c52ab74c8134f3242ac02._comment b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_7_06de36dcde4c52ab74c8134f3242ac02._comment new file mode 100644 index 000000000..c11630ef7 --- /dev/null +++ b/doc/bugs/On_restart__44___most_repositories__44___including_original_one__44___gone./comment_7_06de36dcde4c52ab74c8134f3242ac02._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="comment 7" + date="2013-09-13T10:54:37Z" + content=""" +... and resolved for myself by just deleting (dropping in the trash for now) the annex on the external volume, restarting git-annex assistant and *disabling* that repo from the menu rather than deleting it. + +"""]] 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 index d63394b02..c127bac15 100644 --- 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 @@ -77,4 +77,8 @@ Any thoughts on how I can get git-annex (esp. fsck) to complete would be appreci Thanks Giovanni -[[!tag moreinfo]] +> [[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_6_9e3300b223dd54a3f07c650f5cf70ae0._comment b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_6_9e3300b223dd54a3f07c650f5cf70ae0._comment new file mode 100644 index 000000000..b648eb9a4 --- /dev/null +++ b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_6_9e3300b223dd54a3f07c650f5cf70ae0._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..c7832477c --- /dev/null +++ b/doc/bugs/Out_of_memory_error_in_fsck_whereis_find_and_status_cmds/comment_7_b91f4a87b6d29ae6b4262922fd65a79d._comment @@ -0,0 +1,8 @@ +[[!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/Problem_when_dropping_unused_files.mdwn b/doc/bugs/Problem_when_dropping_unused_files.mdwn new file mode 100644 index 000000000..2c15680b8 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files.mdwn @@ -0,0 +1,21 @@ +### Please describe the problem. + +While dropping 19 unused files from an annex, I got this error: + + error: invalid object 100644 c873416e78db4dd94b6ab40470d6fe99b2ecb8bd for '002/0a6/SHA256E-s427690--03aeabcde841b66168b72de80098d74e047f3ffc832d4bbefa1f2f70ee6c92f8.jpg.log' + fatal: git-write-tree: error building trees + git-annex: failed to read sha from git write-tree + +I've actually seen this before, a few months ago. + +### What steps will reproduce the problem? + +I have no idea, but once it happens I can't interact with unused files anymore. Also, `git annex fsck` now reports this same problem as well. + +### What version of git-annex are you using? On what operating system? + +git-annex version: 4.20130815, OS X 10.8.4 + +> [[done]]; no indication this is anything other than a corrupt git +> repository, which can be caused by system crash, disk data loss, +> cosmic rays, etc. This is why we keep backups... --[[Joey]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment new file mode 100644 index 000000000..9c0e25528 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_10_d4f6bfe8e04560fc661a47b09ed8a5f4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.251.174" + subject="comment 10" + date="2013-09-07T17:14:36Z" + content=""" +Again this error message has nothing to do with git-annex beyond it being a file in the git-annex branch that is corrupt. Your system seems to be repeatedly corrupting git repositories. You need to run `git fsck`, get the git repository in a clean state, and probably check the drive it's on, and run a memory test or otherwise deal with whatever is causing your system to corrupt files in the git repository. +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment new file mode 100644 index 000000000..0e39a96fc --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_1_e1a99bd3eb8b3186653b52a52b1836de._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 1" + date="2013-08-24T05:01:37Z" + content=""" +The following command restored some sanity: + + find .git/annex/ -name '*.log' -delete +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment new file mode 100644 index 000000000..e0c5a2882 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_2_dec3e5ffe5cfdc439f418ee00d7d9810._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="arand" + ip="130.243.226.21" + subject="comment 2" + date="2013-08-24T11:40:54Z" + content=""" +If I recall, such files being stored in the annex object store is a result of using direct mode? +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment new file mode 100644 index 000000000..8c739552d --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_3_d106a87101db52f957da84d90dafcdbb._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 3" + date="2013-08-24T16:04:21Z" + content=""" +Unfortunately, the git error message you pasted suggests very strongly that your git repository has gotten corrupted. You can probably verify that by running `git annex fsck`. Assuming it is corrupted, the best thing to do is to make a new clone and move .git/annex and .git/config over from the corrupted repository to it, and finally run `git annex fsck` + +You then seem to have some reason decided to go delete git-annex's .git/annex/journal/*.log files, which are just files that have not yet been committed to the git-annex branch. The only reason this \"restored some sanity\" is that git-annex was trying to commit that data to git, and failing because your git repository is corrupted. + +(This has nothing at all to do with direct mode.) +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment new file mode 100644 index 000000000..ba2e693ee --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_4_f28ed0635612693e437e64d872af5c37._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 4" + date="2013-08-25T05:27:57Z" + content=""" +Do you have any thoughts on why it may have gotten corrupted, or why it seems to happen so commonly with large git-annex repositories? I've seen this exact same sort of error while processing log files maybe 5 or 6 times now. +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment new file mode 100644 index 000000000..4ad874c08 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_5_f0237075653768c84deb702442645f28._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 5" + date="2013-08-25T05:50:35Z" + content=""" +I meant to say, in 5 or 6 different repositories. Further, when I see it happen the next time, how do you recommend I track down the real problem, instead of always just cloning and starting over? +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment new file mode 100644 index 000000000..60f2165e2 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_6_b509006e1590480a104627369bc910f2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 6" + date="2013-08-30T04:19:57Z" + content=""" +Just saw it happen again today, in a repository that passed \"fsck -A\" multiple times just yesterday. What is going on? +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment new file mode 100644 index 000000000..6f3e42f5c --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_7_fe261c074211ccb94bbcb32cfd8ee654._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 7" + date="2013-08-30T04:25:45Z" + content=""" +I tried your suggestion of cloning the repository and moving `.git/config` and `.git/annex`, and got this: + + fsck Astronomy/12_ATM_2.jpg error: invalid object 100644 06f8fe222f052100101e5c2e77640f2ec3efff98 for '002/0a6/SHA256E-s427690--03aeabcde841b66168b72de80098d74e047f3ffc832d4bbefa1f2f70ee6c92f8.jpg.log' + fatal: git-write-tree: error building trees + git-annex: failed to read sha from git write-tree + +What else can I try? Note that I can't even find this `.log` anywhere under my `.git` directory for this repository. +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment new file mode 100644 index 000000000..0b82af2f1 --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_8_bc8e4dc7e0d6577ba5fcc98f56627b1f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 8" + date="2013-08-30T04:30:14Z" + content=""" +The only thing that worked was nuking `.git/annex/index` and letting `git-annex sync` rebuild it. +"""]] diff --git a/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment b/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment new file mode 100644 index 000000000..b75b3f61b --- /dev/null +++ b/doc/bugs/Problem_when_dropping_unused_files/comment_9_e9a22aa2ebcde5f6595b49dba9375761._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89" + nickname="John" + subject="comment 9" + date="2013-08-30T06:20:58Z" + content=""" +And yet again it happens: + + error: invalid object 100644 3edb1d4a44ffba1ea1491693ae7d9faa82aad717 for '000/4ce/SHA256E-s175006724--a0edc4f880223028b3fa3a27b142c8e027ddf66db973b8272ca845a4a9e01d3e.mp4.log' fatal: git-write-tree: error building trees + +This was in a repository that was working perfectly well until I tried to `git-annex get`. The weird thing is that I don't even have any `SHA256E` files anymore. + +I think that after my recent migration, none of my repositories can be trusted. This is just happening too often (more than 10 times in the last week, across many repositories on many machines). I will just rebuild them all. But I do wish git-annex was more resilient about this. +"""]] diff --git a/doc/bugs/Resource_exhausted.mdwn b/doc/bugs/Resource_exhausted.mdwn index eae2ba8d3..3f125b08a 100644 --- a/doc/bugs/Resource_exhausted.mdwn +++ b/doc/bugs/Resource_exhausted.mdwn @@ -41,5 +41,5 @@ I'm interested in your thoughts. Best, Laszlo -[[!tag /design/assistant moreinfo]] +[[!tag /design/assistant]] [[!meta title="assistant can try to add too many files at once in batch add mode"]] diff --git a/doc/bugs/Resource_exhausted/comment_10_bccf9528ffe963154c92ce49762e7ea6._comment b/doc/bugs/Resource_exhausted/comment_10_bccf9528ffe963154c92ce49762e7ea6._comment new file mode 100644 index 000000000..da2a15ba2 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_10_bccf9528ffe963154c92ce49762e7ea6._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="comment 10" + date="2013-08-26T18:33:40Z" + content=""" +@Joey: it was a \"pretty large\" transfer, several hundred gigabytes in perhaps ~100000 files. The copying was going to a GPG-encrypted directory remote. +The error only happened once or twice so far. Point taken about find in /proc; I'll do that if it happens next time. + +"""]] diff --git a/doc/bugs/Resource_exhausted/comment_5_f55d933bce77fd2185ebd0cc46fe57ec._comment b/doc/bugs/Resource_exhausted/comment_5_f55d933bce77fd2185ebd0cc46fe57ec._comment new file mode 100644 index 000000000..19bcdb376 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_5_f55d933bce77fd2185ebd0cc46fe57ec._comment @@ -0,0 +1,64 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="I just reproduced this with the latest version" + date="2013-08-11T03:17:11Z" + content=""" +At some point during a large copy, there's an ever increasing number of pipes in /proc/git-annex-pid/fd +As soon as it hits the limit (1023 in my case), copies start failing + + etc + r-x------ 1 michael michael 64 Aug 10 20:14 851 -> pipe:[2250609] + l-wx------ 1 michael michael 64 Aug 10 20:14 852 -> pipe:[2251549] + lr-x------ 1 michael michael 64 Aug 10 20:14 853 -> pipe:[2251550] + l-wx------ 1 michael michael 64 Aug 10 20:14 854 -> pipe:[2250612] + lr-x------ 1 michael michael 64 Aug 10 20:14 855 -> pipe:[2250613] + l-wx------ 1 michael michael 64 Aug 10 20:14 856 -> pipe:[2246639] + lr-x------ 1 michael michael 64 Aug 10 20:14 857 -> pipe:[2246640] + l-wx------ 1 michael michael 64 Aug 10 20:14 858 -> pipe:[2246642] + lr-x------ 1 michael michael 64 Aug 10 20:14 859 -> pipe:[2246643] + l-wx------ 1 michael michael 64 Aug 10 20:13 86 -> pipe:[2241378] + l-wx------ 1 michael michael 64 Aug 10 20:14 860 -> pipe:[2246645] + lr-x------ 1 michael michael 64 Aug 10 20:14 861 -> pipe:[2246646] + l-wx------ 1 michael michael 64 Aug 10 20:14 862 -> pipe:[2246648] + lr-x------ 1 michael michael 64 Aug 10 20:14 863 -> pipe:[2246649] + l-wx------ 1 michael michael 64 Aug 10 20:14 864 -> pipe:[2246653] + lr-x------ 1 michael michael 64 Aug 10 20:14 865 -> pipe:[2246654] + lr-x------ 1 michael michael 64 Aug 10 20:14 866 -> pipe:[2249407] + l-wx------ 1 michael michael 64 Aug 10 20:14 867 -> pipe:[2251789] + l-wx------ 1 michael michael 64 Aug 10 20:14 868 -> pipe:[2250627] + lr-x------ 1 michael michael 64 Aug 10 20:14 869 -> pipe:[2250628] + lr-x------ 1 michael michael 64 Aug 10 20:13 87 -> pipe:[2241379] + l-wx------ 1 michael michael 64 Aug 10 20:14 870 -> pipe:[2251778] + lr-x------ 1 michael michael 64 Aug 10 20:14 871 -> pipe:[2251779] + l-wx------ 1 michael michael 64 Aug 10 20:14 872 -> pipe:[2251781] + lr-x------ 1 michael michael 64 Aug 10 20:14 873 -> pipe:[2251782] + l-wx------ 1 michael michael 64 Aug 10 20:14 874 -> pipe:[2250635] + lr-x------ 1 michael michael 64 Aug 10 20:14 875 -> pipe:[2250636] + l-wx------ 1 michael michael 64 Aug 10 20:14 876 -> pipe:[2251575] + lr-x------ 1 michael michael 64 Aug 10 20:14 877 -> pipe:[2251576] + l-wx------ 1 michael michael 64 Aug 10 20:14 878 -> pipe:[2251785] + lr-x------ 1 michael michael 64 Aug 10 20:14 879 -> pipe:[2251786] + l-wx------ 1 michael michael 64 Aug 10 20:13 88 -> pipe:[2247853] + l-wx------ 1 michael michael 64 Aug 10 20:14 880 -> pipe:[2249430] + lr-x------ 1 michael michael 64 Aug 10 20:14 881 -> pipe:[2249431] + l-wx------ 1 michael michael 64 Aug 10 20:14 882 -> pipe:[2251581] + lr-x------ 1 michael michael 64 Aug 10 20:14 883 -> pipe:[2251582] + l-wx------ 1 michael michael 64 Aug 10 20:14 884 -> pipe:[2250653] + lr-x------ 1 michael michael 64 Aug 10 20:14 885 -> pipe:[2250654] + lr-x------ 1 michael michael 64 Aug 10 20:14 886 -> pipe:[2251790] + l-wx------ 1 michael michael 64 Aug 10 20:14 887 -> pipe:[2250670] + l-wx------ 1 michael michael 64 Aug 10 20:14 888 -> pipe:[2250663] + lr-x------ 1 michael michael 64 Aug 10 20:14 889 -> pipe:[2250664] + lr-x------ 1 michael michael 64 Aug 10 20:13 89 -> pipe:[2247854] + l-wx------ 1 michael michael 64 Aug 10 20:14 890 -> pipe:[2250668] + lr-x------ 1 michael michael 64 Aug 10 20:14 891 -> pipe:[2250669] + lr-x------ 1 michael michael 64 Aug 10 20:14 892 -> pipe:[2250671] + l-wx------ 1 michael michael 64 Aug 10 20:14 894 -> pipe:[2251601] + lr-x------ 1 michael michael 64 Aug 10 20:14 895 -> pipe:[2251602] + lr-x------ 1 michael michael 64 Aug 10 20:13 9 -> pipe:[2241268] + lr-x------ 1 michael michael 64 Aug 10 20:13 90 -> pipe:[2242273] + l-wx------ 1 michael michael 64 Aug 10 20:13 91 -> pipe:[2245776] + etc + +"""]] diff --git a/doc/bugs/Resource_exhausted/comment_6_26c98fca45b029a527f9684873db4be5._comment b/doc/bugs/Resource_exhausted/comment_6_26c98fca45b029a527f9684873db4be5._comment new file mode 100644 index 000000000..b95b6cfa2 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_6_26c98fca45b029a527f9684873db4be5._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="comment 6" + date="2013-08-11T03:20:37Z" + content=""" +with every + + git annex + copy blah/blah/blah (to testremote...) + git-annex: runInteractiveProcess: pipe: Too many open files + failed + +The number of open fd's by git-annex increases by 1. + +4.20130802 built with cabal on Ubuntu 13.04 + +"""]] diff --git a/doc/bugs/Resource_exhausted/comment_7_8bab413b472f900e04977db2bc3951b6._comment b/doc/bugs/Resource_exhausted/comment_7_8bab413b472f900e04977db2bc3951b6._comment new file mode 100644 index 000000000..1b050aa33 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_7_8bab413b472f900e04977db2bc3951b6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="comment 7" + date="2013-08-11T03:21:45Z" + content=""" +...increases in the failing case, that is. This doesn't happen all the time. +"""]] diff --git a/doc/bugs/Resource_exhausted/comment_8_e9bec0b80179b1229b6af0979a21c727._comment b/doc/bugs/Resource_exhausted/comment_8_e9bec0b80179b1229b6af0979a21c727._comment new file mode 100644 index 000000000..2135211cd --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_8_e9bec0b80179b1229b6af0979a21c727._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="comment 8" + date="2013-08-11T20:44:19Z" + content=""" +It also looks like the location log has got corrupted (files are actually present, but not recorded in the location log) somewhere along the lines as I was trying to get/drop to figure out what's going on. +Explicitly dropping files then getting files fixes the location log issue. +"""]] diff --git a/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment b/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment new file mode 100644 index 000000000..0e06f5af9 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 9" + date="2013-08-24T19:10:21Z" + content=""" +@Michael how large a copy are you doing? And what kind of remote are you copying the files to? +It would be helpful if you could be more specific about something I could do to reproduce the problem. Without a test case, I am unlikely to fix the bug. With a test case, I'd be surprised if it took long to fix it. + +If you have a process running that is experiencing the problem, you can also narrow it down a *lot* by looking at what these leaking pipe file descriptors are pipes to. For example, if you have: + +lr-x------ 1 michael michael 64 Aug 10 20:14 895 -> pipe:[2251602] + +You can run `find /proc/ -ls 2251602` and find the process at other end of the pipe, and look its pid up in ps to see what command it is. +"""]] diff --git a/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn b/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn new file mode 100644 index 000000000..9a67db0c6 --- /dev/null +++ b/doc/bugs/S3_buckets_with_capital_letters_breaks_authentication.mdwn @@ -0,0 +1,32 @@ +### 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/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment b/doc/bugs/S3_memory_leaks/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment new file mode 100644 index 000000000..0523fd473 --- /dev/null +++ b/doc/bugs/S3_memory_leaks/comment_1_a7268213b090bce6b1f1858a8e23d90e._comment @@ -0,0 +1,14 @@ +[[!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/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt new file mode 100644 index 000000000..7eaf2a71b --- /dev/null +++ b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__.txt @@ -0,0 +1,46 @@ +> git annex status +supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL +supported remote types: git gcrypt S3 bup directory rsync web webdav glacier hook +repository mode: indirect +trusted repositories: 0 +semitrusted repositories: 8 + 00000000-0000-0000-0000-000000000001 -- web + 44AF00F1-511F-4902-8235-DFF741B09400 -- here + 44af00f1-511f-4902-8235-dff741b09400 -- chrissy + 53499200-CA18-4B51-B6B3-651C18208349 -- stevedave + 56C56658-0995-4613-8A1B-B2FA534A834C -- olaf + 8FE9B19F-4FC8-4CFA-AD89-4B70EB432EDC -- passport + AFC75641-B34A-4644-B566-C8D3127823F7 -- glacier + B3238A12-D81B-40EA-BE89-3BDB318AE2B7 -- brodie +untrusted repositories: 0 +transfers in progress: none +available local disk space: 78.8 gigabytes (+1 gigabyte reserved) +local annex keys: 3915 +local annex size: 81.37 gigabytes +known annex keys: 5728 +known annex size: 641.36 gigabytes +bloom filter size: 16 mebibytes (0.8% full) +backend usage: + SHA256E: 8716 + URL: 927 + +> git annex version +git-annex version: 4.20130909 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents 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 + +> git-annex intentionally treats UUIDs as opaque strings, +> so it is not going to go to any bother to consider +> different byte sequences to be the same UUID, sorry. +> (The standard may be arbitrarily complicated, but I have arbitrarily +> decided to ignore it.) +> +> Since git-annex only ever generates each UUID once, and copies +> the exact sequence of bytes as necessary, the only way the situation +> you show above can happen is if you have manually gone in and entered +> UUIDs in two different cases. +> +> [[done]] --[[Joey]] diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment new file mode 100644 index 000000000..b1417816f --- /dev/null +++ b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_1_00b52dba3bc30516e06c44cbfd3a05a2._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" + nickname="Richard" + subject="comment 1" + date="2013-09-12T09:44:54Z" + content=""" +There does not seem to be an actual bug description in here. Can you provide more info? + +To answer the actual question: RFC 4122 clearly answers no: + + Each field is treated as an integer and has its value printed as a + zero-filled hexadecimal digit string with the most significant + digit first. The hexadecimal values \"a\" through \"f\" are output as + lower case characters and are case insensitive on input. + +Yes, that means that git-annex prints them wrongly as that's upper case. +"""]] diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment new file mode 100644 index 000000000..f07a7bf9d --- /dev/null +++ b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_2_8f5fa659c2ab91b1757bac31cd3b15eb._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" + nickname="Richard" + subject="comment 2" + date="2013-09-12T09:49:56Z" + content=""" +What OS are you using? + +versions 4.20130827 and 4.20130911 on Debian Sid print UUIDs which are lower case, as should be expected. +"""]] diff --git a/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment new file mode 100644 index 000000000..76f6c0742 --- /dev/null +++ b/doc/bugs/Should_UUID__39__s_for_Remotes_be_case_sensitive__63__/comment_3_ccf9623d60c58d036d8bf24757e50de3._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q" + nickname="Andrew" + subject="comment 3" + date="2013-09-12T16:24:30Z" + content=""" +This is on OSX 10.8.4 + +If you look at the remote \"chrissy\" and \"here\" they are the same uuid, but with different case. +"""]] diff --git a/doc/bugs/Stale_lock_files_on_Android.mdwn b/doc/bugs/Stale_lock_files_on_Android.mdwn index 77ebc0890..b3451a153 100644 --- a/doc/bugs/Stale_lock_files_on_Android.mdwn +++ b/doc/bugs/Stale_lock_files_on_Android.mdwn @@ -35,3 +35,10 @@ fatal: Unable to create '/mnt/sdcard/reference/.git/index.lock': File exists. # End of transcript or log. """]] + +> The '/mnt/sdcard/reference/.git/index.lock' lock file will now be +> automatically dealt with. Have not done anything about the refs/remotes +> lock files yet. --[[Joey]] +> +> Now the assistant deals with all stale git lock files on startup. +> [[done]] --[[Joey]] diff --git a/doc/bugs/Too_much_system_load_on_startup.mdwn b/doc/bugs/Too_much_system_load_on_startup.mdwn new file mode 100644 index 000000000..fc514ca73 --- /dev/null +++ b/doc/bugs/Too_much_system_load_on_startup.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. +When I log in, if git annex is monitoring a large repo, my desktop is very sluggish getting started. Git-annex causes moderate CPU load, but keeps the disk IO very busy -delaying the opening of desktop applications. + +### What steps will reproduce the problem? +On Linux, with git-annex set to autostart and monitoring a folder with more than a few hundred files (I have a pdf library of a few thousand journal articles). + +### What version of git-annex are you using? On what operating system? +4.20131002 Ubuntu, from Hess's PPA. + +### Please provide any additional information below. + +I solved this problem by changing the call to git-annex in /etc/xdg/autostart/git-annex.desktop from: + +Exec=/usr/bin/git-annex assistant --autostart + +to + +Exec=sleep 5 ionice -c 3 /usr/bin/git-annex assistant --autostart + +This delays the start of git-annex for 5 seconds, letting the desktop get started, and forces git-annex to yield IO to other programs -preventing it from slowing them down by forcing them to wait for disk access. Since this is a background daemon with potentially high IO usage, but no need for quick responsiveness, perhaps that would make a decent default? + +> Added 5 second delay to existing ionice. Provisionally [[done]], +> although it does occur to me that the startup scan could add some delays +> in between actions to run more as a batch job. --[[Joey]] diff --git a/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment b/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment new file mode 100644 index 000000000..31e735985 --- /dev/null +++ b/doc/bugs/Too_much_system_load_on_startup/comment_1_4470cddc0965062588acff1bc77285e9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-10-26T16:44:59Z" + content=""" +git-annex version 4.20131002 *already* ionices itself on startup, assuming it detects a system it can do that on. So the only relevant change you made is delaying it from starting. I have made the assistant wait 5 seconds before running the startup scan when autostarted. +"""]] diff --git a/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn b/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn new file mode 100644 index 000000000..0d9b4f648 --- /dev/null +++ b/doc/bugs/Transfers_continue_after_daemon_stopped.mdwn @@ -0,0 +1,5 @@ +After creating a new pairing, I stopped the daemon through the webapp while it was syncing. The webapp shut down and was no longer accessible, but git-annex continued running in the background, along with git-annex-shell, and they continued to run new transfers with new rsync processes. This continued until I killed them all. + +I expected that when I stopped the daemon in the webapp, all git-annex processes and all transfers would stop. + +Using the 20131101 tarball. diff --git a/doc/bugs/Transfers_continue_after_daemon_stopped/comment_1_39eb527d64367e6762281246f1d49b1f._comment b/doc/bugs/Transfers_continue_after_daemon_stopped/comment_1_39eb527d64367e6762281246f1d49b1f._comment new file mode 100644 index 000000000..9d504f743 --- /dev/null +++ b/doc/bugs/Transfers_continue_after_daemon_stopped/comment_1_39eb527d64367e6762281246f1d49b1f._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-11-05T16:01:14Z" + content=""" +I've checked, and shutting down the daemon does cause it to stop any transfers it is running. + +However, this does not stop other transfers initiated by the other paired computer. + +I'm ambivilant about whether local pairing should only allow transfers when both daemons are running. +"""]] diff --git a/doc/bugs/Unable_to_import_feed.mdwn b/doc/bugs/Unable_to_import_feed.mdwn new file mode 100644 index 000000000..49dc21bfe --- /dev/null +++ b/doc/bugs/Unable_to_import_feed.mdwn @@ -0,0 +1,27 @@ +Using `git-annex version: 4.20130802` on Debian unstable, when trying to add the feed at <http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml>, I get: + +[[!format sh """ +importfeed http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml +--2013-08-16 09:14:13-- http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml +Auflösen des Hostnamen »www.ndr.de (www.ndr.de)«... 212.201.100.171, 212.201.100.187 +Verbindungsaufbau zu www.ndr.de (www.ndr.de)|212.201.100.171|:80... verbunden. +HTTP-Anforderung gesendet, warte auf Antwort... 200 OK +Länge: 61809 (60K) [application/xml] +In »»/tmp/feed4404«« speichern. + +100%[============================================>] 61.809 --.-K/s in 0,03s + +2013-08-16 09:14:13 (2,20 MB/s) - »»/tmp/feed4404«« gespeichert [61809/61809] + +failed +git-annex: importfeed: 1 failed +"""]] + +(Oh, and using `format` with nono-ASCII seems to break down., at least in the preview.) + +> I'm going to close this since I've narrowed it down to a bug in the +> upstream feed library. [[done]]. Of course, if we get a lot of reports of +> the library not working, I may need to revisit using it, but for now this +> seems an isolated problem. Also, I tried validating the feed, and it is +> not 100% valid, and one of the validity problems is a missing enclosure +> length. --[[Joey]] diff --git a/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment b/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment new file mode 100644 index 000000000..7c9c1e129 --- /dev/null +++ b/doc/bugs/Unable_to_import_feed/comment_1_16230fbbb996e165b84787ed4d5f72ea._comment @@ -0,0 +1,45 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 1" + date="2013-08-23T18:09:27Z" + content=""" +When I try this, without the German translation, I get: + +<pre> +joey@gnu:~/tmp/newrepo>git annex importfeed 'http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml' +(checking known urls...) +importfeed http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml +--2013-08-23 13:58:19-- http://www.ndr.de/fernsehen/sendungen/extra_3/videos/zum_mitnehmen/extradrei196_version-hq.xml +Resolving www.ndr.de (www.ndr.de)... 23.73.180.154, 23.73.180.115 +Connecting to www.ndr.de (www.ndr.de)|23.73.180.154|:80... connected. +HTTP request sent, awaiting response... 200 OK +Length: 61865 (60K) [application/xml] +Saving to: ‘/home/joey/tmp/feed31120’ + +100%[======================================>] 61,865 151KB/s in 0.4s + +2013-08-23 13:58:25 (151 KB/s) - ‘/home/joey/tmp/feed31120’ saved [61865/61865] + + + warning: bad feed content +</pre> + +It seems you left out the last line of the error. + +The feed library seems to fail to find any of the enclosures in this feed, although it is able to parse it as far as finding the individual items in the feed: + +<pre> +Prelude Text.Feed.Query Text.Feed.Import> f <- parseFeedFromFile \"extradrei196_version-hq.xml\" +Prelude Text.Feed.Query Text.Feed.Import> map getItemEnclosure $ feedItems f +[Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing,Nothing] +</pre> + +The feed *appears* to contain enclosures, for example: + +<pre> +<enclosure url=\"http://media.ndr.de/progressive/2013/0821/TV-20130821-2329-5942.hq.mp4\" type=\"video/mp4\"/> +</pre> + +It may not be well-formed, or the feed library may have a bug. Assuming the latter, I have filed a bug report on the feed library: https://github.com/sof/feed/issues/3 +"""]] diff --git a/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn b/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn new file mode 100644 index 000000000..6bb6c0782 --- /dev/null +++ b/doc/bugs/Unable_to_use_remotes_with_space_in_the_path.mdwn @@ -0,0 +1,35 @@ +### Please describe the problem. + +Git annex can't use remotes with the type "file://" if the path contains spaces + +### What steps will reproduce the problem? + +- Create one repository with a space in the path (and initialize annex in it) +- Clone that repo to an other directory (and initialize annex also in that) +- add a file to the first repository in the annex way +- chdir to the second repository and try to get that file, it won't work (also after git pull or git sync pull) + +Check this typescripts for a more detailed description + +<http://uz.sns.it/~enrico/git-annex-bugreport.txt> + +<http://pastebin.com/f8wkDNrG> (thanks mhameed for that data) + + +### What version of git-annex are you using? On what operating system? + +I'm using debian testing (jessie) on a i386 machine. + +`git-annex` version: 4.20130521 (according to apt data and `git annex version`) + +`git-annex` build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP + +`git` version: 1.7.10.4 + + +### Please provide any additional information below. + +I don't use git annex assistant nor the webapp + +> Tested and only file:// and not other urls have this problem. +> guilhem provided a fix. [[done]] --[[Joey]] diff --git a/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment new file mode 100644 index 000000000..a54d53c58 --- /dev/null +++ b/doc/bugs/Unfortunate_interaction_with_Calibre/comment_5_fc4d5301797589e92cc9a24697b2155d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="https://lot-of-stuff.info/" + nickname="__DL__" + subject="Another solution." + date="2013-08-13T16:39:17Z" + content=""" +calibre store all the metadata for safekeeping of the metadata +(author, title...). + +If like me you do not like much direct mode (because of its not so +cool interaction with plain git), you could use the largfiles config +to let those files in plain git. You will then also need something for +the database. See [[tips/Git_annex_and_Calibre]] for a full solution. + +"""]] diff --git a/doc/bugs/Unknown_command___39__list__39__.mdwn b/doc/bugs/Unknown_command___39__list__39__.mdwn new file mode 100644 index 000000000..f08fc6eef --- /dev/null +++ b/doc/bugs/Unknown_command___39__list__39__.mdwn @@ -0,0 +1,15 @@ +### Please describe the problem. + +The man page claims there exists a query command 'list' but: + + % git annex list somefile + git-annex: Unknown command 'list' + +### What version of git-annex are you using? On what operating system? + +man page online and git-annex version 4.20130909. + +> Your last line explains the problem. The online man page +> documents the latest release, or in some cases +> unrelased git version. You have a version 2 releases old installed. +> [[done]] --[[Joey]] diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment b/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment new file mode 100644 index 000000000..7566dc1ef --- /dev/null +++ b/doc/bugs/Unknown_command___39__list__39__/comment_1_c625d03d1ed2019141ac9202f933466d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://cstork.org/" + nickname="Chris Stork" + subject="News page stopped listing latest releases?" + date="2013-09-30T16:08:18Z" + content=""" +Ah, cabal tells me that 4.20130927 is out now. I missed that because I thought that the [News](http://git-annex.branchable.com/news/) page is 'authoritative' :-) and it's still advertising 4.20130909. Sorry about that. +"""]] diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment b/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment new file mode 100644 index 000000000..f8592b571 --- /dev/null +++ b/doc/bugs/Unknown_command___39__list__39__/comment_2_800e1b6417768bdadda311ebfb5df637._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.80" + subject="comment 2" + date="2013-09-30T16:23:31Z" + content=""" +I've had a bit of a mess with cabal. First my release scripts apparently broke and didn't upload the last 2 releases there. Then when I manually fixed that, hackage has been upgraded to a new version, which is broken and will not accept tarballs > 1 mb. So I had to re-upload git-annex hacked to fit in 1 mb (removing all documentation), and I did so from a current git snapshot. Meh. +"""]] diff --git a/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment b/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment new file mode 100644 index 000000000..1899029ad --- /dev/null +++ b/doc/bugs/Unknown_command___39__list__39__/comment_3_35dfc75ce9efffff139f8929dc311e29._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://cstork.org/" + nickname="Chris Stork" + subject="comment 3" + date="2013-10-04T11:17:42Z" + content=""" +Ah, I could have sworn that I also tried to update via cabal but didn't see a new version and this explains why... + +Your release script might also have a problem with updating the [[News]] page... +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers.mdwn b/doc/bugs/Unnecessary_remote_transfers.mdwn new file mode 100644 index 000000000..9ae23e5a0 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. +This is related to [[http://git-annex.branchable.com/bugs/assistant_does_not_always_use_repo_cost_info_when_queueing_downloads/]] + +### What steps will reproduce the problem? +1. Make a client repo on two machines on the local network. +2. Pair them. +3. Make a remote transfer repo. +4. Set up Jabber on both local machines. +5. Put a large file into the annex on one of the local machines. +6. Watch as the source client repo copies the file directly to the local paired machine, but also copies it to the remote transfer repo. +7. Wait for the local paired transfer to finish. +8. Manually disable syncing to the remote transfer repo. +9. Manually reenable it. +10. Watch as the remote transfer is not resumed. + +### What version of git-annex are you using? On what operating system? +Using the 1 Nov Linux tarball, Ubuntu Raring. + +### Please provide any additional information below. +This is a problem because unless I manually disable the remote repo, it will continue uploading the large file until it finishes, which uses the limited upstream bandwidth on my Internet connection--and this could take hours depending on the size of the file. + +The remote transfer wasn't even necessary to begin with, because it already had a direct connection to the local paired repo. But even so, it should at least abort the remote transfer when the local transfer finishes. + +Thanks for your work on git-annex assistant. diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment b/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment new file mode 100644 index 000000000..8c985243a --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_10_b778fbb1386f0f51bf057ffacd590ebb._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 10" + date="2013-11-03T02:19:04Z" + content=""" +Thanks, Joey. I didn't realize that there were two instances of the assistant running. + +Forgive my ignorance, but if I disable the assistant running in the backup repo, will the other assistant still backup files to it? + +Also, from a UI perspective, does the webapp currently not seem to support secondary internal drives, at least in a useful way? +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment b/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment new file mode 100644 index 000000000..808c5bca6 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_11_55430eac842d0a192dc7f41d7730e4d5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 11" + date="2013-11-03T02:32:47Z" + content=""" +Yes, either of the assistants will still back up files to it, as long as they have it configured as a git remote. The same way that your transfer repository is (probably) not running the git-annex assistant. + +It does sound like using the removable drive UI would have saved you some trouble. I'm not sure why the webapp would not list a llvm device as a removable drive -- from inspecting the code, it seems like it would not be filtered out, as long as /proc/mounts shows the decive as /dev/something (I don't have a llvm device handy to check what it looks like). +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment b/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment new file mode 100644 index 000000000..7baa58489 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_1_00c18e07678dc513a02d974fe059df73._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-11-02T19:54:44Z" + content=""" +In what order does the webapp list your repositories? + +When a new file appears, it will always go through the list of repositories in order, and try to transfer the file to each in turn, unless the configuration indicates it shouldn't. So, if the remote transfer repo is listed before the local repo, it will first upload the file to the transfer repo, and then upload it to the local repo. (And then later on, remove it from the transfer repo, since the file has reached all clients, probably.) OTOH, if the local repo comes first, it will upload the file to it over the LAN, and then when it comes to the transfer repo, if the file has successfully been sent to all clients, the transfer repo will no longer want it, and so no expensive upload is done over the internet. + +You can re-order the repository list in the webapp by dragging them up and down. It should default to having your locally paired repos first, unless you've changed it. If you think it came up with the wrong order, paste in your .git/config before you re-order the repositories.. +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment b/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment new file mode 100644 index 000000000..cc0cb067e --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_2_2e9992dbfceabd6df535a2770626de16._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 2" + date="2013-11-02T22:48:18Z" + content=""" +The webapp has the remote repo at the bottom of the list. But here's .git/config. It has a high repo cost for the local paired repo, and no cost listed for the remote one: + +[[!format sh \"\"\" +[core] + repositoryformatversion = 0 + filemode = true + bare = false + logallrefupdates = true +[annex] + uuid = 946f9095-588b-4421-b66a-4a1e5632ff6b + version = 3 + direct = true + diskreserve = 1 megabyte + numcopies = 1 + debug = false +[gc] + auto = 0 +[remote \"Onyx\"] + url = ssh://me@git-annex-Onyx.local-me_annex/~/annex/ + annex-uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9 + annex-cost = 125.0 + fetch = +refs/heads/*:refs/remotes/Onyx/* +[remote \"Remote\"] + annex-rsyncurl = username@git-annex-example.net-username_annex:annex/ + annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf + fetch = + annex-sync = true +\"\"\"]] +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment b/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment new file mode 100644 index 000000000..b6900f339 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_3_a98f3091a6a658919f0562cf396439c2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 3" + date="2013-11-02T22:59:18Z" + content=""" +Also, I just realized that it's uploading two large files to my remote transfer repo, even though I already have both files in my local paired repo on both systems; i.e. there's no need to send it to the transfer repo at all. And it was yesterday when the two files were transferred. So I have no idea why today it thinks it needs to upload them to the transfer repo. :/ +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment b/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment new file mode 100644 index 000000000..b0d4c1146 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_4_417c1e8e27ee1a1f9ebf9160560605c5._comment @@ -0,0 +1,96 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="Super confused" + date="2013-11-02T23:30:41Z" + content=""" +I think now I'm double- or triple-confused. Here is me@desktop:~/annex/.git/config: + +[[!format sh \"\"\" +[core] + repositoryformatversion = 0 + filemode = true + bare = false + logallrefupdates = true +[annex] + uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9 + version = 3 + direct = true + fscknudge = true +[gc] + auto = 0 +[remote \"laptop\"] + url = ssh://me@git-annex-laptop-me_annex/~/annex/ + annex-uuid = 946f9095-588b-4421-b66a-4a1e5632ff6b + annex-cost = 175.0 + fetch = +refs/heads/*:refs/remotes/laptop/* +[remote \"Remote\"] + annex-rsyncurl = username@example.net:annex/ + annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf + fetch = + annex-sync = false +[remote \"backupOndesktop\"] + url = /mnt/debian/home/me/annex-backup + annex-uuid = 86535965-6ca7-4bf3-89af-bca3a07f96f9 + fetch = +refs/heads/*:refs/remotes/backupOndesktop/* +\"\"\"]] + +What I have set up (or intended to set up) is: + +* Client: me@laptop:~/annex +* Client: me@desktop:~/annex +* Transfer: username@example.net:~/annex +* Full Backup: me@desktop:/mnt/debian/home/me/annex-backup + +What I expected was that: + +1. The two Client repos would sync directly over the LAN whenever possible. +2. The transfer repo would be used only to sync the laptop and desktop, and then only if my laptop were not on the LAN with my desktop. +3. The Full Backup repo would be synced directly with the me@desktop Client repo, within the same system, from one hard disk to the other. + +But what I'm seeing is...not quite that. + +1. It's very confusing (to me, at least) that on my desktop system I can look at my annex setup from the \"perspective\" of both local repos. When I \"switch\" to the other repo, the setup looks different: even the same repos can have different names and descriptions, and can be enabled and disabled independently depending on the \"perspective\"...but their Type is still the same. + +2. Looking from the \"perspective\" of the Full Backup repo, I'm seeing files being transferred to the Transfer repo, even though those files are already present in both Client repos, and even though the webapp says that the Full Backup repo has been synced. When I disable and reenable the Transfer repo, it starts those transfers over again, even though they aren't necessary. For example, here is the log from disabling and reenabling the Transfer repo from the \"perspective\" of the Full Backup repo: + +[[!format sh \"\"\" +[2013-11-02 18:24:35 CDT] main: Syncing with example.net_annex +(gpg) +gpg: Terminated caught ... exiting +[2013-11-02 18:24:49 CDT] call: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"config\",\"remote.example.net_annex.annex-sync\",\"true\"] +[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:49 CDT] main: Syncing with example.net_annex +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"symbolic-ref\",\"HEAD\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"refs/heads/master\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"git-annex\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"log\",\"refs/heads/git-annex..2c42d607c099b6ec4a20603b809f44d161e42489\",\"--oneline\",\"-n1\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"symbolic-ref\",\"HEAD\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"refs/heads/master\"] +[2013-11-02 18:24:49 CDT] TransferScanner: starting scan of [Remote { name =\"example.net_annex\" }] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"ls-files\",\"--cached\",\"-z\",\"--\"] +[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing : expensive scan found missing object +[2013-11-02 18:24:49 CDT] Transferrer: Transferring: Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing +[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" image.jpg Nothing : expensive scan found missing object +[2013-11-02 18:24:49 CDT] call: /home/me/.bin/git-annex.linux/git-annex [\"transferkeys\",\"--readfd\",\"35\",\"--writefd\",\"34\"] +[2013-11-02 18:24:49 CDT] TransferScanner: queued Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" linux-image-3.8.0-29-generic_3.8.0-29.42_i386.deb Nothing : expensive scan found missing object +[2013-11-02 18:24:49 CDT] TransferScanner: finished scan of [Remote { name =\"example.net_annex\" }] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"git-annex\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"show-ref\",\"--hash\",\"refs/heads/git-annex\"] +[2013-11-02 18:24:49 CDT] read: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"log\",\"refs/heads/git-annex..2c42d607c099b6ec4a20603b809f44d161e42489\",\"--oneline\",\"-n1\"] +[2013-11-02 18:24:49 CDT] chat: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"cat-file\",\"--batch\"] +[2013-11-02 18:24:49 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:49 CDT] TransferWatcher: transfer starting: Upload UUID \"33930bae-63d2-4a52-b330-58872aaeb1bf\" video.flv Nothing +(gpg) [2013-11-02 18:24:49 CDT] chat: gpg [\"--batch\",\"--no-tty\",\"--use-agent\",\"--quiet\",\"--trust-model\",\"always\",\"--batch\",\"--passphrase-fd\",\"20\",\"--symmetric\",\"--force-mdc\",\"--no-textmode\"] +[2013-11-02 18:24:50 CDT] call: git [\"--git-dir=/mnt/debian/home/me/annex-backup/.git\",\"--work-tree=/mnt/debian/home/me/annex-backup\",\"config\",\"remote.example.net_annex.annex-sync\",\"false\"] +[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"] +[2013-11-02 18:24:50 CDT] read: git [\"config\",\"--null\",\"--list\"] + +gpg: Terminated caught ... exiting\"\"\"]] + +I have no idea why it's doing that, because all three of those files are already in both Client repos and the Full Backup repo. +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment b/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment new file mode 100644 index 000000000..0e2ec4ec8 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_5_eb5a2717a1f0c7bb761d2a7866b23def._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="Deleting repos from different perspectives" + date="2013-11-02T23:33:48Z" + content=""" +One other thing, sorry, but I think this is important: From the perspective of the Full Backup repo, I set the Transfer repo to be deleted, thinking that would prevent the desktop's Client and Full Backup repos from syncing through the Transfer repo. But then when I switch to the perspective of the desktop's Client repo, it is \"cleaning out\" the Transfer repo--but I wanted the Transfer repo to be used for syncing the two Client repos! So I set it back to Transfer instead of Unwanted...but then when I switch back to the Full Backup perspective, the Transfer repo is no longer Unwanted. +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment b/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment new file mode 100644 index 000000000..509cc3f3f --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_6_89f756db1f3f2e60a3bd1f35f55fee43._comment @@ -0,0 +1,40 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="config from backup repo" + date="2013-11-03T00:20:11Z" + content=""" +Sorry for posting over and over again, just trying to provide info when I discover it. + +Here's **/mnt/debian/home/me/annex-backup/.git/config** + +[[!format sh \"\"\" +[core] + repositoryformatversion = 0 + filemode = true + bare = false + logallrefupdates = true +[annex] + uuid = 86535965-6ca7-4bf3-89af-bca3a07f96f9 + version = 3 + direct = true + fscknudge = true + diskreserve = 100 megabyte + numcopies = 1 + debug = false +[gc] + auto = 0 +[remote \"desktop\"] + url = /home/me/annex + fetch = +refs/heads/*:refs/remotes/desktop/* + annex-uuid = 80709bc2-3cbe-434b-b7b9-306278b9a4e9 +[remote \"Remote\"] + annex-rsyncurl = username@example.net:annex/ + annex-uuid = 33930bae-63d2-4a52-b330-58872aaeb1bf + annex-sync = false + fetch =\"\"\"]] + +1. Should I remove the \"Remote\" Transfer repo from this config file to prevent it from using the Transfer repo? I only want this repo to sync directly with the other internal hard disk. + +2. Is it correct for git-annex to add this Transfer repo to this config file in the first place? +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment b/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment new file mode 100644 index 000000000..f117f15c1 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_7_5aaf8766a7ba05c4f92715e5d5175a8f._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 7" + date="2013-11-03T00:45:09Z" + content=""" +* The costs you show look fine. +* Yes, deleting a repository in the webapp actually deletes it. It doesn't just remove the remote from .git/config. Most people using the webapp don't want to draw such a fine distinction, I think. +* It's not a very usual configuration to have 2 repositories on the same machine with the git-annex assistant running in both. You might just want to configure the assistant to not run in the backup repository. + +Some of the things you've said suggest that the backup repository might not be immediately noticing when changes are pushed to it. Since its location is shown as /mnt/debian/home/me, I have to wonder if that's some NFS mount or other network filesystem causing problems. + +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment b/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment new file mode 100644 index 000000000..1177205e3 --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_8_e856b350632cc865d16d1995a6cdf065._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 8" + date="2013-11-03T01:07:31Z" + content=""" +> It's not a very usual configuration to have 2 repositories on the same machine with the git-annex assistant running in both. You might just want to configure the assistant to not run in the backup repository. + +Maybe that's the crux of the problem. But I'm not sure what I did wrong to make that happen. I have a second internal hard disk in my desktop system, and I wanted to put a Full Backup repo on it. I tried to add a \"Removable drive\" repo (since I sometimes unplug it to swap cables with a DVD drive), but since the assistant didn't detect any actual removable drives, that didn't work. So I used \"Add another repository\" and set it to a Full Backup repo. Is that the wrong way to do it? :) + +> Some of the things you've said suggest that the backup repository might not be immediately noticing when changes are pushed to it. Since its location is shown as /mnt/debian/home/me, I have to wonder if that's some NFS mount or other network filesystem causing problems. + +/mnt/debian is /dev/mapper/lvm-root, another internal disk. The disk is working fine. :) +"""]] diff --git a/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment b/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment new file mode 100644 index 000000000..03127c4ad --- /dev/null +++ b/doc/bugs/Unnecessary_remote_transfers/comment_9_64f831545b34b78452952cf49b5f5b05._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 9" + date="2013-11-03T01:52:56Z" + content=""" +Ok, since we don't have NFS craziness, I'm going to put theories about it not noticing incoming syncs on hold. (I think I probably misunderstood [this comment](http://git-annex.branchable.com/bugs/Unnecessary_remote_transfers/#comment-39490c318620c141e7557b7bcba0e5c8) and anyway the assistant has some throttling so won't always immediately load config changes that have been synced to it if some other config changes were loaded a minute before.) + +I think this behavior can probably be explained without resorting to any bugs, now that I have, I think, a full picture of the repository network: + +<pre> +laptop <-> desktop <-> backup + | | | + v v v + transfer (cloud) +</pre> + +Now when a file is added to desktop, it immediately copies it to backup, which is on the same machine, so that happens quite quickly. Then it starts sending it across the LAN to laptop. + +Meanwhile, the assistant daemon running on backup wakes up, notices it's just received an object, and sees that this object is currently located on only desktop and backup, but not yet on laptop or transfer. Which means that it should send the object to transfer, from which it will eventually reach laptop. + +The only ways I can think of to avoid such an unnecessary transfer would be a) for desktop could somehow tell backup that it's in the process of sending the file to laptop or b) for a map of current state of the network to be constructed and maintained and analyzed automatically, so it it could conclude backup does not need to send files to transfer if they're already present on desktop. There is some discussion about this in [[design/assistant/syncing]]. Hard problem in general I think, although slightly less hard in this specific case since desktop and backup know they're in the same machine. + +But it should be easy to configure it so this doesn't happen. Just make backup not have the transfer repository configured as a remote (or just pause it syncing to there in the webapp). Or, don't run the assistant at all on backup (see `~/.config/git-annex/autostart`). +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key.mdwn b/doc/bugs/Using_a_revoked_GPG_key.mdwn new file mode 100644 index 000000000..4e522ab78 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key.mdwn @@ -0,0 +1,34 @@ +### Please describe the problem. +git-annex refuses to use revoked GPG keys. This may be understandable for the initial remote setup, but it hit me when I tried to add a new key to a remote. The previous key has been revoked (because it has been superseded by the new one), and git-annex refused to reinvoke the shared key with both keys because one of them was revoked. + +Given the encryption model does not allow key replacement, it should not refuse to reencrypt using a revoked key. Maybe using `--expert` would help. + +### What steps will reproduce the problem? +Encrypt a special remote with a key K1. Revoke key K1. Try to add key K2 with enableremote. git-annex will refuse to encrypt the shared key with the revoked one. + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20130802-g1452ac3 + +### Please provide any additional information below. + +[[!format sh """ +% git annex enableremote zoidberg-crypted encryption=42B8F7C2 +enableremote zoidberg-crypted (encryption update) +You need a passphrase to unlock the secret key for +user: "Samuel Tardieu <sam@rfc1149.net>" +2048-bit ELG key, ID F0D70BAF, created 2002-05-31 (main key ID 1B80ADE6) + +gpg: NOTE: key has been revoked +gpg: reason for revocation: Key is superseded +gpg: revocation comment: Key superseded by 42B8F7C2 +gpg: revocation comment: (fingerprint 1D36 D924 8B33 DCAB 7BA5 BA44 7A30 BCF4 42B8 F7C2) +gpg: F13322411B80ADE6: skipped: Unusable public key +gpg: [stdin]: encryption failed: Unusable public key + +git-annex: user error (gpg ["--quiet","--trust-model","always","--encrypt","--no-encrypt-to","--no-default-recipient","--recipient","7A30BCF442B8F7C2","--recipient","F13322411B80ADE6"] exited 2) +failed +git-annex: enableremote: 1 failed +"""]] + +> [[done]]; can now use: `git annex enableremote foo keyid-=REVOKEDKEY +> keyid+=NEWKEY` to remove it, and add a new key. --[[Joey]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment new file mode 100644 index 000000000..baddbbf49 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_1_7bb01d081282e5b02b7720b2953fe5be._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmWg4VvDTer9f49Y3z-R0AH16P4d1ygotA" + nickname="Tobias" + subject="comment 1" + date="2013-08-12T11:47:28Z" + content=""" +I'd be very unhappy indeed if I couldn't revoke access to my annex. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment new file mode 100644 index 000000000..003f9a34a --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_2_9c0c40360f0058a4bd346c1362e302b6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://www.rfc1149.net/" + nickname="Sam" + subject="comment 2" + date="2013-08-13T07:28:30Z" + content=""" +Tobias: I don't understand what you mean. The issue here is that once an existing key is revoked, git-annex will refuse to add *another non-revoked* key. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment new file mode 100644 index 000000000..7f18cfe39 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_3_8f69f58107246595f5603f35c4aa7395._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmWg4VvDTer9f49Y3z-R0AH16P4d1ygotA" + nickname="Tobias" + subject="comment 3" + date="2013-08-13T08:47:45Z" + content=""" +Ah, sorry, i'm uncomprehending :) +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment new file mode 100644 index 000000000..61b03c109 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_4_78b3c52ba85edfa6ee6e273bec3bea5c._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 4" + date="2013-08-16T07:14:12Z" + content=""" +The [[OpenPGP standard|https://tools.ietf.org/html/rfc4880]] specifies that revoked keys/subkeys \"are not to be used\". AFIK GnuPG, as any RFC-compliant implementation, will not let you encrypt to a revoked key no matter what. An extremely dirty workaround is to set up your system clock prior to the revocation date (but that might put your whole system at risk since other applications may rely synced clocks to work properly). + +That said, what you really wanted to do was to revoke access to K1 and add K2 instead. That seems to be a perfectly valid use-case, and it shouldn't be hard to add to git-annex; stay tunned ;-) + + +Tobias: Not sure what you meant by \"revoke access to my annex\", but if you were thinking of the key owner, note that with the current [[encryption design|http://git-annex.branchable.com/design/encryption]], since that person may simply grab from the git repo and then at any time decrypt the passphrase for the symmetric cipher, it makes little sense to revoke access for that person unless you change that passphrase, and reencrypt all annexed files on the remote, which of course needs to be done locally for the encryption to make sense at all. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment new file mode 100644 index 000000000..ff441671f --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_5_a85ccf2f09ebe87147f8761b81a02326._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://www.rfc1149.net/" + nickname="Sam" + subject="comment 5" + date="2013-08-19T11:35:52Z" + content=""" +Indeed, removing the revoked key and putting the new one would be acceptable, there is no reason to keep the revoked one around. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment new file mode 100644 index 000000000..eb9cd0f54 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_6_8b89eb5e6386acd0a922310c04f863ac._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 6" + date="2013-08-19T13:22:59Z" + content=""" +All right, what would be a nice user interface, compatible with the current commands? I was thinking of something along the lines of `git annex enableremote +encryption=newKey -encryption=oldKey`, with an alias `+encryption=encryption` to be backward compatible. It's probably not optimal though, feel free to comment :-) + +Of course, `git-annex` should ensure that at any point in time the passphrase is always encrypted using an OpenPGP key. (Otherwise it might be stored clear in the git repository, which would void the encryption.) Also, anyone who can decrypt the passphrase can revoke all existing keys and reencrypt it using another key; this not really a big deal since the cipher is version-controlled anyway, so loosing access to the repo is unlikely. + +By the way, since we're about to amend the arguments for `enableremote`, it'd be nice to take advantage of the situation to allow pure asymmetric encryption. I propose `git annex initremote ... encryption=myKey crypto={none,hybrid,pubkey}` to use respectively no-encryption, an asymmetrically encrypted passphrase (the current design, default), and OpenPGP keys only. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment new file mode 100644 index 000000000..02be72e36 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_7_20dc5a7ce7cb6ca97ccdfb923c3b24bb._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 7" + date="2013-08-19T16:08:49Z" + content=""" +On second thought, I think it makes more sense to have something like `git annex initremote ... encryption={none,shared,hybrid,pubkey} keyid=whatever` and `git annex enableremote ... [+keyid=newkey] [-keyid=oldkey]`, where `keyid` can only be used when `encryption` is either `hybrid` (default) or `pubkey`. + +This would break compatibility with the current interpretation of `encryption`, but I believe it's not so invasive: People are not creating new remotes every day, and an error message could clarify the new behavior. It's also clearer, since key IDs can be added and deleted at will, whereas the encryption scheme cannot. +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment new file mode 100644 index 000000000..a63ce1262 --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 8" + date="2013-08-22T17:05:49Z" + content=""" +Note that the assistant generates initremote parameters so code there also needs to be changed if the syntax changes. + +I think I am ok with changing the syntax. However, it seems that `encryption=-oldkey encryption=newkey` could be used to remove the old revoked key and add a new one. Using `-keyid` as a parameter to initremote is a bit tricky since git-annex's regular option parser would see it, before the parameter could get to initremote. (Unless -keyid was defined as a regular option specific to initremote.) OR, git-annex could just try to detect when a key is revoked and automatically remove it when a new encryption key is specified. + +Hmm, it would be possible to have it just notice, when adding a new key, if one of the existing keys is revoked, and +remove the revoked key automatically. + +The above doesn't deal with the case of wanting to add pure asymmetric encryption. It seems to me that from a user's point of view, what they really need to know about asymmetric encryption is that they can't easily give additional keyids access after the fact (without reencrypting and reuploading everything). So I think it would be good if the syntax made that obvious. Perhaps `encryptiononly=key` +"""]] diff --git a/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment b/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment new file mode 100644 index 000000000..d86de4e1b --- /dev/null +++ b/doc/bugs/Using_a_revoked_GPG_key/comment_9_f50c802d78041fd1522f0e7599ce6a45._comment @@ -0,0 +1,42 @@ +[[!comment format=mdwn + username="guilhem" + ip="129.16.20.209" + subject="comment 9" + date="2013-08-22T18:42:28Z" + content=""" +Hehe, I ran into the option parser issue when implementing that change +;-) So I moved to `git annex enableremote ... [keyid+=newkey] +[keyid-=oldkey]` (where `+` is optional, for consistency) which doesn't +prevent users from specifying a key by something starting with a sign. + +While it's certainly possible to tell git-annex to manage the authorized +keys itself, users may have other reasons to remove a key so I'm not +sure it's a good idea. Also, what if someone forgets to add his/her new +key after revocation (it's still possible to decrypt after all)? If +another person updates the keyring afterwards, the first user will be +denied further access, and will have to retrieve and reencrypt the +\"cipher\" manually, which is not so trivial. + + +I understand that asymmetric encryption needs special care, but Sam's +use case could be reproduced with that scheme I believe. For instance a +user may superseed and revoke his/her old key; then new files would be +uploaded with the new one, but as long as the old key is not +compromised, I don't see why s/he should reupload everything instead of +using the old key when pulling from the remote. Of course one may argue +that the key shouldn't be revoked at the first place, but if it's used +for other purposes (e.g., it's publicly available on a key server) it's +good practice to revoke it IMHO. + +As for the removal of keys with pure asymmetric encryption, it is just +required I think: Otherwise revoking a key would prevent any further +content to be encrypted. There I can't see any problem with git-annex +managing the keyring itself (beside the extra code to write :-P). + +All in all if we are to allow deletion/addition of keyIDs (and I think +we should!), I think it should be done for both `hybrid` and `pubkey` +schemes. Do you really want another syntax? I'd say clarify the manage +(plus maybe a warning when running the CLI) is enough, but true it's +easy to shoot oneself in the foot there... + +"""]] diff --git a/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_2_6d360a15818866242f9cbcf383094f8a._comment b/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_2_6d360a15818866242f9cbcf383094f8a._comment deleted file mode 100644 index b0fe1b0fa..000000000 --- a/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_2_6d360a15818866242f9cbcf383094f8a._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawnaH44G3QbxBAYyDwy0PbvL0ls60XoaR3Y" - nickname="Nigel" - subject="log file" - date="2013-07-30T19:03:03Z" - content=""" -Yes, will do. But need to recreate - I repeatedly executed rm -rf .git to repeat the test and left it 'clean'. - -PS. Is there an easy(er) way to 'undo' the creation of a repository without loosing any file content? One day I will run rm -rf in the wrong place! -After an uninstall of annex it was hard for me to figure out how to start with a clean system when the webapp found the previously created repo. -"""]] diff --git a/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_3_1a7542249b9c37507126e97441057c12._comment b/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_3_1a7542249b9c37507126e97441057c12._comment new file mode 100644 index 000000000..9bc0c90e6 --- /dev/null +++ b/doc/bugs/Watcher_crashed_in_Android_on___47__storage__47__sdcard1_-_bug__63__/comment_3_1a7542249b9c37507126e97441057c12._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.246" + subject="comment 3" + date="2013-11-10T18:18:09Z" + content=""" +Seems to me this was probably fixed in [[!commit 6b37fcffd872b62fb78047a77e4cee5ab0bb57f1]]. + +However, I don't know why permission problems would happen on Android, which typically uses a filesystem that does not have restricted permissions for the sdcard. + +If you upgrade, you should be able to see if it fixed the crash, and it will also mention any file or directory that it's unable to read in the log. +"""]] diff --git a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn new file mode 100644 index 000000000..dd4b6a921 --- /dev/null +++ b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git.mdwn @@ -0,0 +1,384 @@ +### Please describe the problem. +I try to share some files between a windows machine and a linux machine in direct mode, with a remote repository between the two. I can't seem to reproduce the problem in indirect mode... + +I add a file on the windows machine then copy it to the remote repository. I then get it on the linux machine and edit it there. If I `git annex sync` and copy the file's data to the remote repository, a `git annex sync` on windows will fail like this: + +[[!format sh """ +$ git annex sync +commit +ok +pull origin +remote: Counting objects: 41, done. +remote: Compressing objects: 100% (24/24), done. +remote: Total 31 (delta 9), reused 0 (delta 0) +Unpacking objects: 100% (31/31), done. +From ssh://192.168.1.29:/home/raz/work/test + b23cb44..9073cc3 git-annex -> origin/git-annex + 7d4f0e2..87438fc master -> origin/master + 57a661c..b33b025 synced/git-annex -> origin/synced/git-annex + 7d4f0e2..87438fc synced/master -> origin/synced/master +ok +(merging origin/git-annex origin/synced/git-annex into git-annex...) +(Recording state in git...) +push origin +Counting objects: 17, done. +Delta compression using up to 8 threads. +Compressing objects: 100% (4/4), done. +Writing objects: 100% (5/5), 565 bytes | 0 bytes/s, done. +Total 5 (delta 2), reused 0 (delta 0) +To ssh://192.168.1.29:/home/raz/work/test.git + b33b025..dcfaf23 git-annex -> synced/git-annex + ! [rejected] master -> synced/master (non-fast-forward) +error: failed to push some refs to 'ssh://192.168.1.29:/home/raz/work/test.git' +hint: Updates were rejected because a pushed branch tip is behind its remote +hint: counterpart. Check out this branch and merge the remote changes +hint: (e.g. 'git pull') before pushing again. +hint: See the 'Note about fast-forwards' in 'git push --help' for details. +failed +git-annex: sync: 1 failed +"""]] + +A `git log` tells me the master branch is not properly merged so I assume the pull failed silently (I paste the log in the transcript). + +I can then try to manually fix the windows working copy and sometimes it kind of work, but sometimes I have a hard time recovering and I am better off cloning a new version and moving data's around... + +### What steps will reproduce the problem? +Create a repository on a windows. + +Add a file. + +`git clone --bare` the repository and put it on a remote machine. + +Clone the remote repository to a linux machine. + +Get the file's data. + +Edit the file on linux. + +Commit it and copy the data's to the remote machine. + +`git clone sync` on the windows machine --> Error. + +### What version of git-annex are you using? On what operating system? +On Windows: +[[!format sh """ +git-annex version: 4.20130827-g4f18612 +build flags: Pairing Testsuite S3 WebDAV DNS +local repository version: 4 +default repository version: 3 +supported repository versions: 3 4 +upgrade supported from repository versions: 2 +"""]] + +On Linux +[[!format sh """ +git-annex version: 4.20130815 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP +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 + +### On Windows + +$ mkdir test_windows + +$ cd test_windows/ + +$ git init +Initialized empty Git repository in c:/Users/raz/test_windows/.git/ + +$ 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...) + +$ echo "test 1" > test.txt + +$ git annex add test.txt +add test.txt (checksum...) ok +(Recording state in git...) + +$ git annex sync +commit +ok +git-annex: no branch is checked out + +$ cd .. + +$ git clone --bare test_windows/ test.git +Cloning into bare repository 'test.git'... +done. + +$ scp -r test.git 192.168.1.29:/home/raz/work/ +config 100% 183 0.2KB/s 00:00 +description 100% 73 0.1KB/s 00:00 +HEAD 100% 23 0.0KB/s 00:00 +applypatch-msg.sample 100% 452 0.4KB/s 00:00 +commit-msg.sample 100% 896 0.9KB/s 00:00 +post-commit.sample 100% 160 0.2KB/s 00:00 +post-receive.sample 100% 552 0.5KB/s 00:00 +post-update.sample 100% 189 0.2KB/s 00:00 +pre-applypatch.sample 100% 398 0.4KB/s 00:00 +pre-commit.sample 100% 1704 1.7KB/s 00:00 +pre-push.sample 100% 1348 1.3KB/s 00:00 +pre-rebase.sample 100% 4951 4.8KB/s 00:00 +prepare-commit-msg.sample 100% 1239 1.2KB/s 00:00 +update.sample 100% 3611 3.5KB/s 00:00 +exclude 100% 240 0.2KB/s 00:00 +825dc642cb6eb9a060e54bf8d69288fbee4904 100% 15 0.0KB/s 00:00 +a31b7a55380d79248658d3fffff6d2dc41a726 100% 116 0.1KB/s 00:00 +dcabbf728abe62b6e2bcc06b8306eb3aa9a497 100% 176 0.2KB/s 00:00 +332ecbfe923879df51a7a3f9bb86ebdfb64273 100% 45 0.0KB/s 00:00 +4f0e20d38d6dc757340a8c569270b5a857fc67 100% 160 0.2KB/s 00:00 +62956bcf45c63b24a637b22a742db0d9458248 100% 86 0.1KB/s 00:00 +7ec519eb1b257a85ae8f9373d0835dea9ddc04 100% 82 0.1KB/s 00:00 +1d1559a050b4a2df2e653b1e7ac15bdf7d56b1 100% 51 0.1KB/s 00:00 +b74dbedfac4d6a0a90580cff2088a5d61f6675 100% 130 0.1KB/s 00:00 +0ca042f439ef997f04a25a449aa1f539b93cf4 100% 53 0.1KB/s 00:00 +bbce5e51e5a90ffd26900de3546fc4f9704181 100% 151 0.2KB/s 00:00 +18bd66316298fcc5c06af9865c30a2fe4d2476 100% 176 0.2KB/s 00:00 +edf8b5cc207e16ca0173785a2ba569c5d4208c 100% 71 0.1KB/s 00:00 +packed-refs 100% 160 0.2KB/s 00:00 + +$ cd test_windows/ + +$ git remote add origin ssh://192.168.1.29:/home/raz/work/test.git + +$ git annex copy --to origin +copy test.txt (checking origin...) (to origin...) +test.txt + 7 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) + +sent 79 bytes received 31 bytes 220.00 bytes/sec +total size is 7 speedup is 0.06 +ok +(Recording state in git...) + +$ git annex sync +commit +ok +pull origin +remote: Counting objects: 11, done. +remote: Compressing objects: 100% (5/5), done. +remote: Total 6 (delta 1), reused 0 (delta 0) +Unpacking objects: 100% (6/6), done. +From ssh://192.168.1.29:/home/raz/work/test + * [new branch] git-annex -> origin/git-annex + * [new branch] master -> origin/master +ok +(merging origin/git-annex into git-annex...) +(Recording state in git...) +push origin +Counting objects: 18, done. +Delta compression using up to 8 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (10/10), 874 bytes | 0 bytes/s, done. +Total 10 (delta 4), reused 0 (delta 0) +To ssh://192.168.1.29:/home/raz/work/test.git + * [new branch] git-annex -> synced/git-annex + * [new branch] master -> synced/master +ok + +### On Linux + +$ git clone test.git test_linux +Cloning into 'test_linux'... +done. + +$ cd test_linux + +$ git annex init linux +init linux ok +(Recording state in git...) + +$ git annex sync +(merging origin/git-annex origin/synced/git-annex into git-annex...) +(Recording state in git...) +commit +ok +pull origin +ok +push origin +Counting objects: 11, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (6/6), done. +Writing objects: 100% (8/8), 775 bytes | 0 bytes/s, done. +Total 8 (delta 3), reused 0 (delta 0) +To /home/raz/work/test.git + 0b4f175..41fba1d git-annex -> synced/git-annex +ok + +$ git annex get +get test.txt (from origin...) ok +(Recording state in git...) + +$ git annex direct +commit +# On branch master +nothing to commit, working directory clean +ok +direct test.txt ok +direct ok + +$ git annex sync +commit +ok +pull origin +ok +push origin +Counting objects: 9, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (4/4), done. +Writing objects: 100% (5/5), 492 bytes | 0 bytes/s, done. +Total 5 (delta 1), reused 0 (delta 0) +To /home/raz/work/test.git + 41fba1d..57a661c git-annex -> synced/git-annex +ok + +$ cat test.txt +test 1 + +$ echo "test 2" > test.txt + +$ git annex sync +add test.txt (checksum...) ok +(Recording state in git...) +commit +(Recording state in git...) +ok +pull origin +ok +push origin +Counting objects: 22, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (12/12), done. +Writing objects: 100% (16/16), 1.40 KiB | 0 bytes/s, done. +Total 16 (delta 4), reused 0 (delta 0) +To /home/raz/work/test.git + 57a661c..4883cad git-annex -> synced/git-annex + 7d4f0e2..87438fc master -> synced/master +ok + +$ git annex copy --to origin +copy test.txt (to origin...) ok +(Recording state in git...) + +$ git annex sync +commit +ok +pull origin +remote: Counting objects: 6, done. +remote: Compressing objects: 100% (4/4), done. +remote: Total 5 (delta 0), reused 0 (delta 0) +Unpacking objects: 100% (5/5), done. +From /home/raz/work/test + b23cb44..9073cc3 git-annex -> origin/git-annex +ok +(merging origin/git-annex into git-annex...) +(Recording state in git...) +push origin +Counting objects: 18, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (10/10), 924 bytes | 0 bytes/s, done. +Total 10 (delta 3), reused 0 (delta 0) +To /home/raz/work/test.git + 4883cad..b33b025 git-annex -> synced/git-annex +ok + +$ + + +### On Windows + +$ git annex sync +commit +ok +pull origin +remote: Counting objects: 41, done. +remote: Compressing objects: 100% (24/24), done. +remote: Total 31 (delta 9), reused 0 (delta 0) +Unpacking objects: 100% (31/31), done. +From ssh://192.168.1.29:/home/raz/work/test + b23cb44..9073cc3 git-annex -> origin/git-annex + 7d4f0e2..87438fc master -> origin/master + 57a661c..b33b025 synced/git-annex -> origin/synced/git-annex + 7d4f0e2..87438fc synced/master -> origin/synced/master +ok +(merging origin/git-annex origin/synced/git-annex into git-annex...) +(Recording state in git...) +push origin +Counting objects: 17, done. +Delta compression using up to 8 threads. +Compressing objects: 100% (4/4), done. +Writing objects: 100% (5/5), 565 bytes | 0 bytes/s, done. +Total 5 (delta 2), reused 0 (delta 0) +To ssh://192.168.1.29:/home/raz/work/test.git + b33b025..dcfaf23 git-annex -> synced/git-annex + ! [rejected] master -> synced/master (non-fast-forward) +error: failed to push some refs to 'ssh://192.168.1.29:/home/raz/work/test.git' +hint: Updates were rejected because a pushed branch tip is behind its remote +hint: counterpart. Check out this branch and merge the remote changes +hint: (e.g. 'git pull') before pushing again. +hint: See the 'Note about fast-forwards' in 'git push --help' for details. +failed +git-annex: sync: 1 failed + +$ git log --graph --oneline --decorate --all +* 87438fc (origin/synced/master, origin/master) git-annex automatic sync +* 7d4f0e2 (HEAD, synced/master, master) git-annex automatic sync +*-. dcfaf23 (origin/synced/git-annex, git-annex) merging origin/git-annex orig +|\ \ +| | * b33b025 merging origin/git-annex into git-annex +| | |\ +| | |/ +| |/| +| * | 9073cc3 (origin/git-annex) update +| | * 73518bc update +| | * 4883cad update +| | * 1b447f5 update +| |/ +|/| +* | 57a661c update +| | +| \ +*-. \ 41fba1d merging origin/git-annex origin/synced/git-annex into git-annex +|\ \ \ +| | |/ +| |/| +| | * 0b4f175 merging origin/git-annex into git-annex +| | |\ +| | |/ +| |/| +| * | b23cb44 update +| | * b5755a2 update +| |/ +| * 6adcabb update +| * df18bd6 update +| * dcbbce5 branch created +* 0d138eb update +* fe6bccc branch created + +$ + +# End of transcript or log. +"""]] + +> Apparently `test.git` had `receive.denyNonFastForwards` +> set to true, which prevents the forced pushing `git annex sync` +> needs to do. I have made it print out a hint about this setting +> when a push failes. [[done]] --[[Joey]] diff --git a/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment new file mode 100644 index 000000000..1a443fb19 --- /dev/null +++ b/doc/bugs/Windows_and_Linux_in_direct_mode_confuses_git/comment_1_155e0c4d3aa41eebfe27533ab70a91d3._comment @@ -0,0 +1,68 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawknruiCHUcOh2mmpkh7OFJ4iNfAOOamRVs" + nickname="Renaud" + subject="comment 1" + date="2013-08-29T06:38:44Z" + content=""" +I wonder if it isn't related to the fact that even if I do `git annex drop` on windows, the file is still marked as modified in git. +What is in repository is the path to the file's data using unix style folder separator but what is in my working directory is a file containing the path using windows style folder separator. + +I paste a transcript to describe what I mean: + +[[!format sh \"\"\" +$ mkdir tmp + +$ cd tmp + +$ git init +Initialized empty Git repository in c:/Users/raz/tmp/tmp/.git/ + +$ git annex init test +init test + Detected a crippled filesystem. + + Enabling direct mode. + + Detected a filesystem without fifo support. + + Disabling ssh connection caching. +ok +(Recording state in git...) + +$ echo test > test + +$ git annex add +add test (checksum...) ok +(Recording state in git...) + +$ git annex sync +commit +ok +git-annex: no branch is checked out + +$ git annex drop --force +drop test ok +(Recording state in git...) + +$ git status +# On branch master +# 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) +# +# modified: test +# +no changes added to commit (use \"git add\" and/or \"git commit -a\") + +$ git diff +diff --git a/test b/test +index a9dd439..62343b2 120000 +--- a/test ++++ b/test +@@ -1 +1 @@ +-.git/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93 +\ No newline at end of file ++.git\annex\objects\w8\pv\SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93 +\ No newline at end of file +\"\"\"]] +"""]] diff --git a/doc/bugs/Windows_build_test_failures.mdwn b/doc/bugs/Windows_build_test_failures.mdwn index 97027d425..ac4dce13c 100644 --- a/doc/bugs/Windows_build_test_failures.mdwn +++ b/doc/bugs/Windows_build_test_failures.mdwn @@ -1228,3 +1228,5 @@ Some tests failed! # End of transcript or log. """]] + +[[!tag moreinfo]] diff --git a/doc/bugs/Windows_build_test_failures/comment_1_ea7523fdbafdc8be2971df52d9038826._comment b/doc/bugs/Windows_build_test_failures/comment_1_ea7523fdbafdc8be2971df52d9038826._comment new file mode 100644 index 000000000..dc09fb89b --- /dev/null +++ b/doc/bugs/Windows_build_test_failures/comment_1_ea7523fdbafdc8be2971df52d9038826._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 1" + date="2013-09-13T19:18:26Z" + content=""" +The Windows port has improved quite a lot since this bug was filed. Can you still reproduce it? + +If you install the pre-built git-annex for Windows, you can run `git annex test` to run the test suite. Does that work? It works for some others on Windows. +"""]] diff --git a/doc/bugs/Windows_installer_includes_curl_and_wget__44___but_not_required_DLLs.mdwn b/doc/bugs/Windows_installer_includes_curl_and_wget__44___but_not_required_DLLs.mdwn index 60a894b4e..a21813500 100644 --- a/doc/bugs/Windows_installer_includes_curl_and_wget__44___but_not_required_DLLs.mdwn +++ b/doc/bugs/Windows_installer_includes_curl_and_wget__44___but_not_required_DLLs.mdwn @@ -13,3 +13,5 @@ Windows 7. ### Please provide any additional information below. Installing Cygwin and adding to path seems to fix issue. + +[[!tag moreinfo]] diff --git a/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail.mdwn b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail.mdwn new file mode 100644 index 000000000..64e95ca1b --- /dev/null +++ b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail.mdwn @@ -0,0 +1,131 @@ +[[!tag moreinfo]] + +### Please describe the problem. +git annex get on a clone of a repository created on Windows fails. + +### What steps will reproduce the problem? +On Windows: +1. Create an annex using git annex init + +2. git add files + +3. git annex sync (because I forgot about commit) + +On Linux: + +1. Mount the Windows annex via SMB (mine was read only, but probably won't matter) + +2. git clone the folder (works fine) + +3. git annex get (fails, due to Windows drive letter) + +### What version of git-annex are you using? On what operating system? + +*Windows:* + +git-annex version: 4.20130802-g0a52f02 + +build flags: Pairing Testsuite S3 WebDAV DNS + +*Linux: (Debian wheezy on ARMel)* + +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 + + +### 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 + +#output of git annex get on the Linux side. + +get Purchased/Caravan Palace/Panic/01 Queens.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/02 Maniac.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/03 The Dirty Side of the Street.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/04 12 juin 3049.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/05 Rock It for Me.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/06 Clash.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/07 Newbop.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/08 Glory of Nelly.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/09 Dramophone.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/10 Cotton Heads.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/11 Panic.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/12 Pirates.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/13 Beatophone.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/14 Sydney.mp3 (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music +failed +get Purchased/Caravan Palace/Panic/Thumbs.db (not available) + Try making some of these repositories available: + d6c78593-79d2-455a-8202-7be2133e2d48 -- ICARUS:E:\music + + +And the (broken) symlinks: + +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 01 Queens.mp3 -> .git/annex/objects/5P/vq/SHA256E-s9886015--dfb8f452d47f997a9141de3f152de375fad1d5ccb4a20d5c022064a630eaba88.mp3/SHA256E-s9886015--dfb8f452d47f997a9141de3f152de375fad1d5ccb4a20d5c022064a630eaba88.mp3 +lrwxrwxrwx 1 voltagex voltagex 200 Aug 11 23:05 02 Maniac.mp3 -> .git/annex/objects/J0/WV/SHA256E-s10116938--7ce35f4a54c4f74bd2e3813445cb3a07fae76b2854df06ab00876cd0067f34a5.mp3/SHA256E-s10116938--7ce35f4a54c4f74bd2e3813445cb3a07fae76b2854df06ab00876cd0067f34a5.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 03 The Dirty Side of the Street.mp3 -> .git/annex/objects/xz/4F/SHA256E-s8812949--9e15761ae8c6231d11d1f5a67de8a89142e2e4017b43b8ffac1088fd71842ca7.mp3/SHA256E-s8812949--9e15761ae8c6231d11d1f5a67de8a89142e2e4017b43b8ffac1088fd71842ca7.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 04 12 juin 3049.mp3 -> .git/annex/objects/Kp/k6/SHA256E-s8236133--3a6465bea3272ae7a22b77b67e96a91ae389390cc95642fb1456ce80e3313033.mp3/SHA256E-s8236133--3a6465bea3272ae7a22b77b67e96a91ae389390cc95642fb1456ce80e3313033.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 05 Rock It for Me.mp3 -> .git/annex/objects/Wk/Qv/SHA256E-s7701150--8197e499408e64601157df95927ac6b09bd37834a41eceecc5d12667bd7c66a4.mp3/SHA256E-s7701150--8197e499408e64601157df95927ac6b09bd37834a41eceecc5d12667bd7c66a4.mp3 +lrwxrwxrwx 1 voltagex voltagex 200 Aug 11 23:05 06 Clash.mp3 -> .git/annex/objects/ZQ/P4/SHA256E-s10201572--c2a1a8892fcaaab1ed59ca7f5ab9d45f0c3bb3c6d6450b95228039b9e8d7a0b4.mp3/SHA256E-s10201572--c2a1a8892fcaaab1ed59ca7f5ab9d45f0c3bb3c6d6450b95228039b9e8d7a0b4.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 07 Newbop.mp3 -> .git/annex/objects/Fk/wV/SHA256E-s6850587--b5ba0347f6a09a7ff8bec2dd1fbe8076fdff645d4bc1909ddeadfc035bf19fda.mp3/SHA256E-s6850587--b5ba0347f6a09a7ff8bec2dd1fbe8076fdff645d4bc1909ddeadfc035bf19fda.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 08 Glory of Nelly.mp3 -> .git/annex/objects/Pm/K3/SHA256E-s9002048--18149581cbfc3b4e3e72b784777fe34c53f1580e78e97f66058be0b1eb40e809.mp3/SHA256E-s9002048--18149581cbfc3b4e3e72b784777fe34c53f1580e78e97f66058be0b1eb40e809.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 09 Dramophone.mp3 -> .git/annex/objects/k3/Jf/SHA256E-s8199558--925117d9fc47a65e8e5324f3d0638a3c24bf51fd6c0b5d8ac2f63951c893cc48.mp3/SHA256E-s8199558--925117d9fc47a65e8e5324f3d0638a3c24bf51fd6c0b5d8ac2f63951c893cc48.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 10 Cotton Heads.mp3 -> .git/annex/objects/9f/32/SHA256E-s8801425--c6926238c0b1a3bbea1a5d17841ceac591e53e223e4c4c45a2077cabffc85d81.mp3/SHA256E-s8801425--c6926238c0b1a3bbea1a5d17841ceac591e53e223e4c4c45a2077cabffc85d81.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 11 Panic.mp3 -> .git/annex/objects/XF/WF/SHA256E-s9833770--5e837c7fa3ec096f7c0507efbcf398067029749f8a0fc77a2badf864b9ffbb7c.mp3/SHA256E-s9833770--5e837c7fa3ec096f7c0507efbcf398067029749f8a0fc77a2badf864b9ffbb7c.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 12 Pirates.mp3 -> .git/annex/objects/7Z/jz/SHA256E-s8017742--5fd49b2d89577266d2fb740e7e7def9338475af90c2ca99f9d6d513465b2bfac.mp3/SHA256E-s8017742--5fd49b2d89577266d2fb740e7e7def9338475af90c2ca99f9d6d513465b2bfac.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 13 Beatophone.mp3 -> .git/annex/objects/81/xv/SHA256E-s9339544--a1eb8404ecf0503b9f635378fec4e2c95ec08bb1428c2cd4c0cedf492811577d.mp3/SHA256E-s9339544--a1eb8404ecf0503b9f635378fec4e2c95ec08bb1428c2cd4c0cedf492811577d.mp3 +lrwxrwxrwx 1 voltagex voltagex 198 Aug 11 23:05 14 Sydney.mp3 -> .git/annex/objects/3K/99/SHA256E-s8459731--4ff44b25c912e914c79124ff9074c576c0024152442fc96c9bad65f5a50a40d9.mp3/SHA256E-s8459731--4ff44b25c912e914c79124ff9074c576c0024152442fc96c9bad65f5a50a40d9.mp3 +lrwxrwxrwx 1 voltagex voltagex 192 Aug 11 23:05 Thumbs.db -> .git/annex/objects/28/Zv/SHA256E-s85504--3604669cd3a55234516191eb4f19434829c1634d6dd69a9981185f095d2bbaba.db/SHA256E-s85504--3604669cd3a55234516191eb4f19434829c1634d6dd69a9981185f095d2bbaba.db + +# End of transcript or log. +"""]] diff --git a/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_1_c87bae87b7902db60a3fef41e1fca85d._comment b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_1_c87bae87b7902db60a3fef41e1fca85d._comment new file mode 100644 index 000000000..0577531b7 --- /dev/null +++ b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_1_c87bae87b7902db60a3fef41e1fca85d._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlzWwnBfgJrkhPQakBo6DbPXutJIVDHkj0" + nickname="Adam" + subject="comment 1" + date="2013-08-11T14:15:40Z" + content=""" +Confirming the same errors happen with git-annex version: 4.20130802 from sid. + +"""]] diff --git a/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_2_9e3c1f1ba05d8996b5a95829ce32c07e._comment b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_2_9e3c1f1ba05d8996b5a95829ce32c07e._comment new file mode 100644 index 000000000..d98e7976e --- /dev/null +++ b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_2_9e3c1f1ba05d8996b5a95829ce32c07e._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="bad bug report title 101" + date="2013-08-24T19:17:29Z" + content=""" +I don't understand why you think the problem has something to do with Windows drive letters. There are no Windows drive letters in the symlinks you show. The only place I see any Windows drive letter is in the descripton of the remote that `git annex get` displays when it fails to get the file. That description is purely informative, it's not a path that git-annex is trying to use. + +I'd suggest that you run `git annex get --debug` to see if it is doing anything obviously wrong. The mostly likely culprit is your SMB setup, which I am not going to be able to replicate. +"""]] diff --git a/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_3_3a0787912f4a3a8797b7786f5ce38590._comment b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_3_3a0787912f4a3a8797b7786f5ce38590._comment new file mode 100644 index 000000000..16f240cf2 --- /dev/null +++ b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_3_3a0787912f4a3a8797b7786f5ce38590._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlzWwnBfgJrkhPQakBo6DbPXutJIVDHkj0" + nickname="Adam" + subject="comment 3" + date="2013-08-26T06:56:33Z" + content=""" +You're correct. I can see in .git/config that the remote references z:\ which of course will break on the Linux side. Maybe this is a case of the error messages not quite telling me the right thing? +"""]] diff --git a/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_4_c4249f32d65594d79ea01145b93ec948._comment b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_4_c4249f32d65594d79ea01145b93ec948._comment new file mode 100644 index 000000000..31bc7c1a1 --- /dev/null +++ b/doc/bugs/Windows_to_Linux_clone_-_Windows_drive_letters_cause_git_annex_get_to_fail/comment_4_c4249f32d65594d79ea01145b93ec948._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 4" + date="2013-09-13T19:29:25Z" + content=""" +I'd suggest that you run git annex get --debug to see if it is doing anything obviously wrong. The mostly likely culprit is your SMB setup, which I am not going to be able to replicate. + +"""]] 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 new file mode 100644 index 000000000..e7ff53723 --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes.mdwn @@ -0,0 +1,44 @@ +### 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 new file mode 100644 index 000000000..578fecb58 --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_1_0f8b248025722309e9577d7dad74b76b._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..ceb05ea0c --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_2_f5f7db688a2a93ee7453674fb742043b._comment @@ -0,0 +1,52 @@ +[[!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 new file mode 100644 index 000000000..78e816f06 --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_3_ffcae976aa3dc2426188797c1aaffb82._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..2bf32bd37 --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_4_8a7ff6841ad7c27ead06bf12f46b20a0._comment @@ -0,0 +1,49 @@ +[[!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 new file mode 100644 index 000000000..f8f223524 --- /dev/null +++ b/doc/bugs/Zombie_processes_and__47__or_stuck_git_processes/comment_5_406fdee0728680774a69d28446163f10._comment @@ -0,0 +1,26 @@ +[[!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/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn new file mode 100644 index 000000000..9befd7c80 --- /dev/null +++ b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error..mdwn @@ -0,0 +1,39 @@ +### Please describe the problem. + +After setting the username (xyz@gmail.com) and the password the webapp takes several minutes until eventually an error message is displayed stating that: + + Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: host gmail.com:5222 failed: connect: does not exist (Network is unreachable)) + +Testing with xyz@xmpp.l.gmail.com yields: + + Unable to connect to the Jabber server. Maybe you entered the wrong password? (Error message: host xmpp.l.google.com:5222 failed: AuthenticationFailure) + +What's strange about that is that the exact same procedure works on a different (Ubuntu-) system with almost no time spend. + +### What steps will reproduce the problem? + +Trying to set up the jabber connection. + +### What version of git-annex are you using? On what operating system? + + git-annex version: 4.20130922-g7dc188a + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi + (actually a zeroinstall feed from here: http://f12n.de/0install/git-annex-webapp.xml which is based on the standalone build) + +OS: up-to-date ARCH 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 + +[2013-09-23 19:24:04 CEST] main: starting assistant version 4.20130922-g7dc188a +(scanning...) [2013-09-23 19:24:04 CEST] Watcher: Performing startup scan +(started...) +[2013-09-23 20:18:12 CEST] read: host ["-t","SRV","--","_xmpp-client._tcp.gmail.com"] +.git/annex/daemon.log (END) + +# End of transcript or log. +"""]] diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment new file mode 100644 index 000000000..c2dd31f17 --- /dev/null +++ b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_1_6d821af99ab3c83a5b0f52d3713ab8e2._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.220" + subject="comment 1" + date="2013-09-25T18:27:24Z" + content=""" +Sounds like the SRV lookup is failing. Does `git-annex version` list either DNS or ADNS in the build flags? + +Does `host -t SRV _xmpp-client._tcp.gmail.com` work? +"""]] diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment new file mode 100644 index 000000000..1cb191d8f --- /dev/null +++ b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_2_206b6c8cce8350fc088f01c42fc4715b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawknwkXgi8SnK4QT32ANl3GMKvFLyQGeHqo" + nickname="Florian" + subject="comment 2" + date="2013-09-25T21:19:23Z" + content=""" +Aaaah ok ... the *host* command is not installed by default on Arch Linux. I've installed it ... now it works ... will report it to the package maintainer. +"""]] diff --git a/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment new file mode 100644 index 000000000..a69763af7 --- /dev/null +++ b/doc/bugs/__34__Configuring_Jabber_Account__34___fails_with_a___34__Network_unreachable__34___error./comment_3_ed36f503f88611382b50687608b9b7e7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 3" + date="2013-11-08T18:42:22Z" + content=""" +Seems like I should fix the standalone linux tarball to either include the host program, or better, build git-annex with the Haskell [DNS library](https://hackage.haskell.org/package/dns). (I think that the Mac app and other builds are built with DNS by default, since they have dependencies installed using cabal directly). + +I need to first get that library included in Debian, so I can install it reliably on my build systems. +"""]] 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 new file mode 100644 index 000000000..7968d32cc --- /dev/null +++ b/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu.mdwn @@ -0,0 +1,22 @@ +### 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. +"""]] 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 new file mode 100644 index 000000000..34a2ed325 --- /dev/null +++ b/doc/bugs/__40__assistant__41___dependency_on_ssh-askpass_-_not_installed_automatically_on_xubuntu/comment_1_f4656f8a0f36535def0772db06098c5f._comment @@ -0,0 +1,13 @@ +[[!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/__96__git_annex_import__96___clobbers_mtime.mdwn b/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn index ce1c67fee..7edebe584 100644 --- a/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn +++ b/doc/bugs/__96__git_annex_import__96___clobbers_mtime.mdwn @@ -58,3 +58,5 @@ mtimes are clobbered with what I think is the time of the first time `git annex` 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_4_7235130786e764ec3ad5facfecde62da._comment b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_4_7235130786e764ec3ad5facfecde62da._comment new file mode 100644 index 000000000..8bc6274f9 --- /dev/null +++ b/doc/bugs/__96__git_annex_import__96___clobbers_mtime/comment_4_7235130786e764ec3ad5facfecde62da._comment @@ -0,0 +1,8 @@ +[[!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__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn new file mode 100644 index 000000000..1580cee81 --- /dev/null +++ b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories.mdwn @@ -0,0 +1,113 @@ +### Please describe the problem. + +`git annex import otherrepo` does not work. + + +### What steps will reproduce the problem? + + richih@eudyptes ~ % mcd killme/git-annex-source + richih@eudyptes ~/killme/git-annex-source % git init; git annex init + Initialized empty Git repository in /home/richih/killme/git-annex-source/.git/ + init ok + (Recording state in git...) + richih@eudyptes (git)-[master] ~/killme/git-annex-source % dd if=/dev/urandom of=foo bs=1M count=1 + 1+0 records in + 1+0 records out + 1048576 bytes (1.0 MB) copied, 0.281043 s, 3.7 MB/s + richih@eudyptes (git)-[master] ~/killme/git-annex-source % git annex add . + add foo (checksum...) ok + (Recording state in git...) + richih@eudyptes (git)-[master] ~/killme/git-annex-source % git commit -m files + [master (root-commit) 8054eeb] files + 1 file changed, 1 insertion(+) + create mode 120000 foo + richih@eudyptes (git)-[master] ~/killme/git-annex-source % mcd ../git-annex-import + richih@eudyptes ~/killme/git-annex-import % git init; git annex init + Initialized empty Git repository in /home/richih/killme/git-annex-import/.git/ + init ok + (Recording state in git...) + richih@eudyptes (git)-[master] ~/killme/git-annex-import % git annex import ../git-annex-source/foo + richih@eudyptes (git)-[master] ~/killme/git-annex-import % ls + +### What version of git-annex are you using? On what operating system? + +4.20130920 on Debian Sid + + +### PS: + +To add insult to injury, this does "work": + + ih@eudyptes (git)-[master] ~/killme/git-annex-import % mcd bar + richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % git annex import ../../git-annex-source/ + import .git/description (checksum...) ok + import .git/HEAD (checksum...) ok + import .git/config (checksum...) ok + import .git/index (checksum...) ok + import .git/COMMIT_EDITMSG (checksum...) ok + import .git/refs/heads/git-annex (checksum...) ok + import .git/refs/heads/master (checksum...) ok + import .git/hooks/update.sample (checksum...) ok + import .git/hooks/applypatch-msg.sample (checksum...) ok + import .git/hooks/pre-rebase.sample (checksum...) ok + import .git/hooks/pre-commit.sample (checksum...) ok + import .git/hooks/pre-applypatch.sample (checksum...) ok + import .git/hooks/prepare-commit-msg.sample (checksum...) ok + import .git/hooks/commit-msg.sample (checksum...) ok + import .git/hooks/post-update.sample (checksum...) ok + import .git/hooks/pre-push.sample (checksum...) ok + import .git/hooks/pre-commit (checksum...) ok + import .git/info/exclude (checksum...) ok + import .git/objects/4b/825dc642cb6eb9a060e54bf8d69288fbee4904 (checksum...) ok + import .git/objects/a2/6f9bdbe47ada699d537eaa8b6fbfc1e53ef214 (checksum...) ok + import .git/objects/30/4b790d132863d54313e2380bed17e557944f08 (checksum...) ok + import .git/objects/ab/09feaa1b55080f42ccfad8c8bb5612f2397c5a (checksum...) ok + import .git/objects/95/b73ee41ebe8abbd5d8c0c368d1148b5256d4f2 (checksum...) ok + import .git/objects/2e/96f9962c1baf83c563aa59dcc67e19f21d4b1f (checksum...) ok + import .git/objects/74/6306e594874907246b2300b3af22f2805dde3e (checksum...) ok + import .git/objects/5b/11e29d0ef96be4ee73f8dae9b2f525cb808ef1 (checksum...) ok + import .git/objects/fc/0c0dc4d0579a15c20be29186a27feb2ee77304 (checksum...) ok + import .git/objects/73/c38d817e0a9f1ef4699551ae83130edd166364 (checksum...) ok + import .git/objects/c9/80716b5b506515410ca3ad1d88ceae13d8f6f9 (checksum...) ok + import .git/objects/e2/6cb10dbce11f4065c249183bb085d0afc1b55d (checksum...) ok + import .git/objects/80/54eeb150b094b0d8483c43ccf2ddf182c71bd3 (checksum...) ok + import .git/annex/sentinal (checksum...) ok + import .git/annex/sentinal.cache (checksum...) ok + import .git/annex/index (checksum...) ok + import .git/annex/index.lck (checksum...) ok + import .git/annex/journal.lck (checksum...) ok + import .git/annex/objects/F7/zw/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59 + git-annex: ../../git-annex-source/.git/annex/objects/F7/zw/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59/SHA256E-s1048576--74f3a1a65df608d1c8ae575f83c6ee21a5aeb1a914ca73f202a881f8c3ba8f59: rename: permission denied (Permission denied) + failed + import .git/logs/HEAD (checksum...) ok + import .git/logs/refs/heads/git-annex (checksum...) ok + import .git/logs/refs/heads/master (checksum...) ok + (Recording state in git...) + error: Invalid path 'bar/.git/COMMIT_EDITMSG' + error: unable to add bar/.git/COMMIT_EDITMSG to index + fatal: adding files failed + + git-annex: user error (xargs ["-0","git","--git-dir=/home/richih/killme/git-annex-import/.git","--work-tree=/home/richih/killme/git-annex-import","add","--"] exited 123) + failed + git-annex: import: 2 failed + richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % ls -la + total 0 + drwxr-xr-x 3 richih richih 17 Sep 24 01:45 . + drwxr-xr-x 4 richih richih 38 Sep 24 01:45 .. + drwxr-xr-x 8 richih richih 152 Sep 24 01:45 .git + richih@eudyptes (git)-[master] ~/killme/git-annex-import/bar % + +> I have made git-annex import skip .git directories. Of course, +> running it on *any* directory without the --duplicate option +> will result in it moving data to git-annex, so is not advisable +> to do that if you want to keep the data in the directory where it was. +> +> I am doubtful about special-casing git-annex import to do something +> else when told to import a git-annex repository. It seems a bit of a +> slippery slope to it getting very complicated, which we seem to already be +> further down than I would like. If people are this pissed off about +> git-annex import's behavior, +> I would be inclined to *remove* it. Then you can use `mv` and `git annex +> add`. I originally wrote git-annex import just to avoid needing to run +> those 2 commands myself, and I can make my own local shell script +> to do that... --[[Joey]] diff --git a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment new file mode 100644 index 000000000..4de9cc10d --- /dev/null +++ b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_1_94ccd548c084286163eeb2af1ddc18e3._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.220" + subject="comment 1" + date="2013-09-25T18:21:25Z" + content=""" +Import skips symlinks and other non-regular files. It would work if the source repository was in direct mode. +"""]] diff --git a/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment new file mode 100644 index 000000000..9996882fc --- /dev/null +++ b/doc/bugs/__96__git_annex_import__96___does_not_work_on_other_git_annex_repositories/comment_2_befde3ef3d2b171ebb691915ff3af172._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + ip="72.0.72.144" + subject="it's worse than not working, it kills! :)" + date="2013-10-07T12:06:22Z" + content=""" +so yeah, it doesn't really work well, and maybe that is to be expected because of symlinks, but it's much worse than that: the original git annex repo will actually be destroyed because git annex import will [[trash the .git metadata directory|bugs/git_annex_import_destroys_a_fellow_git_annex_repository]]. Recovering from that is... interesting, to say the least. :) +"""]] diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn b/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn new file mode 100644 index 000000000..825d9527b --- /dev/null +++ b/doc/bugs/__96__git_annex_sync__96___ignores_remotes.mdwn @@ -0,0 +1,106 @@ +### Please describe the problem. + +A mere `git annex sync` does not go through the reachable remotes. + +### What steps will reproduce the problem? + +I do not know what could have put my repository in this state. + +### What version of git-annex are you using? On what operating system? + +git-annex version: 4.20130802-g1452ac3 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP +local repository version: 4 +default repository version: 3 +supported repository versions: 3 4 +upgrade supported from repository versions: 0 1 2 + +Linux dawn 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux + +### Please provide any additional information below. + +[[!format sh """ +% 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: 1 + f3cb4e8f-65f1-4ded-a6a1-abef64ddcff5 -- zoidberg (sam@git-annex:/media/git-annex/Music) +semitrusted repositories: 5 + 00000000-0000-0000-0000-000000000001 -- web + 063a31dc-542d-407f-a9ed-124479fa6354 -- here (dawn) + 22b72aa6-058b-4622-8132-27aa2d8950dc -- arrakis (sam@arrakis:~/Music) + 5b3a1abf-5e0b-41bc-a141-774d6236ec76 -- backup on old USB disk + 6affec3c-fd26-11e2-9ddd-53f02e5ca176 -- music on eeePC +untrusted repositories: 0 +transfers in progress: none +available local disk space: 9.83 gigabytes (+1 megabyte reserved) +local annex keys: 3947 +local annex size: 23.51 gigabytes +known annex keys: 3965 +known annex size: 23.56 gigabytes +bloom filter size: 16 mebibytes (0.8% full) +backend usage: + SHA256E: 7912 + +% git remote -v +arrakis arrakis:Music (fetch) +arrakis arrakis:Music (push) +zoidberg ssh://git-annex@zoidberg.rfc1149.net:2222/~/Music (fetch) +zoidberg ssh://git-annex@zoidberg.rfc1149.net:2222/~/Music (push) + +# Note how here it does not seem to sync with any remote +% git annex sync +(Recording state in git...) +commit +ok + +% git annex sync zoidberg +(Recording state in git...) +commit +ok +pull zoidberg +ok +push zoidberg +Everything up-to-date +ok + +% git annex sync arrakis +(Recording state in git...) +commit +ok +pull arrakis +From arrakis:Music + c1a24bd..ba060b7 git-annex -> arrakis/git-annex + 98b9a8e..be9c146 master -> arrakis/master + e0df2be..be9c146 synced/master -> arrakis/synced/master +ok + +# A nameless sync with debug turned on +% git annex sync --debug +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","symbolic-ref","HEAD"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","refs/heads/master"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","git-annex"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--hash","refs/heads/git-annex"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..ba060b7777413ab687d64771b5d6c2b36a072335","--oneline","-n1"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..f401f2b7b67567862df7c5b8d304f52c3af43f4b","--oneline","-n1"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..feaba7c5ea5f4ca73c123e6ea44ffd6333bf383e","--oneline","-n1"] +[2013-08-06 10:59:57 CEST] chat: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","cat-file","--batch"] +[2013-08-06 10:59:57 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","ls-files","--stage","-z","--others","--exclude-standard","--","/home/sam/Music"] +[2013-08-06 10:59:57 CEST] chat: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","cat-file","--batch"] +(Recording state in git...) +[2013-08-06 11:00:16 CEST] feed: xargs ["-0","git","--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","add","-f"] +commit +[2013-08-06 11:00:16 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","commit","-m","git-annex automatic sync"] +ok +[2013-08-06 11:00:17 CEST] call: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--verify","-q","refs/heads/synced/master"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/master..refs/heads/synced/master","--oneline","-n1"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","git-annex"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","show-ref","--hash","refs/heads/git-annex"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..ba060b7777413ab687d64771b5d6c2b36a072335","--oneline","-n1"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..f401f2b7b67567862df7c5b8d304f52c3af43f4b","--oneline","-n1"] +[2013-08-06 11:00:17 CEST] read: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","log","refs/heads/git-annex..feaba7c5ea5f4ca73c123e6ea44ffd6333bf383e","--oneline","-n1"] +[2013-08-06 11:00:17 CEST] call: git ["--git-dir=/home/sam/Music/.git","--work-tree=/home/sam/Music","branch","-f","synced/master"] +"""]] + +[[done]] diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment new file mode 100644 index 000000000..a88baa834 --- /dev/null +++ b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_1_39421e6935233cd8f45949ebdef369fe._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 1" + date="2013-08-07T16:13:31Z" + content=""" +It seems to me that you must have set `git config remote.zoidberg.annex-sync false` +(or clicked around in the webapp and caused it to set that). If you set annex-sync back to true, it will sync with all remotes by default. +"""]] diff --git a/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment new file mode 100644 index 000000000..1b870e1f7 --- /dev/null +++ b/doc/bugs/__96__git_annex_sync__96___ignores_remotes/comment_2_53fb15d6fbf96d43564ff7c866239d18._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://www.rfc1149.net/" + nickname="Sam" + subject="Indeed" + date="2013-08-07T16:17:41Z" + content=""" +You are perfectly right. Every remote had this parameter set to false for a reason I do not know. +"""]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow.mdwn b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow.mdwn index 46024e500..95751527b 100644 --- a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow.mdwn +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow.mdwn @@ -79,3 +79,9 @@ What version of git-annex are you using? On what operating system? git-annex version: 3.20130216 On current Debian sid/experimental + +> [[Done]], thanks to guilhem. We ended up using a different algorythm +> which is faster yet, basically it now does a diff-index between the +> index and each branch for its second stage bloom filter. +> Speedup is 30x with 0 (or 1?) branch, and then massive for each +> additional branch. --[[Joey]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_3_12b20cbbc2b4cd1ab8af7e3eec9589b4._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_3_12b20cbbc2b4cd1ab8af7e3eec9589b4._comment new file mode 100644 index 000000000..9c1da8eea --- /dev/null +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_3_12b20cbbc2b4cd1ab8af7e3eec9589b4._comment @@ -0,0 +1,30 @@ +[[!comment format=mdwn + username="arand" + ip="130.243.226.21" + subject="comment 3" + date="2013-08-10T17:00:21Z" + content=""" +So, if I've understood it correctly (please correct me if that's not the case :) ) + +Currently git-annex unused goes through this process + +* Look through all files in the index and find those which are git-annex keys (git ls-tree + git cat-file) +* Look through all files the current ref and find those which are git-annex keys (git ls-tree + git cat-file) +* For each ref in the repo + - Look through all files and find those which are git-annex keys (git ls-tree + git cat-file) +* Then at the end + - Compare this list of keys with what is stored in .git/annex/objects + - Print out any objects which does not match a key. + +If that's the case, it means if that if you have multiple refs, even is they only differ by single empty commits, git-annex will end up doing a cat-file for the same file multiple times (one per ref), which is expensive. + +Would it be possible to change the algorithm for git-annex unused into instead something like: + +* For the index, HEAD, and all refs + - Create a list all files and remove those which are duplicates based on their sha1 hash (git ls-tree | uniq) +* Then Look through this reduced list to find those which are git-annex keys (git cat-file) +* Then check as before + +Unless this bypasses some safety or case I've overlooked, I think it should be possible to speed up git-annex unused quite a bit. + +"""]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_4_a50b43c15d2650df90f0fa1ced47f532._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_4_a50b43c15d2650df90f0fa1ced47f532._comment new file mode 100644 index 000000000..3de85407e --- /dev/null +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_4_a50b43c15d2650df90f0fa1ced47f532._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 4" + date="2013-08-11T12:48:47Z" + content=""" +I think that could work. It would probably tend to use more memory than the current method, but only a small constant multiplier more. And unused is already the one command that necessarily needs to hold information about the whole repository in memory. + +Note that git cat-file is only needed when dealing with branches other than the current working tree. In that special case, it can, and AFAIK does have the optimisation of looking directly at the symlink target instead. Your method may turn out to be both slower and use more memory in that case. It may make sense to special case handling of that case and keep the current code paths there (most of the necessary code for it is used by other stuff anyway). +"""]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_5_7328bc51bd001f2b732a92a2ae175839._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_5_7328bc51bd001f2b732a92a2ae175839._comment new file mode 100644 index 000000000..21890a4e1 --- /dev/null +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_5_7328bc51bd001f2b732a92a2ae175839._comment @@ -0,0 +1,114 @@ +[[!comment format=mdwn + username="arand" + ip="130.243.226.21" + subject="comment 5" + date="2013-08-11T20:43:22Z" + content=""" +I've compared my bash/coreutils implementation mentioned above [annex-funused](https://gitorious.org/arand-scripts/arand-scripts/blobs/918cc79b99e22cbdca01ea4de10e2ca64abfc27a/annex-funused) with `git annex unused` in various situations, and from what I've seen `annex-funused` is pretty much always faster. + +In the case of no unused files they seem to be about the same. + +In all other cases there is a very considerable difference, for example, in my current main annex I get: + + $ time git annex unused + unused . (checking for unused data...) (checking master...) (checking synced/master...) (checking barracuda160G/master...) ok + + real 5m13.830s + user 2m0.444s + sys 0m28.344s + + +whereas + + $ time annex-funused + == WARNING == + This program should NOT be trusted to reliably find unused files in the + git annex. + + + real 0m1.569s + user 0m2.024s + sys 0m0.184s + +I tried to check memory usage via `/usr/bin/time -v` as well, and that showed (re-running in the same annex as above) + +annex-funused + + Maximum resident set size (kbytes): 13560 + +git annex unused + + Maximum resident set size (kbytes): 29120 + + +I've also written a comparison script [annex-testunused](https://gitorious.org/arand-scripts/arand-scripts/blobs/918cc79b99e22cbdca01ea4de10e2ca64abfc27a/annex-testunused) (needs annex-funused in $PATH) which creates an annex with a bunch of unused files and compares the running time for both versions: + +<pre> +$ annex-testunused +Initialized empty Git repository in /tmp/tmp.fmsAvsPTcd/.git/ +init ok +(Recording state in git...) +### +* b2840d7 (HEAD, master) delete ~1100 files +* c4a1e3a add 3000 files +* bc19777 (git-annex) update +* b3e6539 update +* bec2c8f branch created +annex unused +real 0m4.154s +real 0m2.029s +real 0m2.044s +annex funused +real 0m0.923s +real 0m0.933s +real 0m0.905s +Initialized empty Git repository in /tmp/tmp.7qFoCRWzB3/.git/ +init ok +(Recording state in git...) +### +* a5ff392 (HEAD, master) empty +* cca4810 (1) delete ~1100 files +* 587c406 add 3000 files +* de0afeb (git-annex) update +* 37b7881 update +* 1735062 branch created +annex unused +real 0m3.499s +real 0m3.443s +real 0m3.435s +annex funused +real 0m0.956s +real 0m0.956s +real 0m0.874s +Initialized empty Git repository in /tmp/tmp.L5fjdAgnFv/.git/ +init ok +(Recording state in git...) +### +* 94463a0 (HEAD, master) empty +* e115619 (10) empty +* 20686d4 (9) empty +* 2e01a3f (8) empty +* 043289d (7) empty +* 6a52966 (6) empty +* 0dc866d (5) empty +* 35db331 (4) empty +* 48504bc (3) empty +* e25cac7 (2) empty +* 655d026 (1) delete ~1100 files +* 91a07d1 add 3000 files +* 3c9ac62 (git-annex) update +* c5736e0 update +* 862d5b8 branch created +annex unused +real 0m16.242s +real 0m16.277s +real 0m16.246s +annex funused +real 0m0.960s +real 0m0.960s +real 0m0.927s +</pre> + +So, unless I've missed something fundamental (I keep thinking I might have...), it seems to be very consistently faster, and scale ok where `git annex unused` scales rather poorly. + +"""]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_6_880ef2ee797221332dbb629b2d55522f._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_6_880ef2ee797221332dbb629b2d55522f._comment new file mode 100644 index 000000000..a4fea313f --- /dev/null +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_6_880ef2ee797221332dbb629b2d55522f._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 6" + date="2013-08-12T04:14:18Z" + content=""" +The memory usage is probably lower because `sort` and `comm` and bash's `<(command)` all have particularly well tuned memory usage with 37 years of history behind them. Particularly GNU `sort` will transparently use a temp file rather than storing too much data in memory, and does rather sophisticated stuff to make that work efficiently. It's rather harder to get that kind of behavior when not using the unix tools and instead using stock programming language primatives like sort() and hashes. + +I still suspect that `git cat-file` is slower than a direct readlink(2) of the symlink, when that can be done. +"""]] diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_7_826fd82cdf9b1c79c9b555ca26c2c176._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_7_826fd82cdf9b1c79c9b555ca26c2c176._comment new file mode 100644 index 000000000..c2dbd1810 --- /dev/null +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_7_826fd82cdf9b1c79c9b555ca26c2c176._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="arand" + ip="130.243.226.21" + subject="comment 7" + date="2013-08-12T18:07:44Z" + content=""" +Hmm, probably, do you think this way of getting everything and then doing the filtering could work reasonably in git-annex? Assuming \"git cat-file --batch\" is the main bottleneck, reducing the amount of runs for it would still likely be an improvement? +"""]] diff --git a/doc/bugs/addurl_fails_on_the_internet_archive.mdwn b/doc/bugs/addurl_fails_on_the_internet_archive.mdwn new file mode 100644 index 000000000..556575db6 --- /dev/null +++ b/doc/bugs/addurl_fails_on_the_internet_archive.mdwn @@ -0,0 +1,65 @@ +### Please describe the problem. + +`addurl` doesn't support the internet archive: + +1. it doesn't actually accept the proper URL as a secondary source of content +2. it doesn't parse the HTML from the video page (the "details page") + +### What steps will reproduce the problem? + + # download eben moglen's excellent re:publica presentation from youtube + git annex addurl https://www.youtube.com/watch?v=sKOk4Y4inVY + # copy that file aside + cp -L re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak + # drop it so we can try again + git annex drop re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm + # add the IA URL for the same video, failing + git annex addurl --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm + # try again with --relaxed to skip some checks + git annex addurl --relaxed --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm + # observe both files are the same size and checksum + +The files should look like this: + +[[!format txt """ +anarcat@angela:presentations$ ls -alL re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm* +-r--r--r-- 1 anarcat anarcat 419359123 oct 9 23:41 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +-r--r--r-- 1 anarcat anarcat 419359123 oct 11 19:40 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak +anarcat@angela:presentations$ md5sum re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm* +7892df24a9e1c40e2587be1035728ef0 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +7892df24a9e1c40e2587be1035728ef0 re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm-bak +"""]] + +There are two separate bugs here: one is the above need to use --relaxed even though the file is the same. + +The second is probably simply that quvi doesn't support the internet archive, and maybe that one should be moved to a separate [[todo]]/[[wishlist]]. I was expecting this to "do the right thing" (ie. download the video): + + git annex addurl http://archive.org/details/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia + +... but instead it downloads the HTML. +### What version of git-annex are you using? On what operating system? + +my good old faithful `4.20130921-g434dc22` i compiled manually some time ago. :) + +This is [[done]] in git-annex version: 4.20131011-g2c0badc. Thanks! + +### Please provide any additional information below. + +[[!format sh """ +anarcat@marcos:presentations$ git annex addurl --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://archive.org/download/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +addurl re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm + failed to verify url exists: http://archive.org/download/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +failed +git-annex: addurl: 1 failed +anarcat@marcos:presentations$ git annex addurl --debug --file=re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +[2013-10-09 18:26:30 EDT] call: quvi ["-v","mute","--support","http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm"] +addurl re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm [2013-10-09 18:26:30 EDT] read: curl ["-s","--head","-L","http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm","-w","%{http_code}"] + + failed to verify url exists: http://ia601009.us.archive.org/9/items/Republica2012-EbenMoglen-FreedomOfThoughtRequiresFreeMedia/re_publica_2012___Eben_Moglen___Freedom_of_Thought_Requires_Free_Media.webm +failed +git-annex: addurl: 1 failed +"""]] + +Originally reported in [[tips/Internet_Archive_via_S3]]. --[[anarcat]] + +> [[done]] --[[Joey]] diff --git a/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment b/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment new file mode 100644 index 000000000..4754b8366 --- /dev/null +++ b/doc/bugs/addurl_fails_on_the_internet_archive/comment_1_e227aa25eea0b41f1176037a601c5844._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.22" + subject="comment 1" + date="2013-10-11T18:49:25Z" + content=""" +Afaik this was fixed in 747f5b123cb3c6b3b87d4e79f8767e69d842b96b. + +Probably noone has bothered to add IA support to quvi, but it should be doable. +"""]] diff --git a/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment b/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment new file mode 100644 index 000000000..f24d0583f --- /dev/null +++ b/doc/bugs/addurl_fails_on_the_internet_archive/comment_2_6d4fd58f0caa1f75ee2dd3f0a909cd91._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + ip="72.0.72.144" + subject="awesome, fix confirmed, and IA+quvi forwarded upstream" + date="2013-10-12T11:23:31Z" + content=""" +Great! I confirm latest versions work properly.. I have [written the quvi-devel mailing list](http://sourceforge.net/mailarchive/forum.php?thread_name=20131012104904.GA11972%40angela.anarcat.ath.cx&forum_name=quvi-devel) to ask for help for archive.org support, we'll see where it goes... +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn new file mode 100644 index 000000000..e739b9691 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. + +I installed git-annex on my android device (Nook HD+, with Cyanogenmod 10.1 installed) for the first time today and was excited to get it working. However, I noticed the device warming alarmingly, and, after installing a CPU usage monitor, it became clear that git annex was the problem, as it was hovering around 30-40% even when idle. + +I tried quitting git-annex using the webapp's "Shutdown Daemon" menu option, and it seemed to shut down successfully, but the CPU monitor still showed that process present and taking up high amounts of CPU (sometimes well over 50%). I used the android app switcher and noticed that the terminal emulator for git annex was still running; I tried to quit this by using the X button and it seemed to close, but the CPU monitor still showed the git-annex process consuming large amounts of CPU. Finally I had to quit the process forcefully from the monitor. + +### What steps will reproduce the problem? + +Install & run; observe CPU. I used a dedicated CPU monitor to stop it the first time; another time, I tried stopping it by going to Preferences, Apps, Running Applications, where it told me it had one process and one service running. I stopped the service without issue; it said the process could not be safely stopped but I stopped it anyway and that successfully stopped the app. + + +### What version of git-annex are you using? On what operating system? + +the current (4.20130826-g46f422) version on Android. + +### 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'm not sure how to get a log out of the web app to paste here unfortunately. + +# End of transcript or log. +"""]] + +> [[done]]; I fixed the bug which turned out to be a stupid +> minunderstanding of how a java library worked. --[[Joey]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment new file mode 100644 index 000000000..892894ad4 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_1d841ff0b0ffd814efed2449dc1f35f3._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 10" + date="2013-08-27T01:46:36Z" + content=""" +This seems to be a reversion instroduced in commit a48d340abdaf3296a2ddacd73c18adc9a13a02ef. With that backed out, I get 0% cpu usage for the terminal app. Even if I run top in the terminal, its CPU sits under 1%. + +Clearly the infinite loop in that patch is running faster than expected! +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment new file mode 100644 index 000000000..d8ca9fb05 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_10_cd101e0af45d8f463011fb0d04b3b822._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 10" + date="2013-08-26T20:19:06Z" + content=""" +Yeah, that would definitely explain both what I'm seeing and why you haven't been seeing it. + +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment new file mode 100644 index 000000000..085f3d108 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_11_8595041cfe703d9bea49e792732dc15f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 11" + date="2013-08-27T02:27:08Z" + content=""" +Awesome! I'll grab a new nightly in a day or two and give it another shot. +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment new file mode 100644 index 000000000..756b9d5c6 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_1_8e7bc6965ea967a8d43240791a30c5bc._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 1" + date="2013-08-26T18:34:44Z" + content=""" +Just noticed I was using the autobuild instead of the last release version; I'll try the release version and see if that makes any difference. + +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment new file mode 100644 index 000000000..c26c512ea --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_2_891c1073f908b204651899d41599f944._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 2" + date="2013-08-26T18:42:02Z" + content=""" +If you shut down the daemon, it seems to me that the process that was still running would probably be `git annex transferkey` which runs in its own process to upload/download file contents. I normally see 0% to 1% cpu use from git-annex when it is running on my android tablet. It's possible that the 1% use is due to it waking up every second, which got fixed in 9dc2373977d583b4c4aa6cf0555dc97309f89991. +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment new file mode 100644 index 000000000..71ad88d74 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_3_de02b8f1b5928fa1a7078c4aa2124bea._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 3" + date="2013-08-26T19:03:45Z" + content=""" +OK, so I might have a rogue transferkey process going on, but one which starts over again when I restart the app? + +I've set this all up purely as a \"can I do this\" experiment right now; there is literally zero important data there to lose, either on the tablet or on the laptop, so maybe I could just write this off as a bad result of my first few shaky attempts to get the device paired with my laptop, wipe out both annexes, and start completely from scratch. + +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment new file mode 100644 index 000000000..553a135a0 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_6_506acc4275a81ed9e9b08e8a40fcf96a._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 6" + date="2013-08-26T19:38:12Z" + content=""" +a final note -- according to the process monitor, the process eating CPU is \"ga.androidterm\". There are also a small swarm of about 6 git processes none of which are consuming much CPU time at all. + +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment new file mode 100644 index 000000000..66a560191 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_7_d38d6f40db4c9437764c7b2ddf36b5a9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 7" + date="2013-08-26T20:00:39Z" + content=""" +It's certianly possible that the terminal app eats cpu for some reason even when sitting idle. It's hard for me to tell since I've been measuring cpu use by running top inside that terminal, which necessarily seems to use a lot of the CPU just to draw the screen. + +If it's the terminal at fault, it would continue after you shutdown the git-annex daemon, since that doesn't close the terminal. +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment new file mode 100644 index 000000000..3fce2f21f --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_8_9bb23e9cbc77ecca4b1209b0f66bc2b0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="oh yeah, i can run top in adb.." + date="2013-08-26T20:14:13Z" + content=""" +So, I can tell that on my tablet, the terminal app is using 82% cpu while idle. +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment new file mode 100644 index 000000000..ffd0a44be --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_d1ce7fc251db076da61eed5bb9d71b9a._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="173.162.44.162" + subject="comment 9" + date="2013-08-26T20:49:34Z" + content=""" +(removed my earlier comments with debug info, since it wasn't relevant and I'd just as soon not display my gmail id and home machine's address on the web if I don't need to) + +"""]] diff --git a/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment new file mode 100644 index 000000000..8f32df035 --- /dev/null +++ b/doc/bugs/android:_high_CPU_usage__44___unclear_how_to_quit/comment_9_feb71c1022ff65d82e66a3958a41dfb2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 9" + date="2013-08-26T20:16:05Z" + content=""" +Strace doesn't show it doing anything. I suppose I should try building the terminal without the several patches I added to it to support git-annex to see if I somehow made it use all this cpu.. +"""]] diff --git a/doc/bugs/assistant_always_assumes_port_22__63__.mdwn b/doc/bugs/assistant_always_assumes_port_22__63__.mdwn new file mode 100644 index 000000000..27896acd4 --- /dev/null +++ b/doc/bugs/assistant_always_assumes_port_22__63__.mdwn @@ -0,0 +1,39 @@ +### Please describe the problem. +git-annex assistant always assumes port 22 (I use a different port), despite my editing .ssh/config to correct this. + +Also, assistant doesn't give me a port option like it did in the intro screencast. + +### What steps will reproduce the problem? +Using my version of git-annex, I assume. + +### 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. +I don't see any .git/annex/daemon.log. + +I click the "remote server" link, sign in just fine [note below]. I click "Use a git repository on the server" (but "Use an encrypted rsync repository on the server" also does this), and eventually I get an error: +[[!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 make repository + +Something went wrong setting up the repository on the remote server. + +Transcript: ssh: connect to host <host> port 22: Connection timed out + +# End of transcript or log. +"""]] + +> Your version of git-annex is too old. +> Support for setting the port was added in version 3.20121211 -- +> about a month after the version you have installed +> (ah, the period where everything was 11 and 12.. I don't miss it!) +> +> I don't recommend using such an old version of the assistant, +> *massive* numbers of bugs have been fixed since then. Upgrade to +> the Ubuntu PPA. [[done]] --[[Joey]] + +note: if I use "git-annex webapp" in the terminal it works fine; if I use xfce's "internet -> git annex" menu, it errors trying to use ssh_askpass, which I don't have. I'm going to make a new thread about this. diff --git a/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac.mdwn b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac.mdwn new file mode 100644 index 000000000..23babd797 --- /dev/null +++ b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac.mdwn @@ -0,0 +1,53 @@ +### Please describe the problem. +Tried adding a removable drive repository through git-annex assistant on Mac, asked to encrypt it, got Internal server error with explanation: unable to determine gcrypt-id of remote + +### What steps will reproduce the problem? +current (today's) version of git-annex build for Mountain Lion installed +app launched +default annex initialized, a couple file added +a removable 2GB USB drive (ExFAT) mounted in OS +click Add another repository +choose removable drive +choose to encrypt +a window explaining the need to wait for entropy shows +then we get the Internal server error: unable to determine gcrypt-id of remote + +### What version of git-annex are you using? On what operating system? +git-annex version 4.20130922-g7dc188a +Mac OS X 10.8.5 + +### Please provide any additional information below. + +looking at transcript below, it appears the root cause is the lack of initial git/gcrypt configuration. perhaps this needs to be caught/addressed somehow + +[[!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: can't open `/usr/local/share/gnupg/options.skel': No such file or directory +.......+++++ +.+++++ +gpg: key 71BFBC31 marked as ultimately trusted +ok +(Recording state in git...) +(Recording state in git...) +(encryption setup) (hybrid cipher with gpg key C4B2EA8D71BFBC31) gcrypt: Development version -- Repository format MAY CHANGE +gpg: checking the trustdb +gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model +gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u +gcrypt: WARNING: Skipping missing key C4B2EA8D71BFBC31 +gcrypt: You have not configured any keys you can encrypt to for this repository +gcrypt: Use :: +gcrypt: git config gcrypt.participants YOURKEYID +gcrypt: Development version -- Repository format MAY CHANGE +gcrypt: WARNING: Skipping missing key C4B2EA8D71BFBC31 +gcrypt: You have not configured any keys you can encrypt to for this repository +gcrypt: Use :: +gcrypt: git config gcrypt.participants YOURKEYID +03/Oct/2013:00:05:24 +0400 [Error#yesod-core] unable to determine gcrypt-id of remote @(yesod-core-1.1.8.3:Yesod.Internal.Core ./Yesod/Internal/Core.hs:550:5) + + +# End of transcript or log. +"""]] + +[[!tag moreinfo]] diff --git a/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_1_4ea192e57f86a33087997746722e6acf._comment b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_1_4ea192e57f86a33087997746722e6acf._comment new file mode 100644 index 000000000..2d0802cae --- /dev/null +++ b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_1_4ea192e57f86a33087997746722e6acf._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2013-10-02T20:37:03Z" + content=""" +Can you take a look at ~/annex/.git/config and if there is an entry for this git remote, post it? (Or post the whole thing if unsure..) + +Also, can you get gpg to list your secret keys, and see if key 71BFBC31 is in the list? You can do so by running `gpg --list-secret-keys` ; if you don't have gpg in your path at the terminal, you can use the version from the git-annex DMG by first running `/Volumes/git-annex/git-annex.app/Contents/MacOS/runshell` +"""]] diff --git a/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_2_622ad5b34780fc8468c5c515ad9f27fa._comment b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_2_622ad5b34780fc8468c5c515ad9f27fa._comment new file mode 100644 index 000000000..2ba7a5984 --- /dev/null +++ b/doc/bugs/assistant_bails_when_adding_encrypted_usbdrive_repo_on_mac/comment_2_622ad5b34780fc8468c5c515ad9f27fa._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnyMzZZLS1xGW1raqc_9Md6Ksdkvx5rUJU" + nickname="Michael" + subject="comment 2" + date="2013-10-04T10:59:30Z" + content=""" +Sorry Joey, I was tinkering around trying to get the assistant off the ground and have destroyed the evidence of the bug in the process. I will try to recreate it and post the details. (most of my problems are/were related to bundled git/gpg/other software, I posted a separate comment in OSX Install page) +"""]] diff --git a/doc/bugs/assistant_does_not_allow_adding_an_existing_repo.mdwn b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo.mdwn new file mode 100644 index 000000000..8a6218c04 --- /dev/null +++ b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo.mdwn @@ -0,0 +1,8 @@ +The assistant does not allow adding an existing repo: I tried to add a "remote server", to enter the credits, and then I add to choose between "git-annex" or "rsync". Choosing "git-annex" tries to create a new repo and then fails. The repo on the server is a bare one, accessed via gitolite. Setting the remote manually ("git remote add origin git@example.org:my-annex.git" works (I can pull, push, ...)) + +Mac OS 10.7 version 2013-09-10 + + +[[!meta title="assistant does not interoperate with gitolite when adding a repository"]] + +[2013-09-13 17:00:55 CEST] chat: ssh ["-p","22","git@example.org","sh -c 'mkdir -p '\"'\"'my-annex.git'\"'\"'&&cd '\"'\"'my-annex.git'\"'\"'&&if [ ! -d .git ]; then git init --bare --shared; fi&&git annex init'"] diff --git a/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_1_87e84d56d56abefe8cac8a52b76c9003._comment b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_1_87e84d56d56abefe8cac8a52b76c9003._comment new file mode 100644 index 000000000..b260b8df5 --- /dev/null +++ b/doc/bugs/assistant_does_not_allow_adding_an_existing_repo/comment_1_87e84d56d56abefe8cac8a52b76c9003._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 1" + date="2013-09-13T18:19:03Z" + content=""" +I suppose the assistant could try to add a git remote and pull from it, and only if this pull fails go try to run shell commands to create it. This might work with gitolite, gitosis, github, etc. Although only partially for ones that don't support running git-annex-shell.. +"""]] diff --git a/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_3_f9b2a700c060707fae1bcb2ec0e4e4dc._comment b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_3_f9b2a700c060707fae1bcb2ec0e4e4dc._comment new file mode 100644 index 000000000..757a1c727 --- /dev/null +++ b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_3_f9b2a700c060707fae1bcb2ec0e4e4dc._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmOsy6nbvPyXLd--qqjPMLnVIzxgZwtKlQ" + nickname="Nicolas" + subject="comment 3" + date="2013-09-11T23:19:26Z" + content=""" +This behaviour is indeed very confusing when one attempts to use git-annex with the assistant only, without thinking about the underlying machinery. +Having the assistant automatically put a .gitignore file in empty directories is a possible solution, but maybe printing a warning in the log when the watcher sees an empty directory could be an unobtrusive and helpful solution? (At least it would have helped me) +"""]] diff --git a/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_4_014d213a959dd7993bdd247722a8817e._comment b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_4_014d213a959dd7993bdd247722a8817e._comment new file mode 100644 index 000000000..f6be08ae4 --- /dev/null +++ b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_4_014d213a959dd7993bdd247722a8817e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmOsy6nbvPyXLd--qqjPMLnVIzxgZwtKlQ" + nickname="Nicolas" + subject="comment 4" + date="2013-09-11T23:24:58Z" + content=""" +Another problem with the current behaviour is that when deleting a directory and its contents on a repository, the contents are deleted on the other repositories but empty directories are left behind... +"""]] diff --git a/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_5_440f349781d7d9ca2d1ed81386f7dd26._comment b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_5_440f349781d7d9ca2d1ed81386f7dd26._comment new file mode 100644 index 000000000..0d5f0aa29 --- /dev/null +++ b/doc/bugs/assistant_doesn__39__t_sync_empty_directories/comment_5_440f349781d7d9ca2d1ed81386f7dd26._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 5" + date="2013-11-01T22:12:04Z" + content=""" +I agree that this is very confusing. Also having to manually delete empty, renamed directories is...less than ideal. :) +"""]] diff --git a/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_3_4d5ae51b4c7e6177d934d7c9f21b912c._comment b/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_3_4d5ae51b4c7e6177d934d7c9f21b912c._comment new file mode 100644 index 000000000..6bf189414 --- /dev/null +++ b/doc/bugs/assistant_doesn__39__t_sync_file_permissions/comment_3_4d5ae51b4c7e6177d934d7c9f21b912c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmNu4V5fvpLlBhaCUfXXOB0MI5NXwh8SkU" + nickname="Adam" + subject="comment 3" + date="2013-11-02T23:49:49Z" + content=""" +Dropbox handles permissions, e.g. if I \"chmod -x\" a file on one system, it does the same to my other systems. It would be a bit of a step backward if git-annex can't do this. :/ Just my two cents. +"""]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn new file mode 100644 index 000000000..c5a75b361 --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual.mdwn @@ -0,0 +1,24 @@ +Thanks for git annex! + +### Please describe the problem. + +I've set up two computers A, B to sync to (and each other through) a remote server S. If I add files to A, it syncs with S. But B is not getting synced unless I run 'git annex sync' or restart the daemon in the webapp, i.e. I don't see these files on B at all, not even as broken symlinks. +The same happens if I manually copy files from A to S. B is not updating the copy count in 'git annex whereis' until I manually sync on B. + +It would be great if B could automatically sync when S is changed, either file locations or contents. + +### What steps will reproduce the problem? + +Both computers' local repos were setup with annex assistant, and switched into indirect mode. The server contains git repo and file data. All systems, computers and server are set to manual in the preferred content mode. + +### What version of git-annex are you using? On what operating system? + +A is running Debian testing with git-annex 4.20130827, B and S are running Debian stable with the backports version of git-annex 4.20130815~bpo70+1. A and S are 64 bit, B is 32 bit. All are up to date. + +### Please provide any additional information below. + +I tried this setup before with direct mode and different preferred content settings (A, B as client, S as backup or archive), and syncing of git and file data was working then. + +Despite being able to run 'sync' it is at least inconvenient to not have automatically updated file location information when I run the assistant. (I could then just run without it, but I had it happen to me that I setup a local repo w/o assistant, and when I ran assistant, expecting it would tell me "there are no local repos, would you like to create one?" it somehow automatically found the manually created one and started copying files. But that's another problem.) + +> [[done]] unless my diagnosis is wrong. --[[Joey]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment new file mode 100644 index 000000000..94dc51d0a --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_1_37acb3afafb1b4c4da7c778130cf3035._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE" + nickname="Sten" + subject="Direct oder indirect mode makes no difference" + date="2013-09-09T23:36:49Z" + content=""" +Direct or indirect mode does not make a difference. I created another setup like this, only different is direct mode, otherwise the same (in particular preferred content mode is manual). Result: Still no sync. +"""]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment new file mode 100644 index 000000000..8d388ceee --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_2_9d58887ee0184663852bde83b8d497c7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE" + nickname="Sten" + subject="computer in manual mode seems to be the reason, not server" + date="2013-09-10T02:21:59Z" + content=""" +If I create a setup like originally described with the only difference being S set to full backup mode, I see no change in sync behavior. + +In detail, what happens is: A gets files added. These changes are committed and synced. Because S is in full backup mode, the file content is also sent from A to S (this is different, but expected). However, B still does not sync until manually run. I would expect that B's manual mode only applies to file content (it is the preferred content setting), not to changes to the git repo, thus I'd expect git changes to sync to all involved (and accessible) repos. +"""]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment new file mode 100644 index 000000000..d42cf6cd2 --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_3_b70881c8026e30fd3ddc051bd01a888b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE" + nickname="Sten" + subject="available copies update need manual sync too" + date="2013-09-10T02:55:44Z" + content=""" +After copying files from S to B (as expected manually), I have to (unexpectedly) manually sync again on A to update the #copies on A. +"""]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment new file mode 100644 index 000000000..51e9cc135 --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_4_43f756e2e6ff985c8e050da0e369d486._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlQsgfXntaEvZPKgd_K0dfoFcYBJXKcaFE" + nickname="Sten" + subject="output of git annex sync " + date="2013-09-10T03:19:51Z" + content=""" +When running sync on B after copying file content from A to S (manually or automatically), I saw the following output (copied just the end of it): + ... + file.pdf | 1 + + file.txt | 1 + + 762 files changed, 762 insertions(+) + ... + create mode 120000 file.pdf + create mode 120000 file.txt + +git-annex: /home/sten/Documents/.git/annex/merge/: getDirectoryContents: does not exist (No such file or directory) +failed +push server +Everything up-to-date +ok +git-annex: sync: 1 failed + +A subsequent sync worked without error. + +"""]] diff --git a/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment new file mode 100644 index 000000000..05a3d7f74 --- /dev/null +++ b/doc/bugs/assistant_fails_to_sync_in_preferred_content_mode_manual/comment_5_eda947eb7f8c46b9a61d6430b5f9ebfd._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 5" + date="2013-09-13T18:30:53Z" + content=""" +You have described the following git-annex network: + + A --(ssh)-- S --(ssh)-- B + +So A automatically syncs to S. But there is no way at all for A to tell B that it has made changes. So B does not automatically sync. + +The git-annex webapp will detect this kind of situation, and display this alert: + +[[assistant/xmppnudge.png]] + +Once you set up an XMPP account, the network will look like: + + A --(ssh)-- S --(ssh)-- B + \_________(XMPP)_______/ + +And now B will immediatly know when A has pushed a change to S, and will go get it. + +(The `getDirectoryContents` error is probably because you are running git annex sync in a repository that the git-annex assistant is running in, and they are both using the same tmp directory for merging branches sync pulled. It does not seem to be worth worrying about.) +"""]] diff --git a/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment b/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment new file mode 100644 index 000000000..893be9055 --- /dev/null +++ b/doc/bugs/assistant_ignore_.gitignore/comment_2_22f75af80c779dcb4d6033b90373f74e._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..e58d46084 --- /dev/null +++ b/doc/bugs/assistant_ignore_.gitignore/comment_3_8b2a400e1d44a1c9b183e2b7861efbe3._comment @@ -0,0 +1,8 @@ +[[!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/authentication_to_rsync.net_fails.mdwn b/doc/bugs/authentication_to_rsync.net_fails.mdwn new file mode 100644 index 000000000..707f93d49 --- /dev/null +++ b/doc/bugs/authentication_to_rsync.net_fails.mdwn @@ -0,0 +1,30 @@ +### Please describe the problem. + +Used assistant to "Add a cloud repository". Supplied hostname, username in webapp. Directory "annex" port 22. +Clicked on "Use this rsync.net repository" and got + +********************** +ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory +ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory +ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory +Received disconnect from 69.43.165.7: 2: Too many authentication failures for 2440 +********************** + +### What steps will reproduce the problem? +See above? A simple "ssh user@host.rsync.net ls /usr/bin" reveals that indeed no ssh-askpass is available in that namespace. + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20130521 on debian linux 7.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 + +That log is empty. +# End of transcript or log. +"""]] + +> I added ssh-askpass as a recommends, so I suppose +> I can close this. [[done]] --[[Joey]] diff --git a/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment b/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment new file mode 100644 index 000000000..731d5148f --- /dev/null +++ b/doc/bugs/authentication_to_rsync.net_fails/comment_1_9db65f89415c8d825f268afb75244998._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawliqfHEW134uawIUPwyKiyOdoF-oI5TxnQ" + nickname="Ethan" + subject="Doh. /usr/bin/ssh-askpass needs to be on *local* machine." + date="2013-08-15T20:13:31Z" + content=""" +My mistake; the problem was the I was missing /usr/bin/ssh-askpass on my local machine, not the rsync.net host. + +I still think this is a bug. I'm on a debian machine and installed git-annex from its debian package, so seems like the ssh-askpass package should be listed as a dependency. But that's a debian packaging problem, not a git-annex bug per se, so I'll go file it elsewhere. +"""]] diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment new file mode 100644 index 000000000..4cf86f646 --- /dev/null +++ b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_3_51da7f5881f65422328d341e5ab0d250._comment @@ -0,0 +1,33 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlEhzszkzOIy8-Rx8b2mcr75QcnIc6O_OA" + nickname="Rachel" + subject="I'm afraid I'm getting this too" + date="2013-09-12T12:48:04Z" + content=""" +Very similar setup. Initially set up on a Mac, then tried to set up the first local pairing with a Linux system. Basically seeing exactly the same thing. + + bad comment in ssh public key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDa09lpmgLeRVF1KZn2gX6tmBH4Jpcou/rkPbhwLoFNLtQsdNrbjDKuyc4pDbUhexWVvub1YCLItLK0vYRdMvoJWjNzy926sHs8CxXFVg6PMQXw3wOHousSn0NkVfwUMNn5aS+1vz/WDlStmg7WzXgiPg1Whn6CKIomxA63rUMe3I+2nVkyO6jGlOkliPApVP2utURJbyxBDYDB+Ys7zUxvEcCekhxJO263myuo2gwI4A3mfTLRJMzbz8frRZJz5iuUIcOHaIDy6n0qKFq18BDux4SDwNjQ34yti5yqveRBMwFndHQYN6YHk1k26h0kyhb2T6lXaaAirSqa3dwfZuKp rachel@celestia.local + + +# Versions and Stuff: + +## Mac: + +* OS X 10.8.4 +* git-annex 4.20130909-ga29f960 (downloaded about half an hour ago!) +* BTW I have git installed from Homebrew, version 1.8.3.4 in my shell's $PATH, but obviously /usr/bin/git from the system is intact. +* Hostname: celestia.local +* Username: rachel + +## Linux: +* Ubuntu 13.04 +* git-annex 3.20121112ubuntu4 (from Ubuntu's own repos) +* I note that's later than the version you said this bug was fixed in, hence the report. :-) +* Hostname: twilight.local (mDNS domain not appended even by hostname -f but avahi is working) +* Username: rachel + +IPv6 is active, but I note a comment somewhere that that's probably not relevant for git-annex. + +Machines are very local to each other, in the same room, connected via a gigabit switch. They can definitely see each other. :-) + +"""]] diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment new file mode 100644 index 000000000..4b9e27bba --- /dev/null +++ b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa/comment_4_ba384314c1e47ec4b72e1843e0500df9._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmpBDWko1yZmngBYzm_CeBv8RjoIMXaINE" + nickname="Rachel" + subject="latest works" + date="2013-09-12T13:19:09Z" + content=""" +Downloaded the latest tarball (4.20130911-g6625d0e) and that seems to be able to pair ok. + +Different bug though: It objects to push.default = simple in ~/.gitconfig, but no such complaint on osx. But that's a different bug; i'll report separately when I'm a bit more up to speed. +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing..mdwn b/doc/bugs/box.com_never_stops_syncing..mdwn new file mode 100644 index 000000000..42b2eaf1a --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing..mdwn @@ -0,0 +1,63 @@ +### Please describe the problem. +Git-annex will constantly sync most(if not all) my files to box.com + +### What steps will reproduce the problem? +1 - Use git-annex instead of Dropbox at work +2 - Boot computer. +3 - Watch it sync everything to box.com (even files i believe it has transferred each and every day for the last few months) + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20130827 + +But i have never seen it work satisfactory in any version. + +Also, i have seen this is 10+ different clean git-annexes. So it isn't annex specific. + +### Please provide any additional information below. + +I am going to add more debug to this bug constantly. (I intend to do a full 'git annex copy --to box.com --not --in box.com' daily, and see if the same files are transfered again and again) + + +For now, i see a few different issues already: + + +[[!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 + + +tou@DSK1049:~/work-annex$ git annex copy --to box.com --not --in box.com 2>&1 | tee ../work-annex-copy-to-box.com-not-in-box.com-run1.log +[2013-09-11 09:24:53 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","show-ref","git-annex"] +[2013-09-11 09:24:53 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","show-ref","--hash","refs/heads/git-annex"] +[2013-09-11 09:24:53 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","log","refs/heads/git-annex..dbe8b1cfa5f84126c45a39fdc7c7f26e272c71cc","--oneline","-n1"] +[2013-09-11 09:24:53 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","log","refs/heads/git-annex..45e279375897a2cd7f5b893402e0ec25c1b23436","--oneline","-n1"] +[2013-09-11 09:24:54 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","log","refs/heads/git-annex..c4921be4434f751493fce1c932ac759214abacd4","--oneline","-n1"] +[2013-09-11 09:24:54 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","log","refs/heads/git-annex..d591398dc1cac824a5fc5bdacdcb82301a9b15a3","--oneline","-n1"] +[2013-09-11 09:24:54 CEST] chat: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","cat-file","--batch"] +[2013-09-11 09:24:54 CEST] read: git ["config","--null","--list"] +[2013-09-11 09:24:54 CEST] read: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","ls-files","--cached","-z","--"] +[2013-09-11 09:24:54 CEST] chat: git ["--git-dir=/home/tou/work-annex/.git","--work-tree=/home/tou/work-annex","cat-file","--batch"] +copy Documents/Gamle catillo overførsler/Rapport b-bm.odt (gpg) (checking box.com...) ok +copy Documents/Gamle catillo overførsler/Rapport brandt skorstensfejeren.odt (checking box.com...) (failed to read https://www.box.com/dav/work-annex/4a5/18e/GPGHMACSHA1--5f8660edac93899cf9adc5fadcc480ddc2992bb1/GPGHMACSHA1--5f8660edac93899cf9adc5fadcc480ddc2992bb1.chunkcount) failed +copy Documents/Gamle catillo overførsler/Rapport teamkoege.odt (checking box.com...) (failed to read https://www.box.com/dav/work-annex/98d/ae7/GPGHMACSHA1--5253241407527aa6c980f1174fdbc32713c54c44/GPGHMACSHA1--5253241407527aa6c980f1174fdbc32713c54c44.chunkcount) failed +copy Documents/Gamle catillo overførsler/Rapport vikarborsen.odt (checking box.com...) ok +copy Documents/Gamle catillo overførsler/Rapport-terrariemesteren.odt (checking box.com...) ok +copy Documents/Gamle catillo overførsler/catillo-efhandel.odt (checking box.com...) (failed to read https://www.box.com/dav/work-annex/9d9/aea/GPGHMACSHA1--1516eac1ec7b4ceaa840faebabde1f50f5db0a52/GPGHMACSHA1--1516eac1ec7b4ceaa840faebabde1f50f5db0a52.chunkcount) failed +copy Documents/Nøgeordsanalyse catillo104.xlsx (checking box.com...) (ResponseTimeout) failed +copy Documents/Søgeordsliste.txt (checking box.com...) ok +copy Documents/catillo guide.odt (checking box.com...) ok +copy Documents/guide bruger oprettelse.odt (checking box.com...) (failed to read https://www.box.com/dav/work-annex/49e/175/GPGHMACSHA1--2b47737f8de7faac7704eaa322785edad63a921c/GPGHMACSHA1--2b47737f8de7faac7704eaa322785edad63a921c.chunkcount) failed +copy Documents/guide skift backup bånd.odt (checking box.com...) ok +copy Documents/lilletest.csv (checking box.com...) (failed to read https://www.box.com/dav/work-annex/915/373/GPGHMACSHA1--49ba3d5f63c012ae2cd2c0fc3e729178b1023c33/GPGHMACSHA1--49ba3d5f63c012ae2cd2c0fc3e729178b1023c33.chunkcount) failed +copy Dropbox/adams-scraper/CommonFunctions.py (checking box.com...) (ResponseTimeout) failed +copy Dropbox/adams-scraper/__pycache__/CommonFunctions.cpython-33.pyc (checking box.com...) (to box.com...) [2013-09-11 09:28:30 CEST] chat: gpg ["--batch","--no-tty","--use-agent","--quiet","--trust-model","always","--batch","--passphrase-fd","14","--symmetric","--force-mdc"] + +100% 0.0 B/s 0sResponseTimeout +ResponseTimeout +failed + + +# End of transcript or log. +"""]] + +More to come(full log) diff --git a/doc/bugs/box.com_never_stops_syncing./comment_1_124a5edcd89cc6b61e1a41f5b4d640d7._comment b/doc/bugs/box.com_never_stops_syncing./comment_1_124a5edcd89cc6b61e1a41f5b4d640d7._comment new file mode 100644 index 000000000..ee1c88cc7 --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_1_124a5edcd89cc6b61e1a41f5b4d640d7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 1" + date="2013-09-12T20:29:14Z" + content=""" +It seems you are getting a lot of timeouts from box.com, both when checking if content is present there and when uploading content that it does not have. + +I have heard some grumbles about box.com not being very reliable right now. +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_2_42574181aa721319ba54eadf0a15ddff._comment b/doc/bugs/box.com_never_stops_syncing./comment_2_42574181aa721319ba54eadf0a15ddff._comment new file mode 100644 index 000000000..5a0cde548 --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_2_42574181aa721319ba54eadf0a15ddff._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" + nickname="develop" + subject="comment 2" + date="2013-09-12T20:54:33Z" + content=""" +The problem being. I've used box.com with one of my own hooks(owncloud), where it is completely stable! + +The instability is not a the box.com end. + +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_3_2ad727849070cfd52d6c719478e9cce3._comment b/doc/bugs/box.com_never_stops_syncing./comment_3_2ad727849070cfd52d6c719478e9cce3._comment new file mode 100644 index 000000000..5eab58b3f --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_3_2ad727849070cfd52d6c719478e9cce3._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 3" + date="2013-09-12T20:56:44Z" + content=""" +git-annex is using box.com's WebDAV interface. Is owncloud? +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_4_83ce23e45f5a5845d4f04519ee14ec65._comment b/doc/bugs/box.com_never_stops_syncing./comment_4_83ce23e45f5a5845d4f04519ee14ec65._comment new file mode 100644 index 000000000..eb9dc5134 --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_4_83ce23e45f5a5845d4f04519ee14ec65._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" + nickname="develop" + subject="comment 4" + date="2013-09-12T21:33:29Z" + content=""" +It uses the following url https://www.box.com/dav + +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_5_ef1c9d87b04db5047ab72167d3269687._comment b/doc/bugs/box.com_never_stops_syncing./comment_5_ef1c9d87b04db5047ab72167d3269687._comment new file mode 100644 index 000000000..9d9c1329b --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_5_ef1c9d87b04db5047ab72167d3269687._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 5" + date="2013-09-12T21:44:32Z" + content=""" +It may be that there is a timeout in the http library that I am using for webdav that is too low. See <https://github.com/snoyberg/http-conduit/issues/137> +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_6_c9cb39eba941678035f9b2888da1085c._comment b/doc/bugs/box.com_never_stops_syncing./comment_6_c9cb39eba941678035f9b2888da1085c._comment new file mode 100644 index 000000000..5eaf4f4bb --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_6_c9cb39eba941678035f9b2888da1085c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" + nickname="develop" + subject="comment 6" + date="2013-09-12T21:49:05Z" + content=""" +That would probably do it. With other implementations(fuse mount) i've seen stalls and other bad behaviour with that DAV server. + +The owncloud hook doesn't have a timeout set. It probably should have one to prevent a total stall. +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_7_4b0632a4e37c96959a8e6434e9fd86fb._comment b/doc/bugs/box.com_never_stops_syncing./comment_7_4b0632a4e37c96959a8e6434e9fd86fb._comment new file mode 100644 index 000000000..2ac3f360e --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_7_4b0632a4e37c96959a8e6434e9fd86fb._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" + nickname="develop" + subject="Logs" + date="2013-09-13T11:43:22Z" + content=""" +So have two days of logs now, and it doesn't look like it is retrying old files. + +http://paste.ubuntu.com/6101255/ <- day 1 + +http://paste.ubuntu.com/6101256/ <- day 2 + +Setting the computer to do the following loop over the weekend, lets see if everything is done come monday. + +for i in `seq 3 2000`; do git annex copy --to box.com --not --in box.com 2>&1 | tee ../work-annex-copy-to-box.com-not-in-box.com-run$i.log; done + +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_8_d9d318b8c958de6031ae323da20af625._comment b/doc/bugs/box.com_never_stops_syncing./comment_8_d9d318b8c958de6031ae323da20af625._comment new file mode 100644 index 000000000..8dfbd6944 --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_8_d9d318b8c958de6031ae323da20af625._comment @@ -0,0 +1,55 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmWg4VvDTer9f49Y3z-R0AH16P4d1ygotA" + nickname="Tobias" + subject="Update" + date="2013-09-18T11:17:33Z" + content=""" +Only just got back to work now. The script has done 10 iteration. This is the status: + + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run1.log |grep \" ok\"| wc -l +137 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run2.log |grep \" ok\"| wc -l +77 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run3.log |grep \" ok\"| wc -l +116 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run4.log |grep \" ok\"| wc -l +70 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run5.log |grep \" ok\"| wc -l +26 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run6.log |grep \" ok\"| wc -l +6 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run7.log |grep \" ok\"| wc -l +6 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run8.log |grep \" ok\"| wc -l +0 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run9.log |grep \" ok\"| wc -l +0 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run10.log |grep \" ok\"| wc -l +0 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run11.log |grep \" ok\"| wc -l +0 + +tou@DSK1049:~$ cat work-annex-copy-to-box.com-not-in-box.com-run12.log |grep \" ok\"| wc -l +0 + +I have all the log files of course. + +tou@DSK1049:~/work-annex$ git annex find --not --in box.com| wc -l +1639 + +So, of the last 5 iteration 0 files of 1639 missing were transfered. Most of these files are <10kbyte + +http://paste.ubuntu.com/6123459/ <- pastebin of work-annex-copy-to-box.com-not-in-box.com-run11.log if it is of any use. + +"""]] diff --git a/doc/bugs/box.com_never_stops_syncing./comment_9_689ac6a4a305197cf5566f98dab47b4b._comment b/doc/bugs/box.com_never_stops_syncing./comment_9_689ac6a4a305197cf5566f98dab47b4b._comment new file mode 100644 index 000000000..99a0eb9ae --- /dev/null +++ b/doc/bugs/box.com_never_stops_syncing./comment_9_689ac6a4a305197cf5566f98dab47b4b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.80" + subject="comment 9" + date="2013-09-28T19:34:42Z" + content=""" +Filed a bug on the DAV library about this: <http://bugs.debian.org/724856> +"""]] 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 new file mode 100644 index 000000000..172f28143 --- /dev/null +++ b/doc/bugs/build_fails_in_Assistant__47__WebApp__47__Gpg.hs.mdwn @@ -0,0 +1,57 @@ +### 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/cabal_install_fails_to_install_manpage.mdwn b/doc/bugs/cabal_install_fails_to_install_manpage.mdwn new file mode 100644 index 000000000..265ad2432 --- /dev/null +++ b/doc/bugs/cabal_install_fails_to_install_manpage.mdwn @@ -0,0 +1,43 @@ +### Please describe the problem. + +The git-annex manual page is not installed when using [[install/cabal]] to install git-annex. + +### What steps will reproduce the problem? + +Follow [[install/cabal]] with `--bin-dir=/usr/local` and try `man git-annex`. + +I was expecting the manpage to be installed in `/usr/local/share/man`. + +### What version of git-annex are you using? On what operating system? + +git annex from a recent git build (4.20130909-g7f079d6) in Debian wheezy. + +### Please provide any additional information below. + +<del>This could be just a documentation problem...</del> Actually, the manpage can be read directly from the source tree in `doc/git-annex.mdwn`, but I still think it should be installed, for [[!wikipedia POLA]]'s sake. --[[anarcat]] + +I figured it out - that stuff is in the makefile, I updated [[install/cabal]] accordingly, so <del>done</del> - not done just yet. --[[anarcat]] + +> Doesn't seem right to me; Setup.hs has some stuff to do with +> installing man pages. This does currently require that they +> are distributed in pre-built form in the .tar.gz on hackage, +> which I've just checked and they are. +> +> Perhaps cabal put the man pages somewhere else? After all, you +> apparently did not set --datadir --[[Joey]] + +> > True, I didn't - the docs didn't say to. ;) But really, it's one of two things, either Setup.hs can install manpages, and then the Makefile shouldn't install it, or we should update documentation to use the makefile only. I'll try this again next time I reinstall through cabal i guess... -- [[anarcat]]a + +>>> The default location cabal installs man pages to is +>>> `~/.cabal/share/man/man1`. That is insane, but it is not as +>>> insane as not installing programs into PATH, which is why +>>> the documentation tells how to set --bindir to fix that particular +>>> cabal insanity. (Also, many systems don't have a good per-user +>>> man directory anyway.) +>>> +>>> `make install` does not use `cabal install` because as noted, cabal +>>> install is thurougly bat shit crazy. Not all systems that have +>>> cabal have make, which is why the cabal documentation is the way it is. +>>> --[[Joey]] + +[[done]] diff --git a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn b/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn index d09a13b07..ca47d3a4c 100644 --- a/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn +++ b/doc/bugs/can__39__t_annex_get_from_annex_in_direct_mode.mdwn @@ -19,3 +19,5 @@ Debian Linux: 3.20120629 (from the package manager) there is no <filehash>.<extension> file in the relevant directories, there are only .map and .cache files. The Windows annex is in direct mode, and the Linux annex fails to annex get from this correctly. [[!meta title="can't use a direct mode repository as a http remote"]] + +> [[done]]; unsupported configuration. --[[Joey]] diff --git a/doc/bugs/cannot_determine_uuid_for_origin.mdwn b/doc/bugs/cannot_determine_uuid_for_origin.mdwn new file mode 100644 index 000000000..611a0f236 --- /dev/null +++ b/doc/bugs/cannot_determine_uuid_for_origin.mdwn @@ -0,0 +1,135 @@ +[[!toc]] + +### Please describe the problem. + +I get this error when trying to copy annexed files from my laptop to the bare repository on my server: + + anarcat@angela:ohm2013$ git annex copy -t origin . + git-annex: cannot determine uuid for origin + +### What steps will reproduce the problem? + +Here's my setup: + + * `angela`: regular git repository on my laptop (`angela`) where i ran `git annex init` and `git annex add`ed 4 big files (in `~anarcat/presentations/ohm2013`) + * `marcos-bare`: a bare git repository where i ran `git annex init` on a different server (`marcos`) (in `~anarcat/repos/presentations/ohm2013.git`) + * `marcos-checkout`: a checkout of the above repository on marcos (in `~anarcat/presentations/ohm2013`) + +I ran `git pull/push` everwhere in there, and still get the error. + +Remotes on all repos: + + * `angela`: `origin anarcat.ath.cx:repos/presentations/ohm2013.git` + * `marcos-bare`: no remote + * `marcos-checkout`: `origin /home/anarcat/repos/presentations/ohm2013.git` + +Note that file added with `git annex addurl` on `marcos-checkout` properly gets propagated on `angela` once i do `git annex get` there. + +### What version of git-annex are you using? On what operating system? + +`angela` runs: + +[[!format txt """ +git-annex version: 4.20130730-ge59a8c6 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS +local repository version: 3 +default repository version: 3 +supported repository versions: 3 4 +upgrade supported from repository versions: 0 1 2 +"""]] + +I was able to reproduce with the backport version too. + +I compiled it by hand from git. + +`marcos` runs: + +[[!format txt """ +git-annex version: 3.20120629 +local repository version: unknown +default repository version: 3 +supported repository versions: 3 +upgrade supported from repository versions: 0 1 2 +"""]] + +### Please provide any additional information below. + +In addition, there's this error on `marcos-bare`: + +[[!format sh """ +anarcat@marcos:ohm2013.git$ git annex status -d +supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL +supported remote types: git S3 bup directory rsync web hook +trusted repositories: git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","show-ref","git-annex"] +git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","show-ref","--hash","refs/heads/git-annex"] +git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","log","refs/heads/git-annex..6063e958c02259a39b87d0f1dc44c9272c52df3f","--oneline","-n1"] +git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","cat-file","--batch"] +0 +semitrusted repositories: 4 + 00000000-0000-0000-0000-000000000001 -- web + 5868f840-02e7-11e3-94e9-9b3701bd28bb -- marcos-checkout + aafdd242-02e7-11e3-bb6a-6f16a5c6103e -- here (marcos-bare) + befc3057-d23d-4312-843a-0645e93107d8 -- angela +untrusted repositories: 0 +dead repositories: 0 +available local disk space: 14 gigabytes (+1 megabyte reserved) +local annex keys: 0 +local annex size: 0 bytes +known annex keys: git ["--git-dir=/home/anarcat/repos/presentations/ohm2013.git","ls-files","--cached","-z","--","/home/anarcat/repos/presentations/ohm2013.git"] +fatal: '/home/anarcat/repos/presentations/ohm2013.git' is outside repository +0 +known annex size: 0 bytes +bloom filter size: 16 mebibytes (0% full) +backend usage: +"""]] + +### Workaround! + +I found that I could succesfully push to the non-bare repo, like this: + +[[!format txt """ +anarcat@angela:ohm2013$ git remote add marcos-checkout ssh://anarcat.ath.cx/~/presentations/ohm2013 +anarcat@angela:ohm2013$ git fetch marcos-checkout +From ssh://anarcat.ath.cx/~/presentations/ohm2013 + * [new branch] git-annex -> marcos-checkout/git-annex + * [new branch] master -> marcos-checkout/master +anarcat@angela:ohm2013$ git annex copy AlerteRouge.webm --to marcos-checkout +copy AlerteRouge.webm (checking marcos-checkout...) (to marcos-checkout...) +SHA256E-s138903105--a69db8d4c3835b03bdb08cb1cccfde5c76f586f934d63283694e7101b25352a8.webm +[...] +"""]] + +It seems that git-annex doesn't like bare repos at all... + +### Fix + +It seems that my problem was specifically related to [[bare repositories]], which are not well supported historically. There has been other reports of problems in the past, which I missed in my search because symptoms were different: + + * [[bugs/bare git repos]] + * [[forum/get and copy with bare repositories]] + +Yet while I was able to do `git annex get --all` *from* the `marcos-bare` repository, I still get the original error message while trying to `git annex copy -t marcos-bare`, which is pretty annoying considering the original files are on my laptop, which is not publicly accessible. So I basically need to add the `marcos-checkout` as a remote, copy there, then get from the bare repo to make this work, which is a rather convoluted way of doing things. :) + +It seems to me a proper fix would be to be able to `git annex copy --to marcos-bare`. Thanks! + +Update: it seems te problem was that I had the following in my `.git/config`: + + [remote "marcos-bare"] + url = ssh://anarcat.ath.cx/~/repos/presentations/ohm2013.git + annex-ignore = true + fetch = +refs/heads/*:refs/remotes/marcos-bare/* + +I have *no* idea how that `annex-ignore` got there, but that was the root of my problem. Removing it it allowed my to do `git annex copy`. I really don't know how this happened, but I guess this is [[done]], although I believe this error message is really confusing and could be improved. --[[anarcat]] + +> `annex-ignore` is set automatically by git-annex if it fails to query +> the uuid of a remote the first time it tries to use it. It will say +> when it does that. The assumption +> is that a remote whose uuid cannot be looked up is a git remote +> on a server w/o git-annex support (like github) and it would be annoying +> to constantly be trying and failing to get that uuid. +> +> So, I've improved the error message. Now when annex-ignore is set +> for a remote, the error you got will mention that. +> +> (Also, there is not currently anything lacking in git-annex's support +> for bare repositories.) --[[Joey]] diff --git a/doc/bugs/cannot_link_executable_on_android.mdwn b/doc/bugs/cannot_link_executable_on_android.mdwn new file mode 100644 index 000000000..cb660dd9c --- /dev/null +++ b/doc/bugs/cannot_link_executable_on_android.mdwn @@ -0,0 +1,28 @@ +### 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/clicking_back_in_the_web_browser_crashes.mdwn b/doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn new file mode 100644 index 000000000..1b7e2ec71 --- /dev/null +++ b/doc/bugs/clicking_back_in_the_web_browser_crashes.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. + +When I click on the "back" button in my web browser, I get the following error message: + + git-annex has shut down + + You can now close this browser window. + +### What steps will reproduce the problem? + + 1. git annex webapp + 2. click on "configuration" (or whatever) + 3. click on the back button of your web browser + +### What version of git-annex are you using? On what operating system? + +4.20130815~bpo70+1 on Debian Wheezy, with Chromium Version 29.0.1547.57 Debian 7.1 (217859) + +### Please provide any additional information below. + +Click "forward" actually brings us back to sanity, and the webapp doesn't actually *crash*. -- [[anarcat]] + +> I have applied the page reload fix/hack. [[done]] --[[Joey]] diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment new file mode 100644 index 000000000..ece6ce0e3 --- /dev/null +++ b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_1_c962218657a28494ff837a471d71b43f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T04:23:36Z" + content=""" +This occurs when the javascript long polling code fails 4 times in a row attempting to communicate with git-annex's web server. Normally this will mean that the assistant has been stopped. I have seen it once or twice happen while the web server is still running -- possibly due to the browser killing the connection? I have never seen it happen when navigating between pages in the webapp, which is designed to allow use of back button etc. If you can reproduce it reliably, using the chromium inspector to modify the javascript code (look for \"longpoll\") and perhaps add some debug prints might track down what is going on. +"""]] diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment new file mode 100644 index 000000000..feac21ffe --- /dev/null +++ b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_2_643b2c99ecfe851c576a023ce4385dbb._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + ip="2001:1928:1:9::1" + subject="comment 2" + date="2013-09-09T04:31:30Z" + content=""" +i can reproduce reliably alright. It's quite systematic. I have found the `longpolling.js` file in the inspector, but I am not very familiar with in-browser javascript debugging, so I am not sure where to go from here. + +Note that the assistant doesn't actually crash. This is also reproducable in Debian sid. +"""]] diff --git a/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment new file mode 100644 index 000000000..a3dee1d52 --- /dev/null +++ b/doc/bugs/clicking_back_in_the_web_browser_crashes/comment_3_6e85c50439da81212f4239c74947b75e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 3" + date="2013-09-09T05:22:49Z" + content=""" +Actually I am able to reproduce it. One thing I can see is that git-annex does not see any connection attempts from the browser when these longpolling attempts are made and fail. So this is all failing on the javascript side. Increasing the connection failure counter does not help. Every ajax request fails, no matter how many times it tries. Chromium has apparently decided that, because we've navigated back to a page, it should not be allowed to load any new resources. This seems to be new, buggy behavior. + +It seems the only way out of this bad state would be for the javacript to force a reload of the page. Of course, if git-annex has legitimately exited, that would fail to reload. I suppose the chromium \"this webpage is not available\" that would result is at least accurate... + +(At some point, I should probably try to add support for something more modern than long polling.) +"""]] diff --git a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn new file mode 100644 index 000000000..190f3bb3b --- /dev/null +++ b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work.mdwn @@ -0,0 +1,74 @@ +### Please describe the problem. +Copying to a gpg encrypted webdav remote (with davfs) seems to work, but fails. +The command "git annex copy --to 1und1 some/file" returns ok, but a fsck fails and running +the copy again copies the file again to the remote. + +### What steps will reproduce the problem? +[[!format sh """ +git annex copy --to 1und1 some/file # seems ok +git annex copy --to 1und1 some/file # copies again +git annex fsck --from 1und1 some/file # fails +"""]] + +### What version of git-annex are you using? On what operating system? +4.20131002 on debian (mostly stable), armel. + +### Please provide any additional information below. + +I used strace to see what is going on. It seems the chunkcount file is not written. When I create that file by hand fsck is happy. +(git annex seems to have two different locations for that file (dcf/85a and 3W/Qm). The second (3W/Qm) doesn't exist.) + +[[!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 to webdav (git annex copy --to 1und1 some/file) +output of basically "strace git annex ... | grep media": + +9871 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", <unfinished ...> +9871 stat64("/media/1und1/git-annex/3W/Qm/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", 0xb65145d0) = -1 ENOENT (No such file or directory) +9871 mkdir("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33", 0777 <unfinished ...> +9871 statfs("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", <unfinished ...> +9871 stat64("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +9871 open("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK|O_LARGEFILE, 0666 <unfinished ...> +9871 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", <unfinished ...> +9871 chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", 040755 <unfinished ...> +9871 openat(AT_FDCWD, "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 15 +9871 unlink("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1" <unfinished ...> +9871 rmdir("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/" <unfinished ...> +9871 mkdir("/media/1und1/git-annex/dcf/85a", 0777) = -1 EEXIST (File exists) +9871 stat64("/media/1und1/git-annex/dcf/85a", {st_mode=S_IFDIR|0755, st_size=64, ...}) = 0 +9871 stat64("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 +9871 rename("/media/1und1/git-annex/tmp/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/" <unfinished ...> +9871 openat(AT_FDCWD, "/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 15 +9871 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0644, st_size=11705, ...}) = 0 +9871 chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", 0100444) = 0 +9871 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", {st_mode=S_IFDIR|0755, st_size=152, ...}) = 0 +9871 chmod("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/", 040555 <unfinished ...> + +fsck webdav, but fails (git annex fsck --from 1und1 some/file): + +10208 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", <unfinished ...> +10208 stat64("/media/1und1/git-annex/3W/Qm/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", 0xb6428160) = -1 ENOENT (No such file or directory) + + +manual file creation: +chmod u+w ... +echo -n 1 > /media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount +chmod u-w ... + + +fsck webdav again, now all is fine ("fixing location log"): +10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", {st_mode=S_IFREG|0444, st_size=1, ...}) = 0 +10670 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 14 +10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0444, st_size=11705, ...}) = 0 +10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", {st_mode=S_IFREG|0444, st_size=1, ...}) = 0 +10670 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunkcount", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 14 +10670 stat64("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", {st_mode=S_IFREG|0444, st_size=11705, ...}) = 0 +10672 open("/media/1und1/git-annex/dcf/85a/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33/GPGHMACSHA1--10ff9e1cc8191235670c2fd95375bccf62004f33.chunk1", O_RDONLY|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 20 +# End of transcript or log. +"""]] + +> There was a bug that caused it not to write the chunkcount file. +> I have fixed it, and put in a workaround so fsck, etc, will +> see that the file is stored on the remote despite there being no +> chunkcount file present. [[done]] --[[Joey]] diff --git a/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment new file mode 100644 index 000000000..d5ad2d88d --- /dev/null +++ b/doc/bugs/copy_to_webdav_sometimes_doesn__39__t_work/comment_1_77629f620b28ac62364de44b41fa539d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlqOu7P4tb4D-Xo2pYrjln2NsAObtErliM" + nickname="Alexander" + subject="comment 1" + date="2013-10-27T07:00:01Z" + content=""" +thanks! +"""]] diff --git a/doc/bugs/cross_platform_permissions_woes.mdwn b/doc/bugs/cross_platform_permissions_woes.mdwn new file mode 100644 index 000000000..d67ca4ae0 --- /dev/null +++ b/doc/bugs/cross_platform_permissions_woes.mdwn @@ -0,0 +1,36 @@ +a little introduction: +i am forced to use windows on my work laptop and workstation, also my wife needs windows. +my "servers" would be linux, i am actually using fedora and i upgraded from fc17 since i was not able to get a recent version of git annex to compile there. + +what happens, is that once i try to copy from the windows machine where the file is to the linux through ssh+rsync, i receive this error - as long as the user owning the linux repository isn't root: + + c:\locale>git annex copy --to linux myfile + copy myfile (checking linux...) (to linux...) + rsync: failed to open "/linux/annex/tmp/SHA256E-s10--937a89b559820f8658892" + myfile + 10 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) + rsync error: syntax or usage error (code 1) at /home/lapo/package/rsync-3.0.9-1/src/rsyn + total size is 10 speedup is 0.09 + failed + git-annex: copy: 1 failed + +the file in tmp has no permissions at all: + + me@linux annex]$ ls -lart tmp/SHA256E-s10--937a89b559820f86588921ef3eb12c13074d078b62ef205bb597bf2e895408c3 + ----------. 1 me me 10 Oct 13 22:50 tmp/SHA256Es10--937a89b559820f86588921ef3eb12c13074d078b62ef205bb597bf2e895408c3 + +(just consider the following if the above makes any sense:) in another case (i cannot reproduce it now, possibly due to having upgraded git annex from some 2012 release), it happened that a failed download via copy/move from linux to windows (failed for permissions) would not be recorded as failed (on windows side), causing files to possibly be killed at the first subsequent drop command. + +my question is: are these 0-permissions on tmp files a bug or just due to some ignorance i did put in setting up the git/annex repo ? is a git/annex repo to be run solely as root/sudoer ? or shall i take any other step in configuring it ? + +technicalities: + +"client": windows version: + + git-annex version: 4.20131002-gf25991c + +"server": linux version: + + git-annex version: 3.20130207 + +> [[done]]; fixed in newer git-annex versions. --[[Joey]] diff --git a/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment b/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment new file mode 100644 index 000000000..a3116cdcf --- /dev/null +++ b/doc/bugs/cross_platform_permissions_woes/comment_1_7f01104de38a6a319a8f36aa1dc8b4b3._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 1" + date="2013-10-15T18:29:10Z" + content=""" +Based on the '/linux/annex/' path, your \"linux\" git remote is set up using some sort of network mount of your Linux box to Windows. + +If that's the case, then rsync is running on Windows and probably doesn't know anything about permissions, to probably does something horrible when it's told to write a file to the linux filesystem. + +If I'm right about that, I can easily fix it, by making git-annex on Windows not use rsync for such file to file copies. But I first need you to verify if I'm right about how your \"linux\" git remote is configured. + +(Also, you should be able to work around the problem by changing the git remote to use a ssh:// url to the linux system.) +"""]] diff --git a/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment b/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment new file mode 100644 index 000000000..8ee7c18a5 --- /dev/null +++ b/doc/bugs/cross_platform_permissions_woes/comment_2_0a34e11b466fad287325425e76487fa1._comment @@ -0,0 +1,73 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmCzVCPjgg_Un_114P8iiSwExms0G2csCA" + nickname="Michele" + subject="details about my problem" + date="2013-10-15T23:30:26Z" + content=""" +Thank for your answer, but unfortunately the remote is already an ssh (although i agree it should happen most certainly also via samba/cifs mount). +it happens as long as the remote is NOT defined as root login. +I suppose it could as well be something with my setup (although i've tried different windows/linux hosts) and I have no idea how to debug it. + +this is a transcript of recreating the problem (i've just edited user/hostname): + + Microsoft Windows [Version 6.1.7601] + C:\>git init wintest + Initialized empty Git repository in C:/wintest/.git/ + C:\>cd wintest + C:\wintest>git annex init wintest + init wintest + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + ok + (Recording state in git...) + C:\wintest>echo \"thisisatest\">wintest + C:\wintest>git annex add wintest + add wintest (checksum...) ok + (Recording state in git...) + C:\wintest>git remote add remote ssh://me@linuxbox/home/me/testlinux + C:\wintest>ssh me@linuxbox + [me@home ~]$ git init --bare testlinux + Initialized empty Git repository in /home/me/testlinux/ + [me@home ~]$ cd testlinux/ + [me@home testlinux]$ git annex init linux + init linux ok + (Recording state in git...) + [me@home testlinux]$ exit + C:\wintest>git annex sync + commit + ok + pull remote + warning: no common commits + remote: Counting objects: 5, done. + remote: Compressing objects: 100% (3/3), done. + remote: Total 5 (delta 1), reused 0 (delta 0) + Unpacking objects: 100% (5/5), done. + From ssh://linux/home/me/testlinux + * [new branch] git-annex -> remote/git-annex + ok + (merging remote/git-annex into git-annex...) + (Recording state in git...) + push remote + Counting objects: 18, done. + Delta compression using up to 2 threads. + Compressing objects: 100% (12/12), done. + Writing objects: 100% (16/16), 1.45 KiB, done. + Total 16 (delta 2), reused 0 (delta 0) + To ssh://me@linux/home/michele/testlinux + * [new branch] git-annex -> synced/git-annex + * [new branch] master -> synced/master + ok + C:\wintest>git annex copy --to remote wintest + copy wintest (checking remote...) (to remote...) + wintest + 15 100% 0.00kB/s 0:00:00 (xfer#1, to-check=0/1) + + 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= + total size is 15 speedup is 0.13 + failed + git-annex: copy: 1 failed + + C:\wintest> +"""]] diff --git a/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment b/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment new file mode 100644 index 000000000..1cfed0a90 --- /dev/null +++ b/doc/bugs/cross_platform_permissions_woes/comment_3_278f91b4bc4c32717ab1c39c2abf9305._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 3" + date="2013-10-16T15:47:38Z" + content=""" +I think you will have better luck if you upgrade your server's git-annex version. I checked and some fixes for exactly this problem went in around May. Also, testing with the current version, I followed your procedure exactly and did not see the problem. +"""]] diff --git a/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment b/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment new file mode 100644 index 000000000..08ebe1e6d --- /dev/null +++ b/doc/bugs/cross_platform_permissions_woes/comment_4_eb6a271cb63c71341469c9ff89dc0eb9._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmCzVCPjgg_Un_114P8iiSwExms0G2csCA" + nickname="Michele" + subject="solved" + date="2013-10-18T21:00:38Z" + content=""" +installing very recent version on linux solved the problem !!! indeed a bug, but an old one! (quite difficult to get an updated version with cabal on fc19 and so forth, i would add a couple suggestion to share in the fedora install page) +thank you +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn new file mode 100644 index 000000000..8007ae11f --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos.mdwn @@ -0,0 +1,199 @@ +### Please describe the problem. +Data loss due to incorrect merge of repos in direct mode. (I tested the same scenario in indirect mode and it worked fine there) + +Given 2 repos A and B, in direct mode: + +1. in A: mkdir f, with a file f in it +2. in B: touch f +3. in B: sync + +Result: Only an f.variant-f###remains, which is file f of B, and the merge conflict has already been automatically resolved. I.e. Directory f containing file f, is lost. + +Expected result: remaining contents: f.variant-AAA which is file f of B, f.variant-BBB which is directory f of A, containing a file f. Merge conflict marked resolved. + +### What steps will reproduce the problem? +Execute the script given below in additional information. + +### What version of git-annex are you using? +git-annex version: 4.20130911-g6625d0e +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP Feeds Quvi + +### On what operating system? +Linux basementcat 3.10.10-1-ARCH #1 SMP PREEMPT Fri Aug 30 11:30:06 CEST 2013 x86_64 GNU/Linux + +### Please provide any additional information below. + +[[!format sh """ +[~]$ mkdir test +[~/test]$ mkdir a +[~/test/a]$ git init +Initialized empty Git repository in /home/limyreth/test/a/.git/ +[~/test/a]$ git annex init test +init test ok +(Recording state in git...) +[~/test/a]$ touch firstfile +[~/test/a]$ git annex add firstfile +add firstfile (checksum...) ok +(Recording state in git...) +[~/test/a]$ git annex sync +commit +ok +git-annex: no branch is checked out +[~]$ git clone test/a +Cloning into 'a'... +done. +[~]$ mv a test/b +[~/test/a]$ git annex direct +commit +# On branch master +nothing to commit, working directory clean +ok +direct firstfile ok +direct ok +[~/test/a]$ ls -l +total 0 +-rw-r--r-- 1 limyreth users 0 Oct 12 15:09 firstfile +[~/test/a]$ mkdir f +[~/test/a]$ touch f/f +[~/test/a]$ git annex add f/f +add f/f (checksum...) ok +(Recording state in git...) +[~/test/a]$ git annex sync +commit +ok +[~/test/b]$ git remote -v +origin /home/limyreth/test/a (fetch) +origin /home/limyreth/test/a (push) +[~/test/b]$ ls +firstfile +[~/test/b]$ git annex direct +commit +(Recording state in git...) +# On branch master +nothing to commit, working directory clean +ok +direct ok +[~/test/b]$ touch f +[~/test/b]$ git annex add f +add f (checksum...) ok +(Recording state in git...) +[~/test/b]$ git annex sync +(merging origin/git-annex into git-annex...) +(Recording state in git...) +commit +ok +pull origin +remote: Counting objects: 14, done. +remote: Compressing objects: 100% (7/7), done. +remote: Total 9 (delta 1), reused 0 (delta 0) +Unpacking objects: 100% (9/9), done. +From /home/limyreth/test/a + 2a8fa45..ad6802d master -> origin/master + 1f39016..19e3e12 git-annex -> origin/git-annex + * [new branch] synced/master -> origin/synced/master + +Adding f/f +CONFLICT (file/directory): There is a directory with name f in refs/remotes/origin/master. Adding f as f~HEAD +Automatic merge failed; fix conflicts and then commit the result. +f: needs merge +(Recording state in git...) +ok +[master 37a8019] git-annex automatic merge conflict fix + +Already up-to-date. +ok +(merging origin/git-annex into git-annex...) +(Recording state in git...) +push origin +Counting objects: 36, done. +Delta compression using up to 4 threads. +Compressing objects: 100% (20/20), done. +Writing objects: 100% (25/25), 2.16 KiB | 0 bytes/s, done. +Total 25 (delta 5), reused 0 (delta 0) +To /home/limyreth/test/a + ad6802d..37a8019 master -> synced/master + * [new branch] git-annex -> synced/git-annex +ok +[~/test/b]$ ls -l +total 0 +-rw-r--r-- 1 limyreth users 0 Oct 12 15:11 firstfile +-rw-r--r-- 1 limyreth users 0 Oct 12 15:11 f.variant-f874 +[~/test/b]$ git log --summary +commit 37a80199abe3cf82100bbdb5dd2217ed6bcb4b62 +Merge: 5a8942a ad6802d +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:47 2013 +0200 + + git-annex automatic merge conflict fix + +commit 5a8942a9a1735cb313c1f6624cbd3f48b252d9d9 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:47 2013 +0200 + + git-annex automatic sync + + create mode 120000 f + +commit ad6802dc231d389b86154e2df900a70b18e17b29 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:40 2013 +0200 + + git-annex automatic sync + + create mode 120000 f/f + +commit 2a8fa45bea996ab5ae219a017d4b642153e6d9c9 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:09:40 2013 +0200 + + git-annex automatic sync + + create mode 120000 firstfile +[~/test/a]$ git annex sync +(merging synced/git-annex into git-annex...) +commit +ok +merge synced/master +Updating ad6802d..37a8019 +Fast-forward + f.variant-f874 | 1 + + f/f | 1 - + 2 files changed, 1 insertion(+), 1 deletion(-) + create mode 120000 f.variant-f874 + delete mode 120000 f/f +ok +[~/test/a]$ git log --summary +commit 37a80199abe3cf82100bbdb5dd2217ed6bcb4b62 +Merge: 5a8942a ad6802d +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:47 2013 +0200 + + git-annex automatic merge conflict fix + +commit 5a8942a9a1735cb313c1f6624cbd3f48b252d9d9 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:47 2013 +0200 + + git-annex automatic sync + + create mode 120000 f + +commit ad6802dc231d389b86154e2df900a70b18e17b29 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:11:40 2013 +0200 + + git-annex automatic sync + + create mode 120000 f/f + +commit 2a8fa45bea996ab5ae219a017d4b642153e6d9c9 +Author: timdiels <timdiels.m@gmail.com> +Date: Sat Oct 12 15:09:40 2013 +0200 + + git-annex automatic sync + + create mode 120000 firstfile + +"""]] + +> Bug fixed; test case added; [[done]] --[[Joey]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment new file mode 100644 index 000000000..1b22d2ce5 --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_1_294c33af08649256908a97894f93c05d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" + nickname="Tim" + subject="comment 1" + date="2013-10-13T12:35:47Z" + content=""" +I've just tested a similar scenario with 2 conflicting files, a file-file conflict, and then it works fine. That makes sense, as there's a test written for that. + +So the specific bits are: directory-file conflict of repos in direct mode. +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment new file mode 100644 index 000000000..7df35b33d --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_2_02a2b69adbb04b557146e713b70b34d2._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 2" + date="2013-10-16T18:04:27Z" + content=""" +I can confirm this bug, thanks for a good reproduction recipe. + +However, there is no actual data loss. If you switch to repo to indirect mode, you can use `git checkout` to check out the past versions from before the botched merge. When you do, you'll find that the files that the merge seemingly deleted in fact still have their contents present. It is preserved in `.git/annex/objects` by the automatic merge conflict resolution code, which does that whenever it deletes a file, whether for good reasons or for buggy reasons. + +So if you feel you lost data due to this, you can almost certainly get it back and I'm happy to help with that. + + +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment new file mode 100644 index 000000000..4adee73bd --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_3_d296ef26fc90f4e3166bba6d2de0a1ee._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" + nickname="Tim" + subject="comment 3" + date="2013-10-17T16:04:03Z" + content=""" +I had a recent backup of the data so no real harm was done. +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment new file mode 100644 index 000000000..bff93623c --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_4_33ba2c890c962a71ae9fadc417359f8e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" + nickname="Tim" + subject="comment 4" + date="2013-10-31T19:44:34Z" + content=""" +Has this issue been fixed? I checked out the repository today and compiled with cabal, but I don't see a f.variant-A and a f.variant-B pop up after sync. +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment new file mode 100644 index 000000000..0e5d67f74 --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_5_39eb0bb96fd271bd0de4a3a40814ae1b._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 5" + date="2013-11-01T15:48:21Z" + content=""" +AFAIK this bug is fixed, which is why I wrote above, \"Bug fixed; test case added; done\" + +If you have reason to think otherwise, better follow up. + +"""]] diff --git a/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment new file mode 100644 index 000000000..29457da8a --- /dev/null +++ b/doc/bugs/data_loss:_incorrect_merge_upon_conflicting_directory-file_of_direct_repos/comment_6_d80c4b631bdf58901a06f29a2c5682e2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlWskoNgUB7r70OXglR-4iKI4bOuPJb-xg" + nickname="Tim" + subject="comment 6" + date="2013-11-14T14:58:10Z" + content=""" +Ah indeed, tried it again and it's indeed fixed. Tried some other things as well, and conflict resolution ended up doing just fine. +"""]] diff --git a/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn b/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn index 4ab311174..a705e434f 100644 --- a/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn +++ b/doc/bugs/direct_mode_assistant_in_subdir_confusion.mdwn @@ -4,3 +4,34 @@ into it, and commit them there. These may have been files that needed to be comm 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_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn b/doc/bugs/direct_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn new file mode 100644 index 000000000..1afb9ac14 --- /dev/null +++ b/doc/bugs/direct_repository_on_FAT32_fails_to_addurl_containing___63__.mdwn @@ -0,0 +1,44 @@ +### 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/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn new file mode 100644 index 000000000..8ee66da19 --- /dev/null +++ b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__.mdwn @@ -0,0 +1,51 @@ +### Please describe the problem. + +When I create a directory special remote, with encryption enabled (shared) and a chunk size restriction (any), I can copy files *to* the remote, but git annex can't find/access them afterwards. + +If I do the same, just without specifying chunk size, it works fine. Restricting chunk size on FAT filesystems to something less that 4GB is necessary (otherwise storing bigger files will just fail). + +### What steps will reproduce the problem? + +Assume `~/annex` is a normal git annex repository and it contains a file `data.file`. + + # cd ~/annex + # mkdir /tmp/remote + # git annex initremote dirremote type=directory directory=/tmp/remote encryption=shared chunksize="300 megabytes" + initremote dirremote (encryption setup) (shared cipher) ok + (Recording state in git...) + # git annex copy --to dirremote data.file + copy data.file (gpg) (to dirremote...) + ok + (Recording state in git...) + # git annex fsck --from dirremote + fsck data.file (gpg) (fixing location log) + ** Based on the location log, data.file + ** was expected to be present, but its content is missing. + failed + (Recording state in git...) + git-annex: fsck: 1 failed + +The file is actually in the remote, e.g. `ls -R /tmp/remote` (shortened output): + + /tmp/remote/be5/af7/GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43: + GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43 + GPGHMACSHA1--cb23b50579bf69be9cdc0243b6fda1f66218eb43.chunkcount + +### What version of git-annex are you using? On what operating system? + +- mac OS X (10.8.5) +- git-annex version: 4.20131002-gf25991c +- `PATH` variable has `/Applications/git-annex.app/Contents/MacOS/bundle` at the front, so if git-annex comes with a binary, it is used + + +### 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]]; see my comment. --[[Joey]] diff --git a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment new file mode 100644 index 000000000..e068501ad --- /dev/null +++ b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_1_69dfbf566c75396cdaaf5ad70f1a94a8._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-10-26T19:06:38Z" + content=""" +There was a bug that caused it not to write the chunkcount file. +I have fixed it, and put in a workaround so fsck, etc, will +see that the file is stored on the remote despite there being no +chunkcount file present. + +I was initially puzzled by your output showing the chunkcount file being present. +However, the bug also caused it to write a chunkcount file when chunking was disabled (ie, the logic for when to write the file was inverted). +So, I think that the ls you show is after you set up the remote without specifying chunk size, and copied a file to it. + +Please test with the next autobuild of git-annex (should be one within an hour my my posting this comment) and verify it can now see the files you stored on the remote with chunking. + + +"""]] diff --git a/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment new file mode 100644 index 000000000..81d6b35a3 --- /dev/null +++ b/doc/bugs/directory_remote_+_shared_encryption_+_chunk_size___61___lost_files__63__/comment_2_8d09cc0e06548c4ebde7956edd1b5d85._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://jspk.clavid.com/" + nickname="flabbergast" + subject="comment 2" + date="2013-10-28T09:36:19Z" + content=""" +Thanks! I've checked now and the problem is gone. +"""]] diff --git a/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn b/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn new file mode 100644 index 000000000..ed269277c --- /dev/null +++ b/doc/bugs/encrpyted_ssh_remote_on_macosx.mdwn @@ -0,0 +1,42 @@ +### 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 new file mode 100644 index 000000000..948b2c110 --- /dev/null +++ b/doc/bugs/encrpyted_ssh_remote_on_macosx/comment_1_46c37aacb7ae41864488fb7c7d87d437._comment @@ -0,0 +1,10 @@ +[[!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/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn new file mode 100644 index 000000000..dae654d13 --- /dev/null +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn @@ -0,0 +1,63 @@ +### What steps will reproduce the problem? +[[!format sh """ +C:\Users\Bruno>mkdir annex + +C:\Users\Bruno>cd annex + +C:\Users\Bruno\annex>git init +Initialized empty Git repository in C:/Users/Bruno/annex/.git/ + +C:\Users\Bruno\annex>git annex init +init + Detected a crippled filesystem. + + Enabling direct mode. + + Detected a filesystem without fifo support. + + Disabling ssh connection caching. +ok +(Recording state in git...) + +C:\Users\Bruno\annex>echo test > test + +C:\Users\Bruno\annex>git annex add . +add test (checksum...) ok +(Recording state in git...) + +C:\Users\Bruno\annex>git commit -a -m added +[master (root-commit) 2eea610] added + 1 file changed, 1 insertion(+) + create mode 120000 test + +C:\Users\Bruno\annex>git annex sync +(Recording state in git...) +fatal: unable to access '../../../../C:\Users\Bruno\annex\.git/config': Invalid argument + +git-annex: user error (xargs ["-0","git","--git-dir=C:\\Users\\Bruno\\annex\\.git","--work-tree=C:\\Users\\Bruno\\annex","add","-f"] exited 123) +failed +git-annex: sync: 1 failed +"""]] + +### What version of git-annex are you using? On what operating system? +Windows 8 (64 bits) + +git version 1.8.4.msysgit.0 + +[[!format sh """ +git-annex version: 4.20131008-ge115441 +build flags: 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 +local repository version: 4 +default repository version: 3 +supported repository versions: 3 4 +upgrade supported from repository versions: 2 +"""]] + +### Please provide any additional information below. +C:\Users\Bruno\annex\.git\config exists + +> xargs was one problem; also msysgit seems to just not +> accept DOS style paths anymore in --git-dir or --git-work-tree. +> megaweird. [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment new file mode 100644 index 000000000..cc616aae9 --- /dev/null +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 1" + date="2013-10-16T20:42:07Z" + content=""" +I don't know what to make of this bug report. You say that \"C:\Users\Bruno\annex.git\config\" exists, but you show the creation of a \"C:\Users\Bruno\annex\", and not the other repository. I cannot reproduce it, even if I first \"git init --bare annex.git\". +"""]] diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment new file mode 100644 index 000000000..a40e9cbe5 --- /dev/null +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment @@ -0,0 +1,48 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM" + nickname="Bruno" + subject="comment 2" + date="2013-10-16T22:47:46Z" + content=""" +There's no other repo yet. I have the same problem when I try to sync between two repos but I simplified the instructions to reproduce the bug easily. + +Here's the instructions on Debian : +[[!format sh \"\"\" +bruno@debian:~$ mkdir annex +bruno@debian:~$ cd annex +bruno@debian:~/annex$ git init +Initialized empty Dépôt git dans /home/bruno/annex/.git/ +bruno@debian:~/annex$ git annex init +init ok +(Recording state in git...) +bruno@debian:~/annex$ echo test > test +bruno@debian:~/annex$ git annex add . +add test (checksum...) ok +(Recording state in git...) +bruno@debian:~/annex$ git commit -a -m added +[master (root-commit) 631049d] added + 1 file changed, 1 insertion(+) + create mode 120000 test +bruno@debian:~/annex$ git annex sync +commit +ok +bruno@debian:~/annex$\"\"\"]] + +It seems --git-dir wants 'c:/...' instead of 'c:\\...'. + +[[!format sh \"\"\" +C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex add -f test +fatal: unable to access '../../../../C:\\Users\\Bruno\\annex\\.git/config': Invalid argument + +C:\Users\Bruno\annex>git --git-dir=C:/Users/Bruno/annex/.git --work-tree=C:\\Users\\Bruno\\annex add -f test + +C:\Users\Bruno\annex>\"\"\"]] + +It's weird that I don't have any problem with the following command: +[[!format sh \"\"\"C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex config -l +core.symlinks=false +core.autocrlf=true +[...]\"\"\"]] + +Maybe there's a problem with `git version 1.8.4.msysgit.0`. +"""]] diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment new file mode 100644 index 000000000..ac4a9e91a --- /dev/null +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 4" + date="2013-10-17T21:49:10Z" + content=""" +So this is a problem with msysgit 1.8.4. I have been able to reproduce it with that version. 1.8.3 did not have the problem. + +Seems to perhaps be due to the cygwin xargs flipping git into cygwin path mode somehow. (How all this works is massively complex and confusing to me.) +All the other calls to git with identical parameters work fine. I can also reproduce the problem using some old git 1.7.x in the cygwin terminal. + +BTW, I noticed in your example that you ran \"git commit -a\". You should **never** do that in a [[direct mode]] repository. Read the direct mode documentation to understand why. +"""]] diff --git a/doc/bugs/file_modification_times.mdwn b/doc/bugs/file_modification_times.mdwn new file mode 100644 index 000000000..2f75dcab7 --- /dev/null +++ b/doc/bugs/file_modification_times.mdwn @@ -0,0 +1,13 @@ +### Please describe the problem. +The files created in another remote when syncing is "now" rather than keeping the modification time of the source file. As such, git-annex assistant is removing an important bit of information about the file. + +### What steps will reproduce the problem? +1) create two repositories in your computer using webapp +2) add files to RepoA, see that they are synced to the RepoB. +3) check the file modification times from any file manager. you will see that while files in RepoA carry correct modification time, synced file in RepoB carries current time. + +### What version of git-annex are you using? On what operating system? +Ubuntu 13.10 32bit version 4.20130815 from apt-get. + +> duplicate of [[todo/add_metadata_to_annexed_files]] --[[Joey]] +> [[done]] diff --git a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn new file mode 100644 index 000000000..c256778c8 --- /dev/null +++ b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn @@ -0,0 +1,19 @@ +git-annex 4.20130911 on Debian Wheezy. + +Using `git annex initremote type=gcrypt` as described [here](http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/) creates the repository and pushes the `git-annex` branch to it. It doesn't push `master` (or more generally: the currently checked out branch), as I have verified using `git remote show`. + +Manually pushing the branch makes `git annex sync` sync both branches with the gcrypt remote. + +I think that it should push the current branch upon creation of the special remote, since for at least me, the whole reason for wanting `git-remote-gcrypt` is that metadata as well as data can be stored encrypted on an SSH server. + +Thanks for considering this. + +> The git-annex branch is pushed by initremote because I have to push +> *something* to determine the gcrypt-id. However, this is an implementation +> detail, and not a feature of initremote. (It's more like a bug of +> git-remote-gcrypt.) +> +> `git annex sync` will always push your currently checked out branch, +> as well as the git-annex branch, no matter what `initremote` has done. +> +> [[done]] --[[Joey]] diff --git a/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn b/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn new file mode 100644 index 000000000..5ec1aa9aa --- /dev/null +++ b/doc/bugs/get_from_bup-remote_with_pubkey_failing.mdwn @@ -0,0 +1,93 @@ +### Please describe the problem. + +I'm unable to 'git annex get' a file from a bup-remote with encryption set to 'pubkey'. + +### What steps will reproduce the problem? + +I added a bup-remote using [these instructions](http://git-annex.branchable.com/walkthrough/using_bup/): + + bash-3.2$ git annex initremote mybup type=bup encryption=pubkey keyid=0xABE8244505D63E81 buprepo=gumdrop:/home/gert/.bup + + # now adding files and moving them: + bash-3.2$ mkdir orgmode && touch orgmode/some.org + bash-3.2$ git annex add orgmode/some.org + add orgmode/some.org (checksum...) ok + (Recording state in git...) + bash-3.2$ git commit + [master bce8c83] Some.org + 1 file changed, 1 insertion(+) + create mode 120000 orgmode/some.org + bash-3.2$ git annex move orgmode/ --to=mybup + move orgmode/another.org (gpg) + U moet een geheime zin opgeven om de geheime sleutel te gebruiken + van: “email” + 4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10 + (sub-sleutel bij hoofd sleutel ID 0xE9B90528FDA4E1E6) + + (checking mybup...) ok + (Recording state in git...) + bash-3.2$ less orgmode/another.org + orgmode/another.org: No such file or directory + bash-3.2$ git annex get orgmode/another.org --debug + [2013-11-13 16:18:07 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","ls-files","--cached","-z","--","orgmode/another.org"] + get orgmode/another.org [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","show-ref","git-annex"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","show-ref","--hash","refs/heads/git-annex"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..f25f9bb2b78a8b9c4b64087f1378c68fb5c0a2f1","--oneline","-n1"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..1b0a3dd72be437d800e58d659837d6e528cbbc39","--oneline","-n1"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..f62419efea58245d232a52ceaf0eaefe3b0fdced","--oneline","-n1"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..eb6f0cd983d9a3637e984aa815537fe20a5c2a69","--oneline","-n1"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..5362118e643462a0875bfe31d493ffe64413f2d8","--oneline","-n1"] + [2013-11-13 16:18:08 CET] read: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","log","refs/heads/git-annex..e5afaf82ce25f60a108c0ae873b6fd57c5d28ca7","--oneline","-n1"] + [2013-11-13 16:18:08 CET] chat: git ["--git-dir=/Users/gert/annex/.git","--work-tree=/Users/gert/annex","cat-file","--batch"] + [2013-11-13 16:18:08 CET] read: git ["config","--null","--list"] + (from mybup...) (gpg) [2013-11-13 16:18:08 CET] chat: gpg ["--quiet","--trust-model","always","--decrypt"] + + U moet een geheime zin opgeven om de geheime sleutel te gebruiken + van: “<email>” + 4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10 + (sub-sleutel bij hoofd sleutel ID 0xE9B90528FDA4E1E6) + + [2013-11-13 16:18:15 CET] read: bup ["join","-r","gumdrop:/home/gert/.bup","GPGHMACSHA1--67aec1b62d05d000442cf8e7d9df8d327eaf26d5"] + [2013-11-13 16:18:15 CET] chat: gpg ["--quiet","--trust-model","always","--batch","--decrypt"] + gpg: kan geheime zin niet opvragen in batch modus + gpg: decoderen mislukt: secret key not available + + Unable to access these remotes: mybup + + Try making some of these repositories available: + 080e97d2-4f82-4292-acb7-a48d82009258 -- mybup (mybupmy bup repository at gumdrop) + + (Note that these git remotes have annex-ignore set: origin) + failed + git-annex: get: 1 failed + +### What version of git-annex are you using? On what operating system? + +Running git-annex version 4.20131105-g136b030 on OSX 10.8.5. + +### Please provide any additional information below. + +My ideas: + +"Unable to access these remotes: mybup" is weird, I just moved files there. + +"secret key not available" makes me think it's looking for the primary secret key (which is indeed offline). +When I encrypt a file with the same key I used to create the remote it just works: + + $ gpg --armor --recipient 0xABE8244505D63E81 --encrypt file.txt + $ gpg --decrypt file.txt.asc + +When prompting for my passphrase it states "4096-bit RSA key, ID 0xFF8DE378DE223820, created 2013-11-10". +That is a different subkey than what I entered when I setting up the remote. + +My keys/subkeys: + + pub 4096R/0xE9B90528FDA4E1E6 aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: SC + vertrouwen: ultimate geldigheid: ultimate + sub 4096R/0x98816CFB398B4666 aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: E + sub 4096R/0x91951718D5F11CDD aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: S + sub 4096R/0xABE8244505D63E81 aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: E + sub 4096R/0xB44520A46B27144D aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: S + sub 4096R/0xFF8DE378DE223820 aangemaakt: 2013-11-10 vervaldatum: 2014-11-10 gebruik: E + +> This was already fixed in version 4.20131106. [[done]] --[[Joey]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied.mdwn b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied.mdwn new file mode 100644 index 000000000..260ab9981 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied.mdwn @@ -0,0 +1,48 @@ +### Please describe the problem. +I followed the tip on [fully encrypted git repositories with gcrypt](http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/) to create encrypted git-annex repository on a ssh server. When I try to checkout the repository, things break as follows: + +`git clone gcrypt::ssh://my.server/home/me/encryptedrepo myrepo` + +works as expected but when in the myrepo directory, + +`git annex enableremote encryptedrepo gitrepo=ssh://my.server/home/me/encryptedrepo` + +issues the following text (among normal messages): + +`git-annex-shell: gcryptsetup permission denied` + +Then while the links are there, + +`git annex get --from encryptedrepo` + +does nothing (in the sense that the content is not retrieved). + +This seems to have everything to do with git-annex-shell as the exact same manipulations but with a local repository work perfectly. Unfortunately, I don't know haskell so [this code](https://github.com/joeyh/git-annex/blob/master/Command/GCryptSetup.hs) is cryptic to me. I can guess there is a problem getting the uuid of the repository, but as far as I can tell the bare distant repo looks fine. + +### What steps will reproduce the problem? + +Create a standard git annex local repository and then follow the [fully encrypted git repositories with gcrypt tip](http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/) to create an encrypted git-annex repository on a ssh server. Then follow the instructions in the same tip to clone the remote repository. + +### What version of git-annex are you using? On what operating system? +Both computers run ubuntu 12.04 with all updates and the latest git annex from the ppa, that is: + +git-annex version: 4.20131024 + +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 + + +### 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/git-annex-shell:_gcryptsetup_permission_denied/comment_1_f4584158b35b80ece1060308883e2dc4._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_1_f4584158b35b80ece1060308883e2dc4._comment new file mode 100644 index 000000000..6312a58a5 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_1_f4584158b35b80ece1060308883e2dc4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-11-02T19:46:28Z" + content=""" +It seems to me that the `git-annex-shell` on the remote system must be too old a version to support the gcryptsetup command. You can check this by running `git-annex-shell` there and seeing if it lists gcryptsetup in its usage message. +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_2_a4d7aae848340771a9b8e2c87abeea42._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_2_a4d7aae848340771a9b8e2c87abeea42._comment new file mode 100644 index 000000000..f2fb4f14f --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_2_a4d7aae848340771a9b8e2c87abeea42._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkbpbjP5j8MqWt_K4NASwv0WvB8T4rQ-pM" + nickname="Fabrice" + subject="comment 2" + date="2013-11-02T21:53:37Z" + content=""" +The git-annex version on the remote server is the same as the one on the client, the latest one available from the ppa (4.20131024). When I run git-annex-shell on both computers, I obtain: +[[!format sh \"\"\" +git-annex-shell: bad parameters + +Usage: git-annex-shell [-c] command [parameters ...] [option ...] + +Plumbing commands: + +commit DIRECTORY commits any staged changes to the git-annex branch +configlist DIRECTORY outputs relevant git configuration +dropkey DIRECTORY KEY ... drops annexed content for specified keys +gcryptsetup DIRECTORY VALUE sets up gcrypt repository +inannex DIRECTORY KEY ... checks if keys are present in the annex +recvkey DIRECTORY KEY runs rsync in server mode to receive content +sendkey DIRECTORY KEY runs rsync in server mode to send content +transferinfo DIRECTORY KEY updates sender on number of bytes of content received +\"\"\"]] + +Both sides seem to understand the gcryptsetup action. Actually, the message gcryptsetup permission denied comes from git-annex-shell, as far as I understand (and from the haskell source linked in the report). +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_3_06bda101ad584b4b882de8b2e202d679._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_3_06bda101ad584b4b882de8b2e202d679._comment new file mode 100644 index 000000000..863f401ce --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_3_06bda101ad584b4b882de8b2e202d679._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 3" + date="2013-11-02T23:51:13Z" + content=""" +I should have looked at that error message more closely. The gcryptsetup command will print a permission denied if the repository it's being run in already has a annex.uuid or already has a gcrypt id. Probably that latter needs to be relaxed for enableremote to work. +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_4_4fc6b25401b645cabc04b510bdfa6863._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_4_4fc6b25401b645cabc04b510bdfa6863._comment new file mode 100644 index 000000000..e1049ce60 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_4_4fc6b25401b645cabc04b510bdfa6863._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 4" + date="2013-11-03T00:15:30Z" + content=""" +While I've fixed this bug, in my testing the bug only caused git-annex to fall back to accessing the remote repository using rsync, rather than using git-annex-shell to talk to it, and so `git annex get --from encryptedrepo` was able to retrieve files that were stored in that remote despite the bug. That may have failed for you for some other reason. + +You can set git.encryptedrepo.annex-gcrypt to to \"true\" to make it use the degraded rsync mode, or to \"shell\" to make it use git-annex-shell. Setting it to shell should be all that you need to do to recover from (or indeed, work around this bug). +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_5_4e193306801680bba433e75eb4dcba05._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_5_4e193306801680bba433e75eb4dcba05._comment new file mode 100644 index 000000000..137638aa5 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_5_4e193306801680bba433e75eb4dcba05._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkbpbjP5j8MqWt_K4NASwv0WvB8T4rQ-pM" + nickname="Fabrice" + subject="comment 5" + date="2013-11-03T11:24:28Z" + content=""" +There is something very strange that I did not notice in my first report. When I try `git annex get --from encryptedrepo` nothing happens in the sense that git annex is not even trying to connect to the remote (no ssh connection attempt) while git.encryptedrepo.annex-gcrypt is set to true. When I set it to shell, nothing happens either. + +Another thing I did not report is that I tried the exact same manipulations with another server on which git annex is not installed. The `gcryptsetup permission denied` message was replaced by a `git-annex-shell not found` (or something similar), as expected. But the rest of the behavior was the same: no way to get the actual content with `git annex get --from`. Again, all of this is with 4.20131024, not with the ongoing version. + +I'll try got do more test with the new version. +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_6_76ccdf0542e76e4dbd61f3b3228d40ba._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_6_76ccdf0542e76e4dbd61f3b3228d40ba._comment new file mode 100644 index 000000000..0ad9768f6 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_6_76ccdf0542e76e4dbd61f3b3228d40ba._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 6" + date="2013-11-04T17:12:05Z" + content=""" +It's entirely normal for `git annex get --from remote` to skip files that it does not think are present on the remote. + +What does `git annex whereis` say? +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_7_cd964d0a375c5cba299bf2bbbbb86acb._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_7_cd964d0a375c5cba299bf2bbbbb86acb._comment new file mode 100644 index 000000000..3a24f4349 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_7_cd964d0a375c5cba299bf2bbbbb86acb._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkbpbjP5j8MqWt_K4NASwv0WvB8T4rQ-pM" + nickname="Fabrice" + subject="comment 7" + date="2013-11-04T18:54:54Z" + content=""" +`git annex whereis` says the files are not on the remote git, while they are because of the copy. If I do _exactly_ what's on the tip, that is if I clone the encrypted git just after having done `git annex copy --to encryptedbackup`, the remotes seems to ignore that it has the data. To have it working, I had to call `git annex sync` (push will do, I guess) in the original remote after doing the `git annex copy`. Then I can `git pull` and `git annex whereis` knows where the files are (or I can clone the encrypted remote after doing the sync/pull). + +It seems a bit strange that the copy command does not record the propagation of the file to the encrypted git. I guess this is because gcrypt is the only special remote that stores also the git part, right? Would that be a good idea (and possible) to handle it in a special way? + +Thanks Joey for everything, by the way, both the software and the amazing support via email and the website. +"""]] diff --git a/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_8_9bac87c85deb5bb15795df28533d0cde._comment b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_8_9bac87c85deb5bb15795df28533d0cde._comment new file mode 100644 index 000000000..da2fef585 --- /dev/null +++ b/doc/bugs/git-annex-shell:_gcryptsetup_permission_denied/comment_8_9bac87c85deb5bb15795df28533d0cde._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 8" + date="2013-11-04T19:14:04Z" + content=""" +Right -- Normally a special remote doesn't include a git repository. And when using a regular git remote, `git-annex-shell` is used to receive files into the repository and it records immediately that the repo has the file so there's no need to sync in that case. So gcrypt is special in this way. + +For now, I have fixed the tip to show syncing after sending files to gcrypt. It might be the case that it would make sense to do a push of the git-annex branch automatically in that case, will have to think about that and see if people get tripped up on this. +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long.mdwn b/doc/bugs/git-annex:_Argument_list_too_long.mdwn new file mode 100644 index 000000000..f12d5da65 --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long.mdwn @@ -0,0 +1,40 @@ +### Please describe the problem. + +Creating a SSH remote git-annex repository using the assisstant gives transcript: + +Initialized empty shared Git repository in /home/flindner/annex2/ +exec: 76: git-annex: Argument list too long + +### What steps will reproduce the problem? + +Using assistent: Creating a new empty local repository. Next, add another remote server repository using SSH. Checking the server went fine. I choose creating git repository. After about 5 minutes the error message above appears. In that time on the server runshell and git take plenty of CPU power but almost no memory. The directory on the server is created, but pairing was not successfull. + +### What version of git-annex are you using? On what operating system? + +Local: git-annex-standalone 4.20130909-1 from Archlinux AUR +Remote: git-annex-standalone-i386.tar.gz as of 13. sept. 13. on Debian Squeeze. + +### 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 + +daemon.log is empty. + +Log from the web GUI: + +[2013-09-13 12:34:11 CEST] main: starting assistant version 4.20130827-g4f18612 + + No known network monitor available through dbus; falling back to polling +(scanning...) [2013-09-13 12:34:11 CEST] Watcher: Performing startup scan +(started...) + + +# End of transcript or log. +"""]] + +> [[done]]; I have added a guard to runshell to detect when it has +> started to loop. Although I don't understand how a system could be +> misconfigured to let that happen, without going far out of your way to +> mess it up, it's a failure mode that's worth guarding against. --[[Joey]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment new file mode 100644 index 000000000..43f4aa98b --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_1_3f83ea525436b2379ab29a0f860c4669._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 1" + date="2013-09-13T15:31:35Z" + content=""" +Can you add set -x near the top of the server's runshell script and run this again also with debugging enabled in the local assistant, and post the log, please. +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment new file mode 100644 index 000000000..cd90d9c3b --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_2_b417c94169378ef7d0d278ebae517fa1._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" + nickname="Florian" + subject="comment 2" + date="2013-09-14T08:49:23Z" + content=""" +Is there any way to get the transcript from a log file, not from the web page? The output is so enormous that it crashed my browser out of memory (which is 16 GiB) when I tried to paste it. daemon.log contains no interesting output. +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment new file mode 100644 index 000000000..e182ca2c3 --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_3_fa925cca216cb810ad80482b19fc6053._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" + nickname="Florian" + subject="comment 3" + date="2013-09-15T23:08:48Z" + content=""" +Ok, I managed to get the transcript. It is located at <http://xgm.de/upload/transcript.log> (partly) resp. <http://xgm.de/upload/transcript.log.gz> (complete). Looks like the same script is executed again and again with an ever growing LD_LIBRARY_PATH argument list. The same happens when I simply run \"git-annex\" on the shell of the server. \"runshell\" standalone works fine. +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment new file mode 100644 index 000000000..033e695f5 --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_4_8bd2996107b2d272c32810658e07e715._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" + nickname="Florian" + subject="comment 4" + date="2013-09-15T23:10:38Z" + content=""" +Addendum: git inside runshells works, git-annex not. +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment new file mode 100644 index 000000000..b10c66c81 --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_5_378de7d7503a64611eab62f2f5cffef3._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnsuhFUIfWNT-Q-C02FDaSQqceFDge5M9w" + nickname="Florian" + subject="comment 5" + date="2013-09-16T09:00:34Z" + content=""" +Ok, bug can be closed, it was never a bug (at least not in git-annex). I was using the i386 build on a x86_64 machine. + +Server is virtual machine from Strato. + +$ uname -a +Linux h1774498.stratoserver.net 2.6.32-042stab078.27 #1 SMP Mon Jul 1 20:48:07 MSK 2013 i686 GNU/Linux + +Since there was no x86_64 in the uname output, I thought it was a i386 machine. The git-annex binaries gave a \"File not found\" error message, the git binaries worked. Nothing I connected to a wrong architecture... Sorry for the hassle! +"""]] diff --git a/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment b/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment new file mode 100644 index 000000000..a788f2c8e --- /dev/null +++ b/doc/bugs/git-annex:_Argument_list_too_long/comment_6_a94e17151348d02999442dd1219babfb._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.14.105" + subject="comment 6" + date="2013-09-19T17:31:46Z" + content=""" +I have tried to reproduce this bug, running the amd64 build on i386, and cannot. When I run the git-annex shell script included in the standalone bundle, it runs runshell, which in turn tries to run bin/git-annex. Since the architecture is wrong, that fails. + +I suppose your shell could instead, if presented with a binary of the wrong architecture, skip it and keep searching PATH for another one. That would be a most odd behavior, but if that were the case and you put the git-annex script into PATH, it would lead to what you describe. +"""]] diff --git a/doc/bugs/git-annex:_fd:14:_hGetLine:_end_of_file.mdwn b/doc/bugs/git-annex:_fd:14:_hGetLine:_end_of_file.mdwn index 1e9f3aec4..0d773b52c 100644 --- a/doc/bugs/git-annex:_fd:14:_hGetLine:_end_of_file.mdwn +++ b/doc/bugs/git-annex:_fd:14:_hGetLine:_end_of_file.mdwn @@ -1,3 +1,5 @@ +[[!tag moreinfo]] + ### Please describe the problem. git-annex webapp won't run diff --git a/doc/bugs/git-annex:_status:_1_failed.mdwn b/doc/bugs/git-annex:_status:_1_failed.mdwn new file mode 100644 index 000000000..65f00469c --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed.mdwn @@ -0,0 +1,25 @@ +Hi + +I have a 1 To repository on my local linux box + +when i try : + + git annex status + +i get : + + git-annex: /media/malima/nazare/.git/annex/tmp/0723300. Everywhere I Dub --: getFileStatus: does not exist (No such file or directory) + failed + +how could i fix this issue ? + +many thanks for help + +> [[done]]; I managed to reproduce this bug by making a temp file named +> ".git/annex/tmp/foo-", or indeed with any dash in it. This is enough +> to make git-annex think it's a key, but badly formed enough that +> it fails trying to use that key. Fixed to ignore such non-key files. +> +> I'm unsure why `.git/annex/tmp` would have such files in it. +> Perhaps the assistant was running, but crashed while adding files? +> --[[Joey]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment b/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment new file mode 100644 index 000000000..556982e34 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_10_7cd9de88e55633fc75460f4fe0400f09._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="204.8.156.142" + subject="comment 10" + date="2013-10-15T18:49:26Z" + content=""" +`git annex status` complains about `.git/annex/tmp/problematic_file--`. That file doesn't exist, but `.git/annex/tmp/problematic_file-` (with one dash) does. And the file itself (no dashes) does exist in a subdir of the annex. +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment b/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment new file mode 100644 index 000000000..45ee3a050 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_11_504a944aab34155046f2fd82c2878f3e._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="96.44.189.101" + subject="comment 11" + date="2013-10-27T00:59:56Z" + content=""" +I've tried a few things and found a workaround for the problem. TL;DR: `git annex dropunused` + +First I created a new annex with the same data. This time I used `git annex add` instead of having the assistant add the files. Adding went fine (no status error). Only when I started the assistant I got the error right away, with exactly the same file as the last time. + +When I removed the file from the annex, the error remained, but this time with a different problematic file in the same directory. + +Then I stumbled upon [this forum post](http://git-annex.branchable.com/forum/dot_git_slash_annex_slash_tmp/). It relates to this bug in that the files git-annex is complaining about are located in .git/annex/tmp. `git annex unused` returned about 130 entries (of about 1,200 files total). The last entry was my problematic file. The second-to-last entry was the file that gave me the same error when I removed the original problematic file. This lets me assume that the bug causes `git annex status' to produce 130 errors, of which only the last one gets displayed. + +So I ran `git annex dropunused 1-130 --force`. (The command wouldn't run without `--force`, saying that it couldn't make sure if numcopies were being met. This may or may not be related to network problems I'm having lately.) Anyway, now the error was finally gone and the status output didn't complain anymore. + +Weird stuff. +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment b/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment new file mode 100644 index 000000000..a5a378c99 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_1_c235cc83c75474e6393e08d2d94b119d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T19:38:50Z" + content=""" +You might try moving the .git/annex/transfer/ directory out of the way. + +What version of git-annex do you have installed? +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment b/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment new file mode 100644 index 000000000..98fb1d805 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_2_932f6aaa712298a47868002872e16310._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="eezec" + ip="93.21.246.236" + subject="comment 2" + date="2013-09-10T06:05:32Z" + content=""" +i have + git-annex version: 4.20130815 + +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment b/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment new file mode 100644 index 000000000..0c3604ad6 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_3_4bf55320439de152a65e2f21d4a0604b._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="eezec" + ip="93.21.246.236" + subject="comment 3" + date="2013-09-11T06:12:20Z" + content=""" +Joey .. moving transfer didn't work .. i have the same message when doing + + git annex status + .... + getFileStatus: does not exist (No such file or directory) + .... + git-annex: status: 1 failed +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment b/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment new file mode 100644 index 000000000..3e4ecb82f --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_4_cb2cfb798c6171f77eb7c4c4061c0f0c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.51" + subject="comment 4" + date="2013-09-12T21:10:12Z" + content=""" +can you `strace git-annex status` ? +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment b/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment new file mode 100644 index 000000000..61af9e9df --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_5_05c84dde377298adfd3fc20749b3108f._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="213.61.149.100" + subject="comment 5" + date="2013-10-13T06:33:24Z" + content=""" +I use v4.20130909 and get the same error when running `git-annex status`. Does it matter that my filename in question is shown to have two dashes (--) at the end, just as in OP's case? Other files in .git/annex/tmp only have one dash at the end. + +Joey, I straced the command and sent the output to your kitenet e-mail address. Hope it helps. +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment b/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment new file mode 100644 index 000000000..ab720b6ce --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_6_bb5141e29c665bc0bb82611ea27d4be8._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.22" + subject="comment 6" + date="2013-10-13T17:35:20Z" + content=""" +What is the last line printed before this error message? + +My preliminary analysis is that it is checking the sizes of stale files in .git/annex/tmp, and could fail if a temp file was deleted just as it was running. +But if so it would be unlikely to happen every time `git annex status` is run. Or even if it did happen every time (perhaps because you appear to be running the git-annex assistant and it might be adding a lot of files in the background), the filename in the error message would be different every time. I have just committed a fix for that problem to git, but am not 100% sure it's really the problem that you're seeing. +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment b/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment new file mode 100644 index 000000000..54f87581c --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_7_5fd39168c9e1bf43909ee0ab3c75c40c._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="37.130.227.133" + subject="comment 7" + date="2013-10-13T22:14:05Z" + content=""" +Yes, I run the assistant in the background. The error came up after I ran + + git init + git annex init + git annex direct + git annex assistant + +in a directory containing a lot of files (around 80G). Right away, `git annex status` gave me the error below. The file name in question never changed during the process of adding files and hasn't changed after all files have been added. + +Here's the complete command line output: + + $ git annex status + supported backends: SHA256E SHA1E SHA512E SHA224E SHA384E SHA256 SHA1 SHA512 SHA224 SHA384 WORM URL + supported remote types: git gcrypt S3 bup directory rsync web glacier hook + repository mode: direct + trusted repositories: 0 + semitrusted repositories: 2 + 00000000-0000-0000-0000-000000000001 -- web + c1bb8eb9-fb0c-4bac-b0df-37df25b2d1e7 -- here + untrusted repositories: 0 + transfers in progress: none + available local disk space: 1.74 terabytes (+10 gigabytes reserved) + + git-annex: /storage/media/.git/annex/tmp/problematic_file--: getFileStatus: does not exist (No such file or directory) + failed + git-annex: status: 1 failed + + +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment b/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment new file mode 100644 index 000000000..e4fae1f31 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_8_e493f6bddb0bfcd9478d5f4d9fc170e0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="RaspberryPie" + ip="204.8.156.142" + subject="comment 8" + date="2013-10-14T17:49:05Z" + content=""" +Quick question: Is there any way to get rid of the error in the existing repository (e.g. remove the problematic tmp file entry) so I can get a complete status output? Bonus points if I don't have to annex every single file anew. `git annex fsck` doesn't work, as doesn't `git annex fix` (it's a direct repo). +"""]] diff --git a/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment b/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment new file mode 100644 index 000000000..208f178a3 --- /dev/null +++ b/doc/bugs/git-annex:_status:_1_failed/comment_9_573377d444aee0895b231082bc6839a4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 9" + date="2013-10-15T17:51:04Z" + content=""" +Does the file that it's complaining about exist? +"""]] diff --git a/doc/bugs/git-annex_broken_on_Android_4.3.mdwn b/doc/bugs/git-annex_broken_on_Android_4.3.mdwn index da1f7fd28..4c1b356fb 100644 --- a/doc/bugs/git-annex_broken_on_Android_4.3.mdwn +++ b/doc/bugs/git-annex_broken_on_Android_4.3.mdwn @@ -1,3 +1,7 @@ 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 new file mode 100644 index 000000000..5d56dc84c --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_10_e47c073f1614f7b57f86acedeeb1cadc._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..d84a59b76 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_11_ce34578c45060b7c8b759efd1c1d8df8._comment @@ -0,0 +1,13 @@ +[[!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 new file mode 100644 index 000000000..3f520d7e4 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_12_75965395dc33046ce34ac5ba972b7d64._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..f2a57f731 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_13_f07bc76dd3c5580fc0855a33ae835c8d._comment @@ -0,0 +1,12 @@ +[[!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 new file mode 100644 index 000000000..6336a3bd4 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_14_637c59becc68a1e4f60069d8873489ff._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..6bca41b3a --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_15_d80b87055f72873f5678a01d2630bea4._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..204845eb5 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_16_57ac84868b223b30f005704eefa01b8d._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..9712f5944 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_17_a41f4d8a72c07ad770e6479e9b8c7f1d._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..2dc32cf15 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_18_7d36637f11cda51de395303d5c1c6a3f._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..2f22ad21c --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_19_c8609c3f7f62ae5427fd8c60bc9546ed._comment @@ -0,0 +1,8 @@ +[[!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_20_0886bca6d0c6a9415a7794d256be2e9d._comment b/doc/bugs/git-annex_broken_on_Android_4.3/comment_20_0886bca6d0c6a9415a7794d256be2e9d._comment new file mode 100644 index 000000000..2b547d9a7 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_20_0886bca6d0c6a9415a7794d256be2e9d._comment @@ -0,0 +1,14 @@ +[[!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 new file mode 100644 index 000000000..551334819 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_21_2b39729f95c9c4bba620ecdd3d1558ed._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..e4937e0f8 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_22_8d90d92951919aa70638b31e9248bec5._comment @@ -0,0 +1,16 @@ +[[!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 new file mode 100644 index 000000000..05cb634e6 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_23_6398271f5cd9e94996202ef3bce6f6ed._comment @@ -0,0 +1,20 @@ +[[!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 new file mode 100644 index 000000000..c8fea212b --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_24_c9e399833cc6235077161f490dfa866f._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..e28a9508b --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_25_cf093737eefb2b99f6f0eac9bf3e74b3._comment @@ -0,0 +1,9 @@ +[[!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 new file mode 100644 index 000000000..1c72cd27b --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_26_c122ce53175fc9e0e114a8acd2385c0d._comment @@ -0,0 +1,29 @@ +[[!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 new file mode 100644 index 000000000..dd911955a --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_27_237e41e61781bb058f5fd39362a904e4._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..6341aae80 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_28_97f423a41ee9d2d74291594fae20dd4e._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..1cd4c356f --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_29_7b3fbe7e38f637fcea511441ac243d93._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..3d5003504 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_2_53e2d095b2501844cadec910de286814._comment @@ -0,0 +1,14 @@ +[[!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 new file mode 100644 index 000000000..3409b9c4a --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_30_26c04584c3c6dacf59e1b6c82042c97c._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..14eed81c9 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_3_ddc9cbae1a721400a9acf2153e18f4f0._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..ab721064a --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_4_593235735e32238094121b1f79355bbd._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..cfb75bdd8 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_5_f806fd5930e90920db24456297465bae._comment @@ -0,0 +1,9 @@ +[[!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 new file mode 100644 index 000000000..438e00454 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_6_5741b6a5997328fdcd5cc99f841b18d3._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..4a3819472 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_7_3e0d9949dd810069af0b8076807e5924._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..52326b8e2 --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_8_f58897eff6b4693f0c73474ccfe6e733._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..015efd7ce --- /dev/null +++ b/doc/bugs/git-annex_broken_on_Android_4.3/comment_9_ddba87b2f20d8a63f7b8ebdb9bd13515._comment @@ -0,0 +1,18 @@ +[[!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_happily_deleted_most_of_my_files___36____35____38____33__.mdwn b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__.mdwn new file mode 100644 index 000000000..db8abfdce --- /dev/null +++ b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__.mdwn @@ -0,0 +1,58 @@ +### Please describe the problem. + +When cloning/syncing a repository (and probably doing some nono's in the process), +git annex will happily delete files. +This cost me several files, which just by coincidence were not totally important, still its *very* unsettling. + +### What steps will reproduce the problem? + +I did not try to exactly reproduce it yet (sorry, no time right now), but here is vaguley what I did (sorry its been a process spread over +several hours and i was doing lots of other things in parallel so I'm fuzzy about details): + + * have a repository in direct mode on your local harddrive, say ~/myannex + * git clone ~/myannex to /usbhd/myannex, git annex init. + The usbhd is a FAT, git annex recognizes it as "crippled filessytem". + * Git annex get all from ~/myannex. So far, so good. + * create several files on ~/myannex, git annex add them + * do a git annex add on them, abort it (realizing SHA256E takes forever, so changing to WORM), repeat add + (not sure wheter i did a git annex sync here) + * create several files on /usbhd/myannex, git annex add them + (not sure wheter i did a git annex sync here again) + +All repos are in direct mode. + +From here on i don't remember the exact order of events, one definite -- probably important -- nono i did, +was: +I executed a git annex sync/get on the usbhd in a sub-directory (i.e. not in the git base dir), say /usbhd/myannex/foo/bar/, +so it went on creating /usbhd/myannex/foo/bar/foo, which of course was not intended. +However /usbhd/myannex/foo/bar/foo contained FAT-crippled-symlinks to the new files in ~/myannex (good). + +In order to avoid a potential messy situation i just renamed /usbhd/myannex/foo to /usbhd/myannex/foo_bak +(which I just realize while writing this, saved me the hash values of my files, yay :)) + +However when I tried to repeat the procedure, it seems that the new files would not appear on the usbhd (for a reason i totally don't get, maybe I synced back before realizing my sub-foo mistake). +When I synced usbhd -> ~/myannex again, git-annex happily deleted my new files there which obviously quite upset me. + +Again, sorry for this horribly chaotic description, +I'll try and deliver a more reproducible description, but for the next 2 weeks at least I'm too busy for that. + + + +### What version of git-annex are you using? On what operating system? + +Archlinux, +3.9.2-1-ARCH #1 SMP PREEMPT Sat May 11 20:31:08 CEST 2013 x86_64 GNU/Linux + +aur/git-annex-bin 4.20131002-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 + + +# End of transcript or log. +"""]] + +[[!tag moreinfo]] diff --git a/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_1_5dd4d1cec069c13184f5dd9efca6721b._comment b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_1_5dd4d1cec069c13184f5dd9efca6721b._comment new file mode 100644 index 000000000..a8994ba9a --- /dev/null +++ b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_1_5dd4d1cec069c13184f5dd9efca6721b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://droggl.myopenid.com/" + ip="92.76.150.86" + subject="comment 1" + date="2013-10-08T07:46:35Z" + content=""" +Just in case you wonder: the most important (in the sense of not backupped elswhere) files where some scripts which i did hash with SHA256E and not with WORM. +"""]] diff --git a/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_2_d9b65fe4cb4bfd58f37e7da5350c6401._comment b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_2_d9b65fe4cb4bfd58f37e7da5350c6401._comment new file mode 100644 index 000000000..8574d974b --- /dev/null +++ b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_2_d9b65fe4cb4bfd58f37e7da5350c6401._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://cstork.org/" + nickname="Chris Stork" + subject="git annex get/sync don't delete files" + date="2013-10-10T11:43:29Z" + content=""" +AFAIU it's impossible for the 'get' subcommand to delete anything because it only copies files to .git/annex/objects. + +'sync' should also never delete files because it only adds files to the annex (i.e. checksums them and sets up the links and directories in .git/annex), commits things to git and pulls/pushes the git-annex specific branches to/from other repos. + +So I think some other 'nono' must have messed up your files. + +If you ever used (maybe unintentionally) used indirect mode there seem to be a rather high chance that some of your otherwise lost content is still in .git/annex/objects. Did you check if there's are any files in .git/annex/objects ? +"""]] diff --git a/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_3_1027187b203addd65af8cf1faf28727d._comment b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_3_1027187b203addd65af8cf1faf28727d._comment new file mode 100644 index 000000000..d5c08fb4f --- /dev/null +++ b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_3_1027187b203addd65af8cf1faf28727d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="64.134.31.139" + subject="comment 3" + date="2013-10-16T20:45:25Z" + content=""" +At least part of this sounds like [[direct_mode_assistant_in_subdir_confusion]]. The report is too confused for me to tell if that's the whole of the problem. + +Note that git-annex stores files in git, so if it did something wrong, you can switch to indirect mode, and use regular git commands to check out a tree from before the problem occurred. +"""]] diff --git a/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_4_ac65028203ff0cbdb978200235fb4e9c._comment b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_4_ac65028203ff0cbdb978200235fb4e9c._comment new file mode 100644 index 000000000..be972fa9a --- /dev/null +++ b/doc/bugs/git-annex_happily_deleted_most_of_my_files___36____35____38____33__/comment_4_ac65028203ff0cbdb978200235fb4e9c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 4" + date="2013-10-26T19:26:22Z" + content=""" +I have moreinfoed this bug, until I hear back with a better problem description. + +Using `git log --stat` to investigate any commits where files were removed would probably be a useful way to get a handle on what happened. +"""]] diff --git a/doc/bugs/git-annex_merge_stalls.mdwn b/doc/bugs/git-annex_merge_stalls.mdwn new file mode 100644 index 000000000..98615e352 --- /dev/null +++ b/doc/bugs/git-annex_merge_stalls.mdwn @@ -0,0 +1,16 @@ +### Please describe the problem. + +Running git-annex merge shows the output "git-annex merge ", followed by a blinking cursor. The command never seems to end. + +### What steps will reproduce the problem? + + +### What version of git-annex are you using? On what operating system? + +4.20130827-gd04d9bb on MacOS X Mountain Lion + +### Please provide any additional information below. + +dtruss output at https://www.dropbox.com/s/4b3yqn7ajfz5el2/annex-merge.log + +[[!meta title="no indication when git-annex is stuck waiting for a lock"]] diff --git a/doc/bugs/git-annex_merge_stalls/comment_1_31578a754945bdcb902c62ff58704bcb._comment b/doc/bugs/git-annex_merge_stalls/comment_1_31578a754945bdcb902c62ff58704bcb._comment new file mode 100644 index 000000000..123212d5d --- /dev/null +++ b/doc/bugs/git-annex_merge_stalls/comment_1_31578a754945bdcb902c62ff58704bcb._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T15:45:17Z" + content=""" +The relevant part of the log is: + +<pre> +65332/0x53591a: open(\"/Users/gsolsberry/annex/.git/annex/journal.lck\0\", 0x601, 0x1B6) = 8 0 +65332/0x53591a: fcntl(0x8, 0x9, 0x107009D60) = -1 Err#-1 +</pre> + +waitToSetLock thinks fcntl is failing to lock the file due to something else having it locked, and retries, leading to the hang. + +I'm told on irc that this was installed using the prebuilt image, and that a previous version of it didn't have the problem. +"""]] diff --git a/doc/bugs/git-annex_merge_stalls/comment_2_f3b6bf180466b5931bfd20b2f0229422._comment b/doc/bugs/git-annex_merge_stalls/comment_2_f3b6bf180466b5931bfd20b2f0229422._comment new file mode 100644 index 000000000..2fe9b8ac0 --- /dev/null +++ b/doc/bugs/git-annex_merge_stalls/comment_2_f3b6bf180466b5931bfd20b2f0229422._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl8B4Ima-VCCJ4y32Gvfii8EmvTyN9tFGM" + nickname="Glendon" + subject="comment 2" + date="2013-09-09T15:54:59Z" + content=""" +With latest 20130909 version, the following log from git-annex merge: + +https://www.dropbox.com/s/3hklzfsflpxuk5s/annex-merge.log.1 +"""]] diff --git a/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment new file mode 100644 index 000000000..600044354 --- /dev/null +++ b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 3" + date="2013-09-09T19:35:25Z" + content=""" +This problem cleared up after a reboot (and a crash, apparently). + +<pre> +joeyh so, my thought is that perhaps you had a git-annex process before that was holding the lock. +joeyh for example, if you ran it and ctrl-z'd at just the right time, it could be suspended and holding the lock +joeyh (or the kernel coud have gotten confused, which given you also had a crash, who knows..) +dp sounds logical +joeyh forcing locks is always a problimatic thing +joeyh but git-annex could certianly notice if it seems to be stalled and print some useful messages +joeyh and maybe have a way to run with locks forced +</pre> +"""]] diff --git a/doc/bugs/git-annex_opens_too_many_files.mdwn b/doc/bugs/git-annex_opens_too_many_files.mdwn new file mode 100644 index 000000000..d5830be57 --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files.mdwn @@ -0,0 +1,40 @@ +[[!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. +"""]] 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 new file mode 100644 index 000000000..de5dde9b5 --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_1_37f6f5838c41c533df4be1f927b9b03d._comment @@ -0,0 +1,26 @@ +[[!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 new file mode 100644 index 000000000..381d425fc --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_2_347ef233b9845b84d7c4d49ed166e797._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..fbd3bce8f --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_3_d5f644d97cd2db471deb5dcd728cae60._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..b4c458706 --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_4_c03bde64be8fdd962826bc7afa07d2a9._comment @@ -0,0 +1,137 @@ +[[!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 new file mode 100644 index 000000000..786672eb2 --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_5_33a2e783e5355e981497b9861997570b._comment @@ -0,0 +1,18 @@ +[[!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 new file mode 100644 index 000000000..60c268fc0 --- /dev/null +++ b/doc/bugs/git-annex_opens_too_many_files/comment_6_b3a5a4e4ca29c5cd2840bfeb4c63ea68._comment @@ -0,0 +1,15 @@ +[[!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_quit_unexpectedly___40__macosx__41__.mdwn b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn new file mode 100644 index 000000000..a682c12cc --- /dev/null +++ b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__.mdwn @@ -0,0 +1,358 @@ +### Please describe the problem. + +I installed the git-annex app for MacOSX (10.8.4) + +### What steps will reproduce the problem? + +- Created a repository +- In the configuration, entered my google username/password + +### What version of git-annex are you using? On what operating system? + +bundle version: 0.0.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 + +Process: git-annex [12934] +Path: /Applications/git-annex.app/Contents/MacOS/bundle/git-annex +Identifier: git-annex +Version: 0 +Code Type: X86-64 (Native) +Parent Process: ??? [1] +User ID: 502 + +Date/Time: 2013-08-17 12:27:12.495 -0700 +OS Version: Mac OS X 10.8.4 (12E55) +Report Version: 10 +Sleep/Wake UUID: 6DB42174-0147-4C8B-B83E-F305823297CA + +Interval Since Last Report: 294009 sec +Crashes Since Last Report: 4 +Per-App Crashes Since Last Report: 4 +Anonymous UUID: 0D492F72-DAE5-360C-A6D6-ECB38FD53115 + +Crashed Thread: 3 + +Exception Type: EXC_BAD_ACCESS (SIGSEGV) +Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 + +VM Regions Near 0: +--> + __TEXT 000000010b5e6000-000000010e08d000 [ 42.7M] r-x/rwx SM=COW /Applications/git-annex.app/Contents/MacOS/bundle/git-annex + +Thread 0:: Dispatch queue: com.apple.main-thread +0 libsystem_kernel.dylib 0x00007fff931400fa __psynch_cvwait + 10 +1 libsystem_c.dylib 0x00007fff86adffe9 _pthread_cond_wait + 869 +2 git-annex 0x000000010df20179 0x10b5e6000 + 43229561 +3 git-annex 0x000000010defc8eb 0x10b5e6000 + 43084011 +4 git-annex 0x000000010df0bc86 0x10b5e6000 + 43146374 +5 git-annex 0x000000010df0c6fb 0x10b5e6000 + 43149051 +6 git-annex 0x000000010df07b46 0x10b5e6000 + 43129670 +7 git-annex 0x000000010df07c69 0x10b5e6000 + 43129961 +8 git-annex 0x000000010bcff518 0x10b5e6000 + 7443736 +9 libdyld.dylib 0x00007fff8c3e47e1 start + 1 + +Thread 1: +0 libsystem_kernel.dylib 0x00007fff931400fa __psynch_cvwait + 10 +1 libsystem_c.dylib 0x00007fff86adffe9 _pthread_cond_wait + 869 +2 git-annex 0x000000010df20179 0x10b5e6000 + 43229561 +3 git-annex 0x000000010defc8eb 0x10b5e6000 + 43084011 +4 git-annex 0x000000010df0bc86 0x10b5e6000 + 43146374 +5 git-annex 0x000000010df0c5e0 0x10b5e6000 + 43148768 +6 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +7 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 2: +0 libsystem_kernel.dylib 0x00007fff931400fa __psynch_cvwait + 10 +1 libsystem_c.dylib 0x00007fff86adffe9 _pthread_cond_wait + 869 +2 git-annex 0x000000010df20179 0x10b5e6000 + 43229561 +3 git-annex 0x000000010defc8eb 0x10b5e6000 + 43084011 +4 git-annex 0x000000010df0bc86 0x10b5e6000 + 43146374 +5 git-annex 0x000000010df0c5e0 0x10b5e6000 + 43148768 +6 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +7 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 3 Crashed: +0 libsystem_c.dylib 0x00007fff86ae0bf9 pthread_mutex_lock + 20 +1 H 0x000000010e9fd29f gnutls_system_mutex_lock + 12 +2 H 0x000000010ea7fa29 wrap_nettle_rnd_refresh + 20 +3 H 0x000000010e9fee89 gnutls_deinit + 42 +4 git-annex 0x000000010caf0a3a 0x10b5e6000 + 22063674 + +Thread 4: +0 libsystem_kernel.dylib 0x00007fff93140d2a kevent64 + 10 +1 git-annex 0x000000010deab5fa 0x10b5e6000 + 42751482 + +Thread 5: +0 libsystem_kernel.dylib 0x00007fff931400fa __psynch_cvwait + 10 +1 libsystem_c.dylib 0x00007fff86adffe9 _pthread_cond_wait + 869 +2 git-annex 0x000000010df20179 0x10b5e6000 + 43229561 +3 git-annex 0x000000010defc8eb 0x10b5e6000 + 43084011 +4 git-annex 0x000000010df0bc86 0x10b5e6000 + 43146374 +5 git-annex 0x000000010df0c5e0 0x10b5e6000 + 43148768 +6 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +7 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 6:: Dispatch queue: com.apple.libdispatch-manager +0 libsystem_kernel.dylib 0x00007fff93140d16 kevent + 10 +1 libdispatch.dylib 0x00007fff8e6fedea _dispatch_mgr_invoke + 883 +2 libdispatch.dylib 0x00007fff8e6fe9ee _dispatch_mgr_thread + 54 + +Thread 7: +0 libsystem_kernel.dylib 0x00007fff9313e686 mach_msg_trap + 10 +1 libsystem_kernel.dylib 0x00007fff9313dc42 mach_msg + 70 +2 com.apple.CoreFoundation 0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195 +3 com.apple.CoreFoundation 0x00007fff8c1e7916 __CFRunLoopRun + 1078 +4 com.apple.CoreFoundation 0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290 +5 com.apple.CoreFoundation 0x00007fff8c1f5dd1 CFRunLoopRun + 97 +6 git-annex 0x000000010c72b3ec 0x10b5e6000 + 18109420 +7 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +8 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 8: +0 libsystem_kernel.dylib 0x00007fff9313e686 mach_msg_trap + 10 +1 libsystem_kernel.dylib 0x00007fff9313dc42 mach_msg + 70 +2 com.apple.CoreFoundation 0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195 +3 com.apple.CoreFoundation 0x00007fff8c1e7916 __CFRunLoopRun + 1078 +4 com.apple.CoreFoundation 0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290 +5 com.apple.CoreFoundation 0x00007fff8c1f5dd1 CFRunLoopRun + 97 +6 git-annex 0x000000010c72b3ec 0x10b5e6000 + 18109420 +7 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +8 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 9: +0 libsystem_kernel.dylib 0x00007fff9313e686 mach_msg_trap + 10 +1 libsystem_kernel.dylib 0x00007fff9313dc42 mach_msg + 70 +2 com.apple.CoreFoundation 0x00007fff8c1e2233 __CFRunLoopServiceMachPort + 195 +3 com.apple.CoreFoundation 0x00007fff8c1e7916 __CFRunLoopRun + 1078 +4 com.apple.CoreFoundation 0x00007fff8c1e70e2 CFRunLoopRunSpecific + 290 +5 com.apple.CoreFoundation 0x00007fff8c1f5dd1 CFRunLoopRun + 97 +6 git-annex 0x000000010c72b3ec 0x10b5e6000 + 18109420 +7 libsystem_c.dylib 0x00007fff86adb7a2 _pthread_start + 327 +8 libsystem_c.dylib 0x00007fff86ac81e1 thread_start + 13 + +Thread 3 crashed with X86 Thread State (64-bit): + rax: 0x000000010eaaca28 rbx: 0x00007f9dc38000c0 rcx: 0x000000010f87ce00 rdx: 0x000000010e3c28f0 + rdi: 0x0000000000000000 rsi: 0x001c4500001c4500 rbp: 0x000000010f87ce10 rsp: 0x000000010f87cdd0 + r8: 0x0000000000002060 r9: 0x000000010f87ce00 r10: 0x000000010eabf328 r11: 0x000000010e9fee5f + r12: 0x000000010f5585d8 r13: 0x000000010e3c2798 r14: 0x0000000000000000 r15: 0x000000010f548140 + rip: 0x00007fff86ae0bf9 rfl: 0x0000000000010202 cr2: 0x0000000000000000 +Logical CPU: 0 + +Binary Images: + 0x10b5e6000 - 0x10e08cff7 +git-annex (0) <2C4C13B3-4830-322A-A144-9E51B386EB1E> /Applications/git-annex.app/Contents/MacOS/bundle/git-annex + 0x10e85a000 - 0x10e957ff7 +E (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /Applications/git-annex.app/Contents/MacOS/bundle/E + 0x10e990000 - 0x10e9a4fff +F (0) <FA90B1B1-A866-3A6C-BB97-06955F4C8C0B> /Applications/git-annex.app/Contents/MacOS/bundle/F + 0x10e9ab000 - 0x10e9d8ff7 +G (0) <D80652C0-9A55-351C-8EAF-2364359BA0A2> /Applications/git-annex.app/Contents/MacOS/bundle/G + 0x10e9de000 - 0x10eaabfdf +H (0) <29C3AFF5-8EFB-3A16-81F6-0DA6CF2675A6> /Applications/git-annex.app/Contents/MacOS/bundle/H + 0x10eadd000 - 0x10eaefff7 +B (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /Applications/git-annex.app/Contents/MacOS/bundle/B + 0x10eaf7000 - 0x10ebecfff +D (34) <FEE8B996-EB44-37FA-B96E-D379664DEFE1> /Applications/git-annex.app/Contents/MacOS/bundle/D + 0x10ec01000 - 0x10ed1992f +I (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /Applications/git-annex.app/Contents/MacOS/bundle/I + 0x10ed3d000 - 0x10ef3dfff +S (491.11.3) <5783D305-04E8-3D17-94F7-1CEAFA975240> /Applications/git-annex.app/Contents/MacOS/bundle/S + 0x10f048000 - 0x10f06dff7 +Z (26) <D86169F3-9F31-377A-9AF3-DB17142052E4> /Applications/git-annex.app/Contents/MacOS/bundle/Z + 0x10f0a1000 - 0x10f109ff7 +0A (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /Applications/git-annex.app/Contents/MacOS/bundle/0A + 0x10f163000 - 0x10f1ccfff +0B (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /Applications/git-annex.app/Contents/MacOS/bundle/0B + 0x10f235000 - 0x10f248fff +T (0) <C8970714-4C86-3BE6-94D6-4835DCC8A003> /Applications/git-annex.app/Contents/MacOS/bundle/T + 0x10f257000 - 0x10f264ff7 +U (0) <DCFF385A-090B-3407-868C-91544A2EFEE1> /Applications/git-annex.app/Contents/MacOS/bundle/U + 0x10f26f000 - 0x10f291ff7 +V (0) <51B317C7-94CC-3C58-B515-924BB3AF0BCC> /Applications/git-annex.app/Contents/MacOS/bundle/V + 0x10f29b000 - 0x10f2a8ff7 +W (0) <91CF16BE-027F-3FE6-B1EE-6B8BFD51FC1B> /Applications/git-annex.app/Contents/MacOS/bundle/W + 0x10f2b4000 - 0x10f310fd7 +X (0) <84D934AF-A321-36C0-BBCF-CD3FDAEB0B95> /Applications/git-annex.app/Contents/MacOS/bundle/X + 0x7fff6b1e6000 - 0x7fff6b21a93f dyld (210.2.3) <36CAA36E-72BC-3E48-96D9-B96A2DF77730> /usr/lib/dyld + 0x7fff8652a000 - 0x7fff865d0ff7 com.apple.CoreServices.OSServices (557.6 - 557.6) <FFDDD2D8-690D-388F-A48F-4750A792D2CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices + 0x7fff865d1000 - 0x7fff865e8fff libGL.dylib (8.9.2) <B8E5948D-BCF2-3727-B74E-D74B8EDC82D6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib + 0x7fff865e9000 - 0x7fff86610fff com.apple.framework.familycontrols (4.1 - 410) <50F5A52C-8FB6-300A-977D-5CFDE4D5796B> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls + 0x7fff86611000 - 0x7fff8663cfff libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib + 0x7fff86649000 - 0x7fff86698ff7 libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib + 0x7fff8669d000 - 0x7fff866a3fff com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration + 0x7fff866a4000 - 0x7fff86ac1fff FaceCoreLight (2.4.1) <DDAFFD7A-D312-3407-A010-5AEF3E17831B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLight + 0x7fff86ac7000 - 0x7fff86b93ff7 libsystem_c.dylib (825.26) <4C9EB006-FE1F-3F8F-8074-DFD94CF2CE7B> /usr/lib/system/libsystem_c.dylib + 0x7fff86d50000 - 0x7fff86da1ff7 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <581BF463-C15A-363B-999A-E830222FA925> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration + 0x7fff86dee000 - 0x7fff86deefff com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <B5A18EE8-DF81-38DD-ACAF-7076B2A26225> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib + 0x7fff86def000 - 0x7fff86df4fff com.apple.OpenDirectory (10.8 - 151.10) <CF44120B-9B01-32DD-852E-C9C0E1243FC0> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory + 0x7fff86df5000 - 0x7fff86df6fff libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib + 0x7fff86e0a000 - 0x7fff87201fff libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib + 0x7fff87622000 - 0x7fff87650ff7 libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib + 0x7fff8766c000 - 0x7fff8769dff7 com.apple.DictionaryServices (1.2 - 184.4) <FB0540FF-5034-3591-A28D-6887FBC220F7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices + 0x7fff8769e000 - 0x7fff8769efff libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib + 0x7fff87732000 - 0x7fff87754ff7 libxpc.dylib (140.43) <70BC645B-6952-3264-930C-C835010CCEF9> /usr/lib/system/libxpc.dylib + 0x7fff87755000 - 0x7fff877d7ff7 com.apple.Heimdal (3.0 - 2.0) <C94B0C6C-1320-35A1-8143-FE252E7B2A08> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal + 0x7fff877d8000 - 0x7fff87859fff com.apple.Metadata (10.7.0 - 707.11) <2DD25313-420D-351A-90F1-300E95C970CA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata + 0x7fff87cbf000 - 0x7fff87d19fff com.apple.print.framework.PrintCore (8.3 - 387.2) <5BA0CBED-4D80-386A-9646-F835C9805B71> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore + 0x7fff87e27000 - 0x7fff87e34ff7 com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth + 0x7fff87f54000 - 0x7fff87f68fff com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <94EDF2AB-809C-3D15-BED5-7AD45B2A7C16> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis + 0x7fff87f77000 - 0x7fff87f7dff7 libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib + 0x7fff87fab000 - 0x7fff87fabfff com.apple.Accelerate (1.8 - Accelerate 1.8) <6AD48543-0864-3D40-80CE-01F184F24B45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate + 0x7fff88161000 - 0x7fff88162ff7 libSystem.B.dylib (169.3) <9089D72D-E714-31E1-80C8-698A8E8B05AD> /usr/lib/libSystem.B.dylib + 0x7fff88167000 - 0x7fff88205ff7 com.apple.ink.framework (10.8.2 - 150) <3D8D16A2-7E01-3EA1-B637-83A36D353308> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink + 0x7fff88222000 - 0x7fff88223ff7 libsystem_sandbox.dylib (220.3) <B739DA63-B675-387A-AD84-412A651143C0> /usr/lib/system/libsystem_sandbox.dylib + 0x7fff88224000 - 0x7fff88228ff7 com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC + 0x7fff88229000 - 0x7fff88230fff libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib + 0x7fff88a6e000 - 0x7fff88a8dff7 libresolv.9.dylib (51) <0882DC2D-A892-31FF-AD8C-0BB518C48B23> /usr/lib/libresolv.9.dylib + 0x7fff88a8e000 - 0x7fff88aa1ff7 libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib + 0x7fff88bbd000 - 0x7fff88bbdfff com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices + 0x7fff88bce000 - 0x7fff88bf6fff libJPEG.dylib (850) <DC750E1E-BD07-339B-A4A6-D86BFE969F68> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib + 0x7fff88bf7000 - 0x7fff88bf9fff libquarantine.dylib (52.1) <143B726E-DF47-37A8-90AA-F059CFD1A2E4> /usr/lib/system/libquarantine.dylib + 0x7fff88fe0000 - 0x7fff8933ffff com.apple.Foundation (6.8 - 945.18) <1D7E58E6-FA3A-3CE8-AC85-B9D06B8C0AA0> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation + 0x7fff89340000 - 0x7fff89575ff7 com.apple.CoreData (106.1 - 407.7) <A676E1A4-2144-376B-92B8-B450DD1D78E5> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData + 0x7fff89576000 - 0x7fff8957dfff libGFXShared.dylib (8.9.2) <398F8D57-EC82-3E13-AC8E-470BE19237D7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib + 0x7fff895d4000 - 0x7fff8a201fff com.apple.AppKit (6.8 - 1187.39) <199962F0-B06B-3666-8FD5-5C90374BA16A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit + 0x7fff8a202000 - 0x7fff8a519ff7 com.apple.CoreServices.CarbonCore (1037.6 - 1037.6) <1E567A52-677F-3168-979F-5FBB0818D52B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore + 0x7fff8a5e0000 - 0x7fff8a5e7fff com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS + 0x7fff8a5e8000 - 0x7fff8a63fff7 com.apple.ScalableUserInterface (1.0 - 1) <F1D43DFB-1796-361B-AD4B-39F1EED3BE19> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface + 0x7fff8a71b000 - 0x7fff8a767ff7 libauto.dylib (185.4) <AD5A4CE7-CB53-313C-9FAE-673303CC2D35> /usr/lib/libauto.dylib + 0x7fff8a768000 - 0x7fff8a768fff libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib + 0x7fff8a7e7000 - 0x7fff8a808ff7 libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib + 0x7fff8a809000 - 0x7fff8a815fff com.apple.CrashReporterSupport (10.8.3 - 418) <DE6AFE16-D97E-399D-82ED-3522C773C36E> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport + 0x7fff8a816000 - 0x7fff8b1a64af com.apple.CoreGraphics (1.600.0 - 332) <5AB32E51-9154-3733-B83B-A9A748652847> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics + 0x7fff8b1a7000 - 0x7fff8b1befff com.apple.CFOpenDirectory (10.8 - 151.10) <10F41DA4-AD54-3F52-B898-588D9A117171> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory + 0x7fff8b242000 - 0x7fff8b285ff7 com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom + 0x7fff8b286000 - 0x7fff8b2c3fef libGLImage.dylib (8.9.2) <C38649ED-E1C9-315E-9953-F33E8C6A3C89> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib + 0x7fff8b2c4000 - 0x7fff8b303ff7 com.apple.QD (3.42.1 - 285.1) <77A20C25-EBB5-341C-A05C-5D458B97AD5C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD + 0x7fff8b304000 - 0x7fff8b39efff libvMisc.dylib (380.6) <714336EA-1C0E-3735-B31C-19DFDAAF6221> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib + 0x7fff8b3b8000 - 0x7fff8b566fff com.apple.QuartzCore (1.8 - 304.3) <F450F2DE-2F24-3557-98B6-310E05DAC17F> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore + 0x7fff8ba39000 - 0x7fff8ba4cff7 com.apple.LangAnalysis (1.7.0 - 1.7.0) <2F2694E9-A7BC-33C7-B4CF-8EC907DF0FEB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis + 0x7fff8bd12000 - 0x7fff8bd1cfff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <D803919C-3102-3515-A178-61E9C86C46A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition + 0x7fff8c0d6000 - 0x7fff8c0d7ff7 libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib + 0x7fff8c179000 - 0x7fff8c17efff libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib + 0x7fff8c1b2000 - 0x7fff8c39cff7 com.apple.CoreFoundation (6.8 - 744.19) <0F7403CA-2CB8-3D0A-992B-679701DF27CA> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation + 0x7fff8c39d000 - 0x7fff8c3c4ff7 com.apple.PerformanceAnalysis (1.16 - 16) <E4888388-F41B-313E-9CBB-5807D077BDA9> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis + 0x7fff8c3e2000 - 0x7fff8c3e5ff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib + 0x7fff8c3e6000 - 0x7fff8c3e8fff libCVMSPluginSupport.dylib (8.9.2) <EF1192AC-3357-3A0B-BFAF-6594D7737892> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib + 0x7fff8c3e9000 - 0x7fff8c484fff com.apple.CoreSymbolication (3.0 - 117) <50716F74-41C2-3BB9-AC16-12C4D4C2DD1E> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication + 0x7fff8c75b000 - 0x7fff8c75bfff com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices + 0x7fff8cf1f000 - 0x7fff8d094ff7 com.apple.CFNetwork (596.4.3 - 596.4.3) <A57B3308-2F08-3EC3-B4AC-39A3D9F0B9F7> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork + 0x7fff8d0ae000 - 0x7fff8d0e4fff libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib + 0x7fff8d0e5000 - 0x7fff8d148ff7 com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <9ACD3AED-6C04-3BBB-AB2A-FC253B16D093> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio + 0x7fff8d156000 - 0x7fff8d16cfff com.apple.MultitouchSupport.framework (235.29 - 235.29) <617EC8F1-BCE7-3553-86DD-F857866E1257> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport + 0x7fff8d16d000 - 0x7fff8d171fff libGIF.dylib (850) <D4525F87-759C-338C-B283-BB8DE815D3D5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib + 0x7fff8d264000 - 0x7fff8d2aeff7 libGLU.dylib (8.9.2) <1B5511FF-1064-3004-A245-972CE5687D37> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib + 0x7fff8d2b2000 - 0x7fff8d2dcff7 com.apple.CoreVideo (1.8 - 99.4) <E5082966-6D81-3973-A05A-38AA5B85F886> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo + 0x7fff8d58d000 - 0x7fff8d591fff com.apple.IOSurface (86.0.4 - 86.0.4) <26F01CD4-B76B-37A3-989D-66E8140542B3> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface + 0x7fff8d6de000 - 0x7fff8d78ffff com.apple.LaunchServices (539.9 - 539.9) <07FC6766-778E-3479-8F28-D2C9917E1DD1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices + 0x7fff8d7bf000 - 0x7fff8d80eff7 libFontRegistry.dylib (100) <2E03D7DA-9B8F-31BB-8FB5-3D3B6272127F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib + 0x7fff8d80f000 - 0x7fff8d88fff7 com.apple.ApplicationServices.ATS (332 - 341.1) <39B53565-FA31-3F61-B090-C787C983142E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS + 0x7fff8d94e000 - 0x7fff8d95bfff com.apple.AppleFSCompression (49 - 1.0) <5508344A-2A7E-3122-9562-6F363910A80E> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression + 0x7fff8d95c000 - 0x7fff8d99fff7 com.apple.RemoteViewServices (2.0 - 80.6) <5CFA361D-4853-3ACC-9EFC-A2AC1F43BA4B> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices + 0x7fff8dac2000 - 0x7fff8dac8fff libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib + 0x7fff8dac9000 - 0x7fff8db03ff7 com.apple.GSS (3.0 - 2.0) <970CAE00-1437-3F4E-B677-0FDB3714C08C> /System/Library/Frameworks/GSS.framework/Versions/A/GSS + 0x7fff8db09000 - 0x7fff8db12ff7 com.apple.CommerceCore (1.0 - 26.1) <40A129A8-4E5D-3C7A-B299-8CB203C4C65D> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore + 0x7fff8db13000 - 0x7fff8db15fff com.apple.TrustEvaluationAgent (2.0 - 23) <A97D348B-32BF-3E52-8DF2-59BFAD21E1A3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent + 0x7fff8de6c000 - 0x7fff8de6eff7 libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib + 0x7fff8de6f000 - 0x7fff8de8eff7 com.apple.ChunkingLibrary (2.0 - 133.3) <8BEC9AFB-DCAA-37E8-A5AB-24422B234ECF> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary + 0x7fff8de8f000 - 0x7fff8deeefff com.apple.AE (645.6 - 645.6) <44F403C1-660A-3543-AB9C-3902E02F936F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE + 0x7fff8deef000 - 0x7fff8dfecfff libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib + 0x7fff8e06b000 - 0x7fff8e076ff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement + 0x7fff8e077000 - 0x7fff8e086fff com.apple.opengl (1.8.9 - 1.8.9) <6FD163A7-16CC-3D1F-B4B5-B0FDC4ADBF79> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL + 0x7fff8e087000 - 0x7fff8e092fff com.apple.CommonAuth (3.0 - 2.0) <7A953C1F-8B18-3E46-9BEA-26D9B5B7745D> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth + 0x7fff8e093000 - 0x7fff8e093fff com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa + 0x7fff8e1f3000 - 0x7fff8e1f4fff libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib + 0x7fff8e23c000 - 0x7fff8e23cffd com.apple.audio.units.AudioUnit (1.9 - 1.9) <EC55FB59-2443-3F08-9142-7BCC93C76E4E> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit + 0x7fff8e23d000 - 0x7fff8e30fff7 com.apple.CoreText (260.0 - 275.16) <5BFC1D67-6A6F-38BC-9D90-9C712684EDAC> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText + 0x7fff8e310000 - 0x7fff8e31eff7 libkxld.dylib (2050.24.15) <A619A9AC-09AF-3FF3-95BF-F07CC530EC31> /usr/lib/system/libkxld.dylib + 0x7fff8e31f000 - 0x7fff8e38dff7 com.apple.framework.IOKit (2.0.1 - 755.24.1) <04BFB138-8AF4-310A-8E8C-045D8A239654> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit + 0x7fff8e39f000 - 0x7fff8e525fff libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib + 0x7fff8e553000 - 0x7fff8e597fff libcups.2.dylib (327.6) <9C01D012-6F4C-3B69-B614-1B408B0ED4E3> /usr/lib/libcups.2.dylib + 0x7fff8e598000 - 0x7fff8e5a6fff libcommonCrypto.dylib (60027) <BAAFE0C9-BB86-3CA7-88C0-E3CBA98DA06F> /usr/lib/system/libcommonCrypto.dylib + 0x7fff8e6fa000 - 0x7fff8e70fff7 libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib + 0x7fff8e710000 - 0x7fff8e71eff7 libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib + 0x7fff8e71f000 - 0x7fff8e741ff7 com.apple.Kerberos (2.0 - 1) <C49B8820-34ED-39D7-A407-A3E854153556> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos + 0x7fff8e788000 - 0x7fff8e797ff7 libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib + 0x7fff8f144000 - 0x7fff8f1d1ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit + 0x7fff8f24c000 - 0x7fff8f24ffff libRadiance.dylib (850) <62E3F7FB-03E3-3937-A857-AF57A75EAF09> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib + 0x7fff8f533000 - 0x7fff8f7d7ff7 com.apple.CoreImage (8.4.0 - 1.0.1) <CC6DD22B-FFC6-310B-BE13-2397A02C79EF> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage + 0x7fff8f7d8000 - 0x7fff8f840fff libvDSP.dylib (380.6) <CD4C5EEB-9E63-30C4-8103-7A5EAEA0BE60> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib + 0x7fff8f8ab000 - 0x7fff8f8affff libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib + 0x7fff8fabb000 - 0x7fff8fb28ff7 com.apple.datadetectorscore (4.1 - 269.3) <5775F0DB-87D6-310D-8B03-E2AD729EFB28> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore + 0x7fff8fc60000 - 0x7fff8fcbcff7 com.apple.Symbolication (1.3 - 93) <97F3B1D2-D81D-3F37-87B3-B9A686124CF5> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication + 0x7fff8fd91000 - 0x7fff8fe6bfff com.apple.backup.framework (1.4.3 - 1.4.3) <6B65C44C-7777-3331-AD9D-438D10AAC777> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup + 0x7fff8fe6c000 - 0x7fff8fe79fff libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib + 0x7fff8fe89000 - 0x7fff8ffdbfff com.apple.audio.toolbox.AudioToolbox (1.9 - 1.9) <62770C0F-5600-3EF9-A893-8A234663FFF5> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox + 0x7fff90071000 - 0x7fff90173fff libJP2.dylib (850) <2E43216C-3A5A-3693-820C-38B360698FA0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib + 0x7fff90ab4000 - 0x7fff90b79ff7 com.apple.coreui (2.0 - 181.1) <83D2C92D-6842-3C9D-9289-39D5B4554C3A> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI + 0x7fff90e1a000 - 0x7fff90e1bfff liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib + 0x7fff90f20000 - 0x7fff90fddff7 com.apple.ColorSync (4.8.0 - 4.8.0) <6CE333AE-EDDB-3768-9598-9DB38041DC55> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync + 0x7fff90fde000 - 0x7fff9105dff7 com.apple.securityfoundation (6.0 - 55115.4) <8676E0DF-295F-3690-BDAA-6C9C1D210B88> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation + 0x7fff9105e000 - 0x7fff910b4fff com.apple.HIServices (1.20 - 417) <BCD36950-013F-35C2-918E-05A93A47BE8C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices + 0x7fff910b5000 - 0x7fff910d6fff com.apple.Ubiquity (1.2 - 243.15) <C9A7EE77-B637-3676-B667-C0843BBB0409> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity + 0x7fff910de000 - 0x7fff91133ff7 libTIFF.dylib (850) <EDAF0D99-70AF-3B3F-9EFA-9463C91D0E3C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib + 0x7fff9125c000 - 0x7fff9127cfff libPng.dylib (850) <203C43BF-FAD3-3CCB-81D5-F2770E36338B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib + 0x7fff9127f000 - 0x7fff91398fff com.apple.ImageIO.framework (3.2.1 - 850) <C3FFCEEB-AA0C-314B-9E94-7005EE48A403> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO + 0x7fff9139f000 - 0x7fff913b6fff com.apple.GenerationalStorage (1.1 - 132.3) <FD4A84B3-13A8-3C60-A59E-25A361447A17> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage + 0x7fff91582000 - 0x7fff91586fff libCoreVMClient.dylib (32.3) <AD8391D9-56DD-3A78-A294-6A30E6ECE1A2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib + 0x7fff91587000 - 0x7fff915bdfff com.apple.DebugSymbols (98 - 98) <14E788B1-4EB2-3FD7-934B-849534DFC198> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols + 0x7fff915cd000 - 0x7fff915d5fff liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib + 0x7fff915d6000 - 0x7fff915e1fff libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib + 0x7fff91650000 - 0x7fff917ebfef com.apple.vImage (6.0 - 6.0) <FAE13169-295A-33A5-8E6B-7C2CC1407FA7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage + 0x7fff917ec000 - 0x7fff917f4ff7 libsystem_dnssd.dylib (379.38.1) <BDCB8566-0189-34C0-9634-35ABD3EFE25B> /usr/lib/system/libsystem_dnssd.dylib + 0x7fff9182d000 - 0x7fff91938fff libFontParser.dylib (84.6) <96C42E49-79A6-3475-B5E4-6A782599A6DA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib + 0x7fff919d8000 - 0x7fff919ddfff libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib + 0x7fff919de000 - 0x7fff919defff com.apple.vecLib (3.8 - vecLib 3.8) <794317C7-4E38-338A-A874-5E18001C8503> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib + 0x7fff919df000 - 0x7fff91cb0ff7 com.apple.security (7.0 - 55179.13) <F428E306-C407-3B55-BA82-E58755E8A76F> /System/Library/Frameworks/Security.framework/Versions/A/Security + 0x7fff91d3f000 - 0x7fff9206ffff com.apple.HIToolbox (2.0 - 626.1) <656D08C2-9068-3532-ABDD-32EC5057CCB2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox + 0x7fff92084000 - 0x7fff920deff7 com.apple.opencl (2.2.19 - 2.2.19) <3C7DFB2C-B3F9-3447-A1FC-EAAA42181A6E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL + 0x7fff9216c000 - 0x7fff9216dff7 libremovefile.dylib (23.2) <6763BC8E-18B8-3AD9-8FFA-B43713A7264F> /usr/lib/system/libremovefile.dylib + 0x7fff9312e000 - 0x7fff93149ff7 libsystem_kernel.dylib (2050.24.15) <A9F97289-7985-31D6-AF89-151830684461> /usr/lib/system/libsystem_kernel.dylib + 0x7fff9314d000 - 0x7fff9326dfff com.apple.desktopservices (1.7.4 - 1.7.4) <ED3DA8C0-160F-3CDC-B537-BF2E766AB7C1> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv + +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: 168404 + thread_create: 1 + thread_set_state: 0 + +VM Region Summary: +ReadOnly portion of Libraries: Total=109.3M resident=31.8M(29%) swapped_out_or_unallocated=77.5M(71%) +Writable regions: Total=90.9M written=16.1M(18%) resident=17.5M(19%) swapped_out=0K(0%) unallocated=73.4M(81%) + +REGION TYPE VIRTUAL +=========== ======= +MALLOC 62.5M +MALLOC guard page 48K +STACK GUARD 56.0M +Stack 12.6M +VM_ALLOCATE 12.0M +__DATA 13.8M +__IMAGE 528K +__LINKEDIT 58.6M +__TEXT 134.3M +__UNICODE 544K +shared memory 308K +=========== ======= +TOTAL 351.2M + +Model: MacBookPro10,1, BootROM MBP101.00EE.B03, 4 processors, Intel Core i7, 2.8 GHz, 16 GB, SMC 2.3f35 +Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB +Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB +Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 +Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 +AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.17) +Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports +Network Service: Wi-Fi, AirPort, en0 +Serial ATA Device: APPLE SSD SM768E, 751.28 GB +USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2 +USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3 +USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc52b, 0x14200000 / 1 +USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2 +USB Device: hub_device, 0x0424 (SMSC), 0x2512, 0x1d180000 / 3 +USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 5 +USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4 +USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 6 + +# End of transcript or log. +"""]] + +> This got fixed in haskell gnutls 0.1.5. I have updated the Mtn Lion +> autobuilder and it will be in tonight's build. [[done]] +> --[[Joey]] diff --git a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment new file mode 100644 index 000000000..4dcc5412c --- /dev/null +++ b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_1_97abb8442329d19c9687002f43afac74._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 1" + date="2013-08-26T19:51:48Z" + content=""" +So this is a crash in the gnutls library used for XMPP. Someone else using OSX reported a similar crash to me by email, reproducible reliably by setting up xmpp with google. This is great debugging info: + +<pre> +Thread 3 Crashed: +0 libsystem_c.dylib 0x00007fff86ae0bf9 pthread_mutex_lock + 20 +1 H 0x000000010e9fd29f gnutls_system_mutex_lock + 12 +2 H 0x000000010ea7fa29 wrap_nettle_rnd_refresh + 20 +3 H 0x000000010e9fee89 gnutls_deinit + 42 +4 git-annex 0x000000010caf0a3a 0x10b5e6000 + 22063674 +</pre> + +Looks like `gnutls_deinit` was called and it crashed there, inside pthread code. So I think git-annex has already managed to connect to the XMPP server (to test it) and the cleanup is where it's crashing. + +This is the second time I have seen a gnutls-related crash using XMPP. The other one was tracked down by John Millikin to a resource allocation bug in haskell-gnutls and fixed. + +I have written a test case that reproduces the problem -- just forking a dozen threads that each try to connect to the google xmpp server and then close the connection. After a dozen or so succeed, one will reliably cause a segfault. Forwarded this test case to John. +"""]] diff --git a/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment new file mode 100644 index 000000000..18b2b7a52 --- /dev/null +++ b/doc/bugs/git-annex_quit_unexpectedly___40__macosx__41__/comment_2_3405f3cd699860ee239cf23ade19e92c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.7" + subject="comment 2" + date="2013-08-29T18:15:08Z" + content=""" +I now have a test case that shows that this can happen reliably on OSX if you enter the wrong XMPP password repeatedly. It might also happen if you just enter the wrong password once, with a server like google's, since the assistant will try falling back to different servers. John is aware of this haskell-gnutls problem. + +John also found, and we hope fixed (but it's hard to tell) a bug in haskell-gnutls that caused a crash maybe 1 time in 10 under some conditions on OSX, when the right password was entered. +"""]] 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 new file mode 100644 index 000000000..7a2690be2 --- /dev/null +++ b/doc/bugs/git-annex_sync_may_fail_when_the_directory_I__39__m_in_disepeared.mdwn @@ -0,0 +1,15 @@ +### 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_add_error_with_Andrew_File_System.mdwn b/doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn new file mode 100644 index 000000000..bdddd96e2 --- /dev/null +++ b/doc/bugs/git_annex_add_error_with_Andrew_File_System.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. +I have a git annex clone on Andrew File System. I obtain an error when I try +to add a file to the annex: + +git-annex: test: createLink: unsupported operation (Invalid cross-device link) + +### What steps will reproduce the problem? +Create a test file with touch and add it with git annex add. + +### What version of git-annex are you using? On what operating system? +git-annex 4.20130723 on Debian sid. + +### Please provide any additional information below. + +[[!format sh """ +gio@crack:~/nobackup/archive$ touch test +gio@crack:~/nobackup/archive$ git annex add test +add test +git-annex: test: createLink: unsupported operation (Invalid cross-device link) +failed +git-annex: add: 1 failed +gio@crack:~/nobackup/archive$ logout +"""]] + +It seems to me that AFS doesn't support hard links between different +directories. + +> [[done]] per comments --[[Joey]] diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment new file mode 100644 index 000000000..7a0d15842 --- /dev/null +++ b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_1_bc783e551fc0e8da87bc95bff5b8f73a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://launchpad.net/~giomasce" + nickname="giomasce" + subject="Reference" + date="2013-08-12T11:39:44Z" + content=""" +https://lists.openafs.org/pipermail/openafs-info/2007-December/028158.html +"""]] diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment new file mode 100644 index 000000000..a2301499c --- /dev/null +++ b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_2_faefcf69bd61c47566131cb31b78cc19._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 2" + date="2013-08-24T19:48:46Z" + content=""" +I'm confused by this bug report, because it seems to me I already fixed this same problem in commit a64106dcef5c5aad825662ef115cb2a1cc6985a8. There the problem was that encfs in paranoia mode doesn't support hard links. So I made it detect when createLink fails, and fall back to a code path that doesn't need hard links. + +Can you re-check the version you have, and perhaps try with a current daily build? +"""]] diff --git a/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment new file mode 100644 index 000000000..3d30cea41 --- /dev/null +++ b/doc/bugs/git_annex_add_error_with_Andrew_File_System/comment_3_d5014c8b78437b9fddbb1e83d3679081._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://launchpad.net/~giomasce" + nickname="giomasce" + subject="comment 3" + date="2013-09-07T15:35:48Z" + content=""" +Apparently I wrote a wrong version number. The version actually running on the system I tested is much older. Probably I wrote the one of my own laptop instead. + +The bug can be closed, sorry for the noise. +"""]] diff --git a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn b/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn index a8131df4d..f41a80616 100644 --- a/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn +++ b/doc/bugs/git_annex_copy_trying_to_connect_to_remotes_uninvolved.mdwn @@ -23,3 +23,5 @@ I'm running git-annex 4.20130627 as shipped with debian unstable. Jason P.S. 192.168.1.5 is set as the HostName for one of my other remotes in my ~/.ssh/config, so this isn't _totally_ out of the blue. + +> [[done]]; see comment's explanation. --[[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__.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 new file mode 100644 index 000000000..7e26f63df --- /dev/null +++ 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 @@ -0,0 +1,42 @@ +### 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. 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 new file mode 100644 index 000000000..3875affb7 --- /dev/null +++ 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 @@ -0,0 +1,15 @@ +[[!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 new file mode 100644 index 000000000..17191be04 --- /dev/null +++ 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 @@ -0,0 +1,8 @@ +[[!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_describe_can_break_uuid.log.mdwn b/doc/bugs/git_annex_describe_can_break_uuid.log.mdwn new file mode 100644 index 000000000..16e6981f5 --- /dev/null +++ b/doc/bugs/git_annex_describe_can_break_uuid.log.mdwn @@ -0,0 +1,46 @@ +### Please describe the problem. + +`uuid.log` can end up in a state where `git annex describe` (and probably other things) stops working. + +### What steps will reproduce the problem? + +Run `git annex describe` against a remote that is not a an initialized git-annex repo. + +### What version of git-annex are you using? On what operating system? + +debian-packaged git-annex 4.20131106 on Linux Mint 13/Maya (Ubuntu Precise/12.04) + +### Please provide any additional information below. + +I will follow comments, but can also be found at [[https://microca.st/clacke]]. + +Full transcript to reproduce: + +[[!format sh """ +$ git init a +Initialized empty Git repository in /tmp/annex/a/.git/ +$ git init b +Initialized empty Git repository in /tmp/annex/b/.git/ +$ cd a/ +$ git annex init +init ok +(Recording state in git...) +$ git remote add -f b ../b +Updating b +$ git annex describe b b # this should not be ok +describe b ok +(Recording state in git...) +$ git annex describe b b +describe b git-annex: Prelude.last: empty list +$ git cat-file blob git-annex:uuid.log + b timestamp=1383987654.900868s +... + +# End of transcript. +"""]] + +> Fixed the bug and made git breakage not crash git-annex. [[done]] +> --[[Joey]] + +> > Update: Also made it automatically clean up the cruft this put in the +> > log. --[[Joey]] diff --git a/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment b/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment new file mode 100644 index 000000000..a5616234e --- /dev/null +++ b/doc/bugs/git_annex_describe_can_break_uuid.log/comment_2_9ead36f13cbde6c822b231441de636ae._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://id.clacke.se/" + nickname="clacke" + subject="comment 2" + date="2013-11-11T05:32:14Z" + content=""" +Great, thanks! +"""]] 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 new file mode 100644 index 000000000..db4d3e269 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_10_141819a6b67de2602673698f6f148106._comment @@ -0,0 +1,13 @@ +[[!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 new file mode 100644 index 000000000..d166e8c67 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_11_8be96359fd2bd33ed2961e499dc2685e._comment @@ -0,0 +1,12 @@ +[[!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 new file mode 100644 index 000000000..b05d26c0b --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_12_26950a37e86d4dd83dd59fb2564d0a2e._comment @@ -0,0 +1,11 @@ +[[!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 new file mode 100644 index 000000000..94d962cd8 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_13_cbf8150dbe0da64bde7f6af8e041eda8._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..591123175 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_14_0c203f90d911cf6869894dae89575a49._comment @@ -0,0 +1,13 @@ +[[!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 new file mode 100644 index 000000000..07e76fcb8 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_15_68cbb7268bdad73357da2d11e05d73c4._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..96f379dcf --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_16_816d552f871a1b06306f04d575adb2e5._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..c67cc7add --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_17_7905b097a9c582452fb04cdc88ed4285._comment @@ -0,0 +1,14 @@ +[[!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 new file mode 100644 index 000000000..903a41364 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_18_bd5ac9bb2eaab66af6aa13b39172b49d._comment @@ -0,0 +1,9 @@ +[[!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 new file mode 100644 index 000000000..96356e047 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_19_9881db7bb6fef4e47c54cdc23e995f17._comment @@ -0,0 +1,13 @@ +[[!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_20_41e2ea458669f59f96b5860825745910._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_20_41e2ea458669f59f96b5860825745910._comment new file mode 100644 index 000000000..fca9ba58e --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_20_41e2ea458669f59f96b5860825745910._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..a0a175d30 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_21_515039e321e0595f95430d8082bd54a5._comment @@ -0,0 +1,20 @@ +[[!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_6_94144c0cbdbccc72c13e12daf7657a29._comment b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_6_94144c0cbdbccc72c13e12daf7657a29._comment new file mode 100644 index 000000000..fbb519bdd --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_6_94144c0cbdbccc72c13e12daf7657a29._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..db8e707cd --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_7_9eb064ffdc3fdb70e85572185e151a3f._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..708f21a79 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_8_cde756e8a9b18fe2ca9cda25967bc7fb._comment @@ -0,0 +1,10 @@ +[[!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 new file mode 100644 index 000000000..d70d0a872 --- /dev/null +++ b/doc/bugs/git_annex_doesn__39__t_work_in_Max_OS_X_10.9/comment_9_1fd6a4374a334bc03914c3e0df95ef95._comment @@ -0,0 +1,10 @@ +[[!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_import_destroys_a_fellow_git_annex_repository.mdwn b/doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn new file mode 100644 index 000000000..c8307ca6b --- /dev/null +++ b/doc/bugs/git_annex_import_destroys_a_fellow_git_annex_repository.mdwn @@ -0,0 +1,130 @@ +### Please describe the problem. + +`git annex import` not only [[does not work with git annex repositories|bugs/`git annex import` does not work on other git annex repositories]], it even destroys the meta-data in that repository, because it moves the `.git/*` metadata out of the remote repository. + +### What steps will reproduce the problem? + +[[!format txt """ +git init foo +cd foo +git annex init +dd if=/dev/urandom of=foo bs=1M count=1 +git annex add foo +git commit -m'files' +cd ../ +git init bar +cd bar +git annex init +mkdir foo +cd foo +git annex import ../../foo +cd ../../foo +git status +"""]] + + +### What version of git-annex are you using? On what operating system? + +[[!format txt """ +anarcat@angela:foo$ git annex version +git-annex version: 4.20130921-g434dc22 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi +"""]] + +### 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:~$ cd /tmp +anarcat@angela:/tmp$ mkdir test +anarcat@angela:/tmp$ cd test +anarcat@angela:test$ ls +anarcat@angela:test$ git init foo +Initialized empty Git repository in /tmp/test/foo/.git/ +anarcat@angela:test$ cd foo +anarcat@angela:foo$ git annex init +init ok +(Recording state in git...) +anarcat@angela:foo$ dd if=/dev/urandom of=foo bs=1M count=1 +1+0 enregistrements lus +1+0 enregistrements écrits +1048576 octets (1,0 MB) copiés, 0,410384 s, 2,6 MB/s +anarcat@angela:foo$ git annex add foo +add foo (checksum...) ok +(Recording state in git...) +anarcat@angela:foo$ git commit -m'files' +[master (root-commit) 83daa0b] files + 1 file changed, 1 insertion(+) + create mode 120000 foo +anarcat@angela:foo$ cd ../ +anarcat@angela:test$ git init bar +Initialized empty Git repository in /tmp/test/bar/.git/ +anarcat@angela:test$ cd bar +anarcat@angela:bar$ git annex init +init ok +(Recording state in git...) +anarcat@angela:bar$ mkdir foo +anarcat@angela:bar$ cd foo +anarcat@angela:foo$ git annex import ../../foo +import .git/COMMIT_EDITMSG (checksum...) ok +import .git/description (checksum...) ok +import .git/config (checksum...) ok +import .git/index (checksum...) ok +import .git/HEAD (checksum...) ok +import .git/annex/journal.lck (checksum...) ok +import .git/annex/index.lck (checksum...) ok +import .git/annex/sentinal (checksum...) ok +import .git/annex/sentinal.cache (checksum...) ok +import .git/annex/index (checksum...) ok +import .git/annex/objects/w2/Kz/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b +git-annex: ../../foo/.git/annex/objects/w2/Kz/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b/SHA256E-s1048576--f957108785c8dc30cf792948b89d61af257c40e5ef0e1d20ff6cf6aadaf6f66b: rename: permission denied (Permission denied) +failed +import .git/objects/0e/6881452189b7fc34809f101f075da7cca9d9d8 (checksum...) ok +import .git/objects/03/c0163611cd061af17b2dd58a93c95ffbb05040 (checksum...) ok +import .git/objects/39/10912eab082d015bface04ed3a8ed658b94893 (checksum...) ok +import .git/objects/21/05f6aaf523510f25516b04a0c07d5900df2b0b (checksum...) ok +import .git/objects/83/daa0b1d8290191f53d1d3b5e39e03653a89ce2 (checksum...) ok +import .git/objects/83/8fa78626a6cdc4399186172df9109d321ca0bf (checksum...) ok +import .git/objects/dc/1e1b7b811079e1c5826d44958b736fc3a3a458 (checksum...) ok +import .git/objects/7b/4d3d6a3ee2286b2da15c1aca39353d63c16fa2 (checksum...) ok +import .git/objects/86/2b2a09ebc7a1eb298dccc57be75bad897a7c10 (checksum...) ok +import .git/objects/e1/61ad2ad1843e39937caaf6add6f690fd361126 (checksum...) ok +import .git/objects/4b/825dc642cb6eb9a060e54bf8d69288fbee4904 (checksum...) ok +import .git/objects/9b/47feee99b5f24e0dc96cf4a20fcb88c0ec007d (checksum...) ok +import .git/objects/b0/8c838cfb09bafae40a05312092c37360c880b0 (checksum...) ok +import .git/refs/heads/master (checksum...) ok +import .git/refs/heads/git-annex (checksum...) ok +import .git/logs/HEAD (checksum...) ok +import .git/logs/refs/heads/master (checksum...) ok +import .git/logs/refs/heads/git-annex (checksum...) ok +import .git/info/exclude (checksum...) ok +import .git/hooks/pre-applypatch.sample (checksum...) ok +import .git/hooks/applypatch-msg.sample (checksum...) ok +import .git/hooks/pre-rebase.sample (checksum...) ok +import .git/hooks/update.sample (checksum...) ok +import .git/hooks/commit-msg.sample (checksum...) ok +import .git/hooks/pre-commit (checksum...) ok +import .git/hooks/prepare-commit-msg.sample (checksum...) ok +import .git/hooks/post-update.sample (checksum...) ok +import .git/hooks/pre-commit.sample (checksum...) ok +(Recording state in git...) +error: Invalid path 'foo/.git/COMMIT_EDITMSG' +error: unable to add foo/.git/COMMIT_EDITMSG to index +fatal: adding files failed + +git-annex: user error (xargs ["-0","git","--git-dir=/tmp/test/bar/.git","--work-tree=/tmp/test/bar","add","--"] exited 123) +failed +git-annex: import: 2 failed +anarcat@angela:foo$ cd ../../foo +anarcat@angela:foo$ git status +fatal: Not a git repository (or any of the parent directories): .git +anarcat@angela:foo$ +# End of transcript or log. +"""]] + +Thanks! --[[anarcat]] + +> Would have thought this was obviously something you shouldn't do +> (sorta like running git-annex import on your home directory), +> but ok, it can skip .git directories. [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_importfeed_fails.mdwn b/doc/bugs/git_annex_importfeed_fails.mdwn new file mode 100644 index 000000000..244ed769c --- /dev/null +++ b/doc/bugs/git_annex_importfeed_fails.mdwn @@ -0,0 +1,64 @@ +### Please describe the problem. + +git annex importfeed fails + +### What steps will reproduce the problem? + +git annex importfeed http://www.tatw.co.uk/podcast.xml + +### On what operating system? + +Ubuntu 12.04, the prebuilt linux tarball + +[[!format sh """ +$ 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: 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 + +$ git annex importfeed http://www.tatw.co.uk/podcast.xml +(checking known urls...) +(Recording state in git...) +importfeed http://www.tatw.co.uk/podcast.xml +--2013-09-27 12:16:09-- http://www.tatw.co.uk/podcast.xml +Résolution de www.tatw.co.uk (www.tatw.co.uk)... 88.190.26.130 +Connexion vers www.tatw.co.uk (www.tatw.co.uk)|88.190.26.130|:80... connecté. +requête HTTP transmise, en attente de la réponse... 200 OK +Longueur: 41267 (40K) [application/xml] +Sauvegarde en : «/tmp/user/2166/feed10670» + +100%[==========================================================================>] 41 267 81,6K/s ds 0,5s + +2013-09-27 12:16:10 (81,6 KB/s) - «/tmp/user/2166/feed10670» sauvegardé [41267/41267] + +addurl Above___Beyond__Group_Therapy/_001_Group_Therapy_Radio_with_Above___Beyond (downloading ...) +failed +addurl Above___Beyond__Group_Therapy/_002_Group_Therapy_Radio_with_Above___Beyond (downloading ...) +failed +addurl Above___Beyond__Group_Therapy/_003_Group_Therapy_Radio_with_Above___Beyond (downloading ...) +failed +addurl Above___Beyond__Group_Therapy/_004_Group_Therapy_Radio_with_Above___Beyond (downloading ...) +failed + +etc + + +# End of transcript or log. +"""]] + +> This is a bug in the feed library: <https://github.com/sof/feed/issues/7> +> And already fixed upstream this morning, so if you need the fix +> immediately, build with cabal. Otherwise fix will percolate out to +> builds eventually. +> [[done]] --[[Joey]] diff --git a/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn b/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn new file mode 100644 index 000000000..34096d894 --- /dev/null +++ b/doc/bugs/git_annex_indirect_can_fail_catastrophically.mdwn @@ -0,0 +1,78 @@ +### Please describe the problem. + +I have a repo that I initialized in direct mode because i felt unconfortable with the "symlink forest" approach. + +Now that I prefer that, i want to switch back to indirect mode. The problem is, when I did that, I realized that some files in the repo were not writable by my user, and git annex indirect crashed, and didn't "indirect" all the files. Now the repo is in a "half-direct" state, and I seem to be unable to recover. + +### What steps will reproduce the problem? + +[[!format txt """ +git init +git annex init +git annex direct +git annex add . # make sure some files are not writable by your user +git annex indirect +"""]] + +The `indirect` step will stop at the file that is not writable and will fail to move some files to `.git/annex`. And then the repo is in `indirect` mode yet some files are still not symlinks. + +Doing a `git annex direct` will try to commit all those nasty files into git, as it does a `git commit -a`. + +### What version of git-annex are you using? On what operating system? + + git-annex version: 4.20130912-ga1faca3 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi + +Debian wheezy. + +### Please provide any additional information below. + +Ideally, there would be a way to just tell git annex it's really still in direct mode and migrate the remaining files. + +The workaround is, obviously, to make sure you own all those files before messing around: + + chown -R you * + chmod -R u+w * + +A [[patch]], maybe, that allows you to flip cleanly between the two modes: + +[[!format diff """ +From a21dfc97da96883b2a088bb5f3f466296f08d858 Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@koumbit.org> +Date: Mon, 16 Sep 2013 13:58:29 -0400 +Subject: [PATCH] do not commit -a when going back to direct mode + +without this, if we switched to indirect mode but failed doing so +(because of a permission problem, for example), going back to +direct mode will commit all files to git, which we really want +to avoid. + +--- + Command/Direct.hs | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/Command/Direct.hs b/Command/Direct.hs +index 7835988..ed8ea6c 100644 +--- a/Command/Direct.hs ++++ b/Command/Direct.hs +@@ -33,7 +33,6 @@ perform = do + showOutput + _ <- inRepo $ Git.Command.runBool + [ Param "commit" +- , Param "-a" + , Param "-m" + , Param "commit before switching to direct mode" + ] +-- +1.7.10.4 + +"""]] + +Any update on this? Why is `-a` used here? -- [[anarcat]] + +> -a is not really the problem. You certianly do usually want +> to commit your changes before converting to direct mode. +> +> [[done]]; now when this happens it catches the exception and +> leaves the file in direct mode, which is the same as it being +> unlocked. --[[Joey]] diff --git a/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment b/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment new file mode 100644 index 000000000..68814881d --- /dev/null +++ b/doc/bugs/git_annex_indirect_can_fail_catastrophically/comment_1_0b085e7e8c8e364f479574bc00c7c394._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.220" + subject="comment 1" + date="2013-09-25T18:57:25Z" + content=""" +Worse than being stuck partway converted, it fails in such a way that the file you can't write to is left stuck in .git/annex/objects/ without a symlink pointint to it. + +Here is how to recover: + +1. run `git annex direct` +2. run `git annex indirect` +3. run `git annex direct` +4. run `git annex indirect` +5. run `git revert HEAD` +6. run `git annex direct` +7. fix the permission of the file +8. run `git annex indirect` + +Please don't ask me why this works, but it will.. +"""]] diff --git a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment new file mode 100644 index 000000000..dac018cfa --- /dev/null +++ b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around/comment_1_f3e418144e5a5a9b3eda459546fc2bb0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://nicolas-schodet.myopenid.com/" + ip="2a01:e35:8ae6:f130:1e4b:d6ff:fe78:1ddb" + subject="Hardlink on remote repository?" + date="2013-08-15T06:58:16Z" + content=""" +Does the hardlink magic also work on the remote repository? If I understand correctly, the remote does not know that the new hash is the same file (and also, file needs to be transferred again) unless the migration is done on all remote before synchronizing. Is it right? +"""]] diff --git a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn new file mode 100644 index 000000000..e5960b62e --- /dev/null +++ b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated.mdwn @@ -0,0 +1,11 @@ +### Please describe the problem. +I created a .gitignore file and added it to git annex. In the assistant webapp log, the error "The installed version of git is too old for .gitignores to be honored by git-annex." shows up. According to [[bugs/assistant_ignore_.gitignore/]] this bug should be fixed in a later git version. + +### What steps will reproduce the problem? +Download the current prebuilt linux tarball from [[/install]], extract it, run "./runshell", then "git --version" returns "git version 1.7.10.4" + +### What version of git-annex are you using? On what operating system? +git-annex-standalone-amd64.tar.gz 2013-09-22 09:56 (Linux Ubuntu Precise) + +> Updated to wheezy backport 1.8.4. [[done]] for now, obviously it will go +> out of date again eventually.. --[[Joey]] diff --git a/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment new file mode 100644 index 000000000..5287ea935 --- /dev/null +++ b/doc/bugs/git_version_in_prebuilt_linux_tarball_is_outdated/comment_1_2a5a07498df9d38531d4570f7b463b9a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.220" + subject="comment 1" + date="2013-09-25T18:18:49Z" + content=""" +The tarballs are built on Debian stable in order to have an old enough libc to work most places. So I am limited to what is available in stable and backports. Once there is a backport available of git, I will use it. +"""]] diff --git a/doc/bugs/immediately_drops_files.mdwn b/doc/bugs/immediately_drops_files.mdwn new file mode 100644 index 000000000..70f7faa46 --- /dev/null +++ b/doc/bugs/immediately_drops_files.mdwn @@ -0,0 +1,222 @@ +### Please describe the problem. +When I `git annex get` files in a certain directory, they are got, then are dropped. +When I do the same in a different directory, then the files there remains (as expected). + +`git annex fsck` also fails on these files, but after that the problem persists. + +I'm not really sure where to look to see why this is happening, especially why only on some directories. +The filesystem (ext4) this is on has several GB free. + +Looking at the (broken) symlinks, they are strange: + +[[!format sh """ +git annex fsck IMG_4230.JPG > /dev/null +ls -l IMG_4230.JPG +lrwxrwxrwx 1 walter walter 207 Aug 13 12:14 IMG_4230.JPG -> ../../../.git/annex/objects/86/KF/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG +"""]] + +But then after getting it (and it being dropped somehow), the symlink is different (the number of ..s) + +[[!format sh """ +git annex get IMG_4230.JPG > /dev/null +ls -l IMG_4230.JPG +lrwxrwxrwx 1 walter walter 210 Aug 13 12:16 IMG_4230.JPG -> ../../../../.git/annex/objects/86/KF/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG/SHA256E-s4209479--bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG +"""]] + + + +### What steps will reproduce the problem? + +I'm not really sure; I will test later whether this happens on other computers. + +### What version of git-annex are you using? On what operating system? + git-annex version: 4.20130812-gc590455 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS + local repository version: 3 + default repository version: 3 + supported repository versions: 3 4 + upgrade supported from repository versions: 0 1 2 + +On ubuntu 12.10 + + +--Walter + +### Please provide any additional information below. + +*output of git annex fsck* +[[!format sh """ +git annex fsck 2013/08/01/IMG_4230.JPG +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-files","--cached","-z","--","2013/08/01/IMG_4230.JPG"] +[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","check-attr","-z","--stdin","annex.backend","annex.numcopies","--"] +fsck 2013/08/01/IMG_4230.JPG [2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","cat-file","--batch"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 12:01:25 NZST] read: git ["config","--null","--list"] +ok +[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-w","--stdin-paths","--no-filters"] +[2013-08-13 12:01:25 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"] +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +(Recording state in git...) +[2013-08-13 12:01:25 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","write-tree"] +[2013-08-13 12:01:25 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit-tree","78aca82f86ffb91bc841a3978f410e55aa6e0efe","-p","refs/heads/git-annex"] +[2013-08-13 12:01:25 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-ref","refs/heads/git-annex","14908fedbd44917815dd013125b69def1f7f8f7c"] + +"""]] + +*output of git annex get* (output taken from daemon.log, as output from command does not include the dropping part) +[[!format sh """ +git annex get 2013/08/01/IMG_4230.JPG +[2013-08-13 12:03:46 NZST] TransferWatcher: transfer starting: Download UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d" 2013/08/01/IMG_4230.JPG Nothing +[2013-08-13 12:03:46 NZST] TransferWatcher: transfer starting: Download UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d" 2013/08/01/IMG_4230.JPG Nothing +[2013-08-13 12:03:46 NZST] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "e6bb2ef2-b2b5-11e1-bd1b-3fd40e5e767d", transferKey = Key {keyName = "bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG", keyBackendName = "SHA256E", keySize = Just 4209479, keyMtime = Nothing}} +[2013-08-13 12:03:46 NZST] Watcher: add symlink 01/IMG_4230.JPG +[2013-08-13 12:03:46 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"] +[2013-08-13 12:03:46 NZST] Committer: committing 1 changes +[2013-08-13 12:03:46 NZST] Committer: Committing changes to git +[2013-08-13 12:03:46 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"] +[2013-08-13 12:03:46 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"] +[2013-08-13 12:03:46 NZST] Pusher: Synok +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +drop 01/IMG_4230.JPG cing with Adata, b(checking cloud...) itbucket +[2013-08-13 12:03:46 NZST] Committer: dropped 01/IMG_4230.JPG (from here) (copies now 4) : file renamed +[2013-08-13 12:03:46 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-w","--stdin-paths","--no-filters"] +[2013-08-13 12:03:46 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","write-tree"] +[2013-08-13 12:03:47 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit-tree","f288bfce8d133cc0ce00b65d48ca726809da34e6","-p","refs/heads/git-annex"] +[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-ref","refs/heads/git-annex","5a188246bda51207d12adf86c6d87568ca7076d7"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"] +[2013-08-13 12:03:47 NZST] Pusher: pushing to [Remote { name ="Adata" },Remote { name ="bitbucket" }] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"] +[2013-08-13 12:03:47 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master:synced/master"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 12:03:47 NZST] Watcher: add symlink 01/IMG_4230.JPG +[2013-08-13 12:03:47 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"] +To /media/walter/327D522A6727FE79/Pictures + 3afd101..5a18824 git-annex -> synced/git-annex +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..3afd101dade8be4e1ed7ac48fdf4173274d3ecd7","--oneline","-n1"] +[2013-08-13 12:03:48 NZST] Committer: committing 1 changes +[2013-08-13 12:03:48 NZST] Committer: Committing changes to git +[2013-08-13 12:03:48 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"] +[2013-08-13 12:03:48 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"] +To git@bitbucket.org:waltersom/Pictures.git + 3afd101..5a18824 git-annex -> synced/git-annex +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5a188246bda51207d12adf86c6d87568ca7076d7","--oneline","-n1"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 12:03:52 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 12:03:58 NZST] Pusher: Syncing with Adata, bitbucket +[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"] +[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"] +[2013-08-13 12:03:58 NZST] Pusher: pushing to [Remote { name ="Adata" },Remote { name ="bitbucket" }] +[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"] +[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master:synced/master"] +[2013-08-13 12:03:58 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"] +Everything up-to-date +[2013-08-13 12:03:58 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","Adata","git-annex:synced/git-annex","master"] +Everything up-to-date +[2013-08-13 12:04:02 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"] + +""" +]] + + + +I tried removing the USB drive I had plugged in, and was able to get the file from S3, and it wasn't dropped. +However, checking the logs, I see that it did try to drop the file, but was unable to verify numcopies, so gives up. +Also odd, is that it doesn't suggest making the USB drive available, but `git annex whereis` knows that the drive does have it. Also, annex.numcopies is 1, and it got it from S3, so why can't it drop it on the computer? +Or, why does it say that it needs two copies? `git config annex.numcopies` gives 1. + +[[!format sh """ +[2013-08-13 16:52:08 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Nothing +[2013-08-13 16:54:06 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Just 65504 +[...] +[2013-08-13 16:54:06 NZST] TransferWatcher: transfer starting: Download UUID "be992080-b1db-11e1-8f79-1b10bb4092ef" 01/IMG_4230.JPG Just 4192256 +[2013-08-13 16:54:06 NZST] TransferWatcher: transfer finishing: Transfer {transferDirection = Download, transferUUID = UUID "be992080-b1db-11e1-8f79-1b10bb4092ef", transferKey = Key {keyName = "bba2489f526ed1288d23157b2b985bfda99321c52d05d3f4ddb92144b301318e.JPG", keyBackendName = "SHA256E", keySize = Just 4209479, keyMtime = Nothing}} +[2013-08-13 16:54:06 NZST] Watcher: add symlink 01/IMG_4230.JPG +[2013-08-13 16:54:06 NZST] chat: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","hash-object","-t","blob","-w","--stdin","--no-filters"] +[2013-08-13 16:54:06 NZST] Committer: committing 1 changes +[2013-08-13 16:54:06 NZST] Committer: Committing changes to git +[2013-08-13 16:54:06 NZST] feed: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","update-index","-z","--index-info"] +[2013-08-13 16:54:06 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","commit","--allow-empty-message","--no-edit","-m","","--quiet","--no-verify"] +[2013-08-13 16:54:06 + Could only verify the existence of 1 out of 2 necessary copies + + Try making some of these repositories available: + 416aa28e-b1d4-11e1-9539-c39b14a3f7d2 -- timeline laptop + f42d30a0-b1d2-11e1-8b32-3bdd169e3280 -- my desktop + + (Use --force to override this check, or adjust annex.numcopies.) +failed +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +drop 01/IMG_4230.JPG NZST] Pusher:(checking cloud...) Syncing with bitbucket +(unsafe) [2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","symbolic-ref","HEAD"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","refs/heads/master"] +[2013-08-13 16:54:07 NZST] Pusher: pushing to [Remote { name ="bitbucket" }] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 16:54:07 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","branch","-f","synced/master"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 16:54:07 NZST] call: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master:synced/master"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..7b6b1c6c479a13f9d4ece135bdf3ba31bc484b31","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..11a0c19d7c79f3e574b81295782ab2820caea232","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..5ebb3e46b8fc109c2966ceccdd716f469d94fcad","--oneline","-n1"] +[2013-08-13 16:54:07 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","ls-tree","-z","--","refs/heads/git-annex","uuid.log","remote.log","trust.log","group.log","preferred-content.log"] +To git@bitbucket.org:waltersom/Pictures.git + 5ebb3e4..7b6b1c6 git-annex -> synced/git-annex +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","git-annex"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","push","bitbucket","git-annex:synced/git-annex","master"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","show-ref","--hash","refs/heads/git-annex"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..7b6b1c6c479a13f9d4ece135bdf3ba31bc484b31","--oneline","-n1"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..9be78e75db197a26db6aaaffbcddf5057e30d23f","--oneline","-n1"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..2bae49a6e1ce85ad501b0fa85439da7cde8c8597","--oneline","-n1"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..b5858e25b7f7c45564ab463ecf3e74ecd8979609","--oneline","-n1"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..11a0c19d7c79f3e574b81295782ab2820caea232","--oneline","-n1"] +[2013-08-13 16:54:12 NZST] read: git ["--git-dir=/home/walter/Photos/.git","--work-tree=/home/walter/Photos","log","refs/heads/git-annex..cad75ea77d513a24006ee0b56ff0aad12b7aa805","--oneline","-n1"] +"""]] diff --git a/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment b/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment new file mode 100644 index 000000000..9d630e385 --- /dev/null +++ b/doc/bugs/immediately_drops_files/comment_1_9ef6e694ef8a8eee7a42f88554475db7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 1" + date="2013-08-24T16:41:04Z" + content=""" +You are running the git annex assistant, which takes care of getting and dropping files as it's configured to do, and you are then going in and manually running `git annex get`. If the assistant sees a file's content has appeared, and that file is in a directory that it has been configured to not want the content of file in (the `archive` directory by default), it will immediately try to drop it. + +The only thing I don't understand is why the number of `..` in the symlink would change. +"""]] diff --git a/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment b/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment new file mode 100644 index 000000000..274090c63 --- /dev/null +++ b/doc/bugs/immediately_drops_files/comment_2_76e4f8b73ab60b2540dd2a3e5379791d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="comment 2" + date="2013-08-24T16:41:47Z" + content=""" +BTW if you don't want the assistant to automatically get and drop files in your repository, you can edit the repository in the webapp and select \"manual mode\". +"""]] diff --git a/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment b/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment new file mode 100644 index 000000000..9253caa1a --- /dev/null +++ b/doc/bugs/immediately_drops_files/comment_3_788db083f5ba2e5589c3b952203ec954._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" + nickname="Walter" + subject="comment 3" + date="2013-08-24T21:59:12Z" + content=""" +I have all of my repositories set to either manual (all the computers), or full backup (the usb drive and s3). +So, this is happening in a manual repository. + + +Also, I still don't understand why it would be confused over the annex.numcopies setting (why does it claim it needs 2 copies, when numcopies is 1?) + +I just tested between desktop and laptop. File is also present in s3. + +File on desktop. Copy to laptop --> desktop drops (why? both are set to manual, and both have the other set as manual as well) + +Get on desktop. Works, it gets it from laptop. But then, desktop makes laptop drop it (why? again, both are manual repositories) + + + +"""]] diff --git a/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment b/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment new file mode 100644 index 000000000..aacf2f2dc --- /dev/null +++ b/doc/bugs/immediately_drops_files/comment_4_425b79865eb77d69d0b7a71a14639f81._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 4" + date="2013-09-13T19:27:51Z" + content=""" +> both are set to manual, and both have the other set as manual as well + +I'm not sure what you mean by that. Do you mean that when you run git annex vicfg, it is in group manual? +"""]] diff --git a/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment b/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment new file mode 100644 index 000000000..bb2569893 --- /dev/null +++ b/doc/bugs/immediately_drops_files/comment_5_7c9f660b6bcec31827a44a650e9d4622._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" + nickname="Walter" + subject="comment 5" + date="2013-09-13T21:58:30Z" + content=""" +I had checked in the webapps, and they were all set to manual. + +Looking in `git annex vicfg`, the groups are set to manual, and the content is set to standard. +"""]] diff --git a/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn b/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn new file mode 100644 index 000000000..4ee312be0 --- /dev/null +++ b/doc/bugs/importfeed_fails__44___bad_feed_content.mdwn @@ -0,0 +1,36 @@ +### Please describe the problem. + +I just added a new podcast to my feeds list and it is complaining of "bad feed content" when trying to import. + +### What steps will reproduce the problem? + +1. git-annex importfeed --fast http://redecentralize.org/podcast/feed.rss +3. see the sad error "warning: bad feed content" + +### What version of git-annex are you using? On what operating system? + +git-annex version: 4.20130827 + +### Please provide any additional information below. + +[[!format sh """ +greg@x200s:~/annex/Podcasts$ git-annex importfeed --fast http://redecentralize.org/podcast/feed.rss +(checking known urls...) +importfeed http://redecentralize.org/podcast/feed.rss +--2013-09-09 15:05:17-- http://redecentralize.org/podcast/feed.rss +Resolving redecentralize.org (redecentralize.org)... 204.232.175.78 +Connecting to redecentralize.org (redecentralize.org)|204.232.175.78|:80... connected. +HTTP request sent, awaiting response... 200 OK +Length: 4331 (4.2K) [text/xml] +Saving to: ‘/tmp/feed12649’ + +100%[==============================================================>] 4,331 --.-K/s in 0.08s + +2013-09-09 15:05:17 (56.0 KB/s) - ‘/tmp/feed12649’ saved [4331/4331] + + + warning: bad feed content +ok +"""]] + +> upstream bug <https://github.com/sof/feed/issues/5> ; [[done]] --[[Joey]] diff --git a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn new file mode 100644 index 000000000..0d6bcb05c --- /dev/null +++ b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast.mdwn @@ -0,0 +1,77 @@ +### Please describe the problem. + +importfeed responds with "failed" when using the option --lazy for specific podcast and no symbolic links get created. However when I don't use the --fast option the podcast enclosures do download and links get created as expected. + +### What steps will reproduce the problem? + +git-annex importfeed --fast http://schoolsucksproject.com/category/podcast/feed/ + +### What version of git-annex are you using? On what operating system? + + Ubuntu + git-annex version: 4.20130802-g1452ac3 + 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 + +### Please provide any additional information below. + + git-annex importfeed --fast http://schoolsucksproject.com/category/podcast/feed/ + (checking known urls...) + (Recording state in git...) + importfeed http://schoolsucksproject.com/category/podcast/feed/ + --2013-09-28 00:27:25-- http://schoolsucksproject.com/category/podcast/feed/ + Resolving schoolsucksproject.com (schoolsucksproject.com)... 108.162.199.17, 108.162.198.17 + Connecting to schoolsucksproject.com (schoolsucksproject.com)|108.162.199.17|:80... connected. + HTTP request sent, awaiting response... 200 OK + Length: unspecified [text/xml] + Saving to: `/tmp/feed16555' + + 2013-09-28 00:27:28 (217 KB/s) - `/tmp/feed16555' saved [423071] + + addurl School_Sucks_Project___Podcasts/238f__Presence_and_Productivity__6___Tools_For_A_Freed_Mind_and_A_Voluntary_Life_mp3 + unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-21T08_21_33-07_00.mp3 + failed + addurl School_Sucks_Project___Podcasts/238e__Presence_and_Productivity__5___Habit_Change_mp3 + unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3 + failed + addurl School_Sucks_Project___Podcasts/238d__Presence_and_Productivity__4___Next_Actions__Projects__and_Procrastination_mp3 + unable to access url: http://schoolsucks.podomatic.com/enclosure/2013-09-16T10_10_06-07_00.mp3 + failed + ... + +> (There is no --lazy option. You seem to mean --fast.) +> +> This fine web server rejects the User-Agent used by curl: + +<pre> +joey@darkstar:~>curl http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3 +Forbidden +joey@darkstar:~>wget http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3 +--2013-09-28 11:18:36-- http://schoolsucks.podomatic.com/enclosure/2013-09-18T20_40_40-07_00.mp3 +Resolving schoolsucks.podomatic.com (schoolsucks.podomatic.com)... 38.99.42.46, 38.110.155.212 +Connecting to schoolsucks.podomatic.com (schoolsucks.podomatic.com)|38.99.42.46|:80... connected. +HTTP request sent, awaiting response... 200 OK +<pre> + +> git-annex always uses curl for checking file sizes. So the workaround +> is to use `git annex addurl --relaxed` on this url, which will skip +> the size check. However, if you only had curl installed, `git-annex get` +> would again try to use curl to get the file, and would still fail. +> It only happens to successfully download because git-annex chose +> to use wget and this site has apparently forgotten to block that. +> +> I don't know if it makes sense for git-annex to vary the user-agent +> to get around such (incredibly stupid) blocking. It could retry +> with a random user-agent, but that could be construed as abusive +> behavior; this site has asked us to go away. The only choices +> that seem really defensible would be to add a --user-agent +> switch, and/or to make git-annex set a default user agent header +> of "git-annex", rather than relying on the curl/wget defaults. +> --[[Joey]] + +> I've [[done]] what's discussed above, and verified it fixes +> behavior for this specific server too. +> --[[Joey]] diff --git a/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment new file mode 100644 index 000000000..26430ec91 --- /dev/null +++ b/doc/bugs/importfeed_fails_when_using_the_option_--lazy_for_specific_podcast/comment_1_4ccfabbaf75e139b32f6fa6f7bc6a7fe._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Remy" + ip="82.94.186.146" + subject="Thank you very much" + date="2013-09-30T08:49:33Z" + content=""" +Thank you very much for looking into this! This issue was holding me back from using git-annex as my podcatcher. Hope it helps somebody else as well. +"""]] diff --git a/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn b/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn new file mode 100644 index 000000000..44d25b02d --- /dev/null +++ b/doc/bugs/importfeed_should_allow_pubdate_in_the_template.mdwn @@ -0,0 +1,5 @@ +importfeed is a great feature, but it doesn't allow templating the filename with the publish date. + +I would suggest adding pubdate option, which would fix this problem. + +> duplicate of [[todo/importfeed: allow ${itemdate} with --template]] [[done]] --[[Joey]] diff --git a/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn b/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn new file mode 100644 index 000000000..5f09e2636 --- /dev/null +++ b/doc/bugs/importfeed_uses___34____95__foo__34___as_extension.mdwn @@ -0,0 +1,17 @@ +### Please describe the problem. +When running importfeed on gitminutes <http://feeds.gitminutes.com/gitminutes-podcast> git-annex interprets the extension as "_mp3" rather than ".mp3" which means that renaming is needed for various audio players to accept the files. + +### What steps will reproduce the problem? +git annex importfeed http://feeds.gitminutes.com/gitminutes-podcast --fast + +### What version of git-annex are you using? On what operating system? +git-annex version: 4.20130802 +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 Sid + +> Already fixed in git. [[done]] --[[Joey]] diff --git a/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn b/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn new file mode 100644 index 000000000..df7fc5fb2 --- /dev/null +++ b/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn @@ -0,0 +1,55 @@ +### 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/internal_server_error:_hGetContents:_invalid_argument___40__invalid_byte_sequence__41__.mdwn b/doc/bugs/internal_server_error:_hGetContents:_invalid_argument___40__invalid_byte_sequence__41__.mdwn new file mode 100644 index 000000000..8c9703ed2 --- /dev/null +++ b/doc/bugs/internal_server_error:_hGetContents:_invalid_argument___40__invalid_byte_sequence__41__.mdwn @@ -0,0 +1,29 @@ +### Please describe the problem. + +Some logs fail to be displayed, and instead of displaying parts of the log, no logs at all are displayed in the webapp. + +The problem character is, I believe, a latin-1 encoded filename (as opposed to UTF-8). --[[anarcat]] + +### What steps will reproduce the problem? + +1. download [this logfile](http://paste.anarc.at/daemon.log.1) +2. install it in .git/annex/daemon.log +3. load the webapp +4. visit the logs page + +### What version of git-annex are you using? On what operating system? + +4.20131105-g8efdc1a + +### 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 +Internal Server Error +/srv/video/.git/annex/daemon.log.1: hGetContents: invalid argument (invalid byte sequence) +git-annex version 4.20131105-g8efdc1a +# End of transcript or log. +"""]] + +> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn b/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn new file mode 100644 index 000000000..307eed308 --- /dev/null +++ b/doc/bugs/internal_server_error:_unknown_UUID_on_webapp.mdwn @@ -0,0 +1,147 @@ +### Please describe the problem. + +I am having trouble using the webapp with a setup I did on the commandline that was working fine. + +I have two machines: one, a server called `marcos`, is available on the internetz and I cloned a repo from there into `markov`, a workstation that is hidden behind a NAT connexion (so I can't add it as a remote). + +It seems that because the remote is not locally available as a git remote, the webapp is freaking out because it doesn't recognize `markov` as a proper remote. + +### What steps will reproduce the problem? + +1. setup git annex locally (on `marcos`) in a repository (probably `git annex init; git annex direct; git annex add .` i somewhat followed [[tips/Git_annex_and_Calibre/]]) +2. `git clone` that repo on a remote, unaccessible (NAT'd) server (`markov`) +3. start doing some git annex get, get tired, run the web app on `markov` +4. let that run over there, go back to `marcos` +5. be curious about what is going on on `markov`, run the webapp and enter the path to the repository created in step one when prompted (it's the first time i run the webapp) +6. it starts up fine, but doesn't seem to detect `markov`, marking transfers as going to the remote named `unknown` +7. click on the `unknown` link, crash +8. go back to the dashboard, crash + +From there on, the webapp is pretty much crashed, starting it from scratch asks me if i want to create a git annex repo. + +### What version of git-annex are you using? On what operating system? + +4.20130921-gd4739c5 compiled and installed by hand on debian wheezy. + +### Please provide any additional information below. + +[[!format sh """ +# Here's everything that has been logged by the git-annex assistant, as well as by programs it has run. + +[2013-11-04 22:42:50 EST] main: starting assistant version 4.20130921-gd4739c5 +(merging synced/git-annex into git-annex...) +(Recording state in git...) + + No known network monitor available through dbus; falling back to polling +Already up-to-date. + +(scanning...) [2013-11-04 22:42:50 EST] Watcher: Performing startup scan +04/Nov/2013:22:42:51 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:42:52 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:42:52 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +(Recording state in git...) +(Recording state in git...) +(started...) + + metadata.db still has writers, not adding +[2013-11-04 22:42:59 EST] Committer: Adding cover.jpg Ars Techn..ibre.epub Cyberpres..ibre.epub cover.jpg cover.jpg Ars Techn..ibre.epub cover.jpg Democracy..ibre.epub cover.jpg and 11 other files +add Calibre/Ars Technica [dim., 03 nov. 2013] (645)/cover.jpg (checksum...) ok +add Calibre/Ars Technica [dim., 03 nov. 2013] (645)/Ars Technica [dim., 03 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Cyberpresse [lun., 04 nov. 2013] (647)/Cyberpresse [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Cyberpresse [lun., 04 nov. 2013] (647)/cover.jpg (checksum...) ok +add Calibre/Ars Technica [sam., 02 nov. 2013] (642)/cover.jpg (checksum...) ok +add Calibre/Ars Technica [sam., 02 nov. 2013] (642)/Ars Technica [sam., 02 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Democracy now! [lun., 04 nov. 2013] (649)/cover.jpg (checksum...) ok +add Calibre/Democracy now! [lun., 04 nov. 2013] (649)/Democracy now! [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/xkcd [lun., 04 nov. 2013] (646)/cover.jpg (checksum...) ok +add Calibre/xkcd [lun., 04 nov. 2013] (646)/xkcd [lun., 04 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Cyberpresse [dim., 03 nov. 2013] (644)/cover.jpg (checksum...) ok +add Calibre/Cyberpresse [dim., 03 nov. 2013] (644)/Cyberpresse [dim., 03 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Le Devoir [sam., 02 nov., 2013] (640)/cover.jpg (checksum...) ok +add Calibre/Le Devoir [sam., 02 nov., 2013] (640)/Le Devoir [sam., 02 nov., 2013] - Calibre.epub (checksum...) ok +add Calibre/Le Devoir [lun., 04 nov., 2013] (648)/cover.jpg (checksum...) ok +add Calibre/Le Devoir [lun., 04 nov., 2013] (648)/Le Devoir [lun., 04 nov., 2013] - Calibre.epub (checksum...) ok +add Calibre/Cyberpresse [sam., 02 nov. 2013] (641)/cover.jpg (checksum...) ok +add Calibre/Cyberpresse [sam., 02 nov. 2013] (641)/Cyberpresse [sam., 02 nov. 2013] - Calibre.epub (checksum...) ok +add Calibre/Le Devoir [dim., 03 nov., 2013] (643)/cover.jpg (checksum...) ok +add Calibre/Le Devoir [dim., 03 nov., 2013] (643)/Le Devoir [dim., 03 nov., 2013] - Calibre.epub (checksum...) [2013-11-04 22:43:01 EST] Committer: Committing changes to git +ok +(Recording state in git...) +(Recording state in git...) +04/Nov/2013:22:43:51 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:47:24 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:52:29 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:52:30 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:52:30 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:56:47 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +[2013-11-04 22:57:08 EST] Committer: Adding metadata.db-journal +add metadata.db-journal (checksum...) [2013-11-04 22:57:08 EST] Committer: Committing changes to git +[2013-11-04 22:57:09 EST] Committer: Adding metadata.db-journal metadata.db +ok +(Recording state in git...) +(Recording state in git...) +add metadata.db (checksum...) [2013-11-04 22:57:09 EST] Committer: Committing changes to git +ok +(Recording state in git...) +(Recording state in git...) +04/Nov/2013:22:57:12 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:57:15 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:57:18 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +04/Nov/2013:22:57:20 -0500 [Error#yesod-core] Unknown UUID @(yesod-core-1.2.4.2:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:485:5) +"""]] + +> I wonder if this couldn't be related to [[cannot determine uuid for origin]], although in this case the remote is just not added to `.git/config`. --[[anarcat]] + +> This was fixed in commit 44e1524be53373ddbf28d643bedf5455433c2b2e +> on Sep 29th. You should update. [[done]] +> +> (It also sounds like your repository on markov is for some reason not +> able to push its git repository to marcos. You might need to fix +> something in your setup to get syncing working) --[[Joey]] +> +> > Humm.. Weird. Upgrading fixes the crash, but `marcos` still sees only +> > one repository. It sees some syncs going on from `unknown`, and when +> > I click on that `unknown` link, I get to edit that repository, and +> > it sees it as `here`. So I am not sure I understand what is going +> > on here. +> > +> > (As for the repo on `markov`, it does sync properly: +> > +> > anarcat@desktop008:books$ git annex sync +> > commit +> > ok +> > pull origin +> > From anarc.at:/srv/books +> > 3b4fa7b..c35b13e git-annex -> origin/git-annex +> > ok +> > +> > Or rather - it doesn't fail. But it doesn't push! +> > +> > anarcat@desktop008:books$ git push +> > Everything up-to-date +> > +> > Note that git on `marcos` is the 1.8.4 backport for some reason. +> > I know that branch tracking changed with that release, maybe +> > that's the problem? --[[anarcat]]) +> > +> > > So yep, I confirm that even in 4.20131105-g8efdc1a, the webapp +> > > doesn't find the `markov` remote properly, even though +> > > `git annex status` can: +> > > +> > > $ git annex status +> > > repository mode: direct +> > > trusted repositories: 0 +> > > semitrusted repositories: 3 +> > > 00000000-0000-0000-0000-000000000001 -- web +> > > a75cbbf7-e055-423e-b375-443e0552c9e2 -- here (anarcat@marcos:/srv/books) +> > > aa500f29-42d9-4777-ae02-4a2c3d47db44 -- anarcat@markov:~/books +> > > +> > > I see transfers happening, but they go to "unknown". The link is: +> > > +> > > http://127.0.0.1:56577/config/repository/edit/UUID%20%22aa500f29-42d9-4777-ae02-4a2c3d47db44%22?auth=... +> > > +> > > -- [[anarcat]] +> > > +> > > > I have filed this as a separate bug to close the discussion properly here, sorry for the noise. :) see [[bugs/remote_not_showing_up_in_webapp]] --[[anarcat]] diff --git a/doc/bugs/manpage_has_slight_indentation_error.mdwn b/doc/bugs/manpage_has_slight_indentation_error.mdwn new file mode 100644 index 000000000..56d9d2266 --- /dev/null +++ b/doc/bugs/manpage_has_slight_indentation_error.mdwn @@ -0,0 +1,38 @@ +### 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/merge_causes_out_of_memory_on_large_repos.mdwn b/doc/bugs/merge_causes_out_of_memory_on_large_repos.mdwn new file mode 100644 index 000000000..c081f9799 --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos.mdwn @@ -0,0 +1,26 @@ +### Please describe the problem. + +`git annex merge` goes out of memory on a large repo. + + +### What steps will reproduce the problem? + + $ git annex merge + merge git-annex git-annex: out of memory (requested 1048576 bytes) + +### What version of git-annex are you using? On what operating system? + + git-annex version: 4.20130827 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS + +On debian wheezy i386 + +### Please provide any additional information below. + +The repository contains a lot of files: + + $ cd .git/objects + $ find . -type f | wc -l + 1091548 + +[[!tag moreinfo]] diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_1_6d47485728ea65a9b555f8be7159dea5._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_1_6d47485728ea65a9b555f8be7159dea5._comment new file mode 100644 index 000000000..f87a9a84d --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_1_6d47485728ea65a9b555f8be7159dea5._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnxlx1UrzVhdy6_gFjzmF42x6QXxBUxg00" + nickname="Jakukyo" + subject="pre-commit hook of git annex" + date="2013-09-11T00:58:09Z" + content=""" +The pre-commit hook of git annex throws an 'out of memory' error, too. + +As a workaround, I've deleted ~/.git/hooks/pre-commit, and use `git merge` manually. +"""]] diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_2_06723d13ecdaf87de5ff2b209e3c5198._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_2_06723d13ecdaf87de5ff2b209e3c5198._comment new file mode 100644 index 000000000..76a0d2fd4 --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_2_06723d13ecdaf87de5ff2b209e3c5198._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 2" + date="2013-09-13T18:38:11Z" + content=""" +Can you run this so I can get a better idea of the size of this repository: + +git ls-tree -r git-annex | wc -l +"""]] diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment new file mode 100644 index 000000000..11f03b39d --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_3_9f83ef190547b291a715cda55b7977d4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.14.105" + subject="comment 3" + date="2013-09-19T18:53:14Z" + content=""" +I just fixed a memory leak that occurred when large files were checked directly into git (perhaps by accident by committing files manually when using direct mode). However, I don't think it affected `git annex merge`. + +Still need information about how to reproduce this bug... +"""]] diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_4_0e32ae0300472c56079cfbcd78a3e386._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_4_0e32ae0300472c56079cfbcd78a3e386._comment new file mode 100644 index 000000000..d1c447980 --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_4_0e32ae0300472c56079cfbcd78a3e386._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnxlx1UrzVhdy6_gFjzmF42x6QXxBUxg00" + nickname="Jakukyo" + subject="size of repo" + date="2013-09-21T09:32:03Z" + content=""" + $ git ls-tree -r git-annex | wc -l + 29273 +"""]] diff --git a/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_5_e8998716107e7ae8d0e8d332812517ad._comment b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_5_e8998716107e7ae8d0e8d332812517ad._comment new file mode 100644 index 000000000..272dc2fd2 --- /dev/null +++ b/doc/bugs/merge_causes_out_of_memory_on_large_repos/comment_5_e8998716107e7ae8d0e8d332812517ad._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.220" + subject="comment 5" + date="2013-09-25T18:36:39Z" + content=""" +That doesn't look very big, I merge one 3x that large on a 128 mb machine. + +I think you will need to either email me privately so I can get a copy of your repository to investigate with ... or you can try to investigate on your own. + +I think the first things I would try to debug this are to look over `git annex merge --debug` and see if I see anything unusual, and then I would probably `git checkout git-annex` in the repository, and wc -l on all the files and see if any file has a lot of lines, or is otherwise very large. + +If that found nothing, my next step would be to rebuild git-annex from source with memory profiling enabled, as explained in this book, and try to get a memory profiling graph that explained what was using up the memory. <http://book.realworldhaskell.org/read/profiling-and-optimization.html> +"""]] diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn new file mode 100644 index 000000000..c10176463 --- /dev/null +++ b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build.mdwn @@ -0,0 +1,36 @@ +### Please describe the problem. + +1 thumb drive became corrupted when using as a server on raspberry pi, and 2 microSD cards when using as a client in my phone. Both happened during syncing largish repository. (corrupted = permanent input/output error) + +* Put git annex on my android phone with a 64GB (FAT) micro SD, fired up git annex, it got reported as corrupted half on hour later, reformatting worked but got reported as corrupted again. + +* Put git annex assistant on my raspberry pi, one of the thumbdrives in my LVM (ext4) got corrupted shortly after I began using the assistant. I replaced them with a cheap real SSD drive, and had no problem since. + +* Put git annex back on my android phone. Kept it going for an extended sync session, but it never started syncing. I kept it going for an hour or so, and my new 32GB microSD (FAT) got corrupted. + +The pattern is nothing like proof, but it seems to be too regular to be completely coincidental. The pattern seems to be: ARM + (SDcard|USBstick) + Assistant = drive corruption. + +My guess is that the ARM build might have some kind of unlucky write pattern or loop that causes increased wear, but I know very little of the interna. + +### What steps will reproduce the problem? + +* Get a raspberry pi and a USB stick, or an android phone and a microSD card +* Get an [ARM build of the assistant](https://github.com/tradloff/git-annex-RPi) +* Sync a largish (12GB) repository + +### What version of git-annex are you using? On what operating system? + +4.20131002 on the pi, 20131024 for the 32GB SD, and 20131015 for the 64GB SD. + +### 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 + +Unfortunately, daemon.log was unrecoverable along with the other files on the SD card. + +I can try and autosync the daemon.log somewhere if I happen to come along a bunch of scrap flash storage (not impossible). + +# End of transcript or log. +"""]] diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment new file mode 100644 index 000000000..52324a5a8 --- /dev/null +++ b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_1_0527581ea60d28bb28504fa2a355ed87._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="salvaged logs" + date="2013-10-31T10:00:40Z" + content=""" +The previously corrupt memory drive magically reappeared, so this might indicate a phone bug. In any case, I was able to salvage the logs from the phone. + +[Salvaged Logs](http://capocasa.name/android-4.2-lenovo-daemonlog.tar.gz) +"""]] diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment new file mode 100644 index 000000000..878e8fd7d --- /dev/null +++ b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_2_926a87b60e20d286d49639c8dad13a1a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="correlation does not imply causation" + date="2013-11-01T16:37:31Z" + content=""" +I've been using git-annex on thumbdrives for years without problems. It seems more likely to me that you have a general problem with your hardware than that one program that does nothing special is somehow at fault. +"""]] diff --git a/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment new file mode 100644 index 000000000..01ab119d2 --- /dev/null +++ b/doc/bugs/microsd__47__thumbdrives_seem_to_die_when_using_the_ARM_build/comment_3_c509fba1a9adacfd26a2bd12b4aea988._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" + nickname="Carlo" + subject="comment 3" + date="2013-11-02T17:29:55Z" + content=""" +True, and good to know. Didn't necessarily want to trigger a big bug hunt here anyway, just some data/logs in case any more correlation comes up. +"""]] 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 new file mode 100644 index 000000000..1dca84346 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange.mdwn @@ -0,0 +1,40 @@ +### 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 new file mode 100644 index 000000000..a3c162d61 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_1_6ac691645edb483797bee05043fd83b3._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..c122bd92f --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_2_5d67e3a60b7cc30c2b1857f50895d363._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..d00556c75 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_3_78f1e081b92f418c20893d86a8715501._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..d68b3ea35 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_4_1e2a59e0eec89ef1a57d1488ff40dcf0._comment @@ -0,0 +1,12 @@ +[[!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 new file mode 100644 index 000000000..b2f525648 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_5_5e74431048b07631e0dbeca90fdb365b._comment @@ -0,0 +1,47 @@ +[[!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 new file mode 100644 index 000000000..9c558e05e --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_6_3724e1c1a5fc6d3589452478249792ec._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..e781beae1 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_7_7f841ea7bf7d44f3d810ca097ac9eb47._comment @@ -0,0 +1,8 @@ +[[!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 new file mode 100644 index 000000000..b4ef6b5c7 --- /dev/null +++ b/doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_8_c53ce2274388711ffbde1595b64f932b._comment @@ -0,0 +1,10 @@ +[[!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/remote_not_showing_up_in_webapp.mdwn b/doc/bugs/remote_not_showing_up_in_webapp.mdwn new file mode 100644 index 000000000..f8b4da7b1 --- /dev/null +++ b/doc/bugs/remote_not_showing_up_in_webapp.mdwn @@ -0,0 +1,88 @@ +### Please describe the problem. + +This is a followup on [[bugs/internal_server_error:_unknown_UUID_on_webapp]]. In that issue, webapps previous to 20130929 would crash with `internal server error: unknown UUID`. This was fixed at that date, but some problems remain, namely that the remote that is recognized on the commandline doesn't show up in the webapp. + +`markov` is able to push to `marcos`, but not the reverse because `markov` is hidden behind a NAT. `git annex sync` seems to do the right thing accordingly on both ends (which is: `marcos` doesn't try to push to `markov` but `markov` pushes to `marcos`). + +### What steps will reproduce the problem? + +See [[bugs/internal_server_error:_unknown_UUID_on_webapp]]. I didn't do any further changes other than upgrade `git-annex` on both ends. + +### What version of git-annex are you using? On what operating system? + +`marcos` is now running `Version: 4.20131105-g8efdc1a Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash` + +`markov` is now running the wheezy backport, `4.20131002~bpo70+1`. + +### Please provide any additional information below. + +#### On `marcos` + +Here's the output of `git annex status` on `marcos`: + +[[!format sh """ +anarcat@marcos:books$ git annex status +repository mode: direct +trusted repositories: 0 +semitrusted repositories: 3 + 00000000-0000-0000-0000-000000000001 -- web + a75cbbf7-e055-423e-b375-443e0552c9e2 -- here (anarcat@marcos:/srv/books) + aa500f29-42d9-4777-ae02-4a2c3d47db44 -- anarcat@markov:~/books +untrusted repositories: 0 +transfers in progress: none +available local disk space: 7.04 gigabytes (+1 megabyte reserved) +local annex keys: 736 +local annex size: 3.92 gigabytes +annexed files in working tree: 721 +size of annexed files in working tree: 3.92 gigabytes +bloom filter size: 16 mebibytes (0.1% full) +backend usage: + SHA256E: 1457 +# End of transcript or log. +"""]] + +Here's a screenshot of the idle webapp on marcos: + +<img src="http://i.imgur.com/3HFgj3w.png" /> + +You can clearly see that the webapp doesn't see the `markov` remote. + +When `markov` transfers stuff, `marcos` sees the transfers happening, but marks it as going to the `unknown` remote: + +<img src="http://i.imgur.com/YOu9GbA.png" /> + +Clicking on that link is what was previously triggering [[bugs/internal_server_error:_unknown_UUID_on_webapp]] but now yields a "Unknown remote" error. + +<img src="http://i.imgur.com/y7JxULi.png" /> + +#### On `markov`: + +Here is a screenshot from `markov` that shows *it* knows about both repositories and seem to behave properly: + +<img src="http://i.imgur.com/fTMslVT.png" /> + +And here's the output of `git annex status` on markov: + +[[!format sh """ +anarcat@desktop008:books$ git annex status +repository mode: indirect +trusted repositories: 0 +semitrusted repositories: 3 + 00000000-0000-0000-0000-000000000001 -- web + a75cbbf7-e055-423e-b375-443e0552c9e2 -- origin (anarcat@marcos:/srv/books) + aa500f29-42d9-4777-ae02-4a2c3d47db44 -- here (anarcat@markov:~/books) +untrusted repositories: 0 +transfers in progress: + downloading Patrick K. O'Brien/Philip's Atlas of World History, Concise Edition (115)/Philip's Atlas of World History, Concise Edition - Patrick K. O'Brien.pdf from origin +available local disk space: 93.25 gigabytes (+1 megabyte reserved) +temporary directory size: 50.07 megabytes (clean up with git-annex unused) +local annex keys: 708 +local annex size: 3.81 gigabytes +known annex keys: 721 +known annex size: 3.92 gigabytes +bloom filter size: 16 mebibytes (0.1% full) +backend usage: + SHA256E: 1429 +"""]] + +Finally, note that you sometimes see `desktop008` above: it turns out I am running `git annex` from my workstation, which NFS-mounts the `/home` directory of `markov` into `/srv/musique`. --[[anarcat]] diff --git a/doc/bugs/remote_not_showing_up_in_webapp/comment_1_2a269732fd528f505777542d3556437a._comment b/doc/bugs/remote_not_showing_up_in_webapp/comment_1_2a269732fd528f505777542d3556437a._comment new file mode 100644 index 000000000..ecf697d2c --- /dev/null +++ b/doc/bugs/remote_not_showing_up_in_webapp/comment_1_2a269732fd528f505777542d3556437a._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.47" + subject="comment 1" + date="2013-11-06T16:38:47Z" + content=""" +marcov does not show up in the webapp because there is no configured git remote for it. + +This is a slightly confusing corner of the webapp. The webapp will show repositories that do not have a configured remote, but it only does it for special remotes. ssh repos, being regular git remotes, don't currently show up in the webapp unless that repository is actually set up as a remote. + +It should certianly not show it as \"unknown\"; it would be much better to use the full repo description here, since it does not have a remote name. +(Unless the description is really long!) + +I think you'll also get the \"unknown uuid\" screen even for a special remote that is not configured in the local repository. So that needs to be fixed. + +Finally, it would probably be good for the webapp to show ssh repos that don't have remotes as existing, and let the user enter a ssh address to configure them. The problem with trying to do this is it actually has no idea that this is a ssh repo. It could just as easily be a local directory. The UI to configure it would be pretty elaborate. +"""]] diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn new file mode 100644 index 000000000..c315d4789 --- /dev/null +++ b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch.mdwn @@ -0,0 +1,81 @@ +### Please describe the problem. + +On Mac OS X, I tried to switch a repository to direct mode, but there was a +problem in the middle of the switch (permission denied) and the switch +aborted, leaving the repository in a half switched state. + +I tried different manipulations, one of which was a checkout (oops), switch +back to indirect, then direct again, and now I have the repository in direct +mode except one file which caused the permission denied error. + +### What steps will reproduce the problem? + +Do not know exactly why this file is special. I still have the repository, and +each time I try to get this file, it fails with the same error message. + +### What version of git-annex are you using? On what operating system? + +On Umba, git-annex version: 4.20130723, on Mac OS X 10.6.8. + +### Please provide any additional information below. + +Umba is the Mac OS X, camaar and riva are Debian machines. + +[[!format sh """ +Umba$ git annex version +git-annex version: 4.20130723 +build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS +Umba$ + +Umba$ git annex get --from riva --not --in here +get 2013-07-31/2013-07-31_180411.jpg (from riva...) +Password: +SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c + 2819887 100% 943.08kB/s 0:00:02 (xfer#1, to-check=0/1) + +sent 42 bytes received 2820397 bytes 433913.69 bytes/sec +total size is 2819887 speedup is 1.00 +failed +git-annex: get: 1 failed +Umba$ find . -name SHA256-s2819887-\* +./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c +./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.cache +./.git/annex/objects/wq/3j/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c.map +./.git/annex/transfer/failed/download/13fd5d5a-ed97-11e2-9178-574d3b1c0618/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c +./.git/annex/transfer/failed/download/95443f2e-ed96-11e2-9d3f-8ffa5b1aae7a/SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c +Umba$ git annex fsck +fsck 2013-07-31/2013-07-31_180411.jpg ok +(Recording state in git...) +Umba$ git annex drop 2013-07-31/2013-07-31_180411.jpg +Umba$ git annex get --from riva --not --in here +get 2013-07-31/2013-07-31_180411.jpg (from riva...) +Password: +SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c + 2819887 100% 949.58kB/s 0:00:02 (xfer#1, to-check=0/1) + +sent 42 bytes received 2820397 bytes 512807.09 bytes/sec +total size is 2819887 speedup is 1.00 +failed +git-annex: get: 1 failed +Umba$ + +camaar% git annex copy --to umba --not --in umba +copy 2013-07-31/2013-07-31_180411.jpg (checking umba...) (to umba...) +SHA256-s2819887--987f9811d7b5c7a287a74b7adbb852be4d18eeda61c3507f4e08c534d2356f4c + 2819887 100% 4.19MB/s 0:00:00 (xfer#1, to-check=0/1) +git-annex: //Users/nicolas/Pictures/Petites Boutes/.git/annex/tmp/2013-07-31_18041141700.jpg: rename: permission denied (Operation not permitted) +git-annex-shell: recvkey: 1 failed + +sent 2820393 bytes received 42 bytes 1128174.00 bytes/sec +total size is 2819887 speedup is 1.00 +rsync error: syntax or usage error (code 1) at main.c(1070) [sender=3.0.9] + + rsync failed -- run git annex again to resume file transfer +failed +git-annex: copy: 1 failed +camaar% +"""]] + +> Put in a fix that works, although perhaps not ideal as I do not +> understand how the repo got into the original problem state. [[done]] +> --[[Joey]] diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment new file mode 100644 index 000000000..1aef52076 --- /dev/null +++ b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.80" + subject="comment 1" + date="2013-09-30T16:47:42Z" + content=""" +I was able to cause a permission denied on `git annex direct` if I made the file in .git/annex/objects be owned by an different user than me. I do not know how that could happen in normal operation of git-annex. + + +I have made `git annex direct` catch this exception and continue. So you will get a repository that is switched to direct mode, but with one file that is still a symlink to the content, and if you fix the permissions problem, `git annex fsck` will fix it. + +I am curious about any details of how your repository got into the original state.. +"""]] 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 new file mode 100644 index 000000000..3aa3188af --- /dev/null +++ b/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo.mdwn @@ -0,0 +1,44 @@ +### 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 new file mode 100644 index 000000000..f0f50151a --- /dev/null +++ b/doc/bugs/ssh-keygen_failed_when_adding_remote_server_repo/comment_1_52180983b59c247389a55a9523ec435b._comment @@ -0,0 +1,14 @@ +[[!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/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment b/doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment new file mode 100644 index 000000000..1cae4ea98 --- /dev/null +++ b/doc/bugs/submodule_path_problem/comment_6_cacc91afcb1739dfca3a60590bb70356._comment @@ -0,0 +1,67 @@ +[[!comment format=mdwn + username="konubinix" + ip="82.243.233.186" + subject="Git annexed files symlink are wrong when submodule is not in the same path " + date="2013-08-08T06:36:10Z" + content=""" +Hi, + +First, thanks for the great tool that is git-annex! + +I have a problem with submodules when the git repository is not a submodule everywhere. + + $ git-annex version + git-annex version: 4.20130802 + ... + + $ git --version + git version 1.8.3.2 + +I try to have a repository has a submodule of another. + + # 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 would expect, since this repository is not an annex: +test -> .git/annex/objects/w8/pv/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2/SHA256E-s5--f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2 + +Do you think that is possible? + +Thanks. +"""]] diff --git a/doc/bugs/test_suite_failure_on_samba_mount.mdwn b/doc/bugs/test_suite_failure_on_samba_mount.mdwn new file mode 100644 index 000000000..ab3990c32 --- /dev/null +++ b/doc/bugs/test_suite_failure_on_samba_mount.mdwn @@ -0,0 +1,278 @@ +### Please describe the problem. + +`git annex test` show multiple failures on a samba mounted partition. + +### What steps will reproduce the problem? + +just run `git annex test` (in the mounted dir) + +### What version of git-annex are you using? On what operating system? + +4.20130521, built for architecture `armhf` by the Raspbian maintainers ("jessie" suite at the time of writing) + +### Please provide any additional information below. + +Here are the last lines of `git annex test` output; AFAICT they are the only lines mentioning failures. Before them the output mentions `+++ OK, passed 100 tests.`. + +[[!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 + +Cases: 1 Tried: 0 Errors: 0 Failures: 0---------------------------------------------------------------------- +Now, some broader checks ... + (Do not be alarmed by odd output here; it's normal. + wait for the last line to see how it went.) +---------------------------------------------------------------------- +init + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + Cases: 1 Tried: 1 Errors: 0 Failures: 0 +Cases: 3 Tried: 0 Errors: 0 Failures: 0Cases: 3 Tried: 1 Errors: 0 Failures: 0---------------------------------------------------------------------- +add + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. +Cases: 3 Tried: 2 Errors: 0 Failures: 0 Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. +error: unable to create temporary sha1 filename : No such file or directory + +git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo0/.git","--work-tree=/media/freebox/.t/tmprepo0","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1) + ### Failure in: git-annex add:2 +git annex init failed +Cases: 3 Tried: 3 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0---------------------------------------------------------------------- +reinject + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + Detected a crippled filesystem. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + Cases: 1 Tried: 1 Errors: 0 Failures: 0 +Cases: 2 Tried: 0 Errors: 0 Failures: 0not supported in direct mode; skipping +---------------------------------------------------------------------- +unannex + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. +error: unable to create temporary sha1 filename : No such file or directory + +git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo1/.git","--work-tree=/media/freebox/.t/tmprepo1","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1) + ### Failure in: git-annex unannex:0:no content +git annex init failed +Cases: 2 Tried: 1 Errors: 0 Failures: 1 Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + Detected a crippled filesystem. + Detected a filesystem without fifo support. + Disabling ssh connection caching. + Cases: 2 Tried: 2 Errors: 0 Failures: 1 +Cases: 3 Tried: 0 Errors: 0 Failures: 0not supported in direct mode; skipping +---------------------------------------------------------------------- +drop + Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. +error: unable to create temporary sha1 filename : No such file or directory + +git-annex: user error (git ["--git-dir=/media/freebox/.t/tmprepo2/.git","--work-tree=/media/freebox/.t/tmprepo2","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904"] exited 1) + ### Failure in: git-annex drop:0:no remotes +git annex init failed +Cases: 3 Tried: 1 Errors: 0 Failures: 1 Detected a crippled filesystem. + Enabling direct mode. + Detected a filesystem without fifo support. + Disabling ssh connection caching. +Cases: 3 Tried: 2 Errors: 0 Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex drop:2:untrusted remote +git clone failed +Cases: 3 Tried: 3 Errors: 0 Failures: 2 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex get +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex move +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex copy +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex unlock/lock +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 2 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex edit/commit:0 +git clone failed +Cases: 2 Tried: 1 Errors: 0 Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex edit/commit:1 +git clone failed +Cases: 2 Tried: 2 Errors: 0 Failures: 2 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex fix +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex trust/untrust/semitrust/dead +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 4 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex fsck:0 +git clone failed +Cases: 4 Tried: 1 Errors: 0 Failures: 1/media/freebox/.t/tmprepo3/refs: No such file or directory + ### Failure in: git-annex fsck:1 +git clone failed +Cases: 4 Tried: 2 Errors: 0 Failures: 2/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex fsck:2 +git clone failed +Cases: 4 Tried: 3 Errors: 0 Failures: 3/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex fsck:3 +git clone failed +Cases: 4 Tried: 4 Errors: 0 Failures: 4 +Cases: 2 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex migrate:0 +git clone failed +Cases: 2 Tried: 1 Errors: 0 Failures: 1/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex migrate:1 +git clone failed +Cases: 2 Tried: 2 Errors: 0 Failures: 2 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex unused/dropunused +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex describe +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex find +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex merge +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex status +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex version +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex sync +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: union merge regression +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: automatic conflict resolution +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex map +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex uninit +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex upgrade +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex whereis +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex hook remote +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex directory remote +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex rsync remote +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex bup remote +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +Cases: 1 Tried: 0 Errors: 0 Failures: 0/media/freebox/.t/tmprepo3/.git: No such file or directory + ### Failure in: git-annex crypto +git clone failed +Cases: 1 Tried: 1 Errors: 0 Failures: 1 +---------------------------------------------------------------------- +get +---------------------------------------------------------------------- +move +---------------------------------------------------------------------- +copy +---------------------------------------------------------------------- +lock +---------------------------------------------------------------------- +edit +---------------------------------------------------------------------- +fix +---------------------------------------------------------------------- +trust +---------------------------------------------------------------------- +fsck +---------------------------------------------------------------------- +migrate +---------------------------------------------------------------------- + unused +---------------------------------------------------------------------- +describe +---------------------------------------------------------------------- +find +---------------------------------------------------------------------- +merge +---------------------------------------------------------------------- +status +---------------------------------------------------------------------- +version +---------------------------------------------------------------------- +sync +---------------------------------------------------------------------- +union merge regression +---------------------------------------------------------------------- +conflict resolution +---------------------------------------------------------------------- +map +---------------------------------------------------------------------- +uninit +---------------------------------------------------------------------- +upgrade +---------------------------------------------------------------------- +whereis +---------------------------------------------------------------------- +hook remote +---------------------------------------------------------------------- +directory remote +---------------------------------------------------------------------- +rsync remote +---------------------------------------------------------------------- +bup remote +---------------------------------------------------------------------- +crypto +git-annex: .t/repo/.git/annex: removeDirectory: unsatisified constraints (Directory not empty) + +# End of transcript or log. +"""]] diff --git a/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment b/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment new file mode 100644 index 000000000..623028c80 --- /dev/null +++ b/doc/bugs/test_suite_failure_on_samba_mount/comment_1_e074b20801b921ee2661025a050a8af2._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.63" + subject="seems like a general git problem" + date="2013-08-24T19:55:56Z" + content=""" +\"unable to create temporary sha1 filename\" is a git error message. I don't actually see any git-annex failure here, just a git failure that seems to lead to a cascade of other failures. + +I'm not sure if the \"/media/freebox/.t/tmprepo3/.git: No such file or directory\" is because git clone has failed due to the other errors, or if git clone somehow failed to set up the .git directory. + +It would probably be helpful to have a play around with git on this filesystem and see what breaks. Alternatively, you can use git-annex with `--debug` to see the git commands it's running that fail, and try them yourself and perhaps strace or gdb them or something to see where they go wrong. +"""]] 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 new file mode 100644 index 000000000..25db6d829 --- /dev/null +++ b/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build.mdwn @@ -0,0 +1,9 @@ +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... 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 new file mode 100644 index 000000000..d67330a22 --- /dev/null +++ b/doc/bugs/typo_on_the_Mac_OS_10.7.5_Lion_build/comment_1_e8df4b36a89b37edd94f3a318ae93a32._comment @@ -0,0 +1,8 @@ +[[!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/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn b/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn index 509e12aeb..c31205ede 100644 --- a/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn +++ b/doc/bugs/unannex_and_uninit_do_not_work_when_git_index_is_broken.mdwn @@ -12,3 +12,6 @@ git's index broke and I was unable to restore it. While this is not git-annex' p % Ttbomk, the softlinks and objects are enough to un-annex the files; side-stepping git's index if necessary. + +> `git annex repair` can now repair broken index files and other +> git repository corruption. [[done]] --[[Joey]] diff --git a/doc/bugs/unfinished_repos_in_webapp.mdwn b/doc/bugs/unfinished_repos_in_webapp.mdwn new file mode 100644 index 000000000..b3e667c61 --- /dev/null +++ b/doc/bugs/unfinished_repos_in_webapp.mdwn @@ -0,0 +1,31 @@ +### Please describe the problem. + +Hi, all excited that the new release fixes the unknown UUID issue in the Webapp I hurridly installed the latest versions. + +Some progress in that the webapp now reports my missing/non-existent repo as an "unfinished repository" in the process of being setup. I see a check status box that when clicked says "in progress please be patient". Also I see the ssh config has changed to use IdentitiesOnly option. + +I had a go a deleting details via git-annex vicfg and directly editing the git-annex branch log files as detailed [here](http://git-annex.branchable.com/forum/Reappearing_repos_in_webapp_and_vicfg/). But still no joy. + +Any hints on what to do? Nothing in the log seems to help... + +### What steps will reproduce the problem? + +Not sure anymore. + +### What version of git-annex are you using? On what operating system? + +Latest. + +### 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 [[done]], at least the bug reporter didn't feel the need +> to follow up with the info I asked for and says the problem does not +> affect him. --[[Joey]] diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment b/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment new file mode 100644 index 000000000..e17c1b899 --- /dev/null +++ b/doc/bugs/unfinished_repos_in_webapp/comment_1_9628b100e39489be9f28ef75276a7341._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 1" + date="2013-08-07T16:07:56Z" + content=""" +It seems to me that it has already finished applying the workaround. That IdentitiesOnly change could only be made +if you clicked on a Retry button once it detected a problem. + +You may be experiencing a different problem that it cannot recover from. Paste your .git/config file. +"""]] diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment b/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment new file mode 100644 index 000000000..8170a0175 --- /dev/null +++ b/doc/bugs/unfinished_repos_in_webapp/comment_2_ba0fbff536b1d067c4098db401dc49f2._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnXybLxkPMYpP3yw4b_I6IdC3cKTD-xEdU" + nickname="Matt" + subject="comment 2" + date="2013-08-08T08:33:32Z" + content=""" +Hi, I've sorted this now. The IP address of my laptop had changed on the local network. Fixing it then let the new fix fully work and the in-progress status of the bad repo went away. + +Is it right that in the UI I don't see the local LAN configured branch (which I setup for speed) - it all seems to come under the jabber account now and makes an appropriate choice? +"""]] diff --git a/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment b/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment new file mode 100644 index 000000000..cd21af092 --- /dev/null +++ b/doc/bugs/unfinished_repos_in_webapp/comment_3_fd554aa7d93117177784a29270ccf790._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawniayrgSdVLUc3c6bf93VbO-_HT4hzxmyo" + nickname="Tobias" + subject="comment 3" + date="2013-08-08T12:22:28Z" + content=""" +I also see `unfinished repository` in the assistant, but only at git remotes which don't have git-annex installed (f.e. gitlab). annex-ignore is set to true: `git config remote.gitlab.annex-ignore true`. + +Clicking on `check status` says `Setting up this repository seems to have stalled! Make sure the remote system is available and retry` + +git-annex version: 4.20130802-g1452ac3 +"""]] diff --git a/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn b/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn new file mode 100644 index 000000000..848f1b30b --- /dev/null +++ b/doc/bugs/unfinished_repository_when_using_annex-ignore_true_.mdwn @@ -0,0 +1,25 @@ +### 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/utf8.mdwn b/doc/bugs/utf8.mdwn index 61640ec5f..73b9bd9a9 100644 --- a/doc/bugs/utf8.mdwn +++ b/doc/bugs/utf8.mdwn @@ -185,3 +185,8 @@ ok # End of transcript or log. """]] + +> We seem to have reached a point of confusion, lack of information, +> and/or diminishing returns with this bug report. I have fixed +> it as best I can. If you have any problems, please file a new bug report +> with as complete information as possible. [[done]] --[[Joey]] diff --git a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn new file mode 100644 index 000000000..64e83526f --- /dev/null +++ b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working.mdwn @@ -0,0 +1,28 @@ +### Please describe the problem. +on [[tips/downloading_podcasts/]] it says to look for "Feeds" in the output of version to see if you have the importfeeds support. I have importfeeds support but "Feeds" is not listed when doing version. + +### What steps will reproduce the problem? +# git-annex version +# git-annex importfeed <someurl> + +### What version of git-annex are you using? On what operating system? +4.20130802 on Debian unstable + +### Please provide any additional information below. + +[[!format sh """ +greg@x200s:~/annextest$ git-annex version +git-annex version: 4.20130802 +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 + +greg@x200s:~/annextest$ git-annex importfeed http://feeds.feedburner.com/OpenMetalcast/ogg +(checking known urls...) +importfeed http://feeds.feedburner.com/OpenMetalcast/ogg +....<downloads the episodes etc> +"""]] + +> Forgot I had to manually add that. [[done]] (really this time!) --[[Joey]] diff --git a/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment new file mode 100644 index 000000000..8b156f822 --- /dev/null +++ b/doc/bugs/version_doesn__39__t_show___34__Feeds__34___but_podcasting_feature_working/comment_1_ce06ba4f65f322362b23797f6190c7c3._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="http://a-or-b.myopenid.com/" + ip="203.45.2.230" + subject="comment 1" + date="2013-09-04T01:36:46Z" + content=""" +This still is not fixed. :-( + + $ git annex version + git-annex version: 4.20130827 + build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS + + +...but the ```importfeed``` functionality works. + +I know this isn't a particularly high priority bug... +"""]] 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 new file mode 100644 index 000000000..a1f490061 --- /dev/null +++ b/doc/bugs/web_app_loops_over_a_non-addable_file.mdwn @@ -0,0 +1,56 @@ +### 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:_difficult_to_abort_adding_a_repository.mdwn b/doc/bugs/webapp:_difficult_to_abort_adding_a_repository.mdwn new file mode 100644 index 000000000..41007dbb4 --- /dev/null +++ b/doc/bugs/webapp:_difficult_to_abort_adding_a_repository.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. +I could not find a way to abort the addition of a new remote repository. + +### What steps will reproduce the problem? +- start adding a remote repository (unencrypted, with git-annex installed); +- forget to create the folder on the remote host; +- navigate away from the repository page; +- the dashboard says the repository is partially set-up, and the only thing one can do is look at the log (which says the folder is missing). + +I was able to solve it by creating another repository with the exact same data. + +### What version of git-annex are you using? On what operating system? + +Version: 4.20131002-gf25991c on OS X 10.8.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. +"""]] diff --git a/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn b/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn new file mode 100644 index 000000000..54f6c3a4f --- /dev/null +++ b/doc/bugs/webapp_usability:_put_the_notices_on_the_right.mdwn @@ -0,0 +1,18 @@ +### Please describe the problem. + +The colored notices on the left of the screen are a little off. When they disappear, it also leaves a huge gap on the left side. + +### What steps will reproduce the problem? + +Click the `X` on all the messages on the left. + +### What version of git-annex are you using? On what operating system? + +4.20130815~bpo70+1 on Debian Wheezy, with Chromium Version 29.0.1547.57 Debian 7.1 (217859) + +### Please provide any additional information below. + +This is admittedly a very mild problem, but from a usability perspective, it would be less confusing to show those on the right. When they were gone, I thought git-annex was broken somewhat... -- [[anarcat]] + +> [[done]], although I'm not sure I'm sold on their being on the right +> being better. --[[Joey]] diff --git a/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment b/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment new file mode 100644 index 000000000..a494c5326 --- /dev/null +++ b/doc/bugs/webapp_usability:_put_the_notices_on_the_right/comment_1_ec7a444e09a028b5225bd41fb83442e8._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 1" + date="2013-09-09T04:36:12Z" + content=""" +They're on the left hand side because that's where Bootstrap puts its sidebar. +If someone knows how to make it put its sidebar on the right I'll happily do so. +"""]] diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn b/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn new file mode 100644 index 000000000..0413bb55d --- /dev/null +++ b/doc/bugs/windows_fails_test___34__recoverEncode__34__.mdwn @@ -0,0 +1,39 @@ +### Please describe the problem. + +My windows install (2013-09-09) fails "quick checks" when running "git annex test". See below the errors from two seperate runs of the test in two fresh empty directories: + +*** Failed! Exception: 'recoverEncode: invalid argument (invalid character)' (after 13 tests): +Key {keyName = "\140\DEL\159/\RS'", keyBackendName = "WQACSWJDVY", keySize = Just 6, keyMtime = Just 3} +prop_idempotent_configEscape + +*** Failed! Exception: 'recoverEncode: invalid argument (invalid character)' (after 4 tests): +Key {keyName = "\130", keyBackendName = "Y", keySize = Nothing, keyMtime = Nothing} +prop_idempotent_configEscape + +### What steps will reproduce the problem? + +create a directory +cd to it in cmd or Git Bash +run "git annex test" + + +### What version of git-annex are you using? On what operating system? + +OS Name: Microsoft Windows 7 Professional (64bit) +OS Version: 6.1.7601 Service Pack 1 Build 7601 + +Install Git-1.8.3-preview20130601 (third option to add git and tools to path) +Install git-annex-installer (2013-09-09) + +### 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 released a fix for this problem. Thanks for reporting! [[done]] +> --[[Joey]] diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment new file mode 100644 index 000000000..e94608921 --- /dev/null +++ b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_1_424b3536e21e02f192f7f2b8e833ed18._comment @@ -0,0 +1,67 @@ +[[!comment format=mdwn + username="gary" + ip="82.112.140.250" + subject="Thanks for the fix" + date="2013-09-12T07:20:12Z" + content=""" +Hi the fix works fine, all the tests pass now. However I am having issues when trying to sync two directories. I have had this working in direct mode in fedora but not in the previously mentioned windows install + +2 directories d1 and d2. + +SETUP: + +cd d1 + +mkdir annex + +cd annex + +cp someFile . (as get branch issue if empty) + +git init + +git annex init d1 + +cp someFile . (as get branch issue if empty) + +git annex add . + +git annex sync + +cd ..\..\d2 + +git clone ..\..\d1\annex + +cd annex + +git annex init d2 + +git remote add d1 ..\..\d1\annex + +cd ..\..\d1\annex + +git remote add d2 ..\..\d2\annex + + +SYNCING + +cd d1\annex + +cp someFiles . + +git annex add . + +git annex sync + +cd ..\..\d2\annex + +git annex sync + +git annex mirror --from d1 + +It looks like the files copy across but when I look at them in explorer they are still just the place holders. + +any ideas on what may be going on. Does the work flow look correct? + +(ps typo on all slashes but +"""]] diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment new file mode 100644 index 000000000..f186a0d81 --- /dev/null +++ b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_2_78db183aa401e2023d7faec5f7a4a573._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 2" + date="2013-09-13T17:04:26Z" + content=""" +That is an unrelated bug. You got very lucky that I saw your followup comment. + +I was able to reproduce it, and found bug in git annex fsck that prevented it from finding and fixing this problem on Windows. Am still investigating why the problem occurs in the first place.. +"""]] diff --git a/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment new file mode 100644 index 000000000..a8f7c0a02 --- /dev/null +++ b/doc/bugs/windows_fails_test___34__recoverEncode__34__/comment_3_ed2da19eaf0bd0864f6b28816a79bc23._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.2.134" + subject="comment 3" + date="2013-09-13T17:44:04Z" + content=""" +I have now diagnosed and fixed the underlying problem on Windows. +"""]] diff --git a/doc/bugs/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn b/doc/bugs/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn deleted file mode 100644 index 0dc9ec08a..000000000 --- a/doc/bugs/wishlist:_allow_users_to_provide_UUID_when_running___96__git_annex_init__96__.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -As there's no way to permanently hide remotes and I have to recreate two repos now, I would love to be able to re-use the old UUIDs to remove clutter. - -> git-annex already provides a way to do this: Copy `.git/config` from the -> original repo (or use `git-config` to set `annex.uuid`) *before* running -> `git annex init`. [[done]] --[[Joey]] diff --git a/doc/bugs/wishlist:_generic_annex.cost-command.mdwn b/doc/bugs/wishlist:_generic_annex.cost-command.mdwn deleted file mode 100644 index 6adf1460e..000000000 --- a/doc/bugs/wishlist:_generic_annex.cost-command.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -### Current setup - -ATM git-annex has - -remote.<name>.annex-cost -remote.<name>.annex-cost-command # command is not provided cmdline options by annex - -to set the cost for a given remote. That requires setting up one of those variables per each host, and possibly hardcoding options for the annex-cost-command providing e.g. the remote name. - -### Suggestion - -wouldn't it be more general and thus more flexible to have a repository-wide - -annex.cost-command - -which could take options %remote, %file and assessed accordingly per each file upon '--get' request to allow maximal flexibility: e.g. some files might better be fetched from remotes supporting transfer compression, some from the web, etc. Also it might be worth providing %remote_kind ("special" vs "git") to disambiguate %remote's? - diff --git a/doc/bugs/wishlist:_make_git_annex_reinject_work_in_direct_mode.mdwn b/doc/bugs/wishlist:_make_git_annex_reinject_work_in_direct_mode.mdwn deleted file mode 100644 index 41c8e574b..000000000 --- a/doc/bugs/wishlist:_make_git_annex_reinject_work_in_direct_mode.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -### Please describe the problem. - -`git annex reinject` refuses to work while in direct mode. - -When in direct mode git annex reinject could simply perform `rm $symlink; mv $file_copy .; git annex add $file`. I prefer having git annex doing that so I am sure I am not messing up (mistakenly adding new files for instance) and everything is properly managed. - -### What version of git-annex are you using? On what operating system? - -git-annex 4.20130516.1 - -~~~~ -$ lsb_release -a -No LSB modules are available. -Distributor ID: Ubuntu -Description: Ubuntu 12.04.2 LTS -Release: 12.04 -Codename: precise -~~~~ diff --git a/doc/bugs/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn b/doc/bugs/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn deleted file mode 100644 index 3a891fc9b..000000000 --- a/doc/bugs/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -as of git-annex version 3.20110719, all git-annex commits only contain the word "update" as a commit message. given that the contents of the commit are pretty non-descriptive (SHA1 hashes for file names, uuids for repository names), i suggest to have more descriptive commit messages, as shown here: - - /mnt/usb_disk/photos/2011$ git annex get - /mnt/usb_disk/photos/2011$ git show git-annex - [...] - usb-disk-photos: get 2011 - - * 10 files retrieved from 2 sources (9 from local-harddisk, 1 from my-server) - * 120 files were already present - * 2 files could not be retrieved - /mnt/usb_disk/photos/2011$ cd ~/photos/2011/07 - ~/photos/2011/07$ git copy --to my-server - ~/photos/2011/07$ git show git-annex - [...] - local-harddisk: copy 2011/07 to my-server - - * 20 files pushed - ~/photos/2011/07$ - -in my opinion, the messages should at least contain - -* what command was used -* in which repository they were executed -* which files or directories they affected (not necessarily all files, but what was given on command line or implicitly from the working directory) - ---[[chrysn]] - -> The implementation of the git-annex branch precludes more descriptive -> commit messages, since a single commit can include changes that were -> previously staged to the branch's index file, or spooled to its journal -> by other git-annex commands (either concurrently running or -> interrupted commands, or even changes needed to automatically merge -> other git-annex branches). -> -> It would be possible to make it *less* verbose, with an empty commit -> message. :) --[[Joey]] - ->> Closing as this is literally impossible to do without making ->> git-annex worse. [[done]] --[[Joey]] diff --git a/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn b/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn deleted file mode 100644 index 7a9b81f72..000000000 --- a/doc/bugs/wishlist:_option_to_print_more_info_with___39__unused__39__.mdwn +++ /dev/null @@ -1,37 +0,0 @@ -It would be nice if the 'unused' command could optionally display info about the actual files behind its cryptic keys. - -I created a (very rough) bash script that simply splices in some info from git log -S'KEY' --numstat into the unused list, like so: - - arand@mas:~/annex(master)$ bash ~/utv/scripts/annex-vunused - unused . (checking for unused data...) (checking master...) (checking synced/master...) (checking origin/HEAD...) (checking seagate/master...) - Some annexed data is no longer used by any files: - NUMBER KEY - 1 SHA256E-s1073741824--49bc20df15e412a64472421e13fe86ff1c5165e18b2afccf160d4dc19fe68a14.img - 8f479a4 Sat Feb 23 16:14:12 2013 +0100 remove bigfile - 0 1 dummy_bigfile.img - 2988d18 Sat Feb 23 16:13:48 2013 +0100 dummy file - 1 0 dummy_bigfile.img - (To see where data was previously used, try: git log --stat -S'KEY')To remove unwanted data: git-annex dropunused NUMBER - ok -The script: - - #!/bin/bash - - pipe="$(mktemp -u)" - mkfifo "$pipe" - - git annex unused >"$pipe" || exit 1 & - - while read -r line - do - key="$(echo "$line" | sed 's/^[^-]*-\([^-]*\)-.*/\1/')" - echo -n "$line" - test -n "$key" && \ - echo && \ - git log --format="%h %cd %s" --numstat -S"$key" | \ - sed '/^$/d;/git-annex automatic sync/,/^ /d;s/^/\t\t/' - - done < "$pipe" - rm "$pipe" - -It would be nice if something like this was available as an option, since it's good way to get a quick overview of what the content is, and if it's safe to drop it. diff --git a/doc/bugs/wishlist:_query_things_like_description__44___trust_level.mdwn b/doc/bugs/wishlist:_query_things_like_description__44___trust_level.mdwn deleted file mode 100644 index d158850cd..000000000 --- a/doc/bugs/wishlist:_query_things_like_description__44___trust_level.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -It would be helpful to have a way to query things like a repository's description and trust level, without having to poke in the git-annex branch. For example, "git annex describe ." currently clears the description but could print the current one instead. - -> `git annex status` now breaks down the repository list by type. [[done]] -> --[[Joey]] diff --git a/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment b/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment deleted file mode 100644 index 3ac4ba267..000000000 --- a/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_1_14311384788312b96e550749ab7de9ea._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2011-10-27T17:09:33Z" - content=""" -`git annex describe` only sets the description to avoid complication. Imagine using it in a script for example. - -`git annex status` shows the description. It does not show the trust level because I have not thought of a visually pleasing and compact way to show it in the repository list there.. suggestions appreciated, since the same list is used by `whereis`, and showing trust levels there would be particularly useful. -"""]] diff --git a/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment b/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment deleted file mode 100644 index 3bb92919f..000000000 --- a/doc/bugs/wishlist:_query_things_like_description__44___trust_level/comment_2_342d1ac07573c7ef4e27f003a692e261._comment +++ /dev/null @@ -1,32 +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-10-29T18:28:13Z" - content=""" -Possible solutions: - -This: - - trusted repositories: - UUID -- foo - semi-trusted repositories: - UUID -- bar - untrusted repositories: - UUID -- baz - -or this: - - UUID -- trusted -- foo - UUID -- semi-trusted -- bar - UUID -- untrusted -- baz - -or this: - - known repositories (!/*/X): - UUID -- ! foo - UUID -- * bar - UUID -- X baz - -If you want to reformat this output, putting 'here', 'origin', etc into fixed formatting might make sense, as well. -- Richard -"""]] diff --git a/doc/bugs/wishlist:_simple_url_for_webapp.mdwn b/doc/bugs/wishlist:_simple_url_for_webapp.mdwn deleted file mode 100644 index 4549f2e74..000000000 --- a/doc/bugs/wishlist:_simple_url_for_webapp.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -### Please describe the problem. - -The environment is os/x with chrome as the browser. - -Let's say I close the tab with the webapp running in it. The 'git-annex webapp' process is still running, according to 'ps'. - -So I open a new tab, but then what do I type into the browser url bar to get the app back? What is usually there is a loopback address and an authorisation hash. - -* Should I double-click on the git-annex icon in the dock (or Applications directory)? -* I figured out from observing the startup that if I give the url ://localhost/Users/me/annex/.git/annex/webapp.html I will get redirected to the right place. -Should I set up a bookmark for that? - -### What steps will reproduce the problem? - -see above. - -### What version of git-annex are you using? On what operating system? - -Version: 4.20130723-ge023649 -Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS -os: os/x 10.8.4 - -### Please provide any additional information below. - -I notice that in the webapp ui, all the items at the top of the page highlight when one hovers over them and have useful URLs attached, -with the exception of the 'git-annex' item at the far left.What if that had the entry point url attached to it (so one could bookmark that)? - -> The git-annex assistant is designed to stay running in the background whether you have the web browser open or not. You can open the web display at any time by -> using the git-annex menu item (on linux) or running the git-annex-webapp -> program (which is in the DMG on OSX). -> -> If the file:// url were exposed to users, it would not work if -> the assistant had not already been started. This is why there is a program -> to open the webapp, not an url. -> -> Not a bug; [[done]] --[[Joey]] diff --git a/doc/bugs/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment b/doc/bugs/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment deleted file mode 100644 index 1211be9b5..000000000 --- a/doc/bugs/wishlist:_simple_url_for_webapp/comment_1_552aad504fbb68d1f85abfde8c535e69._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY" - nickname="Vincent" - subject="comment 1" - date="2013-07-24T14:46:22Z" - content=""" -typo - -url should be - file://localhost/Users/me/annex/.git/annex/webapp.html -"""]] diff --git a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn b/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn deleted file mode 100644 index 24cacbf71..000000000 --- a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -Currently there is no way to drop files, or list what files are available, on a special remote. -It would be good if "git annex drop" and "git annex find" supported the --from argument. - -> I agree, drop should support --from. ->> [[done]] --[[Joey]] -> -> To find files *believed* to be present in a given remote, use -> `git annex find --in remote` -> Note that it might show out of date info, since it does not actually go -> check the current contents of the remote. The only reason to support -> `find --from` would be to always check, but I don't think that's needed. -> --[[Joey]] - -For commands that don't support the --from argument, it would also be nice to print an error. -Currently running "git annex drop --from usbdrive" doesn't behave as hoped and instead drops -all content from the local annex. - -> This is done now. --[[Joey]] diff --git a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment b/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment deleted file mode 100644 index 6028933b4..000000000 --- a/doc/bugs/wishlist:_support_drop__44___find_on_special_remotes/comment_1_f11ed642a83d965076778a162f701e84._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://joey.kitenet.net/" - nickname="joey" - subject="comment 1" - date="2011-10-27T17:13:43Z" - content=""" -Well, I don't think you mean \"special remotes\", but just any old remote (special or not). -"""]] diff --git a/doc/bugs/youtube_support_suddenly_stopped_working.mdwn b/doc/bugs/youtube_support_suddenly_stopped_working.mdwn new file mode 100644 index 000000000..bedda7674 --- /dev/null +++ b/doc/bugs/youtube_support_suddenly_stopped_working.mdwn @@ -0,0 +1,62 @@ +### 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]] |