Bug#830178: Possible fix

thanks a lot Piotr! these days i'm going thru the list of packages we care at work for stretch so a mail-ping was super effective :) On Wed, Nov 2, 2016 at 6:39 PM, Piotr Ożarowski wrote: > [Sandro Tosi, 2016-11-02] >> thanks! i pinged that bug to see if upstream will release a

Bug#830178: Possible fix

[Sandro Tosi, 2016-11-02] > thanks! i pinged that bug to see if upstream will release a new > version soo, if not we could just pick up that patch I uploaded -2, thanks for the reminder and sorry for the delay (RL, I will try to keep up a bit with Debian this weekend...)

Bug#830178: Possible fix

thanks! i pinged that bug to see if upstream will release a new version soo, if not we could just pick up that patch On Wed, Nov 2, 2016 at 6:05 PM, Nish Aravamudan wrote: > On Wed, Nov 2, 2016 at 3:00 PM, Sandro Tosi wrote: >> On Mon, 26 Sep

Bug#830178: Possible fix

On Wed, Nov 2, 2016 at 3:00 PM, Sandro Tosi wrote: > On Mon, 26 Sep 2016 17:34:47 -0700 Nish Aravamudan > wrote: >> So I am tracking the same issue seen on Ubuntu 16.10 and I found: >> >> https://github.com/sphinx-doc/sphinx/pull/2396 >> >> I

Bug#830178: Possible fix

On Mon, 26 Sep 2016 17:34:47 -0700 Nish Aravamudan wrote: > So I am tracking the same issue seen on Ubuntu 16.10 and I found: > > https://github.com/sphinx-doc/sphinx/pull/2396 > > I tested the following patch to the sourc3, and it does seem to build, > although I'm

Bug#830178: Possible fix

So I am tracking the same issue seen on Ubuntu 16.10 and I found: https://github.com/sphinx-doc/sphinx/pull/2396 I tested the following patch to the sourc3, and it does seem to build, although I'm not sure I fully understand why yet (I'm completely new to sphinx, just trying to help fix these