On 27/05/16 11:20, Sebastiaan Couwenberg wrote:
> On 05/27/2016 11:12 AM, Emilio Pozuelo Monfort wrote:
>> On 27/05/16 01:45, Sebastiaan Couwenberg wrote:
>>> On 05/22/2016 12:20 PM, Sebastiaan Couwenberg wrote:
>>>> On 05/21/2016 11:19 AM, Emilio Pozuelo Monfort wrote:
>>>>> On 20/05/16 16:07, Sebastiaan Couwenberg wrote:
>>>>>> On 05/20/2016 11:27 AM, Sebastiaan Couwenberg wrote:
>>>>>>> On 05/14/2016 11:30 AM, Bas Couwenberg wrote:
>>>>>>>> The vtk6 issue on mipsel remains. texlive-bin (2016.20160513.41080-1)
>>>>>>>> fixed the FTBFS on most architectures, but still fails on mips, mipsel 
>>>>>>>> &
>>>>>>>> sparc64. I've reported #824260 for this.
>>>>>>>
>>>>>>> texlive-bin on mipsel has been fixed, and r-base is now also available
>>>>>>> on mipsel which should unblock the mipsel build of vtk6, but that hasn't
>>>>>>> started yet.
>>>>>>
>>>>>> tex-common fails to install on mipsel preventing vtk6 builds. I've
>>>>>> reported this in #824862.
>>>>>
>>>>> Thanks. We're also waiting for the d-i release, as mapnik is waiting for
>>>>> harfbuzz which is blocked because of the udeb.
>>>>>
>>>>> So let's wait a couple of days and see where we stand then.
>>>>
>>>> The tex-common installation failure can be worked around by installing
>>>> the context package.
>>>>
>>>> The vtk6 build on mipsel is now also blocked by gtk+3.0 being
>>>> BD-uninstallable on the all architecture, a source-full upload of
>>>> gtk+3.0 should resolve that. I've reported this issue in #824999.
>>>
>>> The vtk6 build for mipsel is finally here, thanks to the tex-common and
>>> gtk+3.0 fixes in their latest uploads.
>>
>> And to the fact that I bumped its build priority when gtk+ got fixed :)
> 
> I didn't know you could do that. Thank you!
> 
>>> I did not expect the vtk6 build before the end of the weekend, so I
>>> updated a couple of rdeps recently which haven't aged 5 days yet.
>>> pktools, qgis & otb need one more day, and postgis needs two.
>>
>> qgis and otb are not in testing so are not a problem. As for pktools, I 
>> already
>> urgented it a couple of days ago. Let's see if everything migrates in the 
>> next
>> non-crashy britney run.
> 
> Shouldn't postgis get an urgent hint too then?

AFAICS that doesn't depend on gdal-abi-*, only on libgdal. So it doesn't need to
migrate with the rest of the packages.

Cheers,
Emilio

Reply via email to