Re: Sphinx 1.3 in Debian experimental

2015-07-09 Thread Dmitry Shachnev
Hi, On Wed, 08 Jul 2015 15:11:18 +0300, Dmitry Shachnev wrote: > I will write a patch to add support for this to Sphinx when I have time. Here it is: https://github.com/sphinx-doc/sphinx/pull/1954 Will upload it to Debian when it is acknowledged by upstream. -- Dmitry Shachnev signature.asc De

Re: Sphinx 1.3 in Debian experimental

2015-07-08 Thread Dmitry Shachnev
Hi Jéremy, On Tue, 7 Jul 2015 12:55:25 +0200, Jéremy Bobbio wrote: > Our current proposal is to implement support for the SOURCE_DATE_EPOCH > environment variable. See: > https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal > > It's already implemented in help2man, and we have patches rea

Re: Sphinx 1.3 in Debian experimental

2015-07-07 Thread Jéremy Bobbio
Dmitry Shachnev: > 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. Our current proposal is to implement support for the SOURCE_DATE_EPOCH environment variable. See: https://wiki.debian.org/ReproducibleBuilds/Tim

Re: Sphinx 1.3 in Debian experimental

2015-07-02 Thread Dmitry Shachnev
Hi Tomasz, On Tue, 30 Jun 2015 21:59:00 +0200, Tomasz Rybak wrote: > According to Sphinx documentation > http://sphinx-doc.org/config.html#confval-html_last_updated_fmt > when "html_last_updated_fmt" is set, "Last updated on ..." should > be added to the bottom. Is this omission on purpose, or doe

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Tomasz Rybak
Dnia 2015-05-03, nie o godzinie 15:18 +0300, Dmitry Shachnev pisze: > Hi all, > > I have finally managed to finalize Sphinx 1.3 upload for > experimental. > > There are many new features and some incompatible changes, please see > the > changelog [1] for the full list of changes. > > If your p

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Sandro Tosi
On Tue, Jun 30, 2015 at 5:05 AM, Dmitry Shachnev wrote: > Hi, > > On Tue, 30 Jun 2015 10:47:34 +0200, Piotr Ożarowski wrote: >> [Dmitry Shachnev, 2015-06-30] >>> Looking at the source of Sphinx' distutils/setuptools command [1], >>> I see that pybuild can already help here by including something l

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Dmitry Shachnev
Hi, On Tue, 30 Jun 2015 10:47:34 +0200, Piotr Ożarowski wrote: > [Dmitry Shachnev, 2015-06-30] >> Looking at the source of Sphinx' distutils/setuptools command [1], >> I see that pybuild can already help here by including something like this >> in its generated setup.cfg: >> >> [build_sphinx] >>

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Piotr Ożarowski
[Dmitry Shachnev, 2015-06-30] > Looking at the source of Sphinx' distutils/setuptools command [1], > I see that pybuild can already help here by including something like this > in its generated setup.cfg: > > [build_sphinx] > today = {date from debian/changelog} [2] > > Piotr, do you think yo

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Dmitry Shachnev
Hi Paul, On Tue, 30 Jun 2015 13:17:53 +0800, Paul Wise wrote: > |today| sounds like a misfeature, more interesting would be |version| > or |source_date|. I agree. |version| is what the people usually need. And Sphinx has it, see . -- Dmitry

Re: Sphinx 1.3 in Debian experimental

2015-06-30 Thread Dmitry Shachnev
Hi, On Mon, 29 Jun 2015 16:14:02 -0400, Barry Warsaw wrote: > Maybe upstream would accept a patch similar to what I've done before. It > could map |today| to the value of an environment variable, if it's set. > E.g. something like SPHINX_TODAY. Then pybuild, dh_python{2,3}, or some other > infra

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Paul Wise
On Tue, Jun 30, 2015 at 4:14 AM, Barry Warsaw wrote: > Maybe upstream would accept a patch similar to what I've done before. It > could map |today| to the value of an environment variable, if it's set. > E.g. something like SPHINX_TODAY. Then pybuild, dh_python{2,3}, or some other > infrastructu

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Barry Warsaw
On Jun 29, 2015, at 04:02 PM, Sandro Tosi wrote: >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. Maybe upstream would accept a patch similar to what I've done before. It cou

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Sandro Tosi
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 wrote: > Hi Sandro, > > On Mon, 29 Jun 2015 15:11:00 -0400, Sandro Tosi wrote: >

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Dmitry Shachnev
On Mon, 29 Jun 2015 22:26:22 +0300, Dmitry Shachnev wrote: > According to codesearch, only 59 packages out of 608 using Sphinx have > |today| somewhere in their .rst files [1]. Forgotten reference: [1] queries I used: \|today\| path:.*\.rst# |today| in source files (not in co

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Dmitry Shachnev
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

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Sandro Tosi
On Mon, Jun 29, 2015 at 2:41 PM, Dmitry Shachnev wrote: > Hi Sandro, > > On Mon, 29 Jun 2015 14:08:40 -0400, Sandro Tosi wrote: >> that's great news! I just recently (like end of last week) received a >> patch for basemap to address dates in the doc, and it seemed like your >> effort and their wer

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Dmitry Shachnev
Hi Sandro, On Mon, 29 Jun 2015 14:08:40 -0400, Sandro Tosi wrote: > that's great news! I just recently (like end of last week) received a > patch for basemap to address dates in the doc, and it seemed like your > effort and their were not in sync. Looking at the patch in #790235, that is a differ

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Sandro Tosi
that's great news! I just recently (like end of last week) received a patch for basemap to address dates in the doc, and it seemed like your effort and their were not in sync. Might just be enough to give them a heads up so they dont waste more time in fixing docs when a the new release of sphinx w

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Dmitry Shachnev
Hi Sandro, On Mon, 29 Jun 2015 13:12:33 -0400, Sandro Tosi wrote: > would you mind talking to the build reproducible folks to understand > how to make sphinx generating reproducible builds by default (instead > of patching all the software using it)? Most of the issues are already fixed in 1.3 (i

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Barry Warsaw
On Jun 29, 2015, at 08:06 PM, Dmitry Shachnev wrote: >Your packages were failing with 1.3.1-1, but are not failing with svn build >because I fixed the issue :) Ah, I guess we need an ITP for snowballstemmer . >FWIW I have went through Yaroslav's logs and filed bugs for most of the >failing packa

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Sandro Tosi
Hi, would you mind talking to the build reproducible folks to understand how to make sphinx generating reproducible builds by default (instead of patching all the software using it)? On Mon, Jun 29, 2015 at 1:06 PM, Dmitry Shachnev wrote: > Hi Barry, > > On Mon, 29 Jun 2015 11:23:36 -0400, Barry

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Dmitry Shachnev
Hi Barry, On Mon, 29 Jun 2015 11:23:36 -0400, Barry Warsaw wrote: > My Perl is pretty rusty, but I am happy to help out with Sphinx as time > allows. Appreciated! > I just added a patch from upstream to support Python 3.5, which might > not help Debian right now, but is useful for my 3.5 rebuild

Re: Sphinx 1.3 in Debian experimental

2015-06-29 Thread Barry Warsaw
On May 03, 2015, at 03:18 PM, Dmitry Shachnev wrote: >I have finally managed to finalize Sphinx 1.3 upload for experimental. Thanks! I just added the Python 3.5 compatibility patch from upstream github to sphinx's svn. >Also, if someone is interested in helping me to maintain Sphinx is Debian,

Re: Sphinx 1.3 in Debian experimental

2015-05-07 Thread Yaroslav Halchenko
On Thu, 07 May 2015, Dmitry Shachnev wrote: > > so -- there is quite a few of new FTBFS. I will report more whenever it is > > done > Thanks a lot for running the rebuild! > How can I access the build logs? The files given in that table are not > available via HTTP on that server. yeah, sorr

Re: Sphinx 1.3 in Debian experimental

2015-05-06 Thread Dmitry Shachnev
Hi Yaroslav, On Wed, 6 May 2015 19:55:40 -0400, Yaroslav Halchenko wrote: > Hi Dmitry, > > thanks for maintaining sphinx and for uploading 1.3!!! > > I am not sure if you got time to do rebuild but meanwhile I ran it on my > box... > runs serially and box is getting aged so it is still running bu

Re: Sphinx 1.3 in Debian experimental

2015-05-06 Thread Yaroslav Halchenko
On Sun, 03 May 2015, Dmitry Shachnev wrote: > Hi all, > I have finally managed to finalize Sphinx 1.3 upload for experimental. > There are many new features and some incompatible changes, please see the > changelog [1] for the full list of changes. > If your package has Sphinx documentation, p