On Tue, Oct 24, 2017 at 02:04:44PM +0100, Dimitri John Ledkov wrote: > On 24 October 2017 at 04:00, Steve M. Robbins <st...@sumost.ca> wrote:
> > If I re-enable the doc packages and build, lintian spews dozens of > > errors of three kinds: privacy-breach-logo, privacy-breach-generic, > > privacy-breach-uses-embedded-file. > > > > E: libboost1.65-doc: privacy-breach-logo > > usr/share/doc/libboost1.65-doc/HTML/doc/html/quickbook/syntax/block.html > > (http://sourceforge.net/sflogo.php?group_id=28447&type=1) > > W: libboost1.65-doc: privacy-breach-generic > > usr/share/doc/libboost1.65-doc/HTML/libs/assert/doc/html/assert.html > > (https://fonts.googleapis.com/css?family=open+sans:300,300italic,400,400italic,600,600italic%7cnoto+serif:400,400italic,700,700italic%7cdroid+sans+mono:400,700) > > E: libboost1.65-doc: privacy-breach-uses-embedded-file > > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/accessors_8hpp.html > > You may use the libjs-mathjax package. > > (https://cdn.mathjax.org/mathjax/latest/mathjax.js) > > E: libboost1.65-doc: privacy-breach-uses-embedded-file > > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adapt__adt_8hpp.html > > You may use the libjs-mathjax package. > > (https://cdn.mathjax.org/mathjax/latest/mathjax.js) > > E: libboost1.65-doc: privacy-breach-uses-embedded-file > > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adapt__struct_8hpp.html > > You may use the libjs-mathjax package. > > (https://cdn.mathjax.org/mathjax/latest/mathjax.js) > > E: libboost1.65-doc: privacy-breach-uses-embedded-file > > usr/share/doc/libboost1.65-doc/HTML/libs/hana/doc/html/adjust_8hpp.html You > > may use the libjs-mathjax package. > > (https://cdn.mathjax.org/mathjax/latest/mathjax.js) > > > > .... etc. > > > > The google fonts in assert appear to be generated by calling asciidoc > -> i wonder if debian's asciidoc can be made to not generate those > and/or use local fonts? > > For the mathjax, there appears to be support in Doxygen files to > specify a url from libjs-mathjax package. > > Let's see if we can fix up these docs to be offline, and also file > issues as appropriate about things we cannot offline. OK. So the original approach -- the one that generated the big lintian list -- is to simply use the files as they appear in the source distribution. To do what you suggest, I think we need to move to a strategy that actually generates documentation during the package build. Will you look into setting that up? The 1.65.1 is otherwise ready to go, from my point of view. Best, -Steve
signature.asc
Description: PGP signature
