[mapnik] 01/01: Release to unstable

[Sebastiaan Couwenberg]

Hi Jérémy,

Thanks for the quick feedback.

On 05/27/2015 10:18 PM, Jérémy Lal wrote:
> 2015-05-27 22:08 GMT+02:00 Sebastiaan Couwenberg <sebastic at xs4all.nl>:
> 
>> On 05/27/2015 09:53 PM, Jérémy Lal wrote:
>>
>>>>     Release to unstable
>>
>>>
>> Why did you decide to upload to unstable instead of experimental after all?
>>
>>>
>> I don't think an upload to unstable is a good idea at this point.
>>
>>>
>> Kind Regards,
>>
>>>
>> Bas
>>
> 
> Since we have a major soname bump, this new version won't replace the old
> one
> right away. Packages depending on version 2.2 will still work and won't be
> broken.
> Only rebuilds against latest libmapnik-dev 3.0.0 will.
> 
> I figured that and went for unstable. Mind that version 3.0.0-rc3 is as
> close to final
> version as it can get - there is actually nothing experimental in either
> upstream
> version, nor debian packaging. The only experience is seeing how it will
> build on
> other platforms.
> 
> If you prefer, you can also block migration to testing with a bug.

To better evaluate the impact I whipped up a quick transition tracker,
and the number of affected reverse dependencies is much more limited
than I thought.

http://linuxminded.nl/tmp/pkg-grass-transitions/html/mapnik.html

The mapnik update only affects mapnik-vector-tile, monav & node-mapnik,
so it's not much of an issue after all.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1