Re: [GRASS-dev] GRASS 8.0 support in GDAL and QGIS

2022-03-23 Thread Sebastiaan Couwenberg

On 3/23/22 21:08, Markus Neteler wrote:

Hi,

On Thu, Feb 24, 2022 at 9:33 AM Sebastiaan Couwenberg
 wrote:


Now that 7.8.7 has been released, I started looking into updating the
Debian package to 8.0.x which requires rebuilding libgdal-grass and qgis.

Initial tests with libgdal-grass are not promising. Both gdalinfo and
ogrinfo show errors because not all libraries are linked. We saw this
too when 7.2 was released: https://trac.osgeo.org/gdal/ticket/6785

The attached patch helps to some extent, but does not resolve all
issues.


Did you propose the path to GDAL in GitHub yet?


No, there was no need after all.

I was led astray by the error from the grass sqlite driver which doesn't 
need changes in gdal-grass.



I just merged and backported
https://github.com/OSGeo/grass/pull/2269

Perhaps that helps, too? It probably also solves this issue:
https://github.com/qgis/QGIS/pull/47576


Perhaps.

libgdal-grass and qgis built with grass 8 have only just been available 
in unstable.


The transition to proj 9 is currently ongoing so and qgis hasn't been 
rebuilt yet, but gdal has, so qgis isn't very usualy right now with 
dependencies on different versions of proj.



Should we perhaps take this opportunity to move the grass libraries to
default library search paths as raised on the debian-gis list?

   https://lists.debian.org/debian-gis/2021/12/msg00023.html


Others have answered positively, so the question is when to introduce
needed changes.


Has any work been done testing and patching gdal-grass and qgis for
GRASS 8 yet?


- I have successfully locally compiled the gdal-grass driver
- also added a COPR for Fedora RPMs:
https://copr.fedorainfracloud.org/coprs/neteler/gdal-grass-plugin/
- Nyall and Sandro have patched QGIS to support GRASS GIS 8, some weeks ago

More tests are welcome.


This seems to be sufficient so far:

https://salsa.debian.org/debian-gis-team/gdal-grass/-/commit/0192b0418e04d79678bdd5c4c377b8cece5e0939

We mostly need gdal-grass for gdal 3.5 now.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


Re: [GRASS-dev] GRASS 8.0 support in GDAL and QGIS

2022-03-23 Thread Markus Neteler
Hi,

On Thu, Feb 24, 2022 at 9:33 AM Sebastiaan Couwenberg
 wrote:
>
> Now that 7.8.7 has been released, I started looking into updating the
> Debian package to 8.0.x which requires rebuilding libgdal-grass and qgis.
>
> Initial tests with libgdal-grass are not promising. Both gdalinfo and
> ogrinfo show errors because not all libraries are linked. We saw this
> too when 7.2 was released: https://trac.osgeo.org/gdal/ticket/6785
>
> The attached patch helps to some extent, but does not resolve all
> issues.

Did you propose the path to GDAL in GitHub yet?

> ogrinfo still shows errors:
>
> # ogrinfo -ro -so /tmp/spearfish60_grass7/PERMANENT/vector/roads/head
>
> Warning 1: GRASS warning: GISBASE environment variable was not set, using:
> /usr/lib/grass80
> /usr/lib/grass80/driver/db/sqlite: error while loading shared libraries:
> libgrass_dbmidriver.8.0.so: cannot open shared object file: No such file
> or directory
> dbmi: Protocol error
> Warning 1: GRASS warning: Unable to start driver 
> ERROR 1: Cannot open database sqlite by driver
> /tmp/spearfish60_grass7/PERMANENT/sqlite/sqlite.db, check if GISBASE
> environment variable is set, the driver is available  and the database
> is accessible.
> INFO: Open of `/tmp/spearfish60_grass7/PERMANENT/vector/roads/head'
>using driver `OGR_GRASS' successful.
> 1: roads (Line String)
>
> The grass drivers lacks the RPATH that was set for ogr_GRASS:
>
> # objdump -x /usr/lib/gdalplugins/ogr_GRASS.so | egrep "NEEDED|RUNPATH"
>NEEDED   libgrass_vector.8.0.so
>NEEDED   libgrass_dig2.8.0.so
>NEEDED   libgrass_dgl.8.0.so
>NEEDED   libgrass_rtree.8.0.so
>NEEDED   libgrass_linkm.8.0.so
>NEEDED   libgrass_dbmiclient.8.0.so
>NEEDED   libgrass_dbmibase.8.0.so
>NEEDED   libgrass_dbmidriver.8.0.so
>NEEDED   libgrass_dbstubs.8.0.so
>NEEDED   libgrass_raster.8.0.so
>NEEDED   libgrass_imagery.so
>NEEDED   libgrass_gproj.8.0.so
>NEEDED   libgrass_gmath.8.0.so
>NEEDED   libgrass_gis.8.0.so
>NEEDED   libgrass_datetime.8.0.so
>NEEDED   libgrass_btree2.8.0.so
>NEEDED   libgrass_ccmath.8.0.so
>NEEDED   libgdal.so.30
>NEEDED   libstdc++.so.6
>NEEDED   libm.so.6
>NEEDED   libgcc_s.so.1
>NEEDED   libc.so.6
>RUNPATH  /usr/lib/grass80/lib
>
> # objdump -x /usr/lib/grass80/driver/db/sqlite | egrep "NEEDED|RUNPATH"
>NEEDED   libgrass_dbmidriver.8.0.so
>NEEDED   libgrass_dbmibase.8.0.so
>NEEDED   libgrass_gis.8.0.so
>NEEDED   libsqlite3.so.0
>NEEDED   libc.so.6


I just merged and backported
https://github.com/OSGeo/grass/pull/2269

Perhaps that helps, too? It probably also solves this issue:
https://github.com/qgis/QGIS/pull/47576

> Should we perhaps take this opportunity to move the grass libraries to
> default library search paths as raised on the debian-gis list?
>
>   https://lists.debian.org/debian-gis/2021/12/msg00023.html

Others have answered positively, so the question is when to introduce
needed changes.

> Has any work been done testing and patching gdal-grass and qgis for
> GRASS 8 yet?

- I have successfully locally compiled the gdal-grass driver
- also added a COPR for Fedora RPMs:
https://copr.fedorainfracloud.org/coprs/neteler/gdal-grass-plugin/
- Nyall and Sandro have patched QGIS to support GRASS GIS 8, some weeks ago

More tests are welcome.

Markus

> Kind Regards,
>
> Bas
>
> --
>   GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 
> 4AF1___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev


Re: [GRASS-dev] Planning 8.2.0

2022-03-23 Thread Vaclav Petras
Here is the current state for 8.0.2 and 8.2.0 milestones:

8.0.2 due: March 31
8.2.0 due: April 05

8.0.2 PRs: 7
8.0.2 issues: 11
8.2.0 PRs: 19
8.2.0 issues: 0

Most of the 11 issues for 8.0.2 are Windows-related. 5 PRs are GSoC 2021
related.

Please, resolve your PRs or move them to 8.4.0.

Let me know if you are interested in having a call about the upcoming
releases.

Best,
Vaclav

8.0.2 https://github.com/OSGeo/grass/milestone/15
8.2.0 https://github.com/OSGeo/grass/milestone/8

On Sun, 27 Feb 2022 at 15:33, Vaclav Petras  wrote:

> TLDR: 8.2.0 with GSoC 2021 work (single window, Jupyter, parallel modules)
> is scheduled for April 5.
>
> Action items: For PRs, merge now or move the milestone to 8.4.0. For
> issues, create a new PR now or move to 8.4.0.
>
>
> Dear all,
>
> We are entering a preparation phase for 8.2 release. (As you may or may
> not know, we are currently skipping odd minor numbers because they are used
> to make the development version, so there is no 8.1 release.)
>
> On a couple occasions, we discussed that the 8.2 release contains the GSoC
> 2021 work, i.e., the release will contain Linda's single window, Caitlin's
> grass.jupyter, and Aaron's parallelized modules.
>
> Unfortunately, I can't find this in PSC minutes or elsewhere perhaps
> because the main discussion happened in the Birthday call. We also lack a
> formalized roadmap, release schedule [1], and release procedure [2] is a
> draft. However, the current state and plan are well represented in the
> GitHub milestone [3].
>
> Because 8.2 is a "GSoC 2021" release, the plan is to release it on April
> 5th before GSoC 2022 starts. Now, it's time to finish and merge any PRs
> which are almost done. For PRs which are not ready to be merged, move them
> to the 8.4.0 milestone. Similarly, for issues, resolve them now or move
> them to 8.4.0.
>
> Importantly, there is no need for 8.2.0 to contain anything else except
> what is already on main plus the GSoC 2021 work because the plan is that
> 8.2 is whatever 8.0 is plus an experimental version of single window,
> grass.jupyter, and most of the newly parallelized modules.
>
> Best,
> Vaclav
>
> [1] https://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
> [2] https://trac.osgeo.org/grass/wiki/Release/Schedule
> [3] https://github.com/OSGeo/grass/milestone/8
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev