Your message dated Sun, 25 Sep 2016 11:20:43 +0200
with message-id <d898ffcf-0b16-3f14-9c5e-af659990e...@debian.org>
and subject line Re: Bug#836447: transition: proj
has caused the Debian Bug report #836447,
regarding transition: proj
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
836447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Control: forwarded -1 https://release.debian.org/transitions/html/auto-proj.html
PROJ.4 4.9.3 has been released and bumps the SOVERSION from 9 to 12,
requiring a transition.
We've had the release candidates in experimental for a little while
already, and the issues identified with those have already been fixed in
unstable. Only gpx2shp needed a patch to support the renamed PI defines
in projects.h from proj 4.9.3.
All reverse dependencies rebuilt successfully with the new proj packages
from experimental (as summarized below), except mapnik (3.0.11+ds-1) in
unstable because it lacks support for Boost 1.61 (#833756), the mapnik
3.0.12 release candidates in experimental do support Boost 1.61.
Mapnik 3.0.11 is scheduled for automatic removal from testing on
2016-09-21, unfortunately I don't expect the 3.0.12 final release before
that time.
Please also schedule binNMUs for the affected packages in experimental
if those have not yet moved to unstable when the transition starts.
spatialite (4.4.0~rc1-1~exp1)
spatialite-tools (4.4.0~rc1-1~exp1),
grass (7.0.5~rc1-1~exp1)
mapnik (3.0.12~rc6+ds-1~exp2)
python-mapnik (1:0.0~20160810-3a60211-1~exp1),
I will move the new pdal & qgis packages from experimental to unstable
today.
Transition: proj
libproj9 (4.9.2-3) -> libproj12 (4.9.3-1~exp1)
The status of the most recent rebuilds is as follows.
gpx2shp (0.71.0-4) OK
libgeo-proj4-perl (1.05-3) OK
libgeotiff-dfsg (1.4.2-2) OK
ogdi-dfsg (3.2.0+ds-1) OK
openorienteering-mapper (0.6.3-2) OK
pdl (1:2.016-4) OK
proj-rdnap (2008-5) OK
python-pyproj (1.9.5.1-2) OK
shapelib (1.3.0-8) OK
sosi2osm (1.0.0-3) OK
spatialite (4.3.0a-5 / 4.4.0~rc1-1~exp1) OK / OK
survex (1.2.27-1) OK
zygrib (7.0.0-4) OK
gdal (2.1.1+dfsg-1) OK
magics++ (2.29.2-1) OK
pyspatialite (3.0.1-11) OK
spatialite-gui (2.0.0~devel2-4) OK
spatialite-tools (4.3.0-2 / 4.4.0~rc1-1~exp1) OK / OK
cdo (1.7.2+dfsg.1-1) OK
dans-gdal-scripts (0.23-6) OK
grass (7.0.4-3 / 7.0.5~rc1-1~exp1) OK / OK
libosmium (2.8.0-2) OK
mapcache (1.4.1-3) OK
mapnik (3.0.11+ds-1 /
3.0.12~rc4+ds-1~exp1) FTBFS / OK
mapproxy (1.9.0-3) OK
mapserver (7.0.1-3) OK
merkaartor (0.18.3-1) OK
metview (4.6.7-1) OK
ncl (6.3.0-11) OK
otb (5.6.1+dfsg-1) OK
pdal (1.3.0-1) OK
postgis (2.2.2+dfsg-4) OK
qlandkartegt (1.8.1+ds-6) OK
qmapshack (1.6.3-1) OK
saga (2.3.1+dfsg-1) OK
sumo (0.27.1+dfsg1-1) OK
thuban (1.2.2-11) OK
vtk6 (6.3.0+dfsg1-1) OK
xastir (2.0.8-2) OK
ifrit (4.1.2-5) OK
libgdal-grass (2.1.1-2) OK
osm2pgsql (0.90.1+ds-1) OK
python-mapnik (1:0.0~20160531-f65767a-1 /
1:0.0~20160810-3a60211-1~exp1) OK / OK
qgis (2.14.6+dfsg-1) OK
therion (5.3.16-10) OK
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
On 24/09/16 21:39, Sebastiaan Couwenberg wrote:
> This transition should be done, time to close this bugreport?
Yep. Closing.
Emilio
--- End Message ---
