From a03a9cedf1090c08750d8d3190a0f8a657d8fa6d Mon Sep 17 00:00:00 2001 From: "root@99e0a30209b856a064fa7d3e42d26b562bdf991c" Date: Tue, 28 May 2019 16:53:35 +0000 Subject: [PATCH 1/3] --- ...l_configuration_of_tor_hidden_service.mdwn | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/Support_manual_configuration_of_tor_hidden_service.mdwn diff --git a/doc/bugs/Support_manual_configuration_of_tor_hidden_service.mdwn b/doc/bugs/Support_manual_configuration_of_tor_hidden_service.mdwn new file mode 100644 index 0000000000..59d863c381 --- /dev/null +++ b/doc/bugs/Support_manual_configuration_of_tor_hidden_service.mdwn @@ -0,0 +1,23 @@ +### Please describe the problem. +I am running NixOS, so the automatic configuration of the tor hidden service does not work because system state is not mutable. Could you provide a way to configure the tor hidden service manually, perhaps printing out the configuration instead of installing it? + +### What steps will reproduce the problem? +N/A + +### What version of git-annex are you using? On what operating system? +7.2, NixOS + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] + +### 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) +Yes, I love it. + + From 89abda9efd08e5aeb16ede6966bfbdd01c0b3006 Mon Sep 17 00:00:00 2001 From: "emanuele.olivetti@47d88ed185b03191e25329caa6fabc2efb3118b2" Date: Tue, 28 May 2019 17:23:57 +0000 Subject: [PATCH 2/3] Added a comment: git-annex not working on arm at all? --- ..._1143917decff204a3965959d1cfaa8f4._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/Linux_standalone_on_armv5tel__58___error__58_____34__git-annex_died_of_signal_4__34__/comment_1_1143917decff204a3965959d1cfaa8f4._comment diff --git a/doc/bugs/Linux_standalone_on_armv5tel__58___error__58_____34__git-annex_died_of_signal_4__34__/comment_1_1143917decff204a3965959d1cfaa8f4._comment b/doc/bugs/Linux_standalone_on_armv5tel__58___error__58_____34__git-annex_died_of_signal_4__34__/comment_1_1143917decff204a3965959d1cfaa8f4._comment new file mode 100644 index 0000000000..ed696deb7a --- /dev/null +++ b/doc/bugs/Linux_standalone_on_armv5tel__58___error__58_____34__git-annex_died_of_signal_4__34__/comment_1_1143917decff204a3965959d1cfaa8f4._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="emanuele.olivetti@47d88ed185b03191e25329caa6fabc2efb3118b2" + nickname="emanuele.olivetti" + avatar="http://cdn.libravatar.org/avatar/f51cc5c6c3a0eb28faa6491c3cbcfcce" + subject="git-annex not working on arm at all?" + date="2019-05-28T17:23:57Z" + content=""" +Further attempts to get a working git-annex on arm (kirkwood), all failed: + +1. I tried to compile git-annex from source, on Debian stretch on my ARM machine - armel, kirkwood subarchitecture, it's a [QNAP Turbo Station](https://www.debian.org/releases/stable/armel/ch02s01.html.en) - following the instruction in [fromsource](http://git-annex.branchable.com/install/fromsource/). Make failed with [this error](https://gist.github.com/emanuele/54d0fb1e8905cb48da0cdf9371679462). Additional comments: I used `sudo apt-get build-dep git-annex` to install dependencies but libghc-microlens was missing and I had to install it separately. Make required a large amount of RAM: >500Mb or resident memory and >1Gb of virtual memory, which is more than what's available on such hardware. So make failed but re-running it multiple times worked, until the bug above. +2. I installed git-annex from the official package of Debian testing (buster), via `apt`. The installation went well. Unfortunately, the executable does not work, issuing the same error mentioned before: + +``` + # which git-annex + /usr/bin/git-annex + # git annex + error: git-annex died of signal 4 + # git-annex + Illegal instruction +``` + +Thanks in advance for any help. + +"""]] From afb1be754af40105e89685412f90760b3798a669 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 28 May 2019 17:25:19 +0000 Subject: [PATCH 3/3] Added a comment: readonly special remotes] --- ...nt_2_ac6dc78235484ee20906dfadaf7506e5._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/checkpresentkey_fails_on_read-only_remote/comment_2_ac6dc78235484ee20906dfadaf7506e5._comment diff --git a/doc/bugs/checkpresentkey_fails_on_read-only_remote/comment_2_ac6dc78235484ee20906dfadaf7506e5._comment b/doc/bugs/checkpresentkey_fails_on_read-only_remote/comment_2_ac6dc78235484ee20906dfadaf7506e5._comment new file mode 100644 index 0000000000..74978945fe --- /dev/null +++ b/doc/bugs/checkpresentkey_fails_on_read-only_remote/comment_2_ac6dc78235484ee20906dfadaf7506e5._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="readonly special remotes]" + date="2019-05-28T17:25:19Z" + content=""" +\"Setting readonly=true for a special remote prevents using the external special remote program at all\" -- that's the part I didn't realize. If I understand correctly: + +1. for all remotes, setting `readonly=true` \"prevents git-annex from making changes to a remote... this both prevents git-annex sync from pushing changes, and prevents storing or removing files from read-only remote.\" +2. additionally, for special remotes, this \"prevents using the external special remote program at all\", and instead causes `git-annex` to be [downloading the content of a file using a regular http connection, with no authentication](https://git-annex.branchable.com/design/external_special_remote_protocol/#index9h2)? + +If so, it would be best to add a separate config setting for (2). I'm not sure, though, why that case needs special handling. If a key's contents is available at a regular `http` URL, shouldn't the key be recorded as present in the built-in web special remote, rather than the user-defined special remote? + +The external special remote here is one I wrote myself, for accessing data on [DNAnexus](https://www.dnanexus.com/). +"""]]