From 20e1afc80464fe93d742cace6684c20ba41f1c18 Mon Sep 17 00:00:00 2001 From: mhauru Date: Sun, 27 Sep 2020 12:40:57 +0000 Subject: [PATCH 1/3] Added a comment: NeuroDebian seems to have stopped updating --- .../comment_15_4ea052431b49a0505b4a58a760054bed._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/install/Ubuntu/comment_15_4ea052431b49a0505b4a58a760054bed._comment diff --git a/doc/install/Ubuntu/comment_15_4ea052431b49a0505b4a58a760054bed._comment b/doc/install/Ubuntu/comment_15_4ea052431b49a0505b4a58a760054bed._comment new file mode 100644 index 0000000000..716cee9d04 --- /dev/null +++ b/doc/install/Ubuntu/comment_15_4ea052431b49a0505b4a58a760054bed._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="mhauru" + avatar="http://cdn.libravatar.org/avatar/2532433a0207ba772e6ca964e61899c0" + subject="NeuroDebian seems to have stopped updating" + date="2020-09-27T12:40:54Z" + content=""" +The comment about NeuroDebian providing more up to date builds is out of date, their version is now more than a year old. An alternative would be welcome, something between the official Ubuntu package and compiling from source. +"""]] From 9651c1da969d10c85134a86877a9b05736590170 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Sun, 27 Sep 2020 13:42:18 +0000 Subject: [PATCH 2/3] Added a comment --- ...ment_16_b5dd1d73309e427d6e817a3a69beea74._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/install/Ubuntu/comment_16_b5dd1d73309e427d6e817a3a69beea74._comment diff --git a/doc/install/Ubuntu/comment_16_b5dd1d73309e427d6e817a3a69beea74._comment b/doc/install/Ubuntu/comment_16_b5dd1d73309e427d6e817a3a69beea74._comment new file mode 100644 index 0000000000..8e79819905 --- /dev/null +++ b/doc/install/Ubuntu/comment_16_b5dd1d73309e427d6e817a3a69beea74._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 16" + date="2020-09-27T13:42:15Z" + content=""" +Eh, true. Our version is year old as the one which doesn't cause regressions in datalad. We are still fighting with some remaining regressions. See eg one of the last attempts https://github.com/datalad/datalad/pull/4915 . + +We do have unannounced on the NeuroDebian debian-devel/ (complement to regular debian/ line in your apt listing) from the main NeuroDebian website (not mirrors). That is where we upload those versions to test. + +Also there is now a daily built git annex .deb (and .dmg for osx) package as artifact of GitHub workflow, eg https://github.com/datalad/datalad-extensions/actions/runs/274613689 . I guess we better automatically upload them somewhere for easier fetching/deployment. +"""]] From 5aa85fa09233f9d140be95cdbae88cf67f08bdfc Mon Sep 17 00:00:00 2001 From: mhauru Date: Sun, 27 Sep 2020 14:03:12 +0000 Subject: [PATCH 3/3] --- ...air_--force_fails_without_explanation.mdwn | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 doc/forum/git_annex_repair_--force_fails_without_explanation.mdwn diff --git a/doc/forum/git_annex_repair_--force_fails_without_explanation.mdwn b/doc/forum/git_annex_repair_--force_fails_without_explanation.mdwn new file mode 100644 index 0000000000..3ce126a982 --- /dev/null +++ b/doc/forum/git_annex_repair_--force_fails_without_explanation.mdwn @@ -0,0 +1,34 @@ +I have a repo for which `git annex fsck --all` goes through without any complaints, and `git fsck` produces + + Checking object directories: 100% (256/256), done. + error in tree 97abf6de76c0c56593f78d2f55b4c60d04345281: gitmodulesSymlink: .gitmodules is a symbolic link + Checking objects: 100% (998477/998477), done. + Checking connectivity: 998477, done. + dangling tree f9a2b542f57770c135631de1ae590475fc0caa54 + +but running `git annex repair --force`, + + repair Running git fsck ... + Unpacking all pack files. + Unpacking objects: 100% (998477/998477), 64.95 MiB | 359.00 KiB/s, done. + Initialized empty Git repository in /tmp/tmprepoqPmkhi/.git/ + Trying to recover missing objects from remote A. + fatal: '[a path I censored]' 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. + Trying to recover missing objects from remote B. + Unpacking all pack files. + Unpacking objects: 100% (923941/923941), 63.54 MiB | 367.00 KiB/s, done. + [A couple of other cases of remotes not available.] + failed + git-annex: repair: 1 failed + +Is the failure likely related to the `gitmodulesSymlink` error? If so, what could I do about it? If not, how do I figure out what's going on? + +Regarding the `.gitmodules` complaint: The repo has a subfolder with its own `.git` and `.gitmodules`, and although nothing in there is commited into the main repo now, I did in the past accidentally, temporarily commit the `subfolder/.gitmodules` into the main repo. + +I don't actually find anything wrong with the repo, the only reason I'm running `repair` on it is because a remote of it is missing some files, although it claims to be all synced up. + +This is on version 8.20200226. I would be happy to try on a more recent one, if there's a way to do so on Ubuntu without compiling from source.