On 09/01/17 17:35 +0100, Flavio Percoco wrote:
On 09/01/17 15:02 +0100, Andreas Jaeger wrote:
On 2016-12-12 09:22, Flavio Percoco wrote:
On 11/12/16 13:32 +0100, Flavio Percoco wrote:
On 09/12/16 17:20 +0100, Flavio Percoco wrote:
Greetings,
Some docs jobs seem to be broken by the latest
On 09/01/17 15:02 +0100, Andreas Jaeger wrote:
On 2016-12-12 09:22, Flavio Percoco wrote:
On 11/12/16 13:32 +0100, Flavio Percoco wrote:
On 09/12/16 17:20 +0100, Flavio Percoco wrote:
Greetings,
Some docs jobs seem to be broken by the latest (or not?) docutils
release. The
breakage seems to
On 2016-12-12 09:22, Flavio Percoco wrote:
> On 11/12/16 13:32 +0100, Flavio Percoco wrote:
>> On 09/12/16 17:20 +0100, Flavio Percoco wrote:
>>> Greetings,
>>>
>>> Some docs jobs seem to be broken by the latest (or not?) docutils
>>> release. The
>>> breakage seems to be related to the latest
On 11/12/16 13:32 +0100, Flavio Percoco wrote:
On 09/12/16 17:20 +0100, Flavio Percoco wrote:
Greetings,
Some docs jobs seem to be broken by the latest (or not?) docutils release. The
breakage seems to be related to the latest addition of the bages patch. The docs
generation doesn't like to
On 09/12/16 17:20 +0100, Flavio Percoco wrote:
Greetings,
Some docs jobs seem to be broken by the latest (or not?) docutils release. The
breakage seems to be related to the latest addition of the bages patch. The docs
generation doesn't like to have remote images. It used to be a warning but it
Greetings,
Some docs jobs seem to be broken by the latest (or not?) docutils release. The
breakage seems to be related to the latest addition of the bages patch. The docs
generation doesn't like to have remote images. It used to be a warning but it
seems to have turned into an error now. While
