[mapnik] 01/01: Release to unstable
This is an automated email from the git hooks/post-receive script. kapouer pushed a commit to branch master in repository mapnik. commit 781b98bc3c3b0556b1f19543cca301c2a59fba7a Author: Jérémy Lal kapo...@melix.org Date: Wed May 27 21:13:35 2015 +0200 Release to unstable --- debian/changelog | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 6d2100a..fd7d0bd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -mapnik (3.0.0~rc3+ds-1) experimental; urgency=medium +mapnik (3.0.0~rc3+ds-1) unstable; urgency=medium * Imported Upstream version 3.0.0~rc3+ds * Python bindings are now in separate upstream project @@ -19,7 +19,7 @@ mapnik (3.0.0~rc3+ds-1) experimental; urgency=medium + build new plugins: pgraster, topojson * Standards-Version 3.9.6 - -- Jérémy Lal kapo...@melix.org Wed, 27 May 2015 18:22:19 +0200 + -- Jérémy Lal kapo...@melix.org Wed, 27 May 2015 21:13:32 +0200 mapnik (2.2.0+ds1-7) unstable; urgency=medium -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/mapnik.git ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: [mapnik] 01/01: Release to unstable
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 -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: [mapnik] 01/01: Release to unstable
2015-05-27 22:08 GMT+02:00 Sebastiaan Couwenberg sebas...@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. Jérémy ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: [mapnik] 01/01: Release to unstable
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 sebas...@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 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
