libassuan-2.1.1 Problem building documentation

[christopher]

Hello,

When trying to build the documentation the following error is reported:

Output written on assuan.pdf (70 pages, 351193 bytes). Transcript written on assuan.log. /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. Makefile:342: recipe for target 'assuan.pdf' failed make: * [assuan.pdf] Error 1

Prior to that it gives the following:

Underfull \hbox (badness 2080) in paragraph at lines 122--122 []@ssecrm A.0.2TERMS AND CON-DI-TIONS FOR COPY-ING,

As a result issuing the install command for the documentation fails:

install: cannot stat ‘doc/assuan.ps’: No such file or directory install: cannot stat ‘doc/assuan.dvi’: No such file or directory

So there is no .ps or .dvi documentation made.

[Fernando de Oliveira]

Actually, pdf builds, but for some reason an error code is generated

Output written on assuan.pdf (70 pages, 351309 bytes).
Transcript written on assuan.log.
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.

and make stops. To reproduce this error:

/usr/bin/texi2dvi --pdf --batch doc/assuan.texi

If you run after the error:

make -C doc ps

then, you can proceed installing package and all docs.

So, documentation does build. But there is a build error.

I am not sure if the texi files are wrong or if there is a problem with texlive.

Searching about it, I found that the problem seem to be with texlive, no reference to libassuan.

I don't know how to fix texlive.

Temporarily fix libassuan, with:

      make -C doc pdf || true &&
      make -C doc ps

However, I would much welcome more comments or probably, a better solution.

[christopher]

I just did a little more research and found a *possible* solution on Arch linux's website:

​https://aur.archlinux.org/packages/libassuan-git/

One poster states this:

Comment by gyscos

2013-05-12 07:32

It seems to be caused by libassuan-git's gpl.texi file. makeinfo returns these errors when processing their file ; but the original gpl.texi file, available at ​http://www.gnu.org/licenses/gpl.texi works fine. Maybe gnu.org updated their file and libassuan didn't ? Similarly, the lgpl.texi file differs from that from gnu.org, and here again the gnu.org version works fine.

However, assuan.texi refers to external nodes ('Library Copying' and 'Copying') present in the assuan version of gpl.texi and/or lgpl.texi, so blindly copying the gnu.org version over does not work. These nodes are actually just one line at the beginning of assuan version of gpl.texi and lgpl.texi. I copied them to the gnu.org versions, and this time the compilation succeeded.

I think this deserves an upstream update to use newer gpl.texi and lgpl.texi, and an accordingly updated assuan.texi.

In the meantime, a patch would be to download (or attach as source) the gnu.org versions of both gpl.texi and lgpl.texi, then prepend at the beginning of gpl.texi the line '@node Copying', and at the beginning of lgpl.texi the line '@node Library Copying'. Then, move these files to the '$srcdir/$_gitname-build/doc' directory. Another solution would be to not build documentation, but I did not find that option in the configure script.

Maybe this will give a hint as to how to go about fixing this. I have had a quick look at the gnu version and have failed to find reference to @node Library Copying, so either I am looking in the wrong place, or the wrong file.

[Fernando de Oliveira]

Using the gnu versions eliminates the error message, but make install fails.

Will use the form in comment:1

[Fernando de Oliveira]

Modified the title because the documentation does build.

Thanks in advance if a better solution is presented.

Fixed at r13874.

[Armin K]

It's in nature of pdflatex to produce pdfs "on the fly". So pdf does not build entirely, rather than not at all.

Fixed in systemd branch at r13881 by updating license files as noted in comment 2.

[Fernando de Oliveira]

I am attaching the diff obtained by updating license files as noted in comment 2 and the full log, from 8 trials.

It is different from what you got.

I don't understand where I am making an error.

On 11-08-2014 13:13, krejzi@higgs.linuxfromscratch.org wrote:
> Author: krejzi
> Date: Mon Aug 11 09:13:34 2014
> New Revision: 13880
> 
> Log:
> Revert ugly workaround for libassuan documentation.

If I could I would revert the extremely disgusting low level rude language above.

Error that I got:

if /bin/sh /home/fernando/tmp/paco-build-2014.08.10-08h57m46s/libassuan-2.1.1/missing --run makeinfo   -I . \
 -o assuan.info assuan.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./assuan.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
assuan.texi:126: @menu reference to nonexistent node `Library Copying'
assuan.texi:128: @menu reference to nonexistent node `Copying'
Makefile:315: recipe for target 'assuan.info' failed
make[1]: *** [assuan.info] Error 1
make[1]: Leaving directory '/home/fernando/tmp/paco-build-2014.08.10-08h57m46s/libassuan-2.1.1/doc'
Makefile:370: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

real	0m2.576s
user	0m1.874s
sys	0m0.310s

real	0m17.143s
user	0m13.463s
sys	0m6.779s

END - Building libassuan-2.1.1 - Dom Ago 10 08:58:03 BRT 2014

[Fernando de Oliveira]

this did not work

[Fernando de Oliveira]

error using comment 2

[Armin K]

You didn't take the second paragraph of the comment 2 into account there. Copying newer versions of the texi files is not enough.

The patch is in the patches repo.

Also, "Ugly workaround" isn't rude language (yet alone low level - I don't speak C, sorry).

[Fernando de Oliveira]

On comment:5:

Thanks in advance if a better solution is presented.

You just solved elsewhere.

But this always what happens, I did many things before, trying to help the other branch, before that, to as compliment to people from the other branch, the response was disappointing. I asked for help from people of the other branch even when it was not even discussed to start, the response was disappointing.

A non-rude attitude would be putting the solution here:

"You are missing... If you do this and that..."

Or perhaps we have a cultural barrier, making it impossible collaborating with each other.

I'm afraid the interaction of the other branch with me will never improve. Please, someone else take their tickets, complaints, posts, etc. I tried but always get in trouble with them. I will eventually try to read them, but from now on, I'm trying to have peace, and will do nothing related to that branch.

At the moment, I am strongly resisting to blocking anything come from there.

On comment:8

Also, "Ugly workaround" isn't rude language (yet alone low level - I don't speak C, sorry)

I see. You think it is very elegant language.

Of course, you do as you like.

I'm sorry, I don't speak C and don't understand what you write in any language, certainly not an elegant language.

But I am sure if I tell "you are the guy!" you will reply: "of course I am", without even a "thanks".

[Armin K]

Replying to fo:

On comment:5:

Thanks in advance if a better solution is presented.

You just solved elsewhere.

Last time I tried to fix something in the main branch it ended up being reverted for no good reason.

But this always what happens, I did many things before, trying to help the other branch, before that, to as compliment to people from the other branch, the response was disappointing. I asked for help from people of the other branch even when it was not even discussed to start, the response was disappointing.

I merge your changes all the time. You can try meging our changes once upon a time.

A non-rude attitude would be putting the solution here:

"You are missing... If you do this and that..."

The solution was in the comment 2. I just "realized it" and even said so in my "fixed ..." comment.

Or perhaps we have a cultural barrier, making it impossible collaborating with each other.

I'm afraid the interaction of the other branch with me will never improve. Please, someone else take their tickets, complaints, posts, etc. I tried but always get in trouble with them. I will eventually try to read them, but from now on, I'm trying to have peace, and will do nothing related to that branch.

Take it as you please. The issues pointed in the tickets are present in the main book too. It's our way of "giving back". We can stop doing that if you please, but that won't bring you nothing good.

At the moment, I am strongly resisting to blocking anything come from there.

On comment:8

Also, "Ugly workaround" isn't rude language (yet alone low level - I don't speak C, sorry)

I see. You think it is very elegant language.

It's a valid English word and not on a list of foul words.

​http://dictionary.reference.com/browse/ugly (see 2.)

​http://lmgtfy.com/?q=ugly+workaround+site%3Alists.linuxfromscratch.org

Of course, you do as you like.

I do as I think it's correct. At least I can admit my work was sort of wrong (or can be improved) and accept someone elses solution anytime.

I'm sorry, I don't speak C and don't understand what you write in any language, certainly not an elegant language.

But I am sure if I tell "you are the guy!" you will reply: "of course I am", without even a "thanks".

[Fernando de Oliveira]

Fixed at r13892.