Re: [release planning] GRASS GIS 8.4.1

Hi devs,

(let’s see if this email reaches discourse, my last apparently one didn’t…)

We are well past the planned release date for the upcoming 8.4.1 release.
So I plan to release RC1 in the next days.

On Mon, Nov 4, 2024 at 11:41 PM Markus Neteler neteler@osgeo.org wrote:

Pull requests · OSGeo/grass · GitHub

One open PR for 8.4.1 is pending.

Open issues: we still have numerous open issues - see list (please
help cleaning it up!):

And here the 8.4.1 milestone (open issues and pull requests together):

What doesn’t make it into 8.4.1 will be bumped to 8.4.2.

Markus


Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog

As we are waaaay overdue the planned release date, may I suggest to bump them all to 8.4.2. If someone will address any of them in these few days they will be able to anyway.

Nicklas

On 6 Feb 2025, at 10:05, Markus Neteler via OSGeo Discourse noreply@discourse.osgeo.org wrote:

neteler
February 6

Hi devs,

(let’s see if this email reaches discourse, my last apparently one didn’t…)

We are well past the planned release date for the upcoming 8.4.1 release.
So I plan to release RC1 in the next days.

On Mon, Nov 4, 2024 at 11:41 PM Markus Neteler neteler@osgeo.org wrote:

Pull requests · OSGeo/grass · GitHub

One open PR for 8.4.1 is pending.

Open issues: we still have numerous open issues - see list (please
help cleaning it up!):

GitHub

OSGeo/grass

GRASS GIS - free and open-source geospatial processing engine - OSGeo/grass

And here the 8.4.1 milestone (open issues and pull requests together):

GitHub

8.4.1 Milestone · OSGeo/grass

GRASS GIS - free and open-source geospatial processing engine - 8.4.1 Milestone · OSGeo/grass

What doesn’t make it into 8.4.1 will be bumped to 8.4.2.

Markus


Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

+1

In archlinux based distribution system, python package has already switched to 3.13 so Grass 8.4.0 doesn’t work anymore. A commit in 8.4.1 solves the issue.

GRASS GIS 8.4.1RC1 has been released!

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

Please test it!

2 Likes

Markus, please upload https://github.com/OSGeo/grass/releases/download/8.4.1RC1/grass-8.4.1RC1.tar.gz to the OSGeo server.

On 10 Feb 2025, at 17:43, Markus Neteler via OSGeo Discourse noreply@discourse.osgeo.org wrote:

neteler
February 10

GRASS GIS 8.4.1RC1 has been released!

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

GitHub

Release GRASS GIS 8.4.1RC1 · OSGeo/grass

The GRASS GIS 8.4.1RC1 release provides more than 70 improvements and fixes with respect to the release 8.4.0. Highlights r.sim.water: tool and its documentation received various updates GUI: stab…

Please test it!


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Nicklas,

I have access to the OSGEO download server for Mac and can upload the binary if you give me a link.

Great Michael, they will be ready tomorrow, will send you the links.

On 10 Feb 2025, at 20:52, Michael Barton via OSGeo Discourse noreply@discourse.osgeo.org wrote:

cmbarton
February 10

Nicklas,

I have access to the OSGEO download server for Mac and can upload the binary if you give me a link.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

1 Like

Dear all,

po 10. 2. 2025 v 21:03 odesílatel Nicklas Larsson via OSGeo Discourse <noreply@discourse.osgeo.org> napsal:

Windows standalone installer uploaded for testing [1]. In order to build binaries [2] has been locally applied (would be nice to have only one script for compilation - either build_osgeo4w.sh or package.sh).

Martin

[1] https://grass.osgeo.org/grass84/binary/mswindows/native/WinGRASS-8.4.1RC1-1-Setup.exe
[2] https://github.com/OSGeo/grass/pull/5084

Nicklas, I did upload the files as per the release procedure:

Edit: apologize, there was a bug. Now really uploaded:

Please check again.

Sorry for the confusion.

Now I see it. It does miss the generated file include/VERSION_GIT, as per:

https://github.com/OSGeo/grass/blob/be43b744ebf6b35b685f771b0f2911d18b658b5d/.github/workflows/create_release_draft.yml#L52

Wouldn’t it be better to just transfer the CI created tarball at: https://github.com/OSGeo/grass/releases/download/8.4.1RC1/grass-8.4.1RC1.tar.gz ?

On 11 Feb 2025, at 16:21, Markus Neteler via OSGeo Discourse noreply@discourse.osgeo.org wrote:

neteler
February 11

nila:

Markus, please upload https://github.com/OSGeo/grass/releases/download/8.4.1RC1/grass-8.4.1RC1.tar.gz to the OSGeo server.

Nicklas, I did upload the files as per the release procedure:

Is anything missing there?


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

1 Like

Yeah, I would so much appreciate more automation here (certainly keeping system security in mind).

And less tedious as well as error prone. We might still upload it (and switch) manually…

8.4.1RC1 Mac binaries posted and available on my site and OSGEO download server for Mac binaries. Thanks Nicklas for creating the signed binaries.

Seems nothing really bad happened, so I’ll prepare GRASS GIS 8.4.1RC2 asap.

Changes after RC1:

  • docker: gdal-grass autoconf workaround (G84) (#5123)
  • ci: Remove Travis-CI (backport)
  • Windows: Fix package.sh: there is no SRC variable (#5084)

I’ll try out the updated doc/howto_release.md, see draft PR.

Did you want the docker workflow (GitHub actions, not Dockerfiles) changes to be there so it could be correctly published as latest and current on release?

As I am unable to do the backport myself I skipped it for now.

There is no actual need for that. The latest gdal-grass is included.

The RC2 preparation fails:

macOS build:

Any ideas?

(I have rolled back the version file to 8.4.1dev)

There seems to be some problem with latest SQLite 3.49.1. (released three days ago) v.db.select and t.unregister fails with SQLite related error. E.g.,

The subprocess ended with a non-zero return code: 1. See the following errors:
DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such column: "Joan's Place" - should this be a string literal in single-quotes?

DBMI-SQLite driver error:
Error in sqlite3_prepare():
no such column: "Joan's Place" - should this be a string literal in single-quotes?

ERROR: Error while executing: 'UPDATE points SET place_name="Joan's Place" WHERE owner_id = 5'
Traceback (most recent call last):
  File "scripts/v.db.update", line 139, in <module>
    sys.exit(main())
             ^^^^^^
  File "scripts/v.db.update", line 127, in main
    grass.write_command(
  File "etc/python/grass/script/core.py", line 654, in write_command
    return handle_errors(returncode, None, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "etc/python/grass/script/core.py", line 366, in handle_errors
    raise CalledModuleError(module=module, code=code, returncode=returncode)
grass.exceptions.CalledModuleError: Module run `db.execute input=- database=/Users/runner/nc_spm_full_v2alpha2/__vector_v_db_select_test_v_db_select_json_csv_Mac_1740155367276_local_26656/sqlite/sqlite.db driver=sqlite` ended with an error.

But I can’t reproduce this locally with same version of SQLite.