> On 03/19/2014 09:28 PM, Aurelien Jarno wrote:
> > On Wed, Mar 19, 2014 at 09:18:20PM +0100, Sebastiaan Couwenberg wrote:
> I'm not sure what the best course of action is. But Jérémy suggested
> backporting a change from upstream, I'll give that a go tomorrow:
>
> https://github.com/mapnik/mapni
On 03/19/2014 09:28 PM, Aurelien Jarno wrote:
> On Wed, Mar 19, 2014 at 09:18:20PM +0100, Sebastiaan Couwenberg wrote:
>> At the end of last year during the mapnik transition the memory
>> exhaustion was fixed by scheduling the builds on buildds with more memory.
>>
>> https://bugs.debian.org/cgi-b
On Wed, Mar 19, 2014 at 09:18:20PM +0100, Sebastiaan Couwenberg wrote:
> At the end of last year during the mapnik transition the memory
> exhaustion was fixed by scheduling the builds on buildds with more memory.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729121#16
>
> Is that an opti
Source: mapnik
Version: 2.2.0+ds1-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 731403 with -1
Hi,
your package FTBFS on the mips and mipsel buildds:
> g++ -o bindings/python/mapnik_geometry.os -c -g -O2 -Wformat
> -Werror=forma
At the end of last year during the mapnik transition the memory
exhaustion was fixed by scheduling the builds on buildds with more memory.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729121#16
Is that an option now too? Or are the more capable buildds already used?
Kind Regards,
Bas
--
5 matches
Mail list logo