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

> 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

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

Markus, > On 28 Jul 2024, at 11:54, Markus Neteler via grass-dev > wrote: > > 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 202

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

Thanks Markus!!! > On 27 Jul 2024, at 18:09, Markus Neteler via grass-dev > wrote: > > 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/gra

Re: [GRASS-dev] A load of updates in OSGeo4W

Jürgen, Thank you very much for this gigantic task of putting all these pieces together, I’m sure the Windows users will be delighted! Best, Nicklas > On 15 Apr 2024, at 01:02, Jürgen E. Fischer via grass-dev > wrote: > > Hi there, > > I just uploaded an update to OSGeo4W. It is basically

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

> On 20 Feb 2024, at 10:14, Markus Neteler via grass-dev > mailto:grass-dev@lists.osgeo.org>> 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:3

Re: [GRASS-dev] configurare fails: Failed check for math library

> On 24 Jan 2024, at 15:31, Martin Landa wrote: > > Hi, > > st 24. 1. 2024 v 15:22 odesílatel Nicklas Larsson > napsal: >> I too would have been surprised if glibc wasn’t there. (I’m shooting from >> the hips :-). >> >> You can investigate the "config.log” for ho

Re: [GRASS-dev] configurare fails: Failed check for math library

I too would have been surprised if glibc wasn’t there. (I’m shooting from the hips :-). You can investigate the "config.log” for hopefully more detailed information on why the math library configure test failed. > On 24 Jan 2024, at 14:59, Martin Landa wrote: > > Hi, > > st 24. 1. 2024 v 14:

Re: [GRASS-dev] configurare fails: Failed check for math library

ot installed, you’ll probably need `glibc`. > >> On 24 Jan 2024, at 14:00, Nicklas Larsson via grass-dev >> wrote: >> >> Martin, >> >> Noting that you use a non-default prefix, you may need to add >> `LDFLAGS="-L/usr/lib”` (and perhaps add ´”-

Re: [GRASS-dev] configurare fails: Failed check for math library

Another thought, configure fails at locating the math library which is part of standard C library. If not installed, you’ll probably need `glibc`. > On 24 Jan 2024, at 14:00, Nicklas Larsson via grass-dev > wrote: > > Martin, > > Noting that you use a non-default prefix, y

Re: [GRASS-dev] configurare fails: Failed check for math library

Martin, Noting that you use a non-default prefix, you may need to add `LDFLAGS="-L/usr/lib”` (and perhaps add ´”-I/usr/include” to CFLAGS and CXXFLAGS). The same result could perhaps be reached with `--with-includes=/usr/include --with-libs=/usr/lib` added to configure, although that I’m not su

[GRASS-dev] GRASS historical documents

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

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

t;>> >>>> >>>> 1. Run `/Applications/GRASS-8.3.app/Contents/MacOS/Grass.sh` >>>> >>>> 2. System will complain… >>>> >>>> 3. Go to 'System Settings > Privacy & Security > Security' >>>>

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

w this can be solved properly. >> Maybe we have to make a binary that does the job the script now does (that >> used to be the case some time ago). We should also invest some time in >> creating a code signed app as well. >> >> >> Nicklas >> >>

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

ave to make a binary that does the job the script now does (that used to be the case some time ago). We should also invest some time in creating a code signed app as well. Nicklas > On 22 Sep 2023, at 11:01, Nicklas Larsson via grass-dev > wrote: > > Gregor, thanks very much for

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

Gregor, thanks very much for the info! At least it ruled some things out, but I have still no idea what is causing this and it’s very difficult do the needed poking around without a similar setup (macOS 14 without Rosetta installed). I’ll have to ponder on this, if this really is caused by some

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

Gregor, thanks very much for the info! At least it ruled some things out, but I have still no idea what is causing this and it’s very difficult do the needed poking around without a similar setup (macOS 14 without Rosetta installed). I’ll have to ponder on this, if this really is caused by some

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

> github.com <http://github.com/> > > From: grass-dev <mailto:grass-dev-boun...@lists.osgeo.org>> on behalf of Nicklas Larsson via > grass-dev mailto:grass-dev@lists.osgeo.org>> > Sent: Wednesday, September 20, 2023 4:14 AM > To: Markus Neteler mailto:nete

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

In general, I wouldn’t mind a quick patch 8.3.1 release. Remaining (non-blocking) issues may be bumped to 8.3.2, which in turn can be released as soon as possible. The changes since 8.3.0: https://github.com/OSGeo/grass/compare/8.3.0...OSGeo:grass:releasebranch_8_3?expand=1

Re: [GRASS-dev] GRASS GIS for Apple Silicon Macs

Gregor, Browsing the content of both GRASS.app and the FreeCAD.app, they seem correctly to have been built for arm machines. Both are based on conda dependencies and both are initiated by shell script. The shell script initialising GRASS involves the use of '/usr/bin/osascript', which on macOS

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

> On 6 Aug 2023, at 15:23, Markus Neteler wrote: > > On Wed, Jul 12, 2023 at 3:36 PM Nicklas Larsson wrote: >> On 29 Jun 2023, at 17:33, Markus Neteler wrote: >>> On Sat, Dec 3, 2022 at 10:55 PM Markus Neteler wrote: On Sun, Jul 3, 2022 at 11:01 PM Markus Neteler wrote: > On Thu, J

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

> On 29 Jun 2023, at 17:33, Markus Neteler wrote: > > Hi devs, > > On Sat, Dec 3, 2022 at 10:55 PM Markus Neteler wrote: >> On Sun, Jul 3, 2022 at 11:01 PM Markus Neteler wrote: >>> On Thu, Jun 16, 2022 at 2:13 PM Martin Landa wrote: Dear all, 7.8.8RC1 was released on May 14

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

Perhaps adding '-std=gnu++17’ to CXXFLAGS might solve it? N. > On 24 Jun 2023, at 18:24, Markus Neteler wrote: > > Hi, > > Binder fails: > > Error loading OSGeo/grass/8.3.0 > ... > configure ... > pdal error. > > (don't have the precise error message right now). > > Markus >

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

On 2023. Jun 20., at 21:03, Markus Neteler wrote:Hi Linda, all,Linda Karlovská schrieb am Di., 20. Juni 2023, 11:29:Hi Martin, hi all,I am going to test this PR today's evening.Thanks for that.But is this now a blocker for the release?If merged, do we need RC2?From Mac

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

> On 23 Mar 2023, at 10:52, Markus Neteler wrote: > >> Still open PRs. Please complete them or bump them to the next milestone. > > Now just a few are remaining: > > - Suppress compiler warnings from GDAL #2899, nilason Just bumped #2899 to 8.4. _

Re: [GRASS-dev] Wiki Compile_and_Install: GRASS 8 on Debian 11 (bullseye) - still uptodate?

Hi Helli! That section was added in January (look at page history). It should be up-to-date. N. > On 8 Mar 2023, at 19:28, Helmut Kudrnovsky wrote: > > Hi devs, > > are the compile and install instructions for Debian > (https://grasswiki.osgeo.org/wiki/Compile_and_Install#GRASS_8_on_Debian_

Re: [GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

> On 26 Jan 2023, at 15:07, Nicklas Larsson wrote: > > The question now is, are there any objections to do the same treatment to > grass-addons)? > There are three PRs in-store [3-5] to make that happen. > I understand there are no objections to apply clang-format and do the general trail

Re: [GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

ot; : just once > > - "pre-commit install": just once per repository > > Cf https://gdal.org/development/dev_practices.html#commit-hooks > <https://gdal.org/development/dev_practices.html#commit-hooks> > Even > > Le 02/01/2023 à 19:20, Nicklas Larsson via grass-dev

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

> On 18 Jan 2023, at 21:16, Markus Neteler wrote: > > Hi devs, > > On Fri, Dec 23, 2022 at 11:09 PM Markus Neteler wrote: >> On Sat, Dec 3, 2022 at 10:57 PM Markus Neteler wrote: >>> On Thu, Oct 20, 2022 at 1:30 PM Markus Neteler wrote: It is time to release 8.2.1 as a number of fixes

Re: [GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

Markus, > On 2 Jan 2023, at 13:48, Markus Neteler wrote: > > Hi Nicklas, > > On Wed, Dec 21, 2022 at 9:25 PM Nicklas Larsson via grass-dev > wrote: >> >> I understand there is agreement on using the .clang-format formatting rules >> suggested with [1]

Re: [GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

] https://github.com/OSGeo/grass/pull/2716 [10] https://lists.osgeo.org/pipermail/gdal-dev/2022-December/056658.html [11] https://gitlab.com/libtiff/libtiff/-/merge_requests/431/diffs?commit_id=01cc265a7c7f24de14cda6dc40c960eb8c3c68bb > On 5 Dec 2022, at 14:06, Nicklas Larsson via grass-dev

Re: [GRASS-dev] [OSGeo/grass] Pre-release 7.8.8RC3 - GRASS GIS 7.8.8RC3 ---> wrong branch!

No worries Markus!. I have no immediate advice on this matter…. But, as long as this isn’t solved, do NOT merge anything on the main!! > On 16 Dec 2022, at 22:46, Markus Neteler wrote: > > Hi devs, > > Seems we (I) am not releasing not often enough. > Unfortunately I created this tag on "main

Re: [GRASS-dev] Question regarding GRASS_NOTIFY

nts wrote: > > > Nicklas Larsson via grass-dev wrote: > >> I personally never had the need for the use of GRASS in this way, so forgive >> my ignorance in this regard. >> However, one thing stands out very clear from my newly gained experience: >> there is

Re: [GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

> On 7 Dec 2022, at 02:51, Vaclav Petras wrote: > > > > On Mon, 5 Dec 2022 at 08:07, Nicklas Larsson via grass-dev > mailto:grass-dev@lists.osgeo.org>> wrote: > > 1. We adapt the formatting policy using ClangFormat. > > +1 > > I would prefer i

[GRASS-dev] Configure changes in main (8.3.dev)

FYI, from now on, on main branch, after PR #2679 [1] configuring png library has changed to: --with-libpng=path/libpng-config The following flags are not usable anymore: --with-png-includes=DIRS --with-png-libs=DIRS Best, Nicklas [1] https://github.com/OSGeo/grass/pull/2679 __

Re: [GRASS-dev] Question on the CDHC library

The deafening response on this issue :-) suggests to me it is safe to remove the unused function 'Cdhc_enormp()’ from the CDHC library. If there are no objections I will shortly merge the PR: https://github.com/OSGeo/grass/pull/2640 > On 10 Nov 2022, at 15:39, Nicklas Larsson wrote: > > H

[GRASS-dev] Proposal for using ClangFormat, replacing GNU indent, for C/C++ code formatting

Dear All, I have put up a PR [1] with the intent to add a “.clang-format” file and ultimately replace the use of “GNU indent” [2] with ClangFormat [3] for formatting GRASS’ source code. ClangFormat, using the Clang compiler parser, is able to format any valid code in both C and C++. (In contras

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

+1 > On 3 Dec 2022, at 22:57, Markus Neteler wrote: > > Hi devs, > > On Thu, Oct 20, 2022 at 1:30 PM Markus Neteler > wrote: >> >> Hi devs, >> >> It is time to release 8.2.1 as a number of fixes and improvements have >> accumulated. For a list, see >> >> https://gi

Re: [GRASS-dev] GitHub backport label proposal

Markus, Please go ahead with new labels for backport, let’s start with “backport [branch name]”. If it becomes too noisy, it is easy to change (ie. the label names). Best, Nicklas > On 22 Nov 2022, at 21:40, Even Rouault wrote: > > > Le 22/11/2022 à 19:51, Nicklas Larsson a écrit : >> Looks

Re: [GRASS-dev] GitHub backport label proposal

gt; > Le 22/11/2022 à 18:47, Nicklas Larsson via grass-dev a écrit : >> I think this is a splendid idea! >> >> Would be good to keep the label as short as possible, perhaps: >> - "backport 8.0" >> - "backport 8.2” >> ? >> >>

Re: [GRASS-dev] GitHub backport label proposal

I think this is a splendid idea! Would be good to keep the label as short as possible, perhaps: - "backport 8.0" - "backport 8.2” ? At any rate, I have no strong opinion regarding the form, I fully support the general idea. Best, Nicklas > On 22 Nov 2022, at 12:00, Markus Neteler wrote: > >

[GRASS-dev] Question on the CDHC library

Hi all! Is there someone tuning in to this list that has knowledge on the content and history of the GRASS library CDHC? In a recent PR dealing with compiler warnings a strange line of code in Cdhc_enormp() was discussed [1]. It turned out we could not find any documentation on what this funct

Re: [GRASS-dev] [GRASS-user] GRASS 8.2 for Mac - wxPython problem?

Stuart, Starting GRASS from CLI (*not* double clicking the app icon) may be done with executing '/Applications/GRASS-8.2.app/Contents/MacOS/Grass.sh’. If that is what you mean with manually. With a GRASS session running, 'echo $GRASS_PYTHON’ and 'which python3’ should both give the same res

Re: [GRASS-dev] Planning 8.2.0

Just a reminder for the 8.0.2 release, there are a number of not yet (?) backported fixes: https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+label%3Abackport_needed+milestone%3A8.0.2 https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aclosed+label%3Abackport_needed+milestone%3A8.0.1 Ni

[GRASS-dev] Replace GNU Indent with ClangFormat?

Formatting the C and C++ code, making a consistent coding style was proposed for G8 [1]. Unfortunately, it didn't make it. There were attempts to do this [2, 3], but numerous problem arose using `util/grass_indent.sh` and its batch script `util/grass_indent_ALL.sh`, which are based on GNU Indent

Re: [GRASS-dev] Question regarding GRASS_NOTIFY

> On 3 Mar 2022, at 22:20, Glynn Clements wrote: > > > Nicklas Larsson via grass-dev wrote: > >> Is there anyone out there who know about usage of the environment >> variable GRASS_NOTIFY, historically and in the present? > > It's an external interfa

[GRASS-dev] Question regarding GRASS_NOTIFY

Hi Devs, Is there anyone out there who know about usage of the environment variable GRASS_NOTIFY, historically and in the present? In addressing an otherwise trivial compiler warning, I stumbled into this for me strange piece of code and usage of GRASS_NOTIFY in the Raster Display Library. I p

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

Just to clarify, on the newly proposed link: https://github.com/OSGeo/grass/tags both *.zip AND *.tar.gz files are available. On Monday, 14 February 2022, 21:27:41 CET, Huidae Cho wrote: +1 for ZIP links. Huidae On Mon, Feb 14, 2022 at 3:24 PM Jeff McKenna wrote: > On 2022-02

Re: [GRASS-dev] Release of 7.8.6 ?

> On Thursday, 7 October 2021, 21:57:03 CEST, Martin Landa > wrote: > > > > Let's release 7.8.6 as it is (with an already big delay). If there are > no objections I will prepare a 7.8.6 release in upcoming days. Martin +1 N. ___ grass-dev

Re: [GRASS-dev] Release of 7.8.6 ?

Hi All! There are some fixes that are labeled for backport for 7.8.6 [1] and yet another bunch without milestone [2], but haven't been backported. I know this is in the nick of time, after the release of RC3, but if there is a very important fix it shouldn't be left out. Otherwise the milestone

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

Hi All again! (Sorry about previous half-letter. Just went away without notice. It’s a real pain with the online interface for my email provider, and sending from an email application will likely be blocked.) I have now merged configure update to autoconf-2.69 to 7.8 branch [1, 2]. This seems

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

Hi All! I have now merged configure update [1, 2] to autoconf-2.69 to 7.8 branch [1]https://github.com/OSGeo/grass/pull/1867[2][3]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992810 On Sunday, 21 March 2021, 09:22:06 CET, Markus Neteler wrote: Hi devs, Since the last stable rel

[GRASS-dev] No more compiler warnings

Hi all! At the beginning of this year, compiling GRASS raised a very high number of compiler warnings. For example with GCC there were about 140 and with Clang about 300 warnings. This was reported with GitHub issue #1247 [1]. Since then these warnings has been addressed in a number of PRs. Tod

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

The GDAL 3.3 conflict has been resolved. Thanks Markus M! I have no further objections to proceed with 7.8.6 RC1. Cheers, Nicklas On Tuesday, 18 May 2021, 21:22:22 CEST, Nicklas Larsson via grass-dev wrote: I think we should wait for an agreement of the PR [1] addressing the GDAL

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

I think we should wait for an agreement of the PR [1] addressing the GDAL 3.3 conflict with GRASS [2], which will become a trivial yet serious issue when GDAL 3.3 becomes more widely distributed. Best, Nicklas [1] https://github.com/OSGeo/grass/pull/1567 [2] https://github.com/OSGeo/grass/iss

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

Search field in Location Wizard has been fixed [1]. [1]  https://github.com/OSGeo/grass/commit/a577a3b4c4b1773647b68d78729784960f9a9d04 Nicklas > On Wednesday, 7 April 2021, 22:30:22 CEST, Michael Barton > wrote:  > Has the broken Location Wizard been fixed? This is very important.

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

Forgot to add: Python support changes with GRASS minor versions adds a bit of complication with add-ons, which are bound to major version. I don't know what would be the better solution for this. N. On Monday, 22 March 2021, 10:24:06 CET, Nicklas Larsson via grass-psc wrote: Hi,

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

Hi, Although I didn't see the need to remove Python from RFC 7 (as it was originally formulated), there is also some logic to treat Python as a whole in a separate RFC. I don't have strong opinion on either way, therefore I lifted out Python from the draft, which now only deals with C and C++.

Re: [GRASS-dev] build system: module overlinking?

Hi Ben, according to manual "ldd prints the shared objects (shared libraries) required by each program or shared object specified on the command line." In my reading not only directly linked objects, but cascading dependencies, are listed too. On mac I can do: otool -L bin/r.surf.area bin/r.su

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

Good, Anna, you brought up this question on regular update of Python version support. I deliberately left that part out of the draft for setting/updating language standards, as I would argue it deserves a RFC on its own. A RFC should't be updatable, but may be overridden, partly or completely,

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

I added the RFC draft to GRASS Wiki [1]. Well, it's only a draft, so any thoughts, modifications, additions are most welcome! Nicklas [1] https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport On Thursday, 11 February 2021, 14:34:44 CET, Moritz Lennert wrote: Am 11.

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

Moritz, I'd be honoured! I will put it on GRASS Wiki [1] if you don't have another suggestion and notify here when done. Best, Nicklas [1] https://trac.osgeo.org/grass/wiki/RFC On Thursday, 11 February 2021, 12:54:30 CET, Moritz Lennert wrote: On 10/02/21 13:16, Nicklas Larsson

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

completeness: On Wed, Feb 10, 2021 at 1:16 PM Nicklas Larsson via grass-dev wrote: > > First of all, thank you all for your feedback and contribution to this topic. > I think it is really important to clearly state the "rules of the game" for > going forward. > > Let m

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

;> > > >>> > > >>> > > >>> > > >>> On Friday, 29 January 2021, 18:50:34 CET, Anna Petrášová < > > >>> kratocha...@gmail.com> wrote: > > >>> > > >>> > > >>> > >

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

On Friday, 29 January 2021, 18:50:34 CET, Anna Petrášová wrote: On Thu, Jan 28, 2021 at 4:28 AM Nicklas Larsson via grass-dev wrote: > Dear Devs! > > As a relatively new member of the GRASS GIS dev community, I have had to > search for information on mailing lis

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

> On 1 Feb 2021, at 08:56, Moritz Lennert wrote: > > Thanks for the clarification. > > In light of that I agree that we should choose the oldest standard possible, > unless we _really_ need something only present in a more recent version. > > @those who want to use more recent standards: wha

[GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

Dear Devs! As a relatively new member of the GRASS GIS dev community, I have had to search for information on mailing lists, old trac comments etc. regarding coding practice and in particular minimum programming language standard support. Ending up in not entirely conclusive understanding. Up u

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

Hi, >From a mac point of view I have no objections with 7.8.5. Cheers, Nicklas On Friday, 4 December 2020, 11:48:20 CET, Markus Neteler wrote: Hi devs, As some urgent fixes have been accumulated, let's prepare the GRASS GIS 7.8.5 release. This is the 7.8.5 milestone in GH: https:/