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

[Michael Barton]

I agree with Nicklas and others that with this one fix, we should move to get 
8.3.1 out ASAP. The bugs that have been fixed were pretty important.

Michael
_

C. Michael Barton
Associate Director, School of Complex Adaptive Systems 
(https://scas.asu.edu)
Professor, School of Human Evolution & Social Change (https://shesc.asu.edu)
Director, Center for Social Dynamics & Complexity (https://complexity.asu.edu)
Arizona State University
Tempe, AZ 85287-2701
USA

Executive Director, Open Modeling Foundation 
(https://openmodelingfoundation.github.io)
Director, Network for Computational Modeling in Social & Ecological Sciences 
(https://comses.net)

personal website: http://www.public.asu.edu/~cmbarton


On Sep 20, 2023, at 8:31 AM, grass-dev-requ...@lists.osgeo.org wrote:

Hi devs,

While 8.3.0 has been released rather recently, an important bug showed up:
- r.watershed: fix streams and basins #3140

Unfortunately r.watershed is partially broken in 8.3.0 such that
streams and basins are no longer correctly calculated. This has been
now been fixed.

Given the importance of r.watershed, I suggest an anticipated release of 8.3.1

Here the milestone:
https://urldefense.com/v3/__https://github.com/OSGeo/grass/milestone/21__;!!IKRxdwAv5BmarQ!fLNgMOj4R48qCK_rC-_C49VxOueIHMI_NzYdWT9wXABdmOLhooK0aiKOQgs95YJ69CsoZqyA8P_pdZu-0XGBWK19Bm__SCwlQrg$

What do you think?

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

[Nicklas Larsson via grass-dev]

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
 



N.

> On 20 Sep 2023, at 17:14, Newcomb, Doug  wrote:
> 
> I wouldn't mind seeing the fix to g.extension for Windows that just went in, 
> so you can load addons  on Windows in 8.3.x 
> https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938 
>  
>     
> g.extension: fix installing addons on the OS MS Windows by tmszi · Pull 
> Request #3166 · OSGeo/grass 
> 
> Fixes #3077. Fix installing addons via g.extension module on the OS MS 
> Windows without dependency on Git program. Gettings official GitHub addons 
> repository branches g.extension -l is based on the ...
> github.com 
> 
> From: grass-dev  > 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...@osgeo.org>>
> Cc: GRASS developers list  >
> Subject: [EXTERNAL] Re: [GRASS-dev] [release planning] GRASS GIS 8.3.1
>  
>  
>  This email has been received from outside of DOI - Use caution before 
> clicking on links, opening attachments, or responding.  
> 
> 
> 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
>  
> 
> 
> 
> Best,
> Nicklas
> 
> 
>> On 19 Sep 2023, at 21:33, Markus Neteler > > wrote:
>> 
>> Any other opinions?
>> What about the Windows g.extension git story, to be added to 8.3.1?
>> 
>> Markus
>> 
>> On Mon, Sep 11, 2023 at 1:48 PM Newcomb, Doug > > wrote:
>>> 
>>> This is an important function of GRASS. I think it would be wise to rectify 
>>> the issue as soon as possible
>>> 
>>> 
>>> From: grass-dev >> > on behalf of Markus Neteler 
>>> mailto:nete...@osgeo.org>>
>>> Sent: Monday, September 11, 2023 6:26 AM
>>> To: GRASS developers list >> >
>>> Subject: [EXTERNAL] [GRASS-dev] [release planning] GRASS GIS 8.3.1
>>> 
>>> Hi devs,
>>> 
>>> While 8.3.0 has been released rather recently, an important bug showed up:
>>> - r.watershed: fix streams and basins #3140
>>> 
>>> Unfortunately r.watershed is partially broken in 8.3.0 such that
>>> streams and basins are no longer correctly calculated. This has been
>>> now been fixed.
>>> 
>>> Given the importance of r.watershed, I suggest an anticipated release of 
>>> 8.3.1
>>> 
>>> Here the milestone:
>>> https://github.com/OSGeo/grass/milestone/21 
>>> 
>>> 
>>> What do you think?
>>> 
>>> Markus
>>> ___
>>> grass-dev mailing list
>>> grass-dev@lists.osgeo.org
>> ___
>> 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] Re: [release planning] GRASS GIS 8.3.1

[Newcomb, Doug via grass-dev]

I wouldn't mind seeing the fix to g.extension for Windows that just went in, so 
you can load addons  on Windows in 8.3.x 
https://github.com/OSGeo/grass/pull/3166#issuecomment-1727462938
[https://opengraph.githubassets.com/f9d53daef25fcfb526eac15d1abc3b2f3aab12de75e83651422088b0bd791720/OSGeo/grass/pull/3166]
g.extension: fix installing addons on the OS MS Windows by tmszi · Pull Request 
#3166 · 
OSGeo/grass
Fixes #3077. Fix installing addons via g.extension module on the OS MS Windows 
without dependency on Git program. Gettings official GitHub addons repository 
branches g.extension -l is based on the ...
github.com


From: grass-dev  on behalf of Nicklas 
Larsson via grass-dev 
Sent: Wednesday, September 20, 2023 4:14 AM
To: Markus Neteler 
Cc: GRASS developers list 
Subject: [EXTERNAL] Re: [GRASS-dev] [release planning] GRASS GIS 8.3.1




 This email has been received from outside of DOI - Use caution before clicking 
on links, opening attachments, or responding.



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


Best,
Nicklas


On 19 Sep 2023, at 21:33, Markus Neteler 
mailto:nete...@osgeo.org>> wrote:

Any other opinions?
What about the Windows g.extension git story, to be added to 8.3.1?

Markus

On Mon, Sep 11, 2023 at 1:48 PM Newcomb, Doug 
mailto:doug_newc...@fws.gov>> wrote:

This is an important function of GRASS. I think it would be wise to rectify the 
issue as soon as possible


From: grass-dev 
mailto:grass-dev-boun...@lists.osgeo.org>> 
on behalf of Markus Neteler mailto:nete...@osgeo.org>>
Sent: Monday, September 11, 2023 6:26 AM
To: GRASS developers list 
mailto:grass-dev@lists.osgeo.org>>
Subject: [EXTERNAL] [GRASS-dev] [release planning] GRASS GIS 8.3.1

Hi devs,

While 8.3.0 has been released rather recently, an important bug showed up:
- r.watershed: fix streams and basins #3140

Unfortunately r.watershed is partially broken in 8.3.0 such that
streams and basins are no longer correctly calculated. This has been
now been fixed.

Given the importance of r.watershed, I suggest an anticipated release of 8.3.1

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

What do you think?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
___
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] [release planning] GRASS GIS 8.3.1

[Nicklas Larsson via grass-dev]

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
 



Best,
Nicklas


> On 19 Sep 2023, at 21:33, Markus Neteler  wrote:
> 
> Any other opinions?
> What about the Windows g.extension git story, to be added to 8.3.1?
> 
> Markus
> 
> On Mon, Sep 11, 2023 at 1:48 PM Newcomb, Doug  wrote:
>> 
>> This is an important function of GRASS. I think it would be wise to rectify 
>> the issue as soon as possible
>> 
>> 
>> From: grass-dev  on behalf of Markus 
>> Neteler 
>> Sent: Monday, September 11, 2023 6:26 AM
>> To: GRASS developers list 
>> Subject: [EXTERNAL] [GRASS-dev] [release planning] GRASS GIS 8.3.1
>> 
>> Hi devs,
>> 
>> While 8.3.0 has been released rather recently, an important bug showed up:
>> - r.watershed: fix streams and basins #3140
>> 
>> Unfortunately r.watershed is partially broken in 8.3.0 such that
>> streams and basins are no longer correctly calculated. This has been
>> now been fixed.
>> 
>> Given the importance of r.watershed, I suggest an anticipated release of 
>> 8.3.1
>> 
>> Here the milestone:
>> https://github.com/OSGeo/grass/milestone/21
>> 
>> What do you think?
>> 
>> Markus
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
> ___
> 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] GRASS GIS for Apple Silicon Macs

[Nicklas Larsson via grass-dev]

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 12 is a universal binary. Perhaps something did change with this 
command, please test the following:

`file /usr/bin/osascript` 

and

`osascript -i`

(which should enter interactive mode, you may exit with Ctrl-C).


You could also try start GRASS manually from Terminal:

`/Applications/GRASS-8.3.app/Contents/MacOS/Grass.sh`

(That step may, however, be prevented because of the app being unsigned).



For control, the FreeCAD shell script contains the following command:

`sw_vers -productVersion`

Could you try that? ’sw_vers' is also a universal binary on macOS 12. What will 
the following give:

`file /usr/bin/sw_vers`


Best,
Nicklas




> On 19 Sep 2023, at 20:54, Michael Barton  wrote:
> 
> I've been corresponding with this GRASS user about how the software works 
> with the new Apple ARM processors. Nicklas and I have compiled GRASS for ARM 
> processors successfully. These are posted on the GRASS for Mac site 
> (https://cmbarton.github.io/grass-mac/). When Gregor tries to launch GRASS 
> under the new MacOS 14 (Sonoma) he gets a notice that Rosetta (Intel 
> processor emulator) is needed. They launch on my ARM MacBook Pro with no 
> notice, but I am not using Sonoma yet. 
> 
> Does anyone have any suggestions about what might be triggering this notice 
> at launch time? AFAIK, initialization only calls the following:
> 1. shell launch script
> 2. wxPython
> 3. Python
> 
> Is there any other module or dependency that gets called at initial launch 
> (no maps displayed)? 
> 
> Michael
> _
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
> 
> Executive Director, Open Modeling Foundation 
> (https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological Sciences 
> (https://comses.net)
> 
> personal website: http://www.public.asu.edu/~cmbarton 
> 
> 
>> Begin forwarded message:
>> 
>> From: Gregor Hintner 
>> Subject: Re: GRASS GIS for Apple Silicon Macs
>> Date: September 18, 2023 at 11:34:02 AM MST
>> To: Michael Barton 
>> 
>> Unfortunately I suspect we have had another miscommunication. 
>> Let me list the specific steps that lead to the Rosetta prompt: 
>> - Download GRASS 8.3.0 Apple ARM or GRASS 8.4dev from your webpage
>> - mount either downloaded Diskimage
>> - copy the GRASS application file from the mounted DMG to the Applications 
>> folder
>> - double click and launch the GRASS application
>> - macOS shows a prompt to install Rosetta to continue
>> 
>> Obviously the prompt only appears when actually launching GRASS, the launch 
>> just never progresses past it, and no console or GUI can appear.
>> 
>> To my eyes the OS behavior seems credible in this case, though I obviously 
>> have no insights beyond the regular UI level.
>> 
>> Could you send me an email contact to the GRASS dev list. I frankly never 
>> understood how these lists work, I assume some kind of e-mail chain, but I 
>> noticed no actual e-mail addresses on the main GRASS webpage, only on your 
>> Mac distribution site.
>> 
>> 
>> Thanks, 
>> Gregor
>> 
>> 
>>> On 2023-09-18, at 8:20 PM, Michael Barton  wrote:
>>> 
>>>  Gregor, 
>>> 
>>> I lean toward this being a bug in the beta at the moment. The reason is 
>>> that installing GRASS should not raise a Rosetta request, at least until 
>>> you run GRASS. This is because GRASS is organized as a set of independent 
>>> modules, overlayed with an optional GUI. Running GRASS invokes a shell 
>>> script (that should not require Rosestta, since it launches an ARM 
>>> terminal) and than the GUI in Python 3 and wxPython. But these should also 
>>> be ARM compatible. It is possible that one or more of the >300 individual 
>>> modules or dependencies require Rosetta. But these should not call Rosetta 
>>> until they are launched. Also, they are mostly in C and Python, with some 
>>> C++ code--all of which was compiled under ARM tools. You might post this 
>>> question to the GRASS dev list. It is hard to say what is causing this 
>>> message to appear in your beta when nothing is launched. 
>>> 
>>> Michael
>>> _
>>> C. Michael Barton
>>> Associate Director, School of Complex Adaptive Systems 
>>> (https://scas.asu.edu)
>>> Professor, School of Human Evolution & Social Change (https://shesc.asu.edu)
>>> Director, Center for Social Dynamics & Complexity 
>>> (https://complexity.asu.edu)
>>> Arizona State University
>>>