Looking at the build log, I understood why the /usr/share/doc/unison/unison-manual.txt file is empty. It is quite simply generated from the output of "unison -doc all". The core issue is that this command does not output anything.
...
I think I found the root cause of the issue. The Unison documentation is maintained in the file doc/unison-manual.tex, which is apparently converted to src/strings.ml in a separate (manual?) build process. Anyway, the resulting src/strings.ml is then stored in Subversion.
Looking at the build log, I understood why the /usr/share/ doc/unison/ unison- manual. txt file is empty. It is quite simply generated from the output of "unison -doc all". The core issue is that this command does not output anything.
...
I think I found the root cause of the issue. The Unison documentation is maintained in the file doc/unison- manual. tex, which is apparently converted to src/strings.ml in a separate (manual?) build process. Anyway, the resulting src/strings.ml is then stored in Subversion.
On the 2.40 branch, src/strings.ml contains an empty array (cf. https:/ /webdav. seas.upenn. edu/viewvc/ unison/ branches/ 2.40/src/ strings. ml?view= markup) In all other branches (2.32, 2.27, trunk), src/strings.ml contains the Unison manual as expected.
So, it seems to me that src/strings.ml needs to be regenerated on the 2.40 branch, and then the build redone.