Hi On Fri, Dec 21, 2018 at 2:49 PM Sarah Conway Schnurr <xenophene...@gmail.com> wrote: > > Looks like the tablespace_dialog.rst was a processing/environmental error on > my end. Please disregard. > > However, there's another error I forgot to mention previously that is > reproducible in the community packages from Git for both 3.2, 3.6, and HEAD, > on a clean install: > > Running Sphinx v1.1.3 > loading pickled environment... not yet created > > Theme error: > no theme named 'classic' found (missing theme.conf?) > make[1]: *** [html] Error 1 > make[1]: Leaving directory `/home/sarah/websites/pgadmin4/docs/en_US' > make: *** [docs] Error 2 > > Removing that line fixes the error, but as before, not ideal:
Is your Sphinx an RPM installation? If so, they may have split that theme out into a different package. We always install using PIP, which works fine in every case I know of. > sed -i "/html_theme = 'classic'/d" docs/en_US/conf.py > > The PDF errors as mentioned previously in detail are additionally > reproducible in the community packages from Git for 3.2, 3.6, and HEAD. > > ! Use of \@icentercr doesn't match its definition. Yeah, I see that as well. There's something in the doc source that is getting converted into invalid TEX I think. I have no idea what though, as I haven't really used TEX directly in 20+ years. It seems like a Sphinx bug, in that it's quite happy with the input for other formats, but barfs on anything that uses TEX. Do you know anyone that is familiar with TEX that might be able to help? Maybe Joe? > On Fri, Dec 21, 2018 at 1:59 AM Dave Page <dp...@pgadmin.org> wrote: >> >> Hi Sarah, >> >> On Fri, Dec 21, 2018 at 3:16 AM Sarah Conway Schnurr >> <xenophene...@gmail.com> wrote: >> > >> > Hello! >> > >> > Came across a couple of errors when building HTML and PDF files with the >> > Makefile. >> > >> > System Info >> > >> > CentOS 7 >> > pdfTeX 3.1415926-2.5-1.40.14 (TeX Live 2013) >> > pgadmin4-3.2 >> > >> > HTML >> > >> > (Relevant) Output: >> > >> > $ make docs >> > ... >> > `tablespace_dialog.rst:: WARNING: document isn't included in any toctree` >> >> There's something very odd going on there - I can see from the git >> history that tablespace_dialog has been in the toc tree since at least >> mid 2016 >> (https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=history;f=docs/en_US/managing_cluster_objects.rst;h=a0d520ec187811f0c2bb3b28d8f196011730caee;hb=f62d35bf3c92a643c7d7f07b89df7ddff56bbf93) >> >> Is it present in your copy of managing_cluster_objects.rst? >> >> How did you get your source code BTW? Please test with 3.6 or git head >> - 3.2 is obsolete now. >> >> > Adding it to ignore_patterns in conf.py results in: >> > >> > Exception occurred: >> > File "/usr/lib/python2.7/site-packages/sphinx/builders/html.py", line >> > 407, in get_doc_context >> > display_toc = (self.env.toc_num_entries[docname] > 1), >> > KeyError: 'tablespace_dialog' >> > >> > Deleting the file in question - tablespace_dialog.rst - (obviously not the >> > ideal solution) resolves the error and allows the files to be built as >> > expected. >> > >> > PDF >> > >> > (Relevant) Output >> > >> > $ make docs-pdf >> > ... >> > (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1phv.fd) >> > [1{/usr/share/texlive >> > /texmf/fonts/map/pdftex/updmap/pdftex.map}] [2] >> > Adding blank page after the table of contents. >> > pdfTeX warning (ext4): destination with the same identifier (name{page.i}) >> > has >> > been already used, duplicate ignored >> > <to be read again> >> > \relax >> > l.113 \tableofcontents >> > [1]pdfTeX warning (ext4): destination with the same >> > iden >> > tifier (name{page.ii}) has been already used, duplicate ignored >> > <to be read again> >> > \relax >> > l.113 \tableofcontents >> > [2] <logo-right-128.png, id=23, 128.48pt x 128.48pt> >> > <use logo-right-128.png> <use logo-right-128.png> [1 >> > <./logo-right-128.png>] >> > [2] >> > Chapter 1. >> > ! Use of \@icentercr doesn't match its definition. >> > <argument> \def >> > >> > l.128 ...r{\index{Getting Started}Getting Started} >> > >> > ? >> > >> > Have not found a workaround for the PDF issue as of yet. >> > >> > Are these actual bugs or am I missing some kind of dependency? >> > >> > Thanks very much for your time & help, ahead of time. >> > >> > -- >> > Sarah Conway Schnurr >> >> >> >> -- >> Dave Page >> Blog: http://pgsnake.blogspot.com >> Twitter: @pgsnake >> >> EnterpriseDB UK: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company > > > > -- > Sarah Conway Schnurr -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
