From 81829125f878ca2c7a733dde028249edbaffe3c4 Mon Sep 17 00:00:00 2001 From: duncan_bayne Date: Mon, 3 Sep 2018 00:39:08 +0000 Subject: [PATCH 01/11] Added a comment: Thanks :) --- .../comment_2_7a5ff239751a2dc0547ad19b5bfa761f._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/git-annex_can__39__t_compile_on_FreeBSD_using_stack/comment_2_7a5ff239751a2dc0547ad19b5bfa761f._comment diff --git a/doc/bugs/git-annex_can__39__t_compile_on_FreeBSD_using_stack/comment_2_7a5ff239751a2dc0547ad19b5bfa761f._comment b/doc/bugs/git-annex_can__39__t_compile_on_FreeBSD_using_stack/comment_2_7a5ff239751a2dc0547ad19b5bfa761f._comment new file mode 100644 index 0000000000..abd4e6f772 --- /dev/null +++ b/doc/bugs/git-annex_can__39__t_compile_on_FreeBSD_using_stack/comment_2_7a5ff239751a2dc0547ad19b5bfa761f._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="duncan_bayne" + avatar="http://cdn.libravatar.org/avatar/2fc23e2009234ad965f9d5d796400417" + subject="Thanks :)" + date="2018-09-03T00:39:08Z" + content=""" +Thanks :) Will open further bugs if necessary. +"""]] From 41b3bbeddfe9c854a03b27962bda4cb4fe21cd0d Mon Sep 17 00:00:00 2001 From: duncan_bayne Date: Mon, 3 Sep 2018 00:42:24 +0000 Subject: [PATCH 02/11] --- ..._58____Issues_with_System.Posix.Files.mdwn | 53 +++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files.mdwn diff --git a/doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files.mdwn b/doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files.mdwn new file mode 100644 index 0000000000..9357a84c13 --- /dev/null +++ b/doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files.mdwn @@ -0,0 +1,53 @@ +### Please describe the problem. + +git-annex can't compile on FreeBSD; specifically, the build fails due to issues with System.Posix.Files. + +### What steps will reproduce the problem? + +1. git clone git://git-annex.branchable.com/ git-annex +2. cd git-annex +3. stack setup +4. stack install + +### What version of git-annex are you using? On what operating system? + +git-annex HEAD. + +FreeBSD 11.1-RELEASE r321309 GENERIC amd64 + +### Please provide any additional information below. + +Let me know if you'd like me to set up a FreeBSD development environment for you to SSH into - happy to do that if it helps you in any way. + +Compilation failure is as follows: + + Configuring git-annex-6.20180807... + git-annex-6.20180807: build (exe) + Preprocessing executable 'git-annex' for git-annex-6.20180807... + [124 of 586] Compiling Utility.DirWatcher.Kqueue ( Utility/DirWatcher/Kqueue.hs, .stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0/build/git-annex/git-annex-tmp/Utility/Di + rWatcher/Kqueue.o ) + + /usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:49: error: + Not in scope: ‘Files.openFd’ + Module ‘System.Posix.Files’ does not export ‘openFd’. + + /usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:66: error: + Not in scope: data constructor ‘Files.ReadOnly’ + Module ‘System.Posix.Files’ does not export ‘ReadOnly’. + + /usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:89: error: + Not in scope: ‘Files.defaultFileFlags’ + Module ‘System.Posix.Files’ does not export ‘defaultFileFlags’. + + /usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:132:15: error: + Not in scope: ‘Files.closeFd’ + Module ‘System.Posix.Files’ does not export ‘closeFd’. + + /usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:170:14: error: + Not in scope: ‘Files.closeFd’ + Module ‘System.Posix.Files’ does not export ‘closeFd’. + + -- While building custom Setup.hs for package git-annex-6.20180807 using: + /usr/home/duncan/code/git-annex/.stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0/setup/setup --builddir=.stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0 build exe:git + -annex --ghc-options " -ddump-hi -ddump-to-file" + Process exited with code: ExitFailure 1 From ff74702d3db7b80b7486a0ce2bb0046cb83bf604 Mon Sep 17 00:00:00 2001 From: ewen Date: Mon, 3 Sep 2018 04:30:42 +0000 Subject: [PATCH 03/11] x86-32 standalone build break on Synology DS216+ --- ...__timer__95__create__58___Bad_address.mdwn | 58 +++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address.mdwn diff --git a/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address.mdwn b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address.mdwn new file mode 100644 index 0000000000..f638638e48 --- /dev/null +++ b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address.mdwn @@ -0,0 +1,58 @@ +### Please describe the problem. + +After updating my Synology DS216+ NAS from [6.2-23739-1](https://www.synology.com/en-uk/releaseNote/DS216+II#ver_23739-1) to [6.2-23739-2](https://www.synology.com/en-uk/releaseNote/DS216+II#ver_23739-2), running `git-annex` with any non-trivial command, locally on the NAS or remotely on the NAS results in: + + git-annex: timer_create: Bad address + +I'm guessing that this means that a library function the standalone binary needs is no longer present, but I'm unsure why. The `-1` to `-2` update seems to only have two security fixes ([SA 18-36](https://www.synology.com/en-uk/support/security/Synology_SA_18_36), and [SA 18-01](https://www.synology.com/en-uk/support/security/Synology_SA_18_01) -- the latter being a Spectre/Meltdown bug). + +Do you know if `timer_create` is a kernel system call? Or a libc (etc) library function? + +### What steps will reproduce the problem? + +Update Synology NAS to [6.2-23739-2](https://www.synology.com/en-uk/releaseNote/DS216+II#ver_23739-2), run `git annex sync`, `git annex version` or similar (remotely or locally). + +### What version of git-annex are you using? On what operating system? + +`x86-32`, stand alone build, for ancient-kernels, as that the 64-bit stand alone build [no longer seemed to work due to locale issues](https://ewen.mcneill.gen.nz/blog/entry/2017-05-28-git-annex-on-synology-ds216+/) (see note added at the end). + +I believe it is `6.20180626`, but `git annex version` currently also fails... + +### Please provide any additional information below. + + ewen@nas01:/volume1/music/podcasts$ hostname --fqdn + nas01 + ewen@nas01:/volume1/music/podcasts$ git annex sync + git-annex: timer_create: Bad address + ewen@nas01:/volume1/music/podcasts$ + ewen@nas01:/volume1/music/podcasts$ git annex version + git-annex: timer_create: Bad address + ewen@nas01:/volume1/music/podcasts$ + ewen@nas01:/volume1/music/podcasts$ uname -mr + 3.10.105 x86_64 + ewen@nas01:/volume1/music/podcasts$ + +There is a [6.2.1 firmware release](https://www.synology.com/en-uk/releaseNote/DS216+) for the Synology NAS released a couple of days ago, but it does not yet seem to be visible to my NAS. I can try that one if it'd help. + +I can also try switching back to one of the more modern `x86-64` / `x86-32` stand alone builds if that'd help. But then I'd need some assistance with working around the: + + sh: loadlocale.c:129: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed. + error: git-annex died of signal 6 + +error I was seeing on those builds. (From other work elsewhere it feels a lot like the LC_TIME structure changed in size in some libc definition somewhere in the last 6-12 months; in another project we had a similar break on Ubuntu 18.04 issues which didn't affect Ubuntu 16.04 and earlier.) + +In case it helps, out of the box defaults give: + + ewen@nas01:/volume1/music/podcasts$ echo $LANG + en_US.utf8 + ewen@nas01:/volume1/music/podcasts$ ls /volume1/thirdparty/git-annex.linux/locales/en_US.utf8/ + LC_ADDRESS LC_IDENTIFICATION LC_MONETARY LC_PAPER + LC_COLLATE LC_MEASUREMENT LC_NAME LC_TELEPHONE + LC_CTYPE LC_MESSAGES LC_NUMERIC LC_TIME + ewen@nas01:/volume1/music/podcasts$ + +(although those files are currently generated with the now broken x86-32 legacy standalone build). + +### 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) + +Definitely. It was working until I updated the NAS firmware image this afternoon... for this repository holding years of podcasts and many others. From 793f71ed0c2f954035ab5d460c91515155a4c24e Mon Sep 17 00:00:00 2001 From: "amoebae@ae902fc700f29a8a9aa2547a9ea8ec77c0f8e30c" Date: Mon, 3 Sep 2018 10:56:04 +0000 Subject: [PATCH 04/11] --- .../Error__58___failed_to_push_some_refs.mdwn | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/forum/Error__58___failed_to_push_some_refs.mdwn diff --git a/doc/forum/Error__58___failed_to_push_some_refs.mdwn b/doc/forum/Error__58___failed_to_push_some_refs.mdwn new file mode 100644 index 0000000000..45d36f51ca --- /dev/null +++ b/doc/forum/Error__58___failed_to_push_some_refs.mdwn @@ -0,0 +1,25 @@ +Hello all, my situation is I have two laptops, one for work and one for home use. I have a lot of simple text files that I use in v6 unlocked mode (used to use direct mode, but recently switched). I run the assistant to sync between these hosts using an intermediate server which is an always-on VPS (visarend.solasistim.net in this example). + +At some point, these files will start to be desynced, and I'll see messages like these in the log files. + + [2018-09-03 11:34:04.062717904] NetWatcherFallback: Syncing with origin + + error: Your local changes to the following files would be overwritten by merge: + howto/c++.md + howto/emacs.mkd + howto/git-annex.mkd + howto/windows.mkd + org/kanban.org + Please commit your changes or stash them before you merge. + Aborting + To visarend.solasistim.net:annex + ! [rejected] master -> synced/master (non-fast-forward) + error: failed to push some refs to 'visarend.solasistim.net:annex' + hint: Updates were rejected because a pushed branch tip is behind its remote + hint: counterpart. Check out this branch and integrate the remote changes + hint: (e.g. 'git pull ...') before pushing again. + hint: See the 'Note about fast-forwards' in 'git push --help' for details. + +Using git-annex 6.20170101.1 on all hosts. + +What exactly does this error mean? How can I get rid of it? I solve it by rm'ing the repository and re-cloning from visarend.solasistim.net, and integrating any changes manually, but I'm wondering why it's happening. From 8b9cd04815ee2364064df3eabf8121a3fa851360 Mon Sep 17 00:00:00 2001 From: ewen Date: Mon, 3 Sep 2018 22:06:00 +0000 Subject: [PATCH 05/11] Added a comment: timer_create --- ..._8ce2cbdf5b5c31fd42b0ed270c54a824._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_1_8ce2cbdf5b5c31fd42b0ed270c54a824._comment diff --git a/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_1_8ce2cbdf5b5c31fd42b0ed270c54a824._comment b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_1_8ce2cbdf5b5c31fd42b0ed270c54a824._comment new file mode 100644 index 0000000000..8970688f90 --- /dev/null +++ b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_1_8ce2cbdf5b5c31fd42b0ed270c54a824._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="ewen" + avatar="http://cdn.libravatar.org/avatar/605b2981cb52b4af268455dee7a4f64e" + subject="timer_create" + date="2018-09-03T22:06:00Z" + content=""" +From some digging around it looks like [`timer_create`](http://man7.org/linux/man-pages/man2/timer_create.2.html) is a Linux system call. So presumably the issue with the Synology NAS is being caused by the kernel being updated. + +Of note, it appears that [Microsoft Windows System for Linux does not support `timer_create` either](https://github.com/Microsoft/WSL/issues/307). And that [system call is apparently required for Haskell binaries](https://github.com/Microsoft/WSL/issues/307#issuecomment-217051052)... Apparently (from this thread) other people have hit this issue trying to run `git-annex` too. + +There's a [suggestion of some work around flags](https://github.com/Microsoft/WSL/issues/307#issuecomment-239617836), but they do not seem to work with the `git-annex` stand alone binary as it is currently built: + + ewen@nas01:~$ git-annex +RTS -V0 -RTS help + git-annex: Most RTS options are disabled. Link with -rtsopts to enable them. + ewen@nas01:~$ export GHCRTS=-V0 + ewen@nas01:~$ git annex help + git-annex: Most RTS options are disabled. Link with -rtsopts to enable them. + ewen@nas01:~$ + +Possibly it'll be necessary to try to persuade Synology to re-enable the `timer_create` system call. But my guess is maybe they turned it off as a Spectre/Meltdown fix, so it may be non-trivial to persuade them to change it back. + +Ewen +"""]] From 8afd9b5c95c65d8a7b86501ac230c95a0bbc9008 Mon Sep 17 00:00:00 2001 From: ewen Date: Mon, 3 Sep 2018 22:36:07 +0000 Subject: [PATCH 06/11] Added a comment: Synology bug report --- ...mment_2_1316ea67dc7df8d3d6f681ac3caf6d3c._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_2_1316ea67dc7df8d3d6f681ac3caf6d3c._comment diff --git a/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_2_1316ea67dc7df8d3d6f681ac3caf6d3c._comment b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_2_1316ea67dc7df8d3d6f681ac3caf6d3c._comment new file mode 100644 index 0000000000..e849792a78 --- /dev/null +++ b/doc/bugs/Synology_NAS__58___timer__95__create__58___Bad_address/comment_2_1316ea67dc7df8d3d6f681ac3caf6d3c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="ewen" + avatar="http://cdn.libravatar.org/avatar/605b2981cb52b4af268455dee7a4f64e" + subject="Synology bug report" + date="2018-09-03T22:36:07Z" + content=""" +FWIW, I've created a Synology Account, to create a Synology Support Request, [#2082132](https://account.synology.com/en-global/support/2082132/detail) for the missing timer_create system call on DSM 6.2-23739-2. I'm not holding out a lot of hope given it's a third party application running on the NAS, and not even one in their app store, but maybe there's a chance it'll get the system call turned back on again. That Synology support request includes a link to this bug report. + +Ewen + +PS: I expect that bug report will only be visible if you're logged in with my Synology account. But at least someone else reporting it can reference the same issue to Synology Support. +"""]] From 1a70df53c864cd64ce7bd388f1b95b421c474aba Mon Sep 17 00:00:00 2001 From: Horus Date: Wed, 5 Sep 2018 07:32:49 +0000 Subject: [PATCH 07/11] --- ...al_operation___40__handle_is_closed__41__.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn diff --git a/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn new file mode 100644 index 0000000000..587c4e518c --- /dev/null +++ b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn @@ -0,0 +1,15 @@ +Hello, + +using git-annex 6.20180807-23 on Arch I get this message from time to time: + +``` +copy archive/Studium/Diplomarbeit/Daten/Vortrag/vortrag.snm (to xgm...) +git-annex-shell: : hGetChar: illegal operation (handle is closed)ok +copy archive/Studium/Diplomarbeit/Daten/Wheels/SingleWheelCalcs/5SpokeWheel/5Spoke_MRF/6000/Lambda2.gz + Lost connection (fd:21: hFlush: resource vanished (Broken pipe)) +(fd:21: hClose: resource vanished (Broken pipe)) failed +``` + +The peer is git-annex, downloaded at Aug 7 at Debian Stable. Repeating the file transfer makes the message goes away, but I have to initiate the transfer multiple times, to be able to transfer all files without this error message. + +Best Thanks! From 72682144bcc81d2ff8a2e6c1a8afea508786d527 Mon Sep 17 00:00:00 2001 From: Horus Date: Wed, 5 Sep 2018 07:33:41 +0000 Subject: [PATCH 08/11] --- ...illegal_operation___40__handle_is_closed__41__.mdwn | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn index 587c4e518c..be7c6cff59 100644 --- a/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn +++ b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn @@ -3,11 +3,11 @@ Hello, using git-annex 6.20180807-23 on Arch I get this message from time to time: ``` -copy archive/Studium/Diplomarbeit/Daten/Vortrag/vortrag.snm (to xgm...) -git-annex-shell: : hGetChar: illegal operation (handle is closed)ok -copy archive/Studium/Diplomarbeit/Daten/Wheels/SingleWheelCalcs/5SpokeWheel/5Spoke_MRF/6000/Lambda2.gz - Lost connection (fd:21: hFlush: resource vanished (Broken pipe)) -(fd:21: hClose: resource vanished (Broken pipe)) failed + copy archive/Studium/Diplomarbeit/Daten/Vortrag/vortrag.snm (to xgm...) + git-annex-shell: : hGetChar: illegal operation (handle is closed)ok + copy archive/Studium/Diplomarbeit/Daten/Wheels/SingleWheelCalcs/5SpokeWheel/5Spoke_MRF/6000/Lambda2.gz + Lost connection (fd:21: hFlush: resource vanished (Broken pipe)) + (fd:21: hClose: resource vanished (Broken pipe)) failed ``` The peer is git-annex, downloaded at Aug 7 at Debian Stable. Repeating the file transfer makes the message goes away, but I have to initiate the transfer multiple times, to be able to transfer all files without this error message. From 3cd10c246c36457e5d79016aa56005a1aa6812f3 Mon Sep 17 00:00:00 2001 From: Horus Date: Wed, 5 Sep 2018 07:34:23 +0000 Subject: [PATCH 09/11] --- ...ar__58___illegal_operation___40__handle_is_closed__41__.mdwn | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn index be7c6cff59..c167a66b1f 100644 --- a/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn +++ b/doc/forum/Getting__58___hGetChar__58___illegal_operation___40__handle_is_closed__41__.mdwn @@ -2,13 +2,11 @@ Hello, using git-annex 6.20180807-23 on Arch I get this message from time to time: -``` copy archive/Studium/Diplomarbeit/Daten/Vortrag/vortrag.snm (to xgm...) git-annex-shell: : hGetChar: illegal operation (handle is closed)ok copy archive/Studium/Diplomarbeit/Daten/Wheels/SingleWheelCalcs/5SpokeWheel/5Spoke_MRF/6000/Lambda2.gz Lost connection (fd:21: hFlush: resource vanished (Broken pipe)) (fd:21: hClose: resource vanished (Broken pipe)) failed -``` The peer is git-annex, downloaded at Aug 7 at Debian Stable. Repeating the file transfer makes the message goes away, but I have to initiate the transfer multiple times, to be able to transfer all files without this error message. From f760555c57ccc311680b454a45cad9e144c0ffb1 Mon Sep 17 00:00:00 2001 From: fft Date: Wed, 5 Sep 2018 12:13:48 +0000 Subject: [PATCH 10/11] --- .../can__39__t_build_without_assistant.mdwn | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/bugs/can__39__t_build_without_assistant.mdwn diff --git a/doc/bugs/can__39__t_build_without_assistant.mdwn b/doc/bugs/can__39__t_build_without_assistant.mdwn new file mode 100644 index 0000000000..43b9c2c1fa --- /dev/null +++ b/doc/bugs/can__39__t_build_without_assistant.mdwn @@ -0,0 +1,32 @@ +### Please describe the problem. +1. Building minimal variant of git-annex failed. +1. Seems, that instructions about [minimal building from source](https://git-annex.branchable.com/install/fromsource/) are out-of-date, at least because options 'xmpp' and 'dns' don't exist in git-annex.cabal. +1. Also seems, that file Utility/SRV.hs unused, may be remove it? + +In git-annex.cabal 'Assistant' flag doesn't influence on list of modules, only on compile flags and dependencies. 'Assistant/\*' modules includes into base variant of building (and some 'Assistant/\*' modules turn on with WebApp flag). + +### What steps will reproduce the problem? +Try to build as in [archlinux package](https://git.archlinux.org/svntogit/community.git/tree/repos/community-x86_64/PKGBUILD?h=packages/git-annex), but turn off assistant: + +`runhaskell Setup configure -O --prefix=/usr --enable-executable-dynamic --disable-library-vanilla --docdir="/usr/share/doc/git-annex" -fconcurrentoutput -ftorrentparser -f-androidsplice -f-android -fproduction -fpairing -fwebapp -f-assistant -fwebdav -fs3 -f-benchmark -fdbus -fmagicmime` + +`runhaskell Setup.hs build` + +After that I got error: + +`Utility/Mounts.hs:13:1: error:` + +` Could not find module ‘System.MountPoints’` + +haskell-mountpoints package is instaled. +If turn on assistant flag, building is ok. + +### Please provide any additional information below. +I don't know haskell, but try to make optional building of Assistant, see [patch](https://github.com/fftmp/git-annex-min-pkgbuild/blob/master/0002-optional-build-assistant-and-other-small-cabal-refin.patch). Seems, that it works. +### What version of git-annex are you using? On what operating system? +6.20180807, Archlinux + + +### 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, use it for several years and have approx 100G repo with 10k+ files. Works fine. + From 165783827b0425a53027d8f43481e16d5e15aa45 Mon Sep 17 00:00:00 2001 From: fft Date: Wed, 5 Sep 2018 12:18:54 +0000 Subject: [PATCH 11/11] --- doc/bugs/can__39__t_build_without_assistant.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/can__39__t_build_without_assistant.mdwn b/doc/bugs/can__39__t_build_without_assistant.mdwn index 43b9c2c1fa..22171a2275 100644 --- a/doc/bugs/can__39__t_build_without_assistant.mdwn +++ b/doc/bugs/can__39__t_build_without_assistant.mdwn @@ -22,7 +22,7 @@ haskell-mountpoints package is instaled. If turn on assistant flag, building is ok. ### Please provide any additional information below. -I don't know haskell, but try to make optional building of Assistant, see [patch](https://github.com/fftmp/git-annex-min-pkgbuild/blob/master/0002-optional-build-assistant-and-other-small-cabal-refin.patch). Seems, that it works. +I don't know haskell, but try to make optional building of Assistant, see [patch](https://github.com/fftmp/git-annex-min-pkgbuild/blob/master/0002-optional-build-assistant-and-other-small-cabal-refin.patch). Seems, that it works for minimal building, but may be incomplete. ### What version of git-annex are you using? On what operating system? 6.20180807, Archlinux