bug#26604: documentation: pdf generation is broken

bug#26604: documentation: pdf generation is broken

[ng0]

As long as I run guix I was never able to build the documentation
as pdf. What's wrong with it?

[user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
  TEXI2PDF doc/guix.pdf
  /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
  make: *** [Makefile:3591: doc/guix.pdf] Error 1

-- 
PGP and more: https://people.pragmatique.xyz/ng0/

bug#26604: documentation: pdf generation is broken

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 713 bytes --]

ng0 <contact.ng0@cryptolab.net> writes:

> As long as I run guix I was never able to build the documentation
> as pdf. What's wrong with it?
>
> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>   TEXI2PDF doc/guix.pdf
>   /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
>   make: *** [Makefile:3591: doc/guix.pdf] Error 1

I looked into this a week or two ago.  I think we're waiting for a newer
release of automake?  Perhaps John Darrington knows more.  See this
email thread, which I found at the time and seems to contain the
relevant information:

https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01074.html

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#26604: documentation: pdf generation is broken

[ng0]

Chris Marusich transcribed 1.7K bytes:
> ng0 <contact.ng0@cryptolab.net> writes:
> 
> > As long as I run guix I was never able to build the documentation
> > as pdf. What's wrong with it?
> >
> > [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
> >   TEXI2PDF doc/guix.pdf
> >   /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
> >   make: *** [Makefile:3591: doc/guix.pdf] Error 1
> 
> I looked into this a week or two ago.  I think we're waiting for a newer
> release of automake?  Perhaps John Darrington knows more.  See this
> email thread, which I found at the time and seems to contain the
> relevant information:
> 
> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01074.html
> 
> -- 
> Chris

Oh, right… I've seen this scroll by some time ago.
Okay, since there is no associated open bug (at least with the
obvious keywords), I'll leave this bug open and once
the .pdf generates again it can be closed.

-- 
PGP and more: https://people.pragmatique.xyz/ng0/

bug#26604: documentation: pdf generation is broken

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

ng0@pragmatique.xyz writes:

> Chris Marusich transcribed 1.7K bytes:
>> ng0 <contact.ng0@cryptolab.net> writes:
>> 
>> > As long as I run guix I was never able to build the documentation
>> > as pdf. What's wrong with it?
>> >
>> > [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>> >   TEXI2PDF doc/guix.pdf
>> >   /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
>> >   make: *** [Makefile:3591: doc/guix.pdf] Error 1
>> 
>> I looked into this a week or two ago.  I think we're waiting for a newer
>> release of automake?  Perhaps John Darrington knows more.  See this
>> email thread, which I found at the time and seems to contain the
>> relevant information:
>> 
>> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01074.html
>> 
>> -- 
>> Chris
>
> Oh, right… I've seen this scroll by some time ago.
> Okay, since there is no associated open bug (at least with the
> obvious keywords), I'll leave this bug open and once
> the .pdf generates again it can be closed.

Sounds good.  I guess I should have opened up a bug report myself.
Thank you for doing it!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#26604: documentation: pdf generation is broken

[Ludovic Courtès]

Chris Marusich <cmmarusich@gmail.com> skribis:

> ng0 <contact.ng0@cryptolab.net> writes:
>
>> As long as I run guix I was never able to build the documentation
>> as pdf. What's wrong with it?
>>
>> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>>   TEXI2PDF doc/guix.pdf
>>   /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
>>   make: *** [Makefile:3591: doc/guix.pdf] Error 1
>
> I looked into this a week or two ago.  I think we're waiting for a newer
> release of automake?

AFAIK the ‘texinfo.tex’ file that Automake 1.15 installs is good enough,
as shown by
<https://hydra.gnu.org/job/gnu/master/guix-0.12.0-9.25a4.x86_64-linux>
<https://hydra.gnu.org/build/2017216/log/raw>.

Can you try running “autoreconf -vfi” with Automake 1.15 installed?

FWIW, I have:

--8<---------------cut here---------------start------------->8---
$ grep def.texinfoversion build-aux/texinfo.tex 
\def\texinfoversion{2016-09-18.18}
$ grep def.texinfoversion $(find $(guix build automake) -name texinfo.tex)
\def\texinfoversion{2013-02-01.11}
$ grep def.texinfoversion ~/src/gnulib/build-aux/texinfo.tex 
\def\texinfoversion{2017-04-14.11}
$ (cd ~/src/gnulib/ ; git describe)
v0.1-1312-ga87d5e5c6
--8<---------------cut here---------------end--------------->8---

HTH,
Ludo’.

bug#26604: documentation: pdf generation is broken

[zimoun]

Dear,

On Fri, 05 May 2017 at 20:53, ludo@gnu.org (Ludovic Courtès) wrote:
> Chris Marusich <cmmarusich@gmail.com> skribis:
>> ng0 <contact.ng0@cryptolab.net> writes:

>>> As long as I run guix I was never able to build the documentation
>>> as pdf. What's wrong with it?
>>>
>>> [user@abyayala ~/src/guix/guix]$ make doc/guix.pdf
>>>   TEXI2PDF doc/guix.pdf
>>>   /gnu/store/jz7jq4w8d4czvgnk9as07rrdbcfjjgjj-profile/bin/texi2dvi: pdftex
>>> exited with bad status, quitting.
>>>   make: *** [Makefile:3591: doc/guix.pdf] Error 1
>>
>> I looked into this a week or two ago.  I think we're waiting for a newer
>> release of automake?
>
> AFAIK the ‘texinfo.tex’ file that Automake 1.15 installs is good enough,
> as shown by
> <https://hydra.gnu.org/job/gnu/master/guix-0.12.0-9.25a4.x86_64-linux>
> <https://hydra.gnu.org/build/2017216/log/raw>.

I do not know what I miss but I get this error:

--8<---------------cut here---------------start------------->8---
$ guix environment -C guix --ad-hoc texlive-base texlive-fonts-ec
[env]$ ./bootstrap && ./configure --localstatedir=/var/ && make
[env]$ make doc/guix.pdf
  TEXI2PDF doc/guix.pdf

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+3/600 --dpi 603 ecrm1095
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+3/600; nonstopmode; input ecrm1095
This is METAFONT, Version 2.7182818 (TeX Live 2019) (preloaded base=mf)

(/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/ecrm1095.mf (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exbase.mf) (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/ecrm.mf (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exroman.mf
 Ok (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exaccess.mf

[...]

 Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57]) (/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/share/texmf-dist/fonts/source/jknappen/ec/exrligtb.mf
 Ok) ) ) )
(some charht values had to be adjusted by as much as 0.07599pt)
Font metrics written on ecrm1095.tfm.
Output written on ecrm1095.603gf (256 characters, 55528 bytes).
Transcript written on ecrm1095.log.
mktexpk: /home/simon/src/guix/wk/emacs-vm/doc/guix.t2p/doc!guix.t2d/pdf/build/ecrm1095.603pk: successfully generated.
/gnu/store/jq35y4na0bciw1i60p9z44aq82dsp5x2-profile/bin/texi2dvi: pdftex exited with bad status, quitting.
make: *** [Makefile:4181: doc/guix.pdf] Error 1
--8<---------------cut here---------------end--------------->8---

And it is a bit cryptic…  What am I doing wrong?


All the best,
simon

bug#26604: documentation: pdf generation is broken

[Andreas Enge]

Hello,

On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
> [env]$ make doc/guix.pdf

try this instead:
    make V=1 pdf
which will print what happens.

I have the monolithic texlive package in my profile and building the pdf
"almost worked":
...
doc/images/coreutils-size-map.png>
!pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
 ==> Fatal error occurred, no output PDF file produced!

It turns out there are a bunch of empty .png files in doc/images/, with
corresponding non-empty .dot files. I deleted them and installed graphviz
into my profile in the hope that "make pdf" would create the missing
.png files, but it does not.

However, the following "almost almost" worked:
- remove the empty .png files and install graphviz
- "make"
- "make pdf"
I obtained the English, German, French and Spanish pdf documentation, but
then a lot of complaints about unicode characters for the Russian
documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).

Andreas

bug#26604: documentation: pdf generation is broken

[Ludovic Courtès]

Hi,

Andreas Enge <andreas@enge.fr> skribis:

> On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
>> [env]$ make doc/guix.pdf
>
> try this instead:
>     make V=1 pdf
> which will print what happens.
>
> I have the monolithic texlive package in my profile and building the pdf
> "almost worked":
> ...
> doc/images/coreutils-size-map.png>
> !pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
>  ==> Fatal error occurred, no output PDF file produced!
>
> It turns out there are a bunch of empty .png files in doc/images/, with
> corresponding non-empty .dot files. I deleted them and installed graphviz
> into my profile in the hope that "make pdf" would create the missing
> .png files, but it does not.
>
> However, the following "almost almost" worked:
> - remove the empty .png files and install graphviz
> - "make"
> - "make pdf"
> I obtained the English, German, French and Spanish pdf documentation, but
> then a lot of complaints about unicode characters for the Russian
> documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).

Simon, can you close the issue if this is fine on your side as well?

Maybe it’s a matter (as usual…) of choosing the right texlive-* packages.

Thanks,
Ludo’.

bug#26604: documentation: pdf generation is broken

[zimoun]

Hi,

On Fri, 16 Oct 2020 at 12:13, Ludovic Courtès <ludo@gnu.org> wrote:
> Andreas Enge <andreas@enge.fr> skribis:

> > On Mon, Sep 28, 2020 at 09:57:43PM +0200, zimoun wrote:
> >> [env]$ make doc/guix.pdf
> >
> > try this instead:
> >     make V=1 pdf
> > which will print what happens.

Thanks for the tip.


> > I have the monolithic texlive package in my profile and building the pdf
> > "almost worked":
> > ...
> > doc/images/coreutils-size-map.png>
> > !pdfTeX error: /home/andreas/.guix-profile/bin/pdftex (file doc/images/coreutils-graph.png): reading image file failed
> >  ==> Fatal error occurred, no output PDF file produced!
> >
> > It turns out there are a bunch of empty .png files in doc/images/, with
> > corresponding non-empty .dot files. I deleted them and installed graphviz
> > into my profile in the hope that "make pdf" would create the missing
> > .png files, but it does not.
> >
> > However, the following "almost almost" worked:
> > - remove the empty .png files and install graphviz
> > - "make"
> > - "make pdf"
> > I obtained the English, German, French and Spanish pdf documentation, but
> > then a lot of complaints about unicode characters for the Russian
> > documentation (and "make doc/guix.zh_CN.pdf" also has unicode problems).
>
> Simon, can you close the issue if this is fine on your side as well?

Well, it is not satisfactory for me, yet.  It is still "almost almost"
and needs some wizardies to work.  At least the doc should be updated
and maybe a manifest file with the correct TeX packages.  I mean we
have modular texlive and we recommend to use it but we do not use it
for our own infrastructure and then we rely on the BIG texlive
package.  Hum?! :-)

> Maybe it’s a matter (as usual…) of choosing the right texlive-* packages.

They should be documented at least.  (How to find them is another story. ;-))


All the best,
simon

bug#26604: documentation: pdf generation is broken

[Ricardo Wurmus]

Commit 71d7702faed660567d165488ef9d3bde287786d5 (on core-updates) 
should have fixed this problem already.

See also this thread: 
https://yhetil.org/guix-devel/86lfg6z0lm.fsf@gmail.com/

Shall we close this now?

-- 
Ricardo

bug#26604: documentation: pdf generation is broken

[zimoun]

Hi Ricardo,

On Mon, 03 May 2021 at 16:06, Ricardo Wurmus <rekado@elephly.net> wrote:

> Shall we close this now?

Personally, I am still puzzled to build PDFs of the documentation, even
on core-updates, though I have not followed the recent updates on
master.  Maybe I am doing wrong but I still get some errors, as reported
in late messages of the thread [1].  Basically, it ends with:

  guix environment -C guix --ad-hoc …wizard stuff…
  …
  make pdf
  …wizard stuff…

I should still miss something.

1: <https://yhetil.org/guix-devel/86lfg6z0lm.fsf@gmail.com/T/#t>


Cheers,
simon

bug#26604: documentation: pdf generation is broken

[Ricardo Wurmus]

zimoun <zimon.toutoune@gmail.com> writes:

> Hi Ricardo,
>
> On Mon, 03 May 2021 at 16:06, Ricardo Wurmus 
> <rekado@elephly.net> wrote:
>
>> Shall we close this now?
>
> Personally, I am still puzzled to build PDFs of the 
> documentation, even
> on core-updates, though I have not followed the recent updates 
> on
> master.  Maybe I am doing wrong but I still get some errors, as 
> reported
> in late messages of the thread [1].  Basically, it ends with:
>
>   guix environment -C guix --ad-hoc …wizard stuff…
>   …
>   make pdf
>   …wizard stuff…
>
> I should still miss something.

At least the first “wizard stuff” is merely a list of packages. 
There isn’t anything we can do to avoid the selection of packages, 
because that stuff is modular by design.  We could have an 
arbitrary collection of Texlive packages, but I’m sure we can’t 
agree on any good set because what exactly is needed depends on 
the document.

It’s like creating an arbitrary set of R packages that should work 
well for any number of projects.

If the problem is in figuring out what Texlive packages to install 
for generating the Guix manual: we can either document that or add 
the required packages to the inputs.

If you still get errors relating to fonts or font maps: this has 
been fixed on the “master” branch; the texlive-configuration 
profile hook didn’t update the font maps.

-- 
Ricardo

bug#26604: documentation: pdf generation is broken

[zimoun]

Hi,

On Tue, 4 May 2021 at 12:04, Ricardo Wurmus <rekado@elephly.net> wrote:

> At least the first “wizard stuff” is merely a list of packages.
> There isn’t anything we can do to avoid the selection of packages,
> because that stuff is modular by design.  We could have an
> arbitrary collection of Texlive packages, but I’m sure we can’t
> agree on any good set because what exactly is needed depends on
> the document.

[...]

> If the problem is in figuring out what Texlive packages to install
> for generating the Guix manual: we can either document that or add
> the required packages to the inputs.

I agree.  Maybe via a manifest file?

> If you still get errors relating to fonts or font maps: this has
> been fixed on the “master” branch; the texlive-configuration
> profile hook didn’t update the font maps.

Cool!  I have missed.

Well, let close this old bug. \o/

Cheers,
simon

bug#26604: documentation: pdf generation is broken

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

zimoun <zimon.toutoune@gmail.com> skriver:

> Hi,
>
> On Tue, 4 May 2021 at 12:04, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> At least the first “wizard stuff” is merely a list of packages.
>> There isn’t anything we can do to avoid the selection of packages,
>> because that stuff is modular by design.  We could have an
>> arbitrary collection of Texlive packages, but I’m sure we can’t
>> agree on any good set because what exactly is needed depends on
>> the document.
>
> [...]
>
>> If the problem is in figuring out what Texlive packages to install
>> for generating the Guix manual: we can either document that or add
>> the required packages to the inputs.
>
> I agree.  Maybe via a manifest file?
>
>> If you still get errors relating to fonts or font maps: this has
>> been fixed on the “master” branch; the texlive-configuration
>> profile hook didn’t update the font maps.
>
> Cool!  I have missed.
>
> Well, let close this old bug. \o/

Agreed, closing!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]