[gdal-dev] GDAL 3.1.0 RC2 available

Sebastiaan Couwenberg sebastic at xs4all.nl
Sun May 3 10:22:11 PDT 2020


On 5/3/20 7:09 PM, Even Rouault wrote:
> Looking at
> https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-rgdal/5203587/log.gz  , 
> there doesn't seem to be much detail about what fails exactly.

>From the log:

 autopkgtest [09:49:06]: test run-unit-test: [-----------------------
 ...
 BEGIN TEST srs_rendering.R

 R version 3.6.3 (2020-02-29) -- "Holding the Windsock"
 Copyright (C) 2020 The R Foundation for Statistical Computing
 Platform: x86_64-pc-linux-gnu (64-bit)

 R is free software and comes with ABSOLUTELY NO WARRANTY.
 You are welcome to redistribute it under certain conditions.
 Type 'license()' or 'licence()' for distribution details.

 R is a collaborative project with many contributors.
 Type 'contributors()' for more information and
 'citation()' on how to cite R or R packages in publications.

 Type 'demo()' for some demos, 'help()' for on-line help, or
 'help.start()' for an HTML browser interface to help.
 Type 'q()' to quit R.

 > suppressPackageStartupMessages(library(rgdal))
 > getPROJ4VersionInfo()
 [1] "Rel. 7.0.0, March 1st, 2020, [PJ_VERSION: 700]"
 > getGDALVersionInfo()
 [1] "GDAL 3.1.0, released 2020/04/28"
 > d <- system.file("vectors", package="rgdal")
 > shps <- ogrListLayers(d)
 terminate called after throwing an instance of 'std::bad_alloc'
   what():  std::bad_alloc
 Aborted
 autopkgtest [09:49:07]: test run-unit-test: -----------------------]
 autopkgtest [09:49:07]: test run-unit-test:  - - - - - - - - - -
results - - - - - - - - - -
 run-unit-test        FAIL non-zero exit status 134

> The following message in the log is also a bit strange:
> """
>  Loaded GDAL runtime: GDAL 3.1.0, released 2020/04/28
>    but rgdal build and GDAL runtime not in sync:
>    ... consider re-installing rgdal!!
> """
> I'd assume everything to match perfectly in a Debian build env.

Nothing has been (re)built with GDAL 3.1.0 yet.

When packages are uploaded to experimental, autopkgtest is triggered for
the rdeps in unstable to test for any regressions.

The same is done when packages are uploaded to unstable, then the
autopkgtest for the rdeps in testing are triggered. Any regressions
block the migration of package.

Kind Regards,

Bas

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


More information about the gdal-dev mailing list