diff --git a/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy.mdwn b/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy.mdwn index 94c08664f8..5c018615f4 100644 --- a/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy.mdwn +++ b/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy.mdwn @@ -81,3 +81,5 @@ Init Tests on days ending with `y` it seems to work quite nicely. +[[!meta author=yoh]] +[[!tag projects/dandi]] diff --git a/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy/comment_2_33143a5f2467c58201496c8f59532b53._comment b/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy/comment_2_33143a5f2467c58201496c8f59532b53._comment new file mode 100644 index 0000000000..8c38c9e370 --- /dev/null +++ b/doc/bugs/beegfs__58___init_tests_FAIL_resource_busy/comment_2_33143a5f2467c58201496c8f59532b53._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 2" + date="2021-07-04T03:27:20Z" + content=""" +Thank you Joey! indeed most likely a \"too fancy\" of a file system. + +On [https://www.beegfs.io/release/beegfs_6/Changelog.txt](https://www.beegfs.io/release/beegfs_6/Changelog.txt) I found + + +``` +== Changes in 6.11 (release date: 2017-05-26) == + +General Changes: + +* client: Add option sysRenameEbusyAsXdev to return EXDEV instead of EBUSY if + rename() is called on open files. (Tools like \"mv\" can handle EXDEV as return + value.) +``` + +do you think EXDEV would be worked out Ok if that is the culprit? (meanwhile I will let the beegfs users know as well - may be they could try) + +"""]] diff --git a/doc/forum/Apple_M1_Silicon/comment_10_5646c616f1897c797ce383f6d4210ce4._comment b/doc/forum/Apple_M1_Silicon/comment_10_5646c616f1897c797ce383f6d4210ce4._comment new file mode 100644 index 0000000000..6a7179d56d --- /dev/null +++ b/doc/forum/Apple_M1_Silicon/comment_10_5646c616f1897c797ce383f6d4210ce4._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="strmd" + avatar="http://cdn.libravatar.org/avatar/035707b9756129bbdea6b36a7f7b38d3" + subject="comment 10" + date="2021-07-05T07:07:34Z" + content=""" +Thanks, but it's still not working for me (tried twice): + + Last 15 lines from /Users/md/Library/Logs/Homebrew/git-annex/02.cabal: + Currently only 10 to 12 is supported. System LLVM version: 12.0.0 + We will try though... + [518 of 668] Compiling Command.InAnnex ( Command/InAnnex.hs, dist/build/git-annex/git-annex-tmp/Command/InAnnex.o, dist/build/git-annex/git-annex-tmp/Command/InAnnex.dyn_o ) + You are using an unsupported version of LLVM! + Currently only 10 to 12 is supported. System LLVM version: 12.0.0 + We will try though... + clang: error: unable to execute command: posix_spawn failed: Resource temporarily unavailable + + : error: + Error running clang! you need clang installed to use the LLVM backend + (or GHC tried to execute clang incorrectly) + `clang' failed in phase `Clang (Assembler)'. (Exit code: 1) + +But perhaps a bottle is not that far away now. +"""]] diff --git a/doc/forum/Apple_M1_Silicon/comment_9_d77519ba5ca217cb3ec6348567731b9d._comment b/doc/forum/Apple_M1_Silicon/comment_9_d77519ba5ca217cb3ec6348567731b9d._comment new file mode 100644 index 0000000000..d61fd0422e --- /dev/null +++ b/doc/forum/Apple_M1_Silicon/comment_9_d77519ba5ca217cb3ec6348567731b9d._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="css@fcd6583660cae4ea6565f44f31443feb8e131139" + nickname="css" + avatar="http://cdn.libravatar.org/avatar/029af00c2f4a43194d6993d4cd2283e3" + subject="comment 9" + date="2021-07-05T03:17:39Z" + content=""" +A new version of criterion-measurement is out with support for Apple Silicon, it's possible to install git-annex via Homebrew now. No bottle is available as of yet but building from source works fine. +"""]] diff --git a/doc/forum/How_to_see_what_will_go_to_annex_vs_git.mdwn b/doc/forum/How_to_see_what_will_go_to_annex_vs_git.mdwn new file mode 100644 index 0000000000..88f629bc69 --- /dev/null +++ b/doc/forum/How_to_see_what_will_go_to_annex_vs_git.mdwn @@ -0,0 +1,10 @@ +I am importing lots of files from various sources, and want to make sure that I don't inadvertently commit big files to git. On a file-by-file basis, it's easy enough to tell if it matches the inclusion pattern. But for lots of files, I find myself doing: + +1. `git annex add .` +2. Look for the "non-large file; adding content to git repository" message +3. `git reset` +4. `git annex config --set annex.largefiles ...` to add the new file extension to the list + +`git add` doesn't provide any info on what goes where. + +So is there a way to see, in a given directory, what would be annexed and what would be stored in git when doing `git add` / `git annex add` ? diff --git a/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_1_d26ea587da51a6f663d64ebb19976a2b._comment b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_1_d26ea587da51a6f663d64ebb19976a2b._comment new file mode 100644 index 0000000000..763e722ffb --- /dev/null +++ b/doc/forum/How_to_see_what_will_go_to_annex_vs_git/comment_1_d26ea587da51a6f663d64ebb19976a2b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="pat" + avatar="http://cdn.libravatar.org/avatar/6b552550673a6a6df3b33364076f8ea8" + subject="comment 1" + date="2021-07-04T00:28:09Z" + content=""" +`git config annex.addsmallfiles false` will make it so `git annex add` only adds files that should be annexed. So I can `git annex add` first, and then if I have any files left over that should have been annexed, I can add their file suffixes to the inclusion list. Slick! +"""]]