Re: [GRASS-dev] Help for compilation of grass gis

[Markus Neteler via grass-dev]

Hi Olivia,

While not having much experience in compilation of winGRASS I still can
probably help.

Please share what the problems are, either here or in a personal message.

Cheers
Markus


Olivia DASSANOU via grass-dev  schrieb am Fr.,
13. Sep. 2024, 00:19:

> hello,
>
>  I really need your help urgently to compile grass gis
> under windows and generate an executable .exe file. In reality I followed
> the instructions but unfortunately I still can't do it and I would like to
> have the assistance of whoever is available to help me by tomorrow evening
> with a planned remuneration. I am working on a project submitted
> individually by our establishment to edit (customize) grass gis and return
> the exe file to it by tomorrow evening. I need assistance to compile the
> version I modified and send it to me for delivery.
>
>  Thank you for your help.
> ___
> 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] Planned transition of grass-dev mailing list to OSGeo Discourse

[Markus Neteler via grass-dev]

On Mon, Aug 12, 2024 at 11:00 PM Anna Petrášová via grass-dev
 wrote:
>
> Hi all,
>
> During our last PSC meeting [1] we decided to go ahead with moving the 
> grass-dev mailing list to OSGeo Discourse [2]. Our intention is to make this 
> transition as smooth as possible and later proceed with other grass mailing 
> lists. The history of the grass-dev list should be ported to discourse and 
> preserved. Once we start using discourse, you have the option of using the 
> web interface to interact with this list or still using email for 
> correspondence, with the only difference being sending to the new email 
> address if you want to start a new topic, or replying to a topic email 
> (grass-...@discourse.osgeo.org). At this point, you don't need to do anything 
> yet, we will inform you once an action is required from you. Let us know if 
> you have any concerns.
>
> Best,
> Anna
>
> [1] https://grasswiki.osgeo.org/wiki/PSC_Meeting_2024-08-09#Minutes
> [2] https://discourse.osgeo.org/t/welcome-to-osgeo/5

Since no concerns have been raised, I have opened a migration ticket
with OSGeo-SAC:

https://trac.osgeo.org/osgeo/ticket/3255

Cheers
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS 8.4.0 released

[Markus Neteler via grass-dev]

The GRASS GIS 8.4.0 release provides more than 520 improvements and fixes
with respect to the release 8.3.2. Highlights

   - *location* becomes *project*: The Python API, command line, and
   graphical user interface are now using *project* instead of *location*
   for the main component of the data hiearchy while maintaining backward
   compatibility.
   - v.fill.holes: New tool to remove inner isles and to keep outer
   boundary only
   - i.svm: New support vector machine image classification (SVM)
   - r.horizon: Output for multiple points, distances, and many other
   improvements
   - r.univar: Parallelization computation extended statistics
   - JSON output format support (format="json") in multiple tools (e.g.,
   r.report, r.info, v.db.select, t.rast.list, etc.)
   - New *grass.jupyter.SeriesMap* class for animating series of vectors or
   rasters
   - ipyleaflet integration for *grass.jupyter* to create a map in
   ipyleaflet and add GRASS data in a single line
   - Greatly simplified the creation of new projects in Python (no more
   chicken and egg problems) - also in Jupyter notebooks
   - GUI: New easy command history navigation through the History browser
   panel browser panel (details
   

   )
   - GUI: Further improvements of new single-window GUI with undockable map
   display window, for a smoother user experience
   - New GRASS GIS Programming Style Guide
   

New Addon Tools

   - i.eodag
   :
   Downloads imagery datasets from various providers through the EODAG API.
   - r.flowaccumulation
   
:
   Calculates flow accumulation from a flow direction raster map using the
   Memory-Efficient Flow Accumulation (MEFA) parallel algorithm by Cho (2023).
   - r.fusion
   :
   image fusion, generalized pan-sharpening.
  - This work was funded by mundialis GmbH & Co. KG
  
   - r.windfetch: addon for computing wind fetch.
   - r.maxent.train
   
   & r.maxent.predict
   :
   train, and predict a Maxent model to create a suitability distribution
   layer.

For further details, see

   - https://grass.osgeo.org/news/2024_07_27_grass_gis_8_4_0_released
   - https://grass.osgeo.org/download/
   - https://github.com/OSGeo/grass/releases/tag/8.4.0

Thanks to all contributors!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Errors compiling main on Ubuntu 22.04

[Markus Neteler via grass-dev]

On Mon, Jul 29, 2024 at 12:02 PM Edouard Choinière via grass-dev
 wrote:
>
> So, if libsclean was the part that made it work, we might have to look at 
> running it on distclean (if distclean is commonly used as a « super clean »).

Yes, "make distclean" is commonly used as a « super clean ».

So, would this change improve the situation?

index be8834ecf4..81390f0dec 100644
--- a/Makefile
+++ b/Makefile
@@ -124,7 +124,7 @@ code-coverage-clean:
-find . -type f \( -name "*.gcda" -o -name "*.gcno" -o -name
"*.gcov" \) -delete
-rm -f .coverage

-distclean: clean
+distclean: libsclean clean
-rm -f config.cache config.log config.status
config.status.$(ARCH) 2>/dev/null
-rm -f ChangeLog ChangeLog.bak $(ERRORLOG) grass.pc
-rm -f include/grass/config.h include/grass/version.h

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

On Sun, Jul 28, 2024 at 3:07 PM Sebastiaan Couwenberg via grass-dev
 wrote:
>
> On 7/28/24 2:51 PM, Nicklas Larsson via grass-dev wrote:
> >> On 28 Jul 2024, at 13:30, Sebastiaan Couwenberg via grass-dev 
> >>  wrote:
> >>
> >> On 7/28/24 11:54 AM, Markus Neteler via grass-dev wrote:
> >>> I just discovered that the tarball no longer contains the version in
> >>> the tarball "grass" subdir (expected "grass-8.4.0"):
> >>> tar tvfz ~/grass-8.4.0.tar.gz  | head
> >>> drwxr-xr-x runner/docker 0 2024-07-27 15:34 grass/
> >>> [...]
> >>> Why is that? Is it a feature?
> >>> It breaks e.g. the (Fedora) RPM packaging procedure...

I need to add that I had tried to use (this time) the tarball from GitHub.

> >> That tarball used for the Debian package from 
> >> https://grass.osgeo.org/grass84/source/ includes the version in the 
> >> toplevel directory:
> >>
> >> $ tar tavf ../grass-8.4.0.tar.gz | head -1
> >> drwxrwxr-x root/root 0 2024-07-27 13:27 grass-8.4.0/
> >
> > The tarball from https://grass.osgeo.org/grass84/source/ is not the same as 
> > the one on Github, it also does not contain the "include/VERSION_GIT” file.
>
> That's obvious.

Not to me :)

> Why that breaks the RPM packaging procedure is not, as it uses the
> tarballs from grass.osgeo.org too:
>
>   https://src.fedoraproject.org/rpms/grass/blob/rawhide/f/grass.spec#_29

Yeah, using that one all goes fine.

So, we may ignore that but may consider to fix
https://github.com/OSGeo/grass/pull/3437

Best,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Hi devs,

I just discovered that the tarball no longer contains the version in
the tarball "grass" subdir (expected "grass-8.4.0"):

tar tvfz ~/grass-8.4.0.tar.gz  | head
drwxr-xr-x runner/docker 0 2024-07-27 15:34 grass/
-rwxr-xr-x runner/docker 458838 2024-07-27 15:32 grass/configure
-rw-r--r-- runner/docker778 2024-07-27 15:32 grass/pyproject.toml
-rw-r--r-- runner/docker   4067 2024-07-27 15:32 grass/CITATION.cff
-rw-r--r-- runner/docker436 2024-07-27 15:32 grass/.dockerignore
-rw-r--r-- runner/docker   3272 2024-07-27 15:32 grass/Vagrantfile
-rw-r--r-- runner/docker   1488 2024-07-27 15:32 grass/TODO
drwxr-xr-x runner/docker  0 2024-07-27 15:32 grass/display/
drwxr-xr-x runner/docker  0 2024-07-27 15:32 grass/display/d.rhumbline/
-rw-r--r-- runner/docker 53 2024-07-27 15:32
grass/display/d.rhumbline/local_proto.h

Why is that? Is it a feature?
It breaks e.g. the (Fedora) RPM packaging procedure...

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Hi all,

The release is done:
https://github.com/OSGeo/grass/releases/tag/8.4.0

Cronjob update PR:
https://github.com/OSGeo/grass-addons/pull/1147

Web news PR:
https://github.com/OSGeo/grass-website/pull/444

Please check them... and screenshot and binaries needed.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Hi,

I have started the G8.4.0 release procedure.
Will report once completed (takes some hours).

Markus



-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

On Fri, Jul 19, 2024 at 4:30 PM Markus Neteler  wrote:
> On Thu, Jul 11, 2024 at 7:09 PM Markus Neteler  wrote:
> >
> > Dear all,
> >
> > It's been some weeks that we have released G 8.4.0RC1.
> >
> > The milestones "8.4.0" still shows many open PRs/Issues:
> >
> > https://github.com/OSGeo/grass/milestone/19
>
> --> 48 issues/PR still open.
>
> So, I'll bump them to 8.4.1 shortly in order to move on with the 8.4.0 
> release.

So, only talking to myself here...

So I'll bump them now.

> Still open is also the Weblate mess.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Assistance compilation de GRASS GIS

[Markus Neteler via grass-dev]

Dear Olivia,

On Fri, Jul 19, 2024 at 3:23 PM Olivia DASSANOU via grass-dev
 wrote:
>
> Bonjour à tous,
>
> Je suis un développeur d'application et je me suis intéressé à GRASS 
> GIS.J'aimerais prendre en main le code source et effectuer des contributions 
> suivant mes petites expériences.J'arrive a essayer une compilation sous 
> Ubuntu mais j'aimerais avoir votre assistance pour compiler une version 
> Windows (version .exe)
>
> Je serais très ravis pour vos guides et conseils afin de franchir cette étape.

We are maintaining a dedicated "Compile and install" Wiki page for
operating system specific compilation instructions.

For Windows, see:
https://grasswiki.osgeo.org/wiki/Compile_and_Install#MS-Windows
--> MS-Windows/native

It will point you to this detailed page:
https://trac.osgeo.org/grass/wiki/CompileOnWindows

HTH,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

On Thu, Jul 11, 2024 at 7:09 PM Markus Neteler  wrote:
>
> Dear all,
>
> It's been some weeks that we have released G 8.4.0RC1.
>
> The milestones "8.4.0" still shows many open PRs/Issues:
>
> https://github.com/OSGeo/grass/milestone/19

--> 48 issues/PR still open.

So, I'll bump them to 8.4.1 shortly in order to move on with the 8.4.0 release.

> with 2 marked as "blockers":
> https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Ablocker
>
> Really blockers or could they be downgraded in their importance (and
> moved to the next 8.4.1 milestone)?

... the blockers have been bumped to 8.4.1.

Still open is also the Weblate mess.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Dear all,

It's been some weeks that we have released G 8.4.0RC1.

The milestones "8.4.0" still shows many open PRs/Issues:

https://github.com/OSGeo/grass/milestone/19

with 2 marked as "blockers":
https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Ablocker

Really blockers or could they be downgraded in their importance (and
moved to the next 8.4.1 milestone)?

Thanks
Markus



-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS 8.4.0RC1 release

[Markus Neteler via grass-dev]

GRASS GIS 8.4.0RC1 release

The GRASS GIS 8.4.0RC1 release provides more than 515 improvements and
fixes with respect to the release 8.3.2.

Please support us in testing this release candidate.
Highlights

   - *location* becomes *project*: The Python API, command line, and
   graphical user interface are now using *project* instead of *location*
   for the main component of the data hiearchy while maintaining backward
   compatibility.
   - v.fill.holes: New tool to remove inner isles and to keep outer
   boundary only
   - i.svm: New support vector machine image classification (SVM)
   - r.horizon: Output for multiple points, distances, and many other
   improvements
  - This work was funded was developed with funding from NSF Award
  #2322073 ,
  granted to Natrx, Inc. 
   - r.univar: Parallelization computation extended statistics
   - JSON output format support (format="json") in multiple tools (e.g.,
   r.report, r.info, v.db.select, t.rast.list, etc.)
   - New *grass.jupyter.SeriesMap* class for animating series of vectors or
   rasters
   - ipyleaflet integration for *grass.jupyter* to create a map in
   ipyleaflet and add GRASS data in a single line
   - Greatly simplified the creation of new projects in Python (no more
   chicken and egg problems) - also in Jupyter notebooks
  - This work was funded was developed with funding from NSF Award
  #2322073 ,
  granted to Natrx, Inc. 
   - GUI: New easy command history navigation through the History browser
   panel browser panel (details
   

   )
   - GUI: Further improvements of new single-window GUI with undockable map
   display window, for a smoother user experience
   - New GRASS GIS Programming Style Guide
   

New Addon Tools

   - i.eodag
   :
   Downloads imagery datasets from various providers through the EODAG API.
   - r.flowaccumulation
   
:
   Calculates flow accumulation from a flow direction raster map using the
   Memory-Efficient Flow Accumulation (MEFA) parallel algorithm by Cho (2023).
   - r.fusion
   :
   image fusion, generalized pan-sharpening.
  - This work was funded by mundialis GmbH & Co. KG
  
   - r.windfetch: addon for computing wind fetch.
   - r.maxent.train
   
   & r.maxent.predict
   :
   train, and predict a Maxent model to create a suitability distribution
   layer.

Monthly Financial Supporters

OpenPlains Inc. , Luis Bojórquez

What's ChangedSee https://github.com/OSGeo/grass/releases/tag/8.4.0RC1New
Contributors

   - Luís de Sousa (@ldesousa ) made their
   first contribution in #3006 
   - Alexandre Detiste (@a-detiste ) made
   their first contribution in #3076
   
   - Michael Barton (@cmbarton ) made their
   first contribution in #3279 
   - Alessandro Frigeri (@afrigeri ) made
   their first contribution in #3258
   
   - Florian Weimer (@fweimer-rh ) made
   their first contribution in #3325
   
   - Gregory Power (@gregorywaynepower
   ) made their first contribution in
   #3338 
   - Sharan Jamanani (@Sharansrj567 ) made
   their first contribution in #3356
   
   - @ymdatta  made their first contribution in
   #3247 
   - @Ntp9413  made their first contribution in
   #3444 
   - Jaden Abrams (@jadenabrams100 )
   made their first contribution in #3451
   
   - @VeronicaKoess  made their first
   contribution in #3311 
   - @naidneelttil  made their first
   contribution in #3469 

[GRASS-dev] GRASS GIS 8.4.0 release branching upcoming now

[Markus Neteler via grass-dev]

Hi devs,

FYI
Vashek and me are going to create the release branching procedure now.

Best
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [PROJ] PROJ was not updated in Zenodo

[Markus Neteler via grass-dev]

On Tue, Jun 4, 2024 at 5:38 PM Vaclav Petras via grass-dev
 wrote:
>
> Thanks Even. This is not clear to me. I see OSGeo/grass enabled. I can't 
> manage that because it
> says that it is managed by another user of my org.

That's me I guess.

> Screenshot attached.

Looks ok?

However, it also frequently fails for GRASS GIS.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Vaclav Petras  schrieb am Di., 30. Apr. 2024, 16:29:

>
> On Fri, 26 Apr 2024 at 05:36, Markus Neteler via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
>
>> The remainder for the 8.4.0 milestone are (currently) 104 open pull
>> requests (PRs) which still need testing or review or to be postponed:
>> https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.0
>>
>
> This is now down to 27. Kudos to Anna, myself and others.
>

We are down to 14, as far as I see.
Excellent.

I created a Future milestone discussed earlier to help with the management.
>

Thanks
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC 2024

[Markus Neteler via grass-dev]

On Thu, May 2, 2024 at 5:29 PM Anna Petrášová via grass-dev
 wrote:
>
> Hi devs,
>
> We plan to have a call with the new Google Summer of Code students. If you 
> want to learn more about the projects and meet the students, please join the 
> call:
>
> Topic: GRASS GIS GSoC 2024
> Time: May 8, 2024 01:00 PM Eastern Time (US and Canada)
>
> Join Zoom Meeting
> https://ncsu.zoom.us/j/91478802764?pwd=NzlNc3ZvN3FMMzZxcVNzUEFsYWV3dz09
>
> Meeting ID: 914 7880 2764
> Passcode: 868437
>
> Best,
> Anna

Here in some other timezones:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=5&day=8&hour=17&min=0&sec=0&p1=207&p2=48&p3=51&p4=671

(hope I got it right)

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [release planning] GRASS GIS 8.4.0

[Markus Neteler via grass-dev]

Hi devs,

I'd like to discuss where we stand with the 8.4.0 release originally
planned for this month.

The remainder for the 8.4.0 milestone are (currently) 104 open pull
requests (PRs) which still need testing or review or to be postponed:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.0

This is the full 8.4.0 milestone (open issues and pull requests):
https://github.com/OSGeo/grass/milestone/19

Please let's rank what still should go into 8.4.0 and what to postpone
to 8.4.1 or later.
Opinions welcome.

Best,
Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS 8.3.2 released

[Markus Neteler via grass-dev]

*GRASS GIS 8.3.2 released*

This new patch release includes important fixes and improvements to the
GRASS GIS modules
and the graphical user interface (GUI), making it even more stable for
daily work.

Some of the most important changes are: fixes for r.horizon and other
modules; improvements
in database connections for vector data as well as selected manual pages.

Translations continue in Weblate
, which automatically
creates pull requests with the translated
chunks. We’d like to thank the translators of all languages for their
ongoing support!
Full list of changes and contributors

For all changes, see our detailed announcement at GitHub / Releases / 8.3.2
.

*News article*

https://grass.osgeo.org/news/2024_03_07_grass_gis_8_3_2_released/

Thanks to all contributors!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Thanks, Peter!

Best
Markus


Peter Löwe  schrieb am Do., 14. März 2024, 15:52:

> Hi Markus, all,
>
> good news:
> Zenodo just fixed the issue for GRASS (an error on their side):
> https://zenodo.org/records/10817962
>
> Best,
> Peter
>
> 
>
>
> > Gesendet: Dienstag, 12. März 2024 um 18:23 Uhr
> > Von: "Markus Neteler" 
> > An: "Peter Löwe" 
> > Cc: "GRASS developers list" 
> > Betreff: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2
> >
> > Hi Peter, all,
> >
> > So GRASS GIS 8.3.2 has been published and no trace of it in Zenodo:
> >
> > https://zenodo.org/records/10685321
> >
> > The GitHub-Zenodo bridge seems to be unstable?
> >
> > Ideas welcome,
> > Markus
> >
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Hi Peter, all,

So GRASS GIS 8.3.2 has been published and no trace of it in Zenodo:

https://zenodo.org/records/10685321

The GitHub-Zenodo bridge seems to be unstable?

Ideas welcome,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Hi,

On Thu, Mar 7, 2024 at 12:14 AM Markus Neteler  wrote:
>
> On Wed, Mar 6, 2024 at 3:00 PM Markus Neteler  wrote:
> >
> > I'd now move on and publish GRASS GIS 8.3.2 unless there are objections.
>
> I have started 2 hs ago but the CI is clogged and the
> release-from-tagging build doesn't finish which is essential to get it
> done.
> Need to sleep now and will continue tomorrow...

Done so.
https://github.com/OSGeo/grass/releases/tag/8.3.2

Here the release announcement PR:
https://github.com/OSGeo/grass-website/pull/413

Still needed: a screenshot!

Once the binaries are prepared we can announce the release.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

On Wed, Mar 6, 2024 at 3:00 PM Markus Neteler  wrote:
>
> I'd now move on and publish GRASS GIS 8.3.2 unless there are objections.

I have started 2 hs ago but the CI is clogged and the
release-from-tagging build doesn't finish which is essential to get it
done.
Need to sleep now and will continue tomorrow...

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Dear all,

On Thu, Feb 22, 2024 at 8:45 PM Anna Petrášová  wrote:
> On Thu, Feb 22, 2024 at 12:33 PM Markus Neteler  wrote:
>> On Thu, Feb 22, 2024 at 3:59 PM Anna Petrášová  wrote:
>> > On Tue, Feb 20, 2024 at 5:45 PM Markus Neteler via grass-dev 
>> >  wrote:
>> ...
>> >> Hopefully no RC2 is needed.
>> >
>> > Markus,
>> >
>> > a bug in r.horizon came up on gitter recently:
>> > https://github.com/OSGeo/grass/pull/3441
>> >
>> > It would be nice to include it in 8.3.2 (with all the other fixes in 
>> > r.horizon) but at the same time I don't want to
>> > trigger RC2 because of this... The bug fix is a small change in r.horizon 
>> > not impacting anything else, so
>> > perhaps we wouldn't need RC2? What do you think?
>>
>> For me that's okay as it is very isolated.
>> Feel free to backport it.
>>
>
> Done!

I'd now move on and publish GRASS GIS 8.3.2 unless there are objections.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.copy doesn't respect computational region??

[Markus Neteler via grass-dev]

On Sun, Mar 3, 2024 at 2:48 AM Vaclav Petras via grass-dev
 wrote:
>> On March 2, 2024 1:00:23 AM GMT+01:00, Michael Barton via grass-dev 
>>  wrote:
>> >It's been awhile since I've done this but I thought I remembered that a new 
>> >map created with r.copy is constrained by the computational region.
>> >That does not seem to the case, at least in 8.4 dev. Maybe it has been this 
>> >way for awhile (long while?) and I didn't notice it.
>>
>> I think, but I'm not 100% sure, that has always been the case.
>
> Here is g.copy documentation from v6.4 it does not mention anything about 
> region. It seems to go back to US Army CERL.
>
> https://github.com/OSGeo/grass-legacy/blob/2734c86fd5cb976b4a94b04a2cdc75b4613f6a77/general/manage/cmd/g.copy.html#L6

Here is also the GRASS GIS 4.0 manual page (:
https://github.com/OSGeo/grass-legacy/blob/releasebranch_4_0/man/man1/g.copy

To easily read it, click the "Raw" button, save to disk as
"g.copy.man", then render the man page with:

man ./g.copy.man

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Hi Peter,

On Sun, Feb 25, 2024 at 12:20 AM Peter Löwe  wrote:
>
> Markus, all,
>
> minting a DOI should take minutes/seconds, not days.
>
> Can more in depth info / metadata about the particular transaction be 
> provided, which states that "https://doi.org/10.5281/zenodo.10685321"; should 
> be the new version DOI for GRASS GIS 8.3.2RC1 ?

Sure:

Version 8.3.2RC1: https://zenodo.org/records/10685321
--> see left side
   --> DOI: https://doi.org/10.5281/zenodo.10685321
 ---> still missing while advertised on the Zenodo page.

Not sure how that could happen?

Best,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Dear Peter,

On Thu, Feb 22, 2024 at 7:33 PM Veronica Andreo  wrote:
>
> Markus, all,
>
> Great! Thanks a lot!
>
> Zenodo link works, but the doi link yields doi not found page... is it ok for 
> the resolver link to take a couple of days?

Still not generated:
https://doi.org/10.5281/zenodo.10685321

Peter, do you have an idea what could be wrong?

thanks,
Markus


> Vero
>
> El mar, 20 feb 2024 a las 19:45, Markus Neteler via grass-dev 
> () escribió:
>>
>> Hi devs,
>>
>> On Thu, Feb 1, 2024 at 10:40 PM Markus Neteler  wrote:
>> > We have accumulated a number of fixes in the past weeks.
>> >
>> > Here the milestone:
>> > https://github.com/OSGeo/grass/milestone/24
>>
>> The RC1 release is now available, please test it:
>> https://github.com/OSGeo/grass/releases/tag/8.3.2RC1
>>
>> The open issues/PR I have moved to a new 8.3.3 milestone. But let's
>> focus on 8.4.0.
>>
>> And yay, the Zenodo bridge works again:
>> Version 8.3.2RC1: https://zenodo.org/records/10685321
>> DOI: https://doi.org/10.5281/zenodo.10685321 (resolver link will work
>> in some hs from now)
>>
>> Hopefully no RC2 is needed.
>>
>> Thanks to all contributors,
>> Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS: backport of CI speed updates to G83?

[Markus Neteler via grass-dev]

On Fri, Feb 23, 2024 at 2:52 AM Vaclav Petras  wrote:
> On Tue, 20 Feb 2024 at 04:14, Markus Neteler via grass-dev 
>  wrote:
>> In fact the slowest CI run determines how much time I have to wait
>> with each release step (i.e., editing VERSION file, wait 1:30hs, do
>> some steps, wait 1:30hs, create tarball, wait 1:30hs, reset VERSION
>> file, wait 1:30hs ... which is a pain).
>
> Isn't the issue the release procedure itself? It has a bunch of steps which 
> need to be done manually.

Sure. But if one has to wait 1:30 hs for the next step it overall
takes a lot of time.
Hence my (meanwhile discarded) wish to have a faster CI as it
meanwhile exists in G84.

> I counted 3 pushes which is what triggers the CI.

Indeed perhaps only 3 pushes and not 5.

> 1) release VERSION file push
> 2) tag push
> 3) development VERSION file push
>
> The release needs step 2 to be completed. We were doing step 2 only after CI 
> for step 1 completed to make sure the CI runs on the branch at that time 
> before the tag is made in step 2.
> I guess the reason to wait after step 2 before doing step 3 is to make sure 
> that the automated part of the release procedure linked to step 2 actually 
> went through. Is this correct?

It also includes that the complete build of artefacts is needed for
download/upload to grass.osgeo.org and the download server.

(unrelated to the CI part then also milestone cleanup, etc. follows,
so after step 3 more is to be done)

Cheers
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

On Thu, Feb 22, 2024 at 3:59 PM Anna Petrášová  wrote:
> On Tue, Feb 20, 2024 at 5:45 PM Markus Neteler via grass-dev 
>  wrote:
...
>> Hopefully no RC2 is needed.
>
> Markus,
>
> a bug in r.horizon came up on gitter recently:
> https://github.com/OSGeo/grass/pull/3441
>
> It would be nice to include it in 8.3.2 (with all the other fixes in 
> r.horizon) but at the same time I don't want to
> trigger RC2 because of this... The bug fix is a small change in r.horizon not 
> impacting anything else, so
> perhaps we wouldn't need RC2? What do you think?

For me that's okay as it is very isolated.
Feel free to backport it.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Hi devs,

On Thu, Feb 1, 2024 at 10:40 PM Markus Neteler  wrote:
> We have accumulated a number of fixes in the past weeks.
>
> Here the milestone:
> https://github.com/OSGeo/grass/milestone/24

The RC1 release is now available, please test it:
https://github.com/OSGeo/grass/releases/tag/8.3.2RC1

The open issues/PR I have moved to a new 8.3.3 milestone. But let's
focus on 8.4.0.

And yay, the Zenodo bridge works again:
Version 8.3.2RC1: https://zenodo.org/records/10685321
DOI: https://doi.org/10.5281/zenodo.10685321 (resolver link will work
in some hs from now)

Hopefully no RC2 is needed.

Thanks to all contributors,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

On Tue, Feb 20, 2024 at 9:29 PM Markus Neteler  wrote:
>
> On Fri, Feb 16, 2024 at 5:20 PM Martin Landa  wrote:
> >> > Markus, can we start the procedure of releasing GRASS 8.3.2RC1?
> >>
> >> Yes, I'll do as soon as I find 3-4 hs of free time in a row.
> >> Hopefully in the next days.
> >
> > Great, thanks a lot. Martin
>
> Procedure started.
> Due to the long CI (GitHub actions) processes in G8.2 this will take
> multiple hours.

Obviously G8.3.

> I'll notify once I am done.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

On Fri, Feb 16, 2024 at 5:20 PM Martin Landa  wrote:
>> > Markus, can we start the procedure of releasing GRASS 8.3.2RC1?
>>
>> Yes, I'll do as soon as I find 3-4 hs of free time in a row.
>> Hopefully in the next days.
>
> Great, thanks a lot. Martin

Procedure started.
Due to the long CI (GitHub actions) processes in G8.2 this will take
multiple hours.
I'll notify once I am done.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS: backport of CI speed updates to G83?

[Markus Neteler via grass-dev]

On Tue, Feb 20, 2024 at 1:59 AM Edouard Choinière  wrote:
>
> I don’t know a lot about backporting,

If "lucky", then it is just

git cherry-pick 

> but if you’re talking about splitting of the Ubuntu workflow’s gunittest 
> tests, I don’t see a reason why the content of the changes couldn’t be copied 
> to a new commit for that branch too. Since they are ran less often, the tests 
> could be split in three or even 4 jobs, where the %of time spent compiling 
> the same code would be a bit higher, but the time for all tests to run could 
> be smaller. The tests in the temporal folder still take half the total test 
> time though.
>
> If you are talking about the macOS arm runner, it might require some other 
> changes to port. My opinion would be to leave that alone in the 8.3 as 
> pre-arm code. But the same splitting could easily be done for 8.3, and split 
> as wished.

In fact the slowest CI run determines how much time I have to wait
with each release step (i.e., editing VERSION file, wait 1:30hs, do
some steps, wait 1:30hs, create tarball, wait 1:30hs, reset VERSION
file, wait 1:30hs ... which is a pain).

> In main, for macOS workflows, with only 20-25 mins spent on tests, with 3-4 
> min spent on compiling, I don’t see the need to split it.

Okay.

> Windows workflows I don’t think it’s advantageous, as more than 20 mins is 
> spent before starting tests.

Alright.
Perhaps I have simply go through it again and hope that we abandon 8.3 soon :-)

Best
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS: backport of CI speed updates to G83?

[Markus Neteler via grass-dev]

Hi Edouard,

Do you see a chance to backport the CI speed updates to G83? That would
make my release manager life much easier as the ever lasting waiting would
probably halfen ... :)

I could also cherry-pick that in case.

Best
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

On Thu, Feb 15, 2024 at 9:07 AM Martin Landa  wrote:
>
> Dear all,
>
> ne 11. 2. 2024 v 15:39 odesílatel Martin Landa  
> napsal:
>>
>> Only one remains: https://github.com/OSGeo/grass/pull/3208
>>
>> After solving the last issue we could release 8.3.1RC1 if no objections will 
>> appear.
>
> solved.

Great!

> Markus, can we start the procedure of releasing GRASS 8.3.2RC1?

Yes, I'll do as soon as I find 3-4 hs of free time in a row.
Hopefully in the next days.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS-Wiki: new OSGeo-ID login method activated

[Markus Neteler via grass-dev]

Dear all,

As of February 2024, we are happy to announce that the GRASS Wiki (
https://grasswiki.osgeo.org/wiki/) is connected to the OSGeo authentication
system!
Many thanks to Regina Obe from OSGeo-SAC (
https://wiki.osgeo.org/wiki/User:Robe).

*What does it mean?*

In order to keep spammers out of the system and to simplify the overall
OSGeo login experience, the centralized OSGeo login method is also
activated for the GRASS GIS Wiki.
Please note that your current GRASS-Wiki username/password will no longer
work here in favor of the OSGeo-ID already used elsewhere (OSGeo-Wiki etc.).

*What do I need to log in?*

As before, no login is required to read the wiki content.

To edit the Wiki, you need to login with your OSGeo-ID (technically your
OSGeo-LDAP account). If you do not have an OSGeo-ID yet, please register
here: https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ .

*What if I already have a GRASS-Wiki account?*

The first time you log in to the GRASS-Wiki with your OSGeo-ID, your
existing old user account will be merged with the OSGeo-ID. This should
work automatically. If not, please contact me directly.

Feel free to ask if you have any questions.

Best regards,
Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Markus Neteler via grass-dev]

On Tue, Feb 6, 2024 at 12:11 AM Luca Delucchi via grass-dev
 wrote:
> On Mon, 5 Feb 2024 at 13:33, Veronica Andreo  wrote:
> > That would be cool Luca! eodag allows you to download different EO datasets.
> >
> > Do you think of a GSoC project idea to include eodag support for 
> > i.sentinel.download, i.landsat.download and i.modis.download or as a new 
> > module to download EO data in general? If you are willing to mentor, I can 
> > be your second... mainly to test and make annoying questions :)
> >
>
> Yes, the idea could be to add it to i.*.download, I was also thinking
> of having a common library in grass python library as an interface to
> eodag, but I'm not sure if it makes sense...
>
> However I tried to log to the wiki and I'm not able, and password
> recover also didn't work

Regina has updated the GRASS Wiki again and we have done a series of
tests, fixing plugins and such.

Please try again, now with your OSGeo-LDAP account.

A "user merge" may come up. Let me know if it gets blocked so that I can assist.

Markus


-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [release planning] GRASS GIS 8.3.2

[Markus Neteler via grass-dev]

Hi devs,

We have accumulated a number of fixes in the past weeks.

Here the milestone:
https://github.com/OSGeo/grass/milestone/24

There are a number of open pull requests which might go in (before
creating RC1).
Please verify.

thanks,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Addons

[Markus Neteler via grass-dev]

On Wed, Dec 13, 2023 at 11:06 AM Markus Neteler  wrote:
>
> Hi Paulo,
>
> On Wed, Dec 13, 2023 at 6:53 AM Paulo van Breugel via grass-dev
>  wrote:
> >
> > Hi all,
> >
> > How often is the addon list on 
> >  updated? And the windows 
> > addon downloads?
>
> It is a daily cronjob, apparently broken.
> I am investigating.

Addons are back!

Cheers,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Addons

[Markus Neteler via grass-dev]

Hi Paulo,

On Wed, Dec 13, 2023 at 6:53 AM Paulo van Breugel via grass-dev
 wrote:
>
> Hi all,
>
> How often is the addon list on 
>  updated? And the windows 
> addon downloads?

It is a daily cronjob, apparently broken.
I am investigating.

Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS historical documents

[Markus Neteler via grass-dev]

Hi Nicklas,

Nice collection, perhaps worth adding here:

https://grasswiki.osgeo.org/wiki/GRASS_Citation_Repository#Historic_citations

Best
markus

PS: in the old site we had a collection but it didn't make it to the
hugo site (AFAIK), and we moved it to the wiki.



On Wed, Dec 6, 2023 at 10:23 AM Nicklas Larsson via grass-dev
 wrote:
>
> I stumbled upon a — for me — nice surprise on the Internet Archive:
>
> Sources of Digital Spatial Data for Geographic Information Systems (1987)
> https://archive.org/details/DTIC_ADA189788
>
> GRASS 3.0 Programmer's Manual (1989)
> https://archive.org/details/DTIC_ADA252461
>
> GRASS/GIS (Geographic Resources Analysis Support System/Geographic 
> Information System) Implementation Guide (1989)
> https://archive.org/details/DTIC_ADA214623/
>
> GRASS/GIS (Geographic Resources Analysis Support System/Geographic 
> Information System) Implementation Guide (1989)
> https://archive.org/details/DTIC_ADA214623
>
> Proceedings of the Geographical Resource Analysis Support System (GRASS) User 
> Group Meeting Held in Champaign, Illinois, 1988 (1989)
> https://archive.org/details/DTIC_ADA213823
>
> Methodology for Performing Return-On-Investment (ROI) Studies for 
> Implementation of GRASS on Military Installations (1989)
> https://archive.org/details/DTIC_ADA222064
>
> GRASS Hardware Configurations Guide (1989)
> https://archive.org/details/DTIC_ADA220954
>
> Guidelines for Running GRASS Benchmarks (1989)
> https://archive.org/details/DTIC_ADA221332
>
> Testing Guidelines for GRASS Ports and Drivers (1989)
> https://archive.org/details/DTIC_ADA221176
>
> Options for Acquiring Elevation Data (1989)
> https://archive.org/details/DTIC_ADA220934
>
> Cartographic Issues in the Development of a Digital GRASS Database (1990)
> https://archive.org/details/DTIC_ADA227582
>
> A Comparison of Manual and Automated Methods for Delimiting Watersheds for 
> Use with GRASS/GIS Software (1991)
> https://archive.org/details/DTIC_ADA242633
>
> Geographic Resources Analysis Support System (GRASS) Version 4.0 User's 
> Reference Manual (1992)
> https://archive.org/details/DTIC_ADA255218
>
> GRASS 4.0 Map Digitizing User's Manual: v.digit (1992)
> https://archive.org/details/DTIC_ADA256859
>
> GRASS-Intergraph Data Conversion Guide (1992)
> https://archive.org/details/DTIC_ADA251458
>
> Predicting Database Requirements for Geographic Information Systems in the 
> Year 2000: Long-Term Design Issues for GRASS (1992)
> https://archive.org/details/DTIC_ADA256862
>
> Flood Damage Analysis Within the Readiness Management System (1992)
> https://archive.org/details/DTIC_ADA273274
>
> Sound Exposure Level Prediction for Impulse Sound Sources Above Variable 
> Terrain (1993)
> https://archive.org/details/DTIC_ADA267535
>
> Estimating dry grass residues using landscape integration analysis (1993)
> https://archive.org/details/NASA_NTRS_Archive_19950017447
>
> Using Neural Networks to Correlate Satellite Imagery and Ground-Truth Data 
> (1994)
> https://archive.org/details/DTIC_ADA285486
>
> A Multiscale Random Field Model for Bayesian Image Segmentation (1994)
> https://archive.org/details/DTIC_ADA283875
>
> Implementation of a Distributed Hydrologic Model within Geographic Resources 
> Analysis Support System (GRASS) (1996)
> https://archive.org/details/DTIC_ADA348892
>
> GRASS to ARC/INFO Data Conversion (1998)
> https://archive.org/details/DTIC_ADA353594
>
>
>
> Documents just tangental to GRASS, but perhaps interesting:
>
> Digital Mapping: Fact or Fiction. (1986)
> https://archive.org/details/DTIC_ADA167571
>
> Geographic Information Systems: A Primer (1990)
> https://archive.org/details/DTIC_ADA231465
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev



--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Bugs in i.cca module

[Markus Neteler via grass-dev]

Hi Māris, all,

On Wed, Nov 15, 2023 at 8:35 AM Maris Nartiss via grass-dev
 wrote:
>
> Hello devs,
> Just playing around I decided to run i.cca module. Seems that it has
> been broken since 2009(!) (there is a bug report from 2014 in Trac
> [1]). I managed to fix the segfault [2] but it left me with a
> different problem – the module runs just fine but produces NULLs as an
> output. This boils down to at one point trying to calculate sqrt from
> negative numbers. I am not that familiar with the CCA algorithm
> implemented in the module and thus have no idea if it is a bug in the
> code or just bad input data.
>
> I hope somebody can help me to sort this out or provide a working example,
> Māris.

Digging in my inbox I found this thread from 2009:
https://lists.osgeo.org/pipermail/grass-dev/2009-August/045656.html

It contains some discussion and examples. Maybe not much of a help but
a kind of pointer.

Markus

> 1. https://trac.osgeo.org/grass/ticket/2297
> 2. https://github.com/OSGeo/grass/pull/3239
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

[Markus Neteler via grass-dev]

On Mon, Oct 30, 2023 at 7:08 PM Veronica Andreo  wrote:
>
> Vashek, do you have access? Perhaps you can share credentials privately?

Ping

> El mié, 25 oct 2023 a las 15:34, Markus Neteler via grass-dev 
> () escribió:
>>
>> Hi Peter, Vaclav, Vero,
>>
>> On Wed, Aug 16, 2023 at 3:34 PM Markus Neteler  wrote:
>> >
>> > Hi all,
>> >
>> > While I have indeed a script to auto-upload code/data to Zenodo.org
>> > along with metadata stored in CITATION.cff, I don't remember who has
>> > access to the GRASS GIS Zenodo account.
>>
>> This wondering... anyone?
>>
>> > This would be needed, otherwise it won't "join" the other releases
>> > stored there under the meta DOI.
>> >
>> > Vaclav or Vero perhaps?
>>
>> Zenodo updates are still broken, see:
>> https://zenodo.org/records/6612307
>> and related.
>>
>> Markus
>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS 8.3.1 released

[Markus Neteler via grass-dev]

*GRASS GIS 8.3.1 released*

The GRASS GIS 8.3.1 release provides more than 60 improvements and fixes
with respect to the release 8.3.0.
Highlights

   - g.extension: fix installing addons on MS Windows
   - r.watershed: fix streams and basins
   - graphical user interface: multiple bugs fixed

Visit the release page 
(see https://github.com/OSGeo/grass/releases/tag/8.3.1) to download the
source code.

*News article*

https://grass.osgeo.org/news/2023_10_25_grass_gis_8_3_1_released

Thanks to all contributors!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Dear all,
I am trying to build G8.3.1 for Fedora (F40) but get a strange error:

GRASS GIS 8.3.1 exported compilation log
--
Started compilation: Thu Oct 26 12:52:40 UTC 2023
--
Errors in:
/builddir/build/BUILD/grass-8.3.1/raster3d/r3.in.ascii

Related to
gcc  x86_64  13.2.1-4.fc40
?

The log is here, help quite welcome:
https://kojipkgs.fedoraproject.org//work/tasks/2196/108132196/build.log

Thanks,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

[Markus Neteler via grass-dev]

Hi Peter, Vaclav, Vero,

On Wed, Aug 16, 2023 at 3:34 PM Markus Neteler  wrote:
>
> Hi all,
>
> While I have indeed a script to auto-upload code/data to Zenodo.org
> along with metadata stored in CITATION.cff, I don't remember who has
> access to the GRASS GIS Zenodo account.

This wondering... anyone?

> This would be needed, otherwise it won't "join" the other releases
> stored there under the meta DOI.
>
> Vaclav or Vero perhaps?

Zenodo updates are still broken, see:
https://zenodo.org/records/6612307
and related.

Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://grassbook.org/neteler/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi all,

GRASS GIS 8.3.1 is now available:
https://github.com/OSGeo/grass/releases/tag/8.3.1

Source code uploaded to
https://grass.osgeo.org/grass83/source/

News item draft:
https://github.com/OSGeo/grass-website/pull/395

Wiki and trac release page already updated.

Packagers are welcome to create binaries.
In the next days we may then post the official announcement.

Thanks to all contributors!

Cheers,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

On Tue, Oct 24, 2023 at 9:34 PM Markus Neteler  wrote:
>
> Hi devs,
>
> I have now started the "final" release procedure.
> Unfortunately it takes several hours, due to the endless waiting for
> the GitHub actions to complete.

Argh!:

Ubuntu / minimum config tests
Failed in 1 hour, 46 minutes, and 4 seconds

I need to sleep, if anyone awake can re-run the time-out'ed ones I'd
be grateful.
Then I can continue the release tomorrow.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi devs,

I have now started the "final" release procedure.
Unfortunately it takes several hours, due to the endless waiting for
the GitHub actions to complete.

Please don't push to the 8.3 release branch at time till the release
is complete.

Markus

On Mon, Oct 23, 2023 at 6:38 PM Michael Barton via grass-dev
 wrote:
>
> Most of these don't affect the Mac and there are more pressing issues for 
> coloring vectors than the #3196 and #3206 IMHO
> (e.g., see #3126-3128). So OK with me to release 8.3.1 to fix a couple of 
> really major issues and bump the others to 8.3.2.
>
> Michael
>
> On Sun, Oct 22, 2023 at 2:27 PM Markus Neteler  wrote:
> >
> > Still 6 items to go or bump to the 8.3.2 milestone:
> > https://github.com/OSGeo/grass/issues?q=is%3Aopen+label%3A%22backport+to+8.3%22+milestone%3A8.3.1
> >
> > Given the urgency of 8.3.1 final I suggest to merge what's possible
> > and bump the rest.
> > Or, rather bump all and release 8.3.1 final.
> >
> > Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi devs,

Still 6 items to go or bump to the 8.3.2 milestone:
https://github.com/OSGeo/grass/issues?q=is%3Aopen+label%3A%22backport+to+8.3%22+milestone%3A8.3.1

Given the urgency of 8.3.1 final I suggest to merge what's possible
and bump the rest.
Or, rather bump all and release 8.3.1 final.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] [TOSprint] Join OSGeo Community Sprint 2023 at BIDS ‘23

[Markus Neteler via grass-dev]

Please consider to join :-)

-- Forwarded message -
From: Angelos Tzotsos via Discuss 
Date: Wed, Oct 18, 2023 at 5:00 PM
Subject: Re: [OSGeo-Discuss] [TOSprint] Join OSGeo Community Sprint
2023 at BIDS ‘23
To: 
Cc: OSGeo Discussions ,
proje...@lists.osgeo.org 


Hi all,

The registration for BiDS closes on Oct 23rd.
https://www.bigdatafromspace2023.org/registration

If you are planning to join the community sprint, please make sure you
have registered both to BiDS and on the community sprint wiki page.

We hope to see you in Vienna.


On 6/19/23 12:18, Angelos Tzotsos wrote:
> Dear OSGeo community,
>
> OSGeo Community Sprint will come to Vienna (Austria) in November 2023
> [1] as part of the Big Data from Space 2023 (BiDS) [2] event. Come
> join us!
>
> When:
>
> - Mon 2023-⁠⁠11-06 09:00 -⁠⁠ Thu 2023-11-09 12:00
>
> Where:
>
> - Venue: Austria Center Vienna [3] [15]
>
>
> Interested? So read more about why & where & when...
>
> The Open Source Geospatial Foundation (OSGeo) has a long tradition of
> organizing code sprints for developers of Free and Open Source GIS
> software.
>
> Since 2009, the Open Source Geospatial Foundation (OSGeo) [4] has been
> organizing a yearly Code Sprint of the "C Tribe" OSGeo projects, which
> has evolved into a full OSGeo Community Sprint and all "Tribes" are
> included/welcome. Leading developers of projects like GDAL, PostGIS,
> MapServer, GeoServer, GRASS, QGIS, PDAL, pygeoapi and many more get
> together to discuss new ideas, hack, decide, tackle large geospatial
> problems & to have fun.
>
> Our last face-to-face OSGeo Community Sprint was held with success in
> Minnesota [5] in 2019.
> In 2020, due to the pandemic, we canceled the Athens code sprint and
> organized a virtual code sprint [6].
> In 2021 and 2022 we organized code sprints during FOSS4G events and
> joint code sprints with OGC and Apache Foundation.
>
> 2023 marks the return of the OSGeo Community Sprint which will return
> to Europe after Vienna (2014)[7], Paris (2016) [8] and Bonn (2018)[9].
> This makes it possible to embed European developers and users. The
> tradition started in 2009 in Toronto [10]. Find a list of the history
> of code sprints at [11].
>
>
> About BiDS
> --
>
> BiDS brings together key actors from industry, academia, EU entities
> and government to reveal user needs, exchange ideas and showcase
> latest technical solutions and applications touching all aspects of
> space and big data technologies, providing a unique opportunity to
> discuss and present the most recent innovations and challenges
> encountered in the context of big data from space. The 2023 edition of
> BiDS will focus not only technologies enabling insight and foresight
> inferable from big data from space. Together, we want to emphasize how
> breakthrough space data driven technologies impact on society’s grand
> challenges, such as climate change and the green transition.
>
> The event, organized by the European Space Agency (ESA) [12] together
> with the European Union Satellite Center (SatCen) [13] and the Joint
> Research Center (JRC)[14], will take place at the Austria Center
> Vienna [15], and counts with the support of the partners FFG [16],
> Austria in Space [17] and the Federal Ministry Republic of Austria [18].
>
>
> OSGeo Community Sprint 2023 in Vienna
> -
> The international code sprint of the OSGeo will take place from 6 to 9
> November 2023. We expect about 60 developers from all over the world
> to come from various OSGeo projects [4].
>
> The code sprint will take place at Austria Center Vienna [3] [15], as
> part of the Big Data from Space 2023 (BiDS) [2] event.
>
>
> Accommodations
> -
> Working zones will be created for you in the dedicated room area. A
> wide variety of drinks and snacks will be provided by OSGeo and
> sponsors. Participation in the code sprint is free of charge. As a
> participant, you are responsible for your own accommodation.
>
> Several hotels and apartments are close to the venue, many of which
> are within walking distance.
>
> Registering for the OSGeo Community Sprint
> 
>
> In order to register for the OSGeo Community Sprint you need to
> register for the BiDS event [2]. More information about Big Data from
> Space and the registration link once opened, can be found under
> bigdatafromspace2023.org [2].
>
> Afterwards, please don't forget to sign up in the OSGeo wiki at our
> OSGeo Community Spint 2023 page:
> https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023#Participants
>
> This is an important step for planning of catering and coordination.
>
> The OSGeo Community Sprint is open to all who wish to participate in
> one or more projects. There is always plenty to do – it’s not all
> about programming. Translation, documentation, feedback, discussions,
> testing – all th

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

On Fri, Oct 13, 2023 at 9:46 AM Sebastiaan Couwenberg via grass-dev
 wrote:
> On 10/13/23 09:07, Markus Neteler via grass-dev wrote:
> > Nonetheless some glitches GRASS GIS 8.3.1RC1 is released:
> >
> > https://github.com/OSGeo/grass/releases/tag/8.3.1RC1
>
> No tarball available via https://grass.osgeo.org/grass83/source/ yet.

Sorry, now there is.

Best,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi devs,

Nonetheless some glitches GRASS GIS 8.3.1RC1 is released:

https://github.com/OSGeo/grass/releases/tag/8.3.1RC1

Please test!

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi all,

On Thu, Oct 12, 2023 at 2:47 PM Ondřej Pešek  wrote:
> so 30. 9. 2023 v 16:12 odesílatel Markus Neteler via grass-dev
>  napsal:
> > As far as I see the git on Windows issue has been solved as well as
> > many wxGUI bugs.
> > Still a few to go which are under review. Shall we wait for them?
> > Please let me know.
>
> Not only Windows wxGUI issues. It is impossible to change the layout
> from single window to the original one. I am using the original one
> with students, meaning that I am still using 8.2.x with them.
> Releasing 8.3.1 (where it is fixed) would let me to use 8.3.x versions
> with them without forcing them to compile it on their own. (the
> 8.3.0-broken r.watershed is also used there)
>
> So a new release would be appreciated also at my side.

I have started with the RC1 release procedure but got stuck: pylint
errors and no changelog possible to create.
Have contacted Vaclav via chat (we recently improved the howto_release
notes in a long video call).

Since it is late here I guess I can only continue tomorrow.

Cheers and sorry for being slow.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS Working Groups

[Markus Neteler via grass-dev]

Dear all,

On Tue, Oct 10, 2023 at 9:35 PM Anna Petrášová via grass-dev
 wrote:
>
> Thanks to everyone who responded! I will keep the survey [1] open until the 
> end of the week. Alternatively, just let me know directly if you want to join.
>
> Based on the responses I created wiki pages for the different working groups 
> [2] and added the respondents to the particular group. I assigned a group 
> coordinator to each group to get us started. For those of you who already 
> have access to the wiki, please add what kind of issues you are interested in 
> within the working group. If you don't have a GRASS wiki account, you can 
> either try to create it or ask me or the other group coordinators to fill 
> those details for you. There may be some changes in the wiki authentication 
> now [3], so I am unsure whether signing up at this point is feasible or not.

Yes, please subscribe to the Wiki as before. We don't know when the
new, simplified method will become available.
Just register here: https://grasswiki.osgeo.org/wiki/Special:RequestAccount
and notify by email me (or another wiki admin).

The (still) annoying part is to manually approve the good account
registrations. But having your notification it will be doable.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP

[Markus Neteler via grass-dev]

Hi,

Please note that test emails may be issued: they come from the staging VM
which is a test clone of the wiki.

These emails please ignore.
See below for the original notification about LDAP migration.

Markus



Markus Neteler  schrieb am Do., 5. Okt. 2023, 09:43:

> Hi devs,
>
> See below for some efforts to connect the GRASS GIS Wiki to OSGeo-LDAP
> (to finally get rid of all the spam registrations).
>
> Cheers
> Markus
>
> -- Forwarded message -
> From: OSGeo via Sac 
> Date: Thu, Oct 5, 2023 at 4:46 AM
> Subject: Re: [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP
> Cc: OSGeo , 
>
>
> #2966: GRASS GIS wiki: connect to OSGeo LDAP
> -+---
>  Reporter:  neteler  |   Owner:  sac@…
>  Type:  task |  Status:  new
>  Priority:  normal   |   Milestone:  Sysadmin Contract 2023-I
> Component:  Systems Admin|  Resolution:
>  Keywords:  mediawiki, ldap  |
> -+---
> Comment (by robe):
>
>  I set up a dev server to get the ball rolling which is just snapshot of
>  prod
>
>  https://grasswiki.staging.osgeo.org/wiki/GRASS-Wiki
>
>  I'll test out upgrading the wiki and then incorporating LDAP
>  authentication on this. I'll let you know once it's ready to test out.
>
> --
> Ticket URL: 
> OSGeo 
> OSGeo committee and general foundation issue tracker.
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Tour of tools used by GDAL CI, testing and documentation by Even Rouault

[Markus Neteler via grass-dev]

(via GDAL maintainer report, perhaps of interest also here)

Tour of tools used by GDAL CI, testing and documentation
by Even Rouault, Sept 2023:
http://download.osgeo.org/gdal/presentations/NumFocus%20Summit%202023%20Tour%20of%20tools%20used%20by%20GDAL%20CI%2C%20testing%20and%20documentation.pdf
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP

[Markus Neteler via grass-dev]

Hi devs,

See below for some efforts to connect the GRASS GIS Wiki to OSGeo-LDAP
(to finally get rid of all the spam registrations).

Cheers
Markus

-- Forwarded message -
From: OSGeo via Sac 
Date: Thu, Oct 5, 2023 at 4:46 AM
Subject: Re: [SAC] [OSGeo] #2966: GRASS GIS wiki: connect to OSGeo LDAP
Cc: OSGeo , 


#2966: GRASS GIS wiki: connect to OSGeo LDAP
-+---
 Reporter:  neteler  |   Owner:  sac@…
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Sysadmin Contract 2023-I
Component:  Systems Admin|  Resolution:
 Keywords:  mediawiki, ldap  |
-+---
Comment (by robe):

 I set up a dev server to get the ball rolling which is just snapshot of
 prod

 https://grasswiki.staging.osgeo.org/wiki/GRASS-Wiki

 I'll test out upgrading the wiki and then incorporating LDAP
 authentication on this. I'll let you know once it's ready to test out.

--
Ticket URL: 
OSGeo 
OSGeo committee and general foundation issue tracker.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi devs,

On Thu, Sep 28, 2023 at 3:30 PM Anna Petrášová  wrote:
> On Thu, Sep 28, 2023 at 1:15 AM Markus Neteler  wrote:
>>
>> Hi devs,
>>
>> May we schedule RC1 by end of the week?
>
> +1 from me

As far as I see the git on Windows issue has been solved as well as
many wxGUI bugs.
Still a few to go which are under review. Shall we wait for them?
Please let me know.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

Hi devs,

May we schedule RC1 by end of the week?

Markus


Anna Petrášová  schrieb am Mo., 25. Sep. 2023, 23:08:

>
>
> On Mon, Sep 25, 2023 at 3:23 PM Tomas Zigo via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
>
>> Citát Markus Neteler :
>> > In addition, we have plenty of wxGUI fixes, which might well go in:
>> >
>> > https://github.com/OSGeo/grass/labels/backport%20to%208.3
>> >
>> > Markus
>>
>> I am in favor of including all necessary wxGUI fixes soon as possible
>> in the 8.3.1 release.
>>
>> https://github.com/OSGeo/grass/labels/backport%20to%208.3
>>
>> Tomas
>>
>
> Thanks for all the fixes, I started to go through them and will continue
> the reviews.
>
> Anna
>
>>
>>
>>
>> ___
>> 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] [EXTERNAL] [release planning] GRASS GIS 8.3.1

[Markus Neteler via grass-dev]

On Wed, Sep 20, 2023 at 5:31 PM Nicklas Larsson  wrote:
>
> https://github.com/OSGeo/grass/issues/3077
> _is_ the one and only blocker for 8.3.1. :
>
> https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3A%22backport+to+8.3%22+label%3Ablocker

In addition, we have plenty of wxGUI fixes, which might well go in:

https://github.com/OSGeo/grass/labels/backport%20to%208.3

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] osgeo.org domain DNS DOS

[Markus Neteler via grass-dev]

FYI, these DNS attacks also affects some of our servers as well as CI
which needs to download files from osgeo.org servers.

Markus

-- Forwarded message -
From: Regina Obe via Discuss 
Date: Thu, May 18, 2023 at 1:30 AM
Subject: [OSGeo-Discuss] osgeo.org domain DNS DOS
To: , 


Sorry all for the outage this afternoon.

I had put in a ticket earlier on PAIRS (our registrar and DNS authority).
They confirmed that osgeo.org DNS calls were under DOS attack.
At the moment things seem to be fine, but I haven't gotten confirmation from
them we are out of the woods.

Thanks for your patience,
Regina

___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev