From c2cdf0f61fbe862e734901ec06d80175d6c71913 Mon Sep 17 00:00:00 2001 From: jkniiv Date: Thu, 14 Jul 2022 20:32:06 +0000 Subject: [PATCH 1/2] Added a comment --- ...ent_2_1d9c331e774138ceb89b1f7920bb76d4._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities/comment_2_1d9c331e774138ceb89b1f7920bb76d4._comment diff --git a/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities/comment_2_1d9c331e774138ceb89b1f7920bb76d4._comment b/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities/comment_2_1d9c331e774138ceb89b1f7920bb76d4._comment new file mode 100644 index 0000000000..c0323240a2 --- /dev/null +++ b/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities/comment_2_1d9c331e774138ceb89b1f7920bb76d4._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="jkniiv" + avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d" + subject="comment 2" + date="2022-07-14T20:32:06Z" + content=""" +> We could go argue with the Win32 maintainer to put it back in. I have: https://github.com/haskell/win32/issues/208 + +Thanks. I see they seem be rather receptive to your suggestion. (I put in a thumbs up, too) The only issue I see is deciding on +how to name the raw version of createFile. Is there some precedent in Haskell land as to naming conventions? C and Python +would just prepend an underscore or two to the name without necessarily indicating that they would be thereby off limits (\"internal\"). +Maybe something like `_raw_CreateFile` with or without the underscore in the beginning? + +"""]] From 8c4ac8e63c53e9968503e80b756537c59e498d0e Mon Sep 17 00:00:00 2001 From: oliv5 Date: Fri, 15 Jul 2022 06:33:25 +0000 Subject: [PATCH 2/2] --- ...sitory_is_not_initialized_for_use_by_.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/Android__58___repository_is_not_initialized_for_use_by_.mdwn diff --git a/doc/forum/Android__58___repository_is_not_initialized_for_use_by_.mdwn b/doc/forum/Android__58___repository_is_not_initialized_for_use_by_.mdwn new file mode 100644 index 0000000000..542b4afcb2 --- /dev/null +++ b/doc/forum/Android__58___repository_is_not_initialized_for_use_by_.mdwn @@ -0,0 +1,22 @@ +I've been using git-annex in android/termux (pixel 3a, android 12 rooted) for a while to manage multiple repositories in command line (no assistant here). So far so good. I upgraded termux packages one day and troubles began: all repositories now throw the following errors for all kind of git-annex commands: + +``` +$ git annex status +git-annex: This repository is not initialized for use by git-annex, but .git/annex/objects/ exists, which indicates this repository was used by git-annex before, and may have lost its annex.uuid and annex.version configs. Either set back missing configs, or run git-annex init to initialize with a new uuid. +error: external filter 'git-annex smudge --clean -- %f' failed 1 +error: external filter 'git-annex smudge --clean -- %f' failed +``` + +Note I filter out the recurring error "WARNING: linker: Warning: failed to find generated linker configuration from ..." for clarity. +git version: 2.36.1 +git annex version: 10.20220121 + +- Funny thing #1: "git config -l" shows the uuid is correctly set. + +- Funny thing #2: I installed nix-on-droid with git (2.33.3) and git-annex (8.20211028) and ... I have the same error (?!?). + +- Funny thing #3: when I clone a repository from scratch, "git annex init" never completes. When interrupted, then "git annex status" never completes... + +- Funny thing #4: git alone works very well, in both git-annex'ed repos or plain git ones. + +If you have any idea of something to check/change/update/try, I'll be happy to report the results.