diff options
Diffstat (limited to 'doc')
9 files changed, 116 insertions, 0 deletions
diff --git a/doc/bugs/Android:_Several_error_messages___47___warnings/comment_4_b38b675a2862d527fad28b7477f7ddde._comment b/doc/bugs/Android:_Several_error_messages___47___warnings/comment_4_b38b675a2862d527fad28b7477f7ddde._comment new file mode 100644 index 000000000..81e0c0fa0 --- /dev/null +++ b/doc/bugs/Android:_Several_error_messages___47___warnings/comment_4_b38b675a2862d527fad28b7477f7ddde._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2015-10-12T17:15:30Z" + content=""" +The assistant will use whatever git remotes and git-annex configuration is +present in the repository when it's started up. +"""]] diff --git a/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment b/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment new file mode 100644 index 000000000..d394ca039 --- /dev/null +++ b/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-10-12T18:52:42Z" + content=""" +You seem to be talking about using https to access a git repository. + +git-annex is not generally able to use https as a transport -- ie, it +can maybe download files from a git repository over https, if +the repository is set up just right. But it can't upload file to that +repository, nor can it promptly notice when changes are synced to that +repository from elsewhere. + +So, there's not much that the assistant can do with such a repository. + +You'll be better off using ssh for your git-annex repositories. +"""]] diff --git a/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_2_1c153ecedc231f5cd4d6b2f081721494._comment b/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_2_1c153ecedc231f5cd4d6b2f081721494._comment new file mode 100644 index 000000000..ca1d9a98f --- /dev/null +++ b/doc/bugs/STANDARD__95__IA_for_S3_remote_not_working/comment_2_1c153ecedc231f5cd4d6b2f081721494._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-10-12T17:08:06Z" + content=""" +The feature is supported in git-annex, but it needs a version of the aws +library that has not seen a stable release yet. +"""]] diff --git a/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck.mdwn b/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck.mdwn index f30bc1d52..49156e366 100644 --- a/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck.mdwn +++ b/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck.mdwn @@ -33,3 +33,4 @@ It runs on Raspbian Testing ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Of course, The movie archive seems to be filling up nicely I just have some problems automating the checks. +> [[done]] diff --git a/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck/comment_1_34df6b7f9b96351130e60a5952816cc7._comment b/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck/comment_1_34df6b7f9b96351130e60a5952816cc7._comment new file mode 100644 index 000000000..7c9c7640a --- /dev/null +++ b/doc/bugs/thread_blocked_indefinitely_in_an_MVar_operation_durin_fsck/comment_1_34df6b7f9b96351130e60a5952816cc7._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-10-12T16:49:11Z" + content=""" +Seems your guess is right: + + joey@darkstar:~/tmp/b4/b>sudo chown root.root -R .git/annex/fsck/4625a6de-d8f5-4036-83a5-6e202ad346da/ + joey@darkstar:~/tmp/b4/b>git annex fsck --incremental-schedule 182d + + sqlite worker thread crashed: SQLite3 returned ErrorCan'tOpen while attempting to perform prepare "SELECT null from fscked limit 1": unable to open database file + git-annex: thread blocked indefinitely in an MVar operation + +So, fix the owner/permissions (or delete .git/annex/fsck) and you should be good to go. + +Cleaned up the error message about the MVar, which is something of a red herring. + +BTW, I double-checked, and core.sharedRepository is honored to set the mode +of the fsck database file, so can be used to share a repo amoung multiple users. +"""]] diff --git a/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment b/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment new file mode 100644 index 000000000..e38def8ba --- /dev/null +++ b/doc/special_remotes/S3/comment_19_9d0d622b6202698f09eb06c097579fbb._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 19""" + date="2015-10-12T17:10:21Z" + content=""" +@darkfeline I suppose you're talking about two completely disjoint git +repositories, and not two clones of the same parent repo. + +If you don't use fileprefix, and have the same file in two disjoint +repositories, git-annex will pick the same key for it in both cases, and +so you'll get deduplication, but only if you don't use different +fileprefixes. + +And this will mostly work pretty well. The danger is, if you drop the file +from the S3 repo, because say, it's not used anymore in one repository, +then you're also removing it from the S3 repo as used by the other +repository. If that was the last copy of the file, that may not be what you +want. +"""]] diff --git a/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry.mdwn b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry.mdwn index d9ea181a8..258b82f6a 100644 --- a/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry.mdwn +++ b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry.mdwn @@ -7,3 +7,5 @@ I keep a database file in git-annex so it stays synced across several machines. git annex sync --content This works fine except it creates an entry in the log for the database file even if that stays unchanged. I would like an option that just returns to the state before `git annex unlock` if the file has not been changed. Maybe `git annex add --restore-unchanged`? + +> [[done]] --[[Joey]] diff --git a/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_1_ef1dbde0fbf20b7fd91503d9df50dcab._comment b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_1_ef1dbde0fbf20b7fd91503d9df50dcab._comment new file mode 100644 index 000000000..3c6df0477 --- /dev/null +++ b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_1_ef1dbde0fbf20b7fd91503d9df50dcab._comment @@ -0,0 +1,33 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-10-12T17:17:12Z" + content=""" +I want to think a little bit about why the location log is updated in this +case before thinking about adding an option. It might make sense to just +not update the location log when it already says the file is present and +only the timestamp is being changed. + +I can think of 2 reasons not to do it: + +1. If it has to query the current state of the log, that might slow down + `git annex add` in the common case, just for this less common case. + + But, updating the log necessarily involves reading it in and outputting + an updated one, so that could probably be finessed. + + (Or, git annex add makes a separate pass to add unlocked files anyway, + so it could only do the query in that case.) + +2. There might be good reasons to want to update the timestamp in the log, + since it's just verified that the content is still present. Maybe. + + But then, fsck doesn't update the timestamps when it does the same kind + of verification. And, the only thing that updates a given repo's entry + in the log is that repo, or another repo that is sending or dropping + content from that repo. + + There don't seem to be any reasons of + distributed consistency to need to worry about updating the timestamp + just to reflect current facts. +"""]] diff --git a/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_2_3a3d793b32b8440a8213b38bc83ea94a._comment b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_2_3a3d793b32b8440a8213b38bc83ea94a._comment new file mode 100644 index 000000000..aeb98f06e --- /dev/null +++ b/doc/todo/wishlist:_allow_re-adding_without_generating_log_entry/comment_2_3a3d793b32b8440a8213b38bc83ea94a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-10-12T17:37:59Z" + content=""" +Ok, I found a way to implement it with no added overhead in the common +case! +"""]] |