I dont have a patch for sphinx to fix that, but what I say is that patching 59 packages to remove |today| instead of changing sphinx /somehow/ is a waste of resources.
On Mon, Jun 29, 2015 at 3:26 PM, Dmitry Shachnev <mity...@debian.org> wrote: > Hi Sandro, > > On Mon, 29 Jun 2015 15:11:00 -0400, Sandro Tosi wrote: >> well that requires to carry the patch in all the packages using >> |today| instead of adapt sphinx to what Debian wants to achieve >> (reproducible build) in the place that makes more sense: the tool >> generating the doc. YMMV tho > > According to codesearch, only 59 packages out of 608 using Sphinx have > |today| somewhere in their .rst files [1]. And I believe most of those 59 > already have bugs filed for them. > > |today| is for Sphinx the same as __DATE__ is for a C compiler. You do not > suggest to patch gcc to remove support for __DATE__, do you? > > Anyway, if you provide a suggestion for how to fix this on Sphinx side > (not *so* hackish as parsing d/changelog), I will look at it. > > -- > Dmitry Shachnev -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cab4xwxzqnbltisbrd2vbjzozwuwtwgzcazhvnumfo6yx-8f...@mail.gmail.com
