Added a comment
authorkyle <kyle@web>
Tue, 10 Mar 2020 19:30:50 +0000 (19:30 +0000)
committeradmin <admin@branchable.com>
Tue, 10 Mar 2020 19:30:50 +0000 (19:30 +0000)
doc/forum/Get_annex.dotfiles__61__true_behavior_without_persistent_configuration__63__/comment_15_994e3e64184a020f9afe21cd9ea34b38._comment [new file with mode: 0644]

diff --git a/doc/forum/Get_annex.dotfiles__61__true_behavior_without_persistent_configuration__63__/comment_15_994e3e64184a020f9afe21cd9ea34b38._comment b/doc/forum/Get_annex.dotfiles__61__true_behavior_without_persistent_configuration__63__/comment_15_994e3e64184a020f9afe21cd9ea34b38._comment
new file mode 100644 (file)
index 0000000..1ca5856
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="kyle"
+ avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3"
+ subject="comment 15"
+ date="2020-03-10T19:30:50Z"
+ content="""
+> If there's no obvious solution, I can probably just re-create the entire datalad dataset from scratch with the new software versions in this conda env.
+
+It's not obvious to me why an uninstalled subdataset would be causing issues with the repo upgrade process.  Quickly trying, I can't trigger an issue, but perhaps the submodule got into some weird, not-really-removed state.  You can open an issue on DataLad's side and we can try to debug it, though doing so might be tricky without a recipe to trigger it.
+"""]]