On Wed, Mar 19, 2014 at 23:45:57 +0100, Sebastiaan Couwenberg wrote: > On 03/18/2014 06:45 PM, Julien Cristau wrote: > > On Tue, Mar 18, 2014 at 00:56:48 +0100, Sebastiaan Couwenberg > > wrote: > > > >> With osgEarth 2.4 and QGIS 2.2 added to the mix, the process > >> becomes: > >> > >> 1) upload spatialite 4.1.1-6 to unstable 2) upload > >> librasterlite 1.1g-4 to unstable 3) binnmu mapnik > >> 2.2.0+ds1-6 in unstable > > > > 1 and 2 happened, so I've done 3 (with a dep-wait on > > librasterlite2). > > > >> 4) upload libgaiagraphics 0.5-2 to unstable 5) upload > >> spatialite-tools 4.1.1-3 to unstable 6) upload > >> spatialite-gui 1.7.1-3 to unstable 7) upload pyspatialite > >> 3.0.1-5 to unstable > > 4 to 7 also happened. > > But only libgaiagraphics is currently built for all architectures, the > others still need to be built on hurd-i386, as does mapnik. > > >> 8) binnmu gdal 1.10.1+dfsg-4 in unstable > > With both spatialite and librasterlite built on all architectures, > it's time for GDAL: > > nmu gdal_1.10.1+dfsg-4+b1 . ALL . -m "Rebuild against libspatialite5" > I'm waiting for the current version here (for the armadillo transition) to move to testing, which should happen tonight. > >> 9) binnmu merkaartor 0.18.1-3 in unstable > > Can be scheduled now too, or maybe wait for GDAL first. > > nmu merkaartor_0.18.1-3+b2 . ALL . -m "Rebuild against libspatialite5" > I'll do that together with gdal. > >> 10) upload osgearth 2.5.0+dfsg-1 to unstable 11) upload > >> qgis 2.2.0-1 to unstable > > Will happen after the GDAL rebuild. > Looks like that's happened anyway. Is anyone taking care of mapnik? Cheers, Julien
Attachment:
signature.asc
Description: Digital signature