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

6 files changed, 243 insertions, 0 deletions

diff --git a/doc/bugs/Metadata_changes_are_not_reflected_in_a_view.mdwn b/doc/bugs/Metadata_changes_are_not_reflected_in_a_view.mdwn
new file mode 100644
index 000000000..cf8e1063c
--- /dev/null
+++ b/doc/bugs/Metadata_changes_are_not_reflected_in_a_view.mdwn
@@ -0,0 +1,31 @@
+### Please describe the problem.
+Changing metadata while being in an active view will not update the view.
+
+### What steps will reproduce the problem?
+(inside a repository)
+
+1. Create a file
+
+        $ uuidgen >file
+
+2. switch into a view
+
+       $ git annex view !blah
+       $ ls
+       file
+
+3. changed the metadata the view is based upon
+
+       $ git annex metadata -t blah file
+       $ ls
+       file
+
+   It would be nice/expected that the view gets updated when the metadata changes, hiding 'file' now
+  
+
+### What version of git-annex are you using? On what operating system?
+
+git-annex version: 5.20141024~bpo70+1
+on debian wheezy with backports
+
+### Please provide any additional information below.
diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state.mdwn b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state.mdwn
new file mode 100644
index 000000000..c7231cd1b
--- /dev/null
+++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state.mdwn
@@ -0,0 +1,151 @@
+### Please describe the problem.
+Shortly after starting the assistant the local client repository is in an inconsistent state. Just using the cli works fine without destroying the repository.
+
+### What steps will reproduce the problem?
+- Working git annex repository
+
+- Start the Git-Annex Assistant
+> git annex assistant
+
+- Wait a short time and then check the repository state:
+> ➜  annex git:(master) ✗ gst
+> On branch master
+> error: Could not read ea63b58d1252e3432280cdce1282eb02035c926e
+> error: Could not read ea63b58d1252e3432280cdce1282eb02035c926e
+> fatal: Failed to traverse parents of commit 108fa97a989aeabff16738558e1aa636c836598b
+
+- refs/heads/synced/git-annex links to an unknown commit
+> ➜  .git git:(master) cat refs/heads/synced/git-annex
+> be8e6023fbb172b12cec8fdbaa8654194f71c4f5% 
+
+> git show be8e6023fbb172b12cec8fdbaa8654194f71c4f5
+> fatal: unable to read source tree (d2959525362dcadd4dbec96a8f18d80cc689a851)
+
+### What version of git-annex are you using? On what operating system?
+- git-annex version: 5.20150508-gf71c23f
+- Mac OSX 10.10.2
+
+### Please provide any additional information below.
+
+[[!format sh """
+
+[2015-05-15 07:06:32 CEST] main: starting assistant version 5.20150508-gf71c23f
+[2015-05-15 07:06:32 CEST] Cronner: Consistency check in progress
+fsck 2015-05-01 07.56.02.jpg (checksum…)
+ok
+fsck 2015-05-01 09.55.58.jpg (checksum…)
+ok
+fsck 2015-05-14 12.38.24.jpg (checksum…)
+ok
+fsck 2015-05-14 12.39.30.jpg (checksum…)
+ok
+fsck 2015-05-14 12.40.49.jpg (checksum…)
+ok
+fsck 2015-05-14 12.40.53.jpg (checksum…)
+ok
+fsck 2015-05-14 12.43.42.jpg (checksum…)
+ok
+fsck 2015-05-14 12.44.16.jpg (checksum…)
+ok
+fsck 2015-05-14 12.45.11.jpg (checksum…)
+ok
+(recording state in git…)
+[2015-05-15 07:06:39 CEST] TransferScanner: Syncing with nas 
+(scanning…) [2015-05-15 07:06:39 CEST] Watcher: Performing startup scan
+gpg: Unterschrift vom Fr  8 Mai 22:10:28 2015 CEST mittels DSA-Schlüssel ID 89C809CB
+gpg: Unterschrift kann nicht geprüft werden: Öffentlicher Schlüssel nicht gefunden
+(started…) 
+[2015-05-15 07:06:41 CEST] Committer: Committing changes to git
+(recording state in git…)
+[2015-05-15 07:06:41 CEST] Pusher: Syncing with nas 
+
+
+0%            0.0 B/s 0s
+2%          32.0KB/s 47s
+...
+90%         467.6KB/s 0s
+                        
+[2015-05-15 07:06:47 CEST] Transferrer: Uploaded 2015-05-1..38.24.jpg
+
+
+0%            0.0 B/s 0s
+1%          32.0KB/s 54s
+...
+91%         534.5KB/s 0s
+                        
+[2015-05-15 07:06:54 CEST] Transferrer: Uploaded 2015-05-1..45.11.jpg
+
+
+0%            0.0 B/s 0s
+2%        16.0KB/s 1m30s
+…
+90%         440.4KB/s 0s
+                        
+[2015-05-15 07:07:01 CEST] Transferrer: Uploaded 2015-05-1..44.16.jpg
+
+
+0%            0.0 B/s 0s
+1%        16.0KB/s 1m42s
+...
+91%         508.2KB/s 0s
+                        
+[2015-05-15 07:07:07 CEST] Transferrer: Uploaded 2015-05-1..43.42.jpg
+
+
+0%            0.0 B/s 0s
+1%        16.0KB/s 1m40s
+...
+91%         371.6KB/s 0s
+                        
+[2015-05-15 07:07:13 CEST] Transferrer: Uploaded 2015-05-1..40.53.jpg
+
+
+0%            0.0 B/s 0s
+1%          32.0KB/s 50s
+...
+91%         495.1KB/s 0s
+                        
+[2015-05-15 07:07:19 CEST] Transferrer: Uploaded 2015-05-1..40.49.jpg
+
+
+0%            0.0 B/s 0s
+1%          32.0KB/s 53s
+...
+92%         528.2KB/s 0s
+                        
+[2015-05-15 07:07:25 CEST] Transferrer: Uploaded 2015-05-1..39.30.jpg
+ssh: connect to host 1.2.3.43 port 22: Operation timed out
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights
+and the repository exists.
+fatal: ‚/Volumes/WD1500GB/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.
+ssh: connect to host 1.2.3.43 port 22: Operation timed out
+s(recording state in git…)
+fatal: ‚/Volumes/WD1500GB/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.
+ssh: connect to host 1.2.3.43 port 22: Operation timed out
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights
+and the repository exists.
+[2015-05-15 07:08:16 CEST] Cronner: Attempting to repair aether [here]
+Unpacking all pack files.
+ssh: connect to host 1.2.3.43 port 22: Operation timed out
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights
+and the repository exists.
+ssh: connect to host 1.2.3.36 port 22:sssssh: connect to host 1.2.3.43 port 22: Operation timed out
+fatal: early EOF
+
+
+# End of transcript or log.
+"""]]
diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment
new file mode 100644
index 000000000..be48ca87f
--- /dev/null
+++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="Marco"
+ subject="git annex repair --force"
+ date="2015-05-15T08:01:25Z"
+ content="""
+This command removed all history. It looks like no file was ever added.
+
+Any idea how I should handle this client repository? I could clone again from a backup. Is it possible to keep the annex UUID for a new clone?
+"""]]
diff --git a/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_2_5c5e7356cae8ddf8d2c8964fb69000f5._comment b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_2_5c5e7356cae8ddf8d2c8964fb69000f5._comment
new file mode 100644
index 000000000..5d39e8ac2
--- /dev/null
+++ b/doc/bugs/OSX:_Assistant_leaves_repo_in_inconsistent_state/comment_2_5c5e7356cae8ddf8d2c8964fb69000f5._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="Marco"
+ subject="Disaster recovery"
+ date="2015-05-15T09:40:16Z"
+ content="""
+Ah, found it:
+
+https://git-annex.branchable.com/design/assistant/disaster_recovery/
+
+> As long as the git repository has at least one remote, another method is to clone the remote, sync from all other remotes, move over .git/config and .git/annex/objects, and tar up the old broken git repo and git annex add it
+"""]]
diff --git a/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn b/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn
new file mode 100644
index 000000000..1e4efe9da
--- /dev/null
+++ b/doc/bugs/transfer_in_progress_not_present_in_json_output.mdwn
@@ -0,0 +1,28 @@
+### Please describe the problem.
+
+i can't find a key in the JSON output of `git annex info` for the "transfer in progress" field. is it missing on purpose? or am I missing some field?
+
+### What steps will reproduce the problem?
+
+<pre>
+git annex info
+git annex info --json
+</pre>
+
+
+### What version of git-annex are you using? On what operating system?
+5.20150406-g2a9fbec debian jessie
+
+### Please provide any additional information below.
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+anarcat@desktop008:mp3$ git annex info  --fast --json | grep -i transfer
+anarcat@desktop008:mp3$ git annex info  --fast | grep -i transfer
+transfers in progress:
+
+# End of transcript or log.
+"""]]
+
+[[anarcat]]
diff --git a/doc/devblog/day_285__tuning_git-annex_unused_refs/comment_1_a3f0dd4fc8457af7c72040fbe8fd5fee._comment b/doc/devblog/day_285__tuning_git-annex_unused_refs/comment_1_a3f0dd4fc8457af7c72040fbe8fd5fee._comment
new file mode 100644
index 000000000..a94383fa2
--- /dev/null
+++ b/doc/devblog/day_285__tuning_git-annex_unused_refs/comment_1_a3f0dd4fc8457af7c72040fbe8fd5fee._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="anarcat"
+ subject="mailing lists and support sites"
+ date="2015-05-14T20:26:59Z"
+ content="""
+after years subscribing to zillions of them, i have acquired an allergy to mailing lists. it seems that i get this every once in a while: i'm subscribed to a bunch of them and i stop reading and just hit \"d\" on my mail client. :)
+
+i think there are very interesting alternatives, online web forums (yes yes, i know, bear with me) where knowledge is established and shared instead of just having a threaded conversation. i'm thinking of http://ask.debian.net/ or the stackexchange sites. as i [[analysed before|devblog/day_268_stressed_out/#comment-e0814585df0047e6d4e11515aebe1dec]], the forum is the biggest part of this website (and consequently the git-annex source code!), bug tracker coming in second, and the two together forming the majority of disk usage of the git repository.  there are alternative discussion tools like discourse.org that may also be interesting for people wanting to run such a service.
+
+anyways, the ideas of those is to converge on a set of FAQs and knowledge items more than just have random discussion, and force people to reuse existing topics.
+
+if i had more time, i'd probably setup something like this but really, i can only encourage those initiatives at this point. :)
+"""]]