Bug#784160: transition: proj
On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. Both cdo pdl are good now too, and so is xastir. For some reason postgis is still marked as bad on mips, but I don't understand why. The mips build for 2.1.7+dfsg-1 depends on libproj9 as expected, so it should be good. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 11/05/15 08:14, Sebastiaan Couwenberg wrote: On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. Both cdo pdl are good now too, and so is xastir. For some reason postgis is still marked as bad on mips, but I don't understand why. The mips build for 2.1.7+dfsg-1 depends on libproj9 as expected, so it should be good. That's because of the old binaries. emilio@tatooine:~$ grep-excuses postgis postgis (2.1.4+dfsg-3 to 2.1.7+dfsg-1) Maintainer: Debian GIS Project Too young, only 3 of 5 days old old binaries left on mips: liblwgeom-2.1.4 (from 2.1.4+dfsg-3) Not considered Depends: postgis proj (not considered) I've requested a decruft for both postgis and proj. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 09/05/15 17:58, Sebastiaan Couwenberg wrote: On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. pdl/i386 has been fixed, an NMU for cdo is available but not uploaded yet. Please upload your cdo NMU to delayed/2. If the maintainer reacts before then he can cancel the upload or make a maintainer upload. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/10/2015 06:15 PM, Emilio Pozuelo Monfort wrote: On 09/05/15 17:58, Sebastiaan Couwenberg wrote: On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. pdl/i386 has been fixed, an NMU for cdo is available but not uploaded yet. Please upload your cdo NMU to delayed/2. If the maintainer reacts before then he can cancel the upload or make a maintainer upload. Thanks, I've uploaded cdo (1.6.5+dfsg.1-1.1) to DELAYED/2. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/05/2015 17:15, Emilio Pozuelo Monfort wrote: On 09/05/15 17:58, Sebastiaan Couwenberg wrote: On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. pdl/i386 has been fixed, an NMU for cdo is available but not uploaded yet. Please upload your cdo NMU to delayed/2. If the maintainer reacts before then he can cancel the upload or make a maintainer upload. Regards, Emilio Please proceed with upload. Thanks Alastair -- Alastair McKinstry, alast...@sceal.ie, mckins...@debian.org, https://diaspora.sceal.ie/u/amckinstry Software is like Poetry - most of it shouldn't have been written. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVT7BAAAoJEMvmu05dmtOlA6wQAJV7md7umzA1kjkNdiC/4YTJ wBmgFtQj+QVM+ZzyvuidkgLk9aXKARxXyYscwsbiGdxB1WqgavFKj+7CMcIvv+Zg MXss2v5Jw5+XKB1vBvIny03X9lE5hWEn0GIw6+jMfkYxUPL1HY+OdpoDVLlmN1DN 6dc+5H1OctZUPo5vpLTWJPUFLVUqhRbNyPVCW51HFwgDByEXjzl9Ja4U77+xxn52 ex4foFyq/wbZR1vjJspMn+T4fD78bJfhdWQGdm7sOhVzSnK4UOcSRdsvW/jrmipt qWSiCZKQQemwNz+eDguH0SkXH60OfJob69H1aM3x6RMNh0Wt5cNXpmW33YOEawI3 lyRXShM7OOaciEhPXwhVa/xatccwkEucjiP0I4WrcyDSNBIn8yDmSUEnIfm/7xWZ lYpuxDYLJaluYAoLArVcUr0w5YmMfRXIVYQZRWqA5oBd2Dg46Zu62vc+sdUQtBNZ GVX/1kwVb89jGXYAvJw/PvZzuGw62agyQ/qIlAbRxQlJ7Wg8+BmwXHQqBdD4T4b0 0ejlffYi1JXGkH2F1wvXOLh60lmUrQ60zegKR4dZO9Hl/kSl4Sjs/NwgpIwJ7gDX S0r5rmdMPyrvKT+nTTyzmIzid90oO/WDRbDxibY/r9Nlome7OMbpiE2F6yrpC0Nw yXJ9e2pTVlCuAOpD5V+o =2DwS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/10/2015 09:23 PM, Alastair McKinstry wrote: On 10/05/2015 17:15, Emilio Pozuelo Monfort wrote: On 09/05/15 17:58, Sebastiaan Couwenberg wrote: On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. pdl/i386 has been fixed, an NMU for cdo is available but not uploaded yet. Please upload your cdo NMU to delayed/2. If the maintainer reacts before then he can cancel the upload or make a maintainer upload. Regards, Emilio Please proceed with upload. Thanks, I've rescheduled the NMU from 2-day to 0-day. Kind Regards, Bas - -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVT7ufAAoJEGdQ8QrojUrx1Z4P/0mYtXjSGGS6IDHxuC4jwxd+ LlcEd4DYNmI7JboGBb8Sm1sYBpyPDd7J5onwbA/5GNRrXO0d/Q3sfkrRYE5i6G5S HIdsYmPAwnmHYyArB/qsdjLebpCfA7SFRuH4t0/jou9Y1Hp6sbJU+cYu/6DOih1K F0zxvRd+oWpcfsUNd8KvF+extsUEHp+zOWsLqZd8RcbfmuDGG1wn8dfXeWDEMslI 3aRZOZ8+cTYs5PEkpU16Xqt9mOaiycSX4ZpxtUzzKbSCKPUaCtLuZruCW68OzCbf /KZrWa/vlfX7ZjTPl51I8EtewV6ZKFW54+F55SzWzGjRPCJp69KdlAgHO+/7wBbK 0jEBzsXQjrPMPguQtndKhWb/8Um44puuHAp1r+7cCVARvYxghhPTcXJY28A3nJfM ZPXHTnedw+El1zH3Uvcd9WWQGkZaLynu+Tsv7DabOaZfDD54K92VpSyNw2ZpZOu9 DqLhAqWjGXcJFdh722pOhSLMQXo/nYr2mpCtokA5yY4Y1pdiFfzB30qjOzVdQ9vW evUWHqSsh9d9q4sN3waK58VoEhZ3HV0NYPbcQC97KJKO6LyIgXCvZi1cK8sNLbXh UUqu3i/q1yLXvMJiq2Y/L0h1b/98SU9onEzB2py+oe63KuPr+y0kDJHXyMBBdapf odTOdkdbXaH3R6aDR+rw =AwHq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. pdl/i386 has been fixed, an NMU for cdo is available but not uploaded yet. There is also xastir/amd64 which cannot be built because festival on amd64 requires a build dependency on speech-tools (1:2.4~release-1) that's currently stuck in NEW. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/09/2015 05:58 PM, Sebastiaan Couwenberg wrote: There is also xastir/amd64 which cannot be built because festival on amd64 requires a build dependency on speech-tools (1:2.4~release-1) that's currently stuck in NEW. I've prepared a binNMU for xastir/amd64 built with the festival dependencies from testing. Shall I upload that resolve this blocker? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/08/2015 03:40 PM, Henning Glawe wrote: On Fri, May 08, 2015 at 03:21:33PM +0200, Sebastiaan Couwenberg wrote: On 05/08/2015 02:56 PM, Henning Glawe wrote: t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated I opened a PDL bug report [1] for this issue and will look into it as soon as I start working on a released 2.008 From what I understand of the upstream discussion the library ordering changes fix the projection initialization issue that currently disables the Proj support in PDL. Skipping the tests on i386 may be sufficient for a successful build, that would at least allow the proj transition to continue. Proj support in PDL can be restored in the new upstream release. Just found out why the build was killed on i386: Build killed with signal TERM after 150 minutes of inactivity this happend after 160 minutes, while a typical build of PDL on i386 should take about 10 minutes... the really interesting question is why the build hangs somewhere for 150minutes; on all other platforms, the test suite directly continues with t/pthread.t I suspect this is an environment issue on the buildd, my manual binNMU of pdl on i386 succeeded without this test failure. It also used DEB_BUILD_OPTIONS=parallel=4 like the buildd which could have been a cause, the autotools test-driver for the spatialite package fails when parallel builds are enabled for example. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 2015-05-09 18:15, Sebastiaan Couwenberg wrote: On 05/09/2015 05:58 PM, Sebastiaan Couwenberg wrote: There is also xastir/amd64 which cannot be built because festival on amd64 requires a build dependency on speech-tools (1:2.4~release-1) that's currently stuck in NEW. I've prepared a binNMU for xastir/amd64 built with the festival dependencies from testing. Shall I upload that resolve this blocker? No, don't worry about that. Thanks for the other fixes. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 06/05/15 23:51, Sebastiaan Couwenberg wrote: On 05/03/2015 09:45 PM, Sebastiaan Couwenberg wrote: On 05/03/2015 09:08 PM, Jonathan Wiltshire wrote: On 2015-05-03 17:25, Bas Couwenberg wrote: We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. Please go ahead; there are (currently) no entanglements. Thanks for testing thoroughly in experimental. Thanks, I've uploaded proj 4.9.1-1. To resolve the build failures for postgis in hurd-i386 mipsel, I've manually bin-nmu'ed the packages on the respective porterboxes. The testsuite is known to fail on these architectures, using DEB_BUILD_OPTIIONS=nocheck allows the builds to succeed. Since postgis (2.1.5+dfsg-1~exp2) for hurd-i386, and postgis (2.1.6+dfsg-1~exp1) for mipsel, the testsuite is skipped on these architecture via d/rules. Unfortunately these more recent postgis versions are still stuck in NEW. That got accepted. The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
Hi Henning, Thanks for the feedback. On 05/08/2015 02:56 PM, Henning Glawe wrote: On Fri, May 08, 2015 at 01:47:28PM +0200, Sebastiaan Couwenberg wrote: That got accepted. The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. For PDL some patches from the upcoming release are required, see the discussion on their list [1] and Proj commits in their git repository [2]. There are several Proj related commits, so it may make more sense to update to PDL-2.007_17. Henning, what do you think? PDL-2.007_17 is a release candidate for the upcoming PDL-2.008, so I suggest we wait up to the official release of 2.008. BTW: In your build logs, PDL proj bindings are actually not built on any architecture, search the logs for PROJ4 library found but cannot initialize projection The error you observe on i386 is an independent problem, the package build is interrupted by a SIGTERM; where did that one come from? excessive resource usage on the buildd? t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated I opened a PDL bug report [1] for this issue and will look into it as soon as I start working on a released 2.008 From what I understand of the upstream discussion the library ordering changes fix the projection initialization issue that currently disables the Proj support in PDL. Skipping the tests on i386 may be sufficient for a successful build, that would at least allow the proj transition to continue. Proj support in PDL can be restored in the new upstream release. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On Fri, May 08, 2015 at 03:21:33PM +0200, Sebastiaan Couwenberg wrote: On 05/08/2015 02:56 PM, Henning Glawe wrote: t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated I opened a PDL bug report [1] for this issue and will look into it as soon as I start working on a released 2.008 From what I understand of the upstream discussion the library ordering changes fix the projection initialization issue that currently disables the Proj support in PDL. Skipping the tests on i386 may be sufficient for a successful build, that would at least allow the proj transition to continue. Proj support in PDL can be restored in the new upstream release. Just found out why the build was killed on i386: Build killed with signal TERM after 150 minutes of inactivity this happend after 160 minutes, while a typical build of PDL on i386 should take about 10 minutes... the really interesting question is why the build hangs somewhere for 150minutes; on all other platforms, the test suite directly continues with t/pthread.t -- c u henning -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 08/05/15 14:56, Henning Glawe wrote: On Fri, May 08, 2015 at 01:47:28PM +0200, Sebastiaan Couwenberg wrote: That got accepted. The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. For PDL some patches from the upcoming release are required, see the discussion on their list [1] and Proj commits in their git repository [2]. There are several Proj related commits, so it may make more sense to update to PDL-2.007_17. Henning, what do you think? PDL-2.007_17 is a release candidate for the upcoming PDL-2.008, so I suggest we wait up to the official release of 2.008. BTW: In your build logs, PDL proj bindings are actually not built on any architecture, search the logs for PROJ4 library found but cannot initialize projection The error you observe on i386 is an independent problem, the package build is interrupted by a SIGTERM; where did that one come from? excessive resource usage on the buildd? t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated The whole thing is: t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated make: *** [test-stamp] Terminated Makefile:1048: recipe for target 'test_dynamic' failed debian/rules:58: recipe for target 'test-stamp' failed Build killed with signal TERM after 150 minutes of inactivity So there was no output for 150 minutes. Most likely something hanged. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On Fri, May 08, 2015 at 01:47:28PM +0200, Sebastiaan Couwenberg wrote: That got accepted. The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. For PDL some patches from the upcoming release are required, see the discussion on their list [1] and Proj commits in their git repository [2]. There are several Proj related commits, so it may make more sense to update to PDL-2.007_17. Henning, what do you think? PDL-2.007_17 is a release candidate for the upcoming PDL-2.008, so I suggest we wait up to the official release of 2.008. BTW: In your build logs, PDL proj bindings are actually not built on any architecture, search the logs for PROJ4 library found but cannot initialize projection The error you observe on i386 is an independent problem, the package build is interrupted by a SIGTERM; where did that one come from? excessive resource usage on the buildd? t/proj_transform.t .. skipped: PDL::Transform::Proj4 module not compiled. t/proj_transform2.t . skipped: PDL::Transform::Proj4 module not compiled. E: Caught signal ‘Terminated’: terminating immediately make[1]: *** [test_dynamic] Terminated I opened a PDL bug report [1] for this issue and will look into it as soon as I start working on a released 2.008 [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784748 -- c u henning -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/08/2015 11:26 AM, Emilio Pozuelo Monfort wrote: On 06/05/15 23:51, Sebastiaan Couwenberg wrote: On 05/03/2015 09:45 PM, Sebastiaan Couwenberg wrote: On 05/03/2015 09:08 PM, Jonathan Wiltshire wrote: On 2015-05-03 17:25, Bas Couwenberg wrote: We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. Please go ahead; there are (currently) no entanglements. Thanks for testing thoroughly in experimental. Thanks, I've uploaded proj 4.9.1-1. To resolve the build failures for postgis in hurd-i386 mipsel, I've manually bin-nmu'ed the packages on the respective porterboxes. The testsuite is known to fail on these architectures, using DEB_BUILD_OPTIIONS=nocheck allows the builds to succeed. Since postgis (2.1.5+dfsg-1~exp2) for hurd-i386, and postgis (2.1.6+dfsg-1~exp1) for mipsel, the testsuite is skipped on these architecture via d/rules. Unfortunately these more recent postgis versions are still stuck in NEW. That got accepted. The current blockers are the cdo/ppc64el build failure (#763691) and the pdl/i386 one. For PDL some patches from the upcoming release are required, see the discussion on their list [1] and Proj commits in their git repository [2]. There are several Proj related commits, so it may make more sense to update to PDL-2.007_17. Henning, what do you think? [1] http://sourceforge.net/p/pdl/mailman/message/33627488/ [2] https://github.com/PDLPorters/pdl/commits/master Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/03/2015 09:45 PM, Sebastiaan Couwenberg wrote: On 05/03/2015 09:08 PM, Jonathan Wiltshire wrote: On 2015-05-03 17:25, Bas Couwenberg wrote: We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. Please go ahead; there are (currently) no entanglements. Thanks for testing thoroughly in experimental. Thanks, I've uploaded proj 4.9.1-1. To resolve the build failures for postgis in hurd-i386 mipsel, I've manually bin-nmu'ed the packages on the respective porterboxes. The testsuite is known to fail on these architectures, using DEB_BUILD_OPTIIONS=nocheck allows the builds to succeed. Since postgis (2.1.5+dfsg-1~exp2) for hurd-i386, and postgis (2.1.6+dfsg-1~exp1) for mipsel, the testsuite is skipped on these architecture via d/rules. Unfortunately these more recent postgis versions are still stuck in NEW. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
Control: tag -1 confirmed Control: forwarded -1 https://release.debian.org/transitions/html/auto-proj.html On 2015-05-03 17:25, Bas Couwenberg wrote: We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. Please go ahead; there are (currently) no entanglements. Thanks for testing thoroughly in experimental. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. I've rebuilt all reverse dependencies to verify that they still build successfully with PROJ.4 4.9.1. python-pyproj won't need a rebuild, after proj 4.9.1-1 is available in unstable I'll upload python-pyproj 1.9.4-1 to unstable too. The version currently in experimental build with the system installed proj instead of its embedded copy. There already is an automatically created transition tracker at: https://release.debian.org/transitions/html/auto-proj.html That ben configuration looks good, so we don't need to create another although reportbug kindly generated one anyway. Transition: proj libproj0 (4.8.0-5) - libproj9 (4.9.1-1) The status of the most recent rebuilds is as follows. python-pyproj (1.9.4-1) OK gpx2shp (0.71.0-1) OK libgeo-proj4-perl (1.05-2) OK libgeotiff-dfsg (1.4.1-1) OK magics++ (2.22.7.dfsg.1-4) OK ogdi-dfsg (3.2.0~beta2-7.1) OK osm2pgsql (0.87.3-3) OK pdl (1:2.007-4)OK shapelib (1.3.0-4) OK sosi2osm (1.0.0-1) OK spatialite(4.1.1-10 / 4.2.1~rc1-1~exp2) OK / OK survex(1.2.16-1) OK zygrib(6.2.3-1) OK cdo (1.6.5+dfsg.1-1) OK gdal (1.10.1+dfsg-8 / 1.11.2+dfsg-1~exp2) OK / OK libgaiagraphics (0.5-3)OK librasterlite (1.1g-5) OK metview (4.4.8+dfsg.1-8) OK pyspatialite (3.0.1-6) OK spatialite-tools (4.1.1-4 / 4.2.1~rc1-1) OK / OK grass (6.4.4-1 / 7.0.0-1~exp1) OK / OK mapnik(2.2.0+ds1-7) OK mapserver (6.4.1-6) OK merkaartor(0.18.1-3) OK ncl (6.2.0-3) OK postgis (2.1.0-4 / 2.1.7+dfsg-1) OK / OK qlandkartegt (1.8.1+ds-1) OK qmapshack (1.2.2-1) OK saga (2.1.4+dfsg-1) OK spatialite-gui(1.7.1-5) OK sumo (0.21.0+dfsg-1 / 0.23.0+dfsg1-2~exp1) OK / OK thuban(1.2.2-6) OK xastir(2.0.6-3) OK mapcache (1.2.1-3) OK qgis (2.8.1+dfsg1-1)OK Ben file: title = proj; is_affected = .depends ~ libproj0 | .depends ~ :libproj9; is_good = .depends ~ :libproj9; is_bad = .depends ~ libproj0; -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784160: transition: proj
On 05/03/2015 09:08 PM, Jonathan Wiltshire wrote: On 2015-05-03 17:25, Bas Couwenberg wrote: We've had proj 4.9.x in experimental for some time now, and I'd like to move it from experimental to unstable as the first stretch transition for the Debian GIS team. Currently PROJ.4 4.8.0 is unstable and jessie, and PROJ.4 4.9.1 is in experimental. Updating PROJ.4 from 4.8.0 to 4.9.1 involves a SONAME bump from libproj.so.0 to libproj.so.9. Please go ahead; there are (currently) no entanglements. Thanks for testing thoroughly in experimental. Thanks, I've uploaded proj 4.9.1-1. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
