On Thu, Apr 11, 2019 at 12:02 PM Christoph Berg <m...@debian.org> wrote:
> Re: Dave Page 2019-04-11 < > ca+ocxoyb3wkj5u+uv+a_4sk_7i15ok4dt01zidj5cpma528...@mail.gmail.com> > > > Fwiw, this release broke compatibility with the sphinx version in > > > Ubuntu xenial (16.04), 1.3.6-2ubuntu1.2. > > > > Hmm, that was changed in 4.4. I assume Xenial has an ancient version of > > Sphinx? > > 1.3, as said above. > Oh, sorry - I parsed that as part of the Ubuntu version. > > > Can a newer version be used for running the build? It doesn't need to be > > there at runtime. > > I'd rather not get into the business of maintaining a sphinx backport. > Such packages tend to have a gazillion of dependencies for plugins. > > I haven't verified the result, are the tables expected to look very > bad now that I removed the :widths: options? It will be a little bit > annoying to maintain that patch, but it's not really that bad. > The annoying thing is, they're not used at all by the HTML output you're producing I don't think. They're used by the latex builds like PDF. Would it make sense to run the doc build in a temporary Python venv that has the newer Sphinx installed? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
