[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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


Reply to: