Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LaTeX docs build blows up #1836

Closed
takluyver opened this issue Mar 19, 2013 · 7 comments
Closed

LaTeX docs build blows up #1836

takluyver opened this issue Mar 19, 2013 · 7 comments

Comments

@takluyver
Copy link
Contributor

From the latest Launchpad builds, the docs have failed in spectacular fashion. There are some docstring changes in recent commits (e.g. 9159f11), but nothing obviously amiss. It might also be that dependencies have shifted, although at a glance it doesn't look like there have been major updates recently.

Pages and pages of warnings (mostly "Hyper reference ... undefined") end with:

<hexbin_demo.pdf, id=45117, 397.485pt x 325.215pt> <use hexbin_demo.pdf>
<use hexbin_demo.pdf>
Underfull \hbox (badness 10000) in paragraph at lines 95148--95148
\T1/txr/m/it/10.95 tom=None\T1/txr/m/n/10.95 , \T1/txr/m/it/10.95 hist-type='ba
r'\T1/txr/m/n/10.95 , \T1/txr/m/it/10.95 align='mid'\T1/txr/m/n/10.95 , \T1/txr
/m/it/10.95 ori-en-ta-tion='vertical'\T1/txr/m/n/10.95 , \T1/txr/m/it/10.95 rwi
dth=None\T1/txr/m/n/10.95 ,
[934 <./hexbin_demo.pdf>]

! LaTeX Error: Too deeply nested.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...                                              

l.95200 \begin{Verbatim}[commandchars=\\\{\}]

? 
! Emergency stop.
 ...                                              

l.95200 \begin{Verbatim}[commandchars=\\\{\}]

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on Matplotlib.log.
make[1]: *** [Matplotlib.pdf] Error 1

Buildlog

@pelson
Copy link
Member

pelson commented Mar 19, 2013

Ouch. Thanks for the head-up @takluyver. The commit you reference was a PR from @NelleV. @NelleV, do you see this on your machine?

@NelleV
Copy link
Member

NelleV commented Mar 19, 2013

I just tested and I seem to have this error too.

@takluyver
Copy link
Contributor Author

Just to let you know, this is still failing. I've turned the daily build off for now - let me know when this should be fixed, and I'll turn it back on. Or if it's going to take a long time, I could tell it to skip the pdf build.

@mdboom
Copy link
Member

mdboom commented Mar 25, 2013

@takluyver: I think @NelleV is probably still in the best position to get to the bottom of this and revert what's necessary, but if it continues later in the week I'll try to find some time myself.

Tangentially -- if Ubuntu/Launchpad is doing daily builds from git, is there a way for non-Debian-Ubuntu users to see the doc build products? That could be really handy for a lot of reasons.

@takluyver
Copy link
Contributor Author

When it builds successfully, you should be able to download a python-matplotlib-doc....deb file from this page:
https://code.launchpad.net/~takluyver/+archive/matplotlib-daily/+packages

.deb packages are apparently stored in the 'ar' archive format - the standard Archive Manager tool on Gnome can open them.

If you want to get more sophisticated, then you could set up an Ubuntu server, add the PPA, configure it to update automatically, and get it to serve the docs at devdocs.matplotlib.org.

@NelleV
Copy link
Member

NelleV commented Apr 22, 2013

I've finally took the time to have a closer look at the problem: it's more a latex problem and a sphinx problem. We'll have to adapt the documentation to avoid those. I've got a quickfix, but I'm not happy with it.

I'll keep you posted.

@mdboom
Copy link
Member

mdboom commented Apr 22, 2013

I just remembered we had a similar problem with LaTeX "too deeply nested" in astropy -- the solution there was to use the enumitem package. But I'm also not opposed to reducing the levels of nesting as you've done here.

mdboom/astropy@33a9779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants