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=5=8=17=0=0=207=48=51=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 
> > <https://grass.osgeo.org/grass83/manuals/addons/> 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 
> <https://grass.osgeo.org/grass83/manuals/addons/> 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 

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: <https://trac.osgeo.org/osgeo/ticket/2966#comment:5>
> OSGeo <https://osgeo.org/>
> 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

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

[Markus Neteler]

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

Re: [GRASS-dev] How to reformat markdown to pass pre-commit?

[Markus Neteler]

On Thu, Sep 14, 2023 at 5:42 AM Vaclav Petras  wrote:
> On Wed, 13 Sept 2023 at 15:13, Markus Neteler  wrote:
>>
>> Hi,
>>
>> I have updated doc/infrastructure.md in my local Git copy and fail to
>> commit it in a new PR due to pre-commit linting checks:
>>
>> markdownlint.Failed
>> ...
>>
>> I tried to use `mdformat` on the file but the result isn't compatible
>> with markdownlint.
>>
>> Is there any other tool to auto-format the file (even a 90% solution is 
>> fine)?
>
>
> I used these two in the past with GRASS GIS:
>
> npx markdownlint-cli --fix  doc/infrastructure.md
> npx prettier --print-width 80 -w  doc/infrastructure.md
>
> I don't remember exactly, but I guess at least one worked okay.

Nice, the second one does the job tp 95%.

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

[GRASS-dev] How to reformat markdown to pass pre-commit?

[Markus Neteler]

Hi,

I have updated doc/infrastructure.md in my local Git copy and fail to
commit it in a new PR due to pre-commit linting checks:

markdownlint.Failed
- hook id: markdownlint
- exit code: 1

doc/infrastructure.md:33:81 MD013/line-length Line length [Expected:
80; Actual: 107]
doc/infrastructure.md:34:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:54:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:55:1 MD007/ul-indent Unordered list indentation
[Expected: 4; Actual: 8]
...
doc/infrastructure.md:148:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 5]
doc/infrastructure.md:148:81 MD013/line-length Line length [Expected:
80; Actual: 90]
doc/infrastructure.md:149:81 MD013/line-length Line length [Expected:
80; Actual: 120]
doc/infrastructure.md:151:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 5]
doc/infrastructure.md:152:81 MD013/line-length Line length [Expected:
80; Actual: 153]
doc/infrastructure.md:177:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:178:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:179:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:180:1 MD007/ul-indent Unordered list indentation
[Expected: 2; Actual: 4]
doc/infrastructure.md:232:33 MD034/no-bare-urls Bare URL used
[Context: "https://github.com/OSGeo/grass...;]
...

I tried to use `mdformat` on the file but the result isn't compatible
with markdownlint.

Is there any other tool to auto-format the file (even a 90% solution is fine)?

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

[GRASS-dev] Fwd: [GRASS-web] Inclusion of your Website in the Library of Congress Web Archives

[Markus Neteler]

FYI!

-- Forwarded message -
From: Webcapture [Library of Congress] 
Date: Tue, Sep 12, 2023 at 6:20 PM
Subject: [GRASS-web] Inclusion of your Website in the Library of Congress
Web Archives
To: 

To Whom It May Concern:

The United States Library of Congress has selected your website for
inclusion in the Geospatial Software and File Formats Web Archive, which is
part of a larger collection of historically and culturally significant
websites that have been designated for preservation. The following URL has
been selected: https://grass.osgeo.org/.

The Library of Congress or its agent will engage in the collection of
content from your website at regular intervals over time. In order to
properly archive the above URL, we may archive other portions of the
website and public content that your page links to on third party sites
such as social media platforms. In addition to the aforementioned
collection, archived content from your website may be added to other
relevant collections in the future. This content will be available to
researchers at Library facilities and by special arrangement. It may also
become more broadly available through hosting on the Library’s public
website, which would be done no sooner than one year after it was
collected. For more information on the web archiving process, please read
our frequently asked questions

.

The Library hopes that you share its vision of preserving digital content
and making it available to current and future generations of researchers.
As the internet has become an increasingly important and influential part
of our lives, we believe the historical record would be incomplete if
websites like yours are not preserved and made a part of it. We encourage
you to learn more about the Library’s Web Archiving program
 and explore our collections
 to see examples of how we archive
websites. If you have any questions, comments, or recommendations
concerning the archiving of your website, please email the Library's Web
Archiving Team at webcapt...@loc.gov.

Thank you.

*Library of Congress Web Archiving Team*
webcapt...@loc.gov
[image: Library of Congress logo]

___
grass-web mailing list
grass-...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-web
___
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.1

[Markus Neteler]

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
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Send GRASS news to mailing list

[Markus Neteler]

Vaclav Petras  schrieb am Fr., 1. Sep. 2023, 16:45:

> I just realized this would also be a good match for the grass-announce
> mailing list. To cross-post or not to cross-post?
>

Yes, cross-post.

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

Re: [GRASS-dev] Send GRASS news to mailing list

[Markus Neteler]

Hi Vaclav,

Just a hint: the email limit can be lifted easily. Just post and I (or any
other list admin) can approve it.

Markus


Vaclav Petras  schrieb am Fr., 1. Sep. 2023, 14:53:

> Dear all,
>
> Having the very nice post about the meeting in Prague and others at the
> GRASS website, I was thinking we should send this to the grass-user mailing
> list too and maybe grass-dev.
>
> Given the mailing list emails have size limitations and may end up
> potentially ASCII, I'm suggesting sending an email with a link to the new
> item and the first paragraph of the news item to the grass-user mailing
> list. So, the one for Prague, would look like this:
>
> 
> Report of the GRASS GIS Community Meeting in Prague
>
> The GRASS GIS Community Meeting was held in the Czech Republic from June 2
> to 6 at the Faculty of Civil Engineering of the Czech Technical University
> in Prague. The meeting was a milestone event to celebrate the 40th birthday
> of GRASS GIS and brought together users, supporters, contributors, power
> users and developers to celebrate, collaborate and chart the future of
> GRASS GIS.
>
> Read more at:
>
>
> https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/
> """
>
> What do you think?
>
> Vaclav
> ___
> 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: screenshots of old GRASS

[Markus Neteler]

On Tue, Jul 11, 2023 at 2:00 PM Newcomb, Doug via grass-dev
 wrote:
>
> Screenshots from the Shatner video?  https://youtu.be/cZia3ShzTWM

Please see the reconstructed *original* video for a much better quality:

Original GRASS GIS Video from 1987 with William Shatner (Speaker):
https://doi.org/10.5446/12963

The story behind:

- GRASS GIS, Star Trek and old Video Tape.
  P. Löwe, J. Neumann, M. Plank, F. Ziedorn, R. Lozar, J. Westervelt
and R Inman.
  OSGeo Journal Volume 14.
  
https://oa.tib.eu/renate/backend/api/core/bitstreams/1304be91-c087-4ff5-ba11-d9de08e3664a/content

- Presentation at FOSSGIS 2014:
  https://av.tib.eu/media/31768

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

[GRASS-dev] GRASS GIS 7.8.8 released

[Markus Neteler]

The new GRASS GIS 7.8.8 release provides more than 80 improvements and
fixes compared to the 7.8.7 release.

For details see
https://github.com/OSGeo/grass/releases/tag/7.8.8

Binary packages are ready for download at
https://grass.osgeo.org/news/2023_08_06_grass_gis_7_8_8_released

NOTE: This release is expected to be the last 7.8 release.
Development continues with GRASS GIS 8.x.

Thanks to all contributors!

Happily,
GRASS Development Team
___
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]

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 would be needed, otherwise it won't "join" the other releases
stored there under the meta DOI.

Vaclav or Vero perhaps?

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]

On Wed, Aug 16, 2023 at 8:31 AM Peter Löwe  wrote:
>
> Hi Markus,
>
> Zenodo says that another release by the GRASS project is necessary to 
> retrieve the changes.

Well, so that sounds like manual upload if we want to see 8.3.0 there.

> Maybe a "minor technical maintenance" release could be considered ?

That would be 8.3.1 then, right? ... planned for Oct. 2023:
https://github.com/OSGeo/grass/milestone/21

Best,
Markus

> Other projects did such minor relase to obtain a DOI for the references in 
> the Handbook of Geographic
> Information, since the publication deadlines were not in synch with the 
> release cycles of the projects.
>
> Best,
> Peter
___
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]

Hi Peter,

On Mon, Aug 14, 2023 at 2:50 PM Markus Neteler  wrote:
>
> Hi Peter,
>
> On Mon, Aug 14, 2023 at 1:23 PM Peter Löwe  wrote:
> >
> > Vacek, Markus, all,
> >
> > according to the Zenodo helpdesk there are still issues with the CFF file 
> > of GRASS GIS 8.3:
>
> Ok, got it. And fixed:
>
> https://github.com/OSGeo/grass/pull/3123

Merged. The updated CITATION.cff is now in place in GitHub (main, 8.3,
8.2 branches).

For our case:
https://github.com/OSGeo/grass/blob/releasebranch_8_3/CITATION.cff

May the Zenodo helpdesk try again?

Best,
Markus


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

Re: [GRASS-dev] proj versions question

[Markus Neteler]

On Mon, Aug 14, 2023 at 8:06 PM Michael Barton  wrote:
>
> Which versions of proj are being used and required for GRASS 7.8.8 and 8.3.0?

I think any PROJ version 5+ is fine. But 7+ might be better (I am using PROJ 9).

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]

Hi Peter,

On Mon, Aug 14, 2023 at 1:23 PM Peter Löwe  wrote:
>
> Vacek, Markus, all,
>
> according to the Zenodo helpdesk there are still issues with the CFF file of 
> GRASS GIS 8.3:

Ok, got it. And fixed:

https://github.com/OSGeo/grass/pull/3123

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]

Hi Peter,

On Tue, Aug 8, 2023 at 5:04 PM Peter Löwe  wrote:
>
> Hi Markus,
> the licence ID for GRASS GIS 7.8.8. on its landing page reads:
> "Other (Open)"

I have seen it, too. Unfortunately not the precise licence description.

> This setting goes back to GRASS GIS 7.8.6.
> Since this is (just) landing page metadata, this can be changed after the 
> minting of the DOI and the file upload into Zenodo.
>
> The landing page for GRASS GIS 8.2.0 (https://zenodo.org/record/6612307) has 
> different licence metadata: "GNU General Public License v2.0 or later", which 
> points to https://opensource.org/license/gpl-2-0/
>
> Did GRASS GIS 8.2.0 get maybe manually checked into Zenodo ?

I am not aware that anyone manually uploaded a GRASS GIS release to Zenodo.

> Otherwise this could be a Zenodo-sided bug ("worked before")..?

Probably they treated non-SPDX conformant license identifiers (here:
"GPL-2.0-or-later") differently?
Just guessing: In the past they changed it to "Other (Open)" and now
it is (randomly) failing?

Anyway, we now have updated the CITATION.cff with the correct SPDX
license identifier "GPL-2.0-or-later" in GRASS GIS 8.x.

It would be cool if Zenodo helpdesk could retrigger the 8.3.0 upload.

Best,
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]

On Tue, Aug 8, 2023 at 2:10 PM Markus Neteler  wrote:
> On Tue, Aug 8, 2023 at 1:03 PM Sebastiaan Couwenberg  
> wrote:
> > On 8/8/23 12:33, Markus Neteler wrote:
> > > In detail:
> > >
> > > 8.3.0 OSGeo/grass: GRASS GIS 8.3.0
> > > GRASS GIS 8.3.0
> > > Failed
> > >
> > > {
> > >  "errors": "The license ID you have selected is not present in our
> > > system. For the available licenses please check in the following URL
> > > https://developers.zenodo.org/#licenses;
> > > }
> > >
> > > https://github.com/OSGeo/grass/blob/4428fae82aba5e9033bae7ea4ba84da914949602/CITATION.cff#L109
> > > --> license: GNU General Public License v2 or later
> > >
> > > I guess it dislikes the "... or later" part. How to write it properly?
> >
> > Perhaps it supports SPDX license identifiers: GPL-2.0-or-later
>
> Yes, that will be the proper wording.
>
> > https://spdx.org/licenses/
>
> https://spdx.org/licenses/GPL-2.0-or-later.html
>
> I'll open a PR for this.

https://github.com/OSGeo/grass/pull/3115

Thanks
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.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]

On Tue, Aug 8, 2023 at 1:03 PM Sebastiaan Couwenberg  wrote:
> On 8/8/23 12:33, Markus Neteler wrote:
> > In detail:
> >
> > 8.3.0 OSGeo/grass: GRASS GIS 8.3.0
> > GRASS GIS 8.3.0
> > Failed
> >
> > {
> >  "errors": "The license ID you have selected is not present in our
> > system. For the available licenses please check in the following URL
> > https://developers.zenodo.org/#licenses;
> > }
> >
> > https://github.com/OSGeo/grass/blob/4428fae82aba5e9033bae7ea4ba84da914949602/CITATION.cff#L109
> > --> license: GNU General Public License v2 or later
> >
> > I guess it dislikes the "... or later" part. How to write it properly?
>
> Perhaps it supports SPDX license identifiers: GPL-2.0-or-later

Yes, that will be the proper wording.

> https://spdx.org/licenses/

https://spdx.org/licenses/GPL-2.0-or-later.html

I'll open a PR for this.

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]

HI Peter,

On Tue, Aug 8, 2023 at 11:24 AM Peter Löwe  wrote:
>
> Hi Markus, all,
>
> would it be feasible for the maintainers to do a manual Zenodo-check-in for 
> GRASS GIS 8.3 similar  to GRASS GIS 7.8.8 ?

Well, the Zenodo part of 7.8.8 was automated.

> Alternatively I can contact the Zenodo helpdesk to get this fixed.

Hold on - I just checked it here:

https://zenodo.org/account/settings/github/repository/OSGeo/grass

7.8.8 OSGeo/grass: GRASS GIS 7.8.8
DOI: 10.5281/zenodo.8219486
GRASS GIS 7.8.8
Published
a day ago


8.3.0 OSGeo/grass: GRASS GIS 8.3.0
GRASS GIS 8.3.0
Failed<<<<- !
a month ago


8.3.0RC1 OSGeo/grass: GRASS GIS 8.3.0RC1
GRASS GIS 8.3.0RC1
Failed
2 months ago


8.2.1 OSGeo/grass: GRASS GIS 8.2.1
DOI: 10.5281/zenodo.7764250
GRASS GIS 8.2.1
Published
4 months ago


...

In detail:

8.3.0 OSGeo/grass: GRASS GIS 8.3.0
GRASS GIS 8.3.0
Failed

{
"errors": "The license ID you have selected is not present in our
system. For the available licenses please check in the following URL
https://developers.zenodo.org/#licenses;
}

https://github.com/OSGeo/grass/blob/4428fae82aba5e9033bae7ea4ba84da914949602/CITATION.cff#L109
--> license: GNU General Public License v2 or later

I guess it dislikes the "... or later" part. How to write it properly?

Best,
Markus

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.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]

Hi Peter, all,

On Tue, Aug 8, 2023 at 9:37 AM Peter Löwe  wrote:
>
> Hi Markus, all,
>
> FWIW; the DOI minting _did_ work as expected for GRASS 7.8.8 on August 6: 
> https://zenodo.org/record/8219486

Ok, that's good. I released it using the manual way of doing things.

> > On Mon, Aug 7, 2023 at 4:47 PM Peter Löwe  wrote:
> > > I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't 
> > > received a version DOI in Zenodo yet.
...
> > > This is weird since the Zenodo - GitHub hookup used to be / is automated.

For GRASS GIS 8 we use the scripted/semi-automated way. However, I
don't see why this should behave differently towards Zenodo.

Best,
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]

On Mon, Aug 7, 2023 at 4:47 PM Peter Löwe  wrote:
>
> Hello List,
>
> I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't 
> received a version DOI in Zenodo yet.
> The latest version DOIs were minted for 7.8.8. and 8.2.1:
> https://zenodo.org/search?page=1=20=conceptrecid:%225176030%22=mostrecent_versions=True
>
> This is weird since the Zenodo - GitHub hookup used to be / is automated.

Oh, too bad.

> Ideas, anyone ?

Maybe the "bridge" is broken again?
Does it still work for others, e.g. GDAL?

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 7.8.8

[Markus Neteler]

Hi devs,

GRASS GIS 7.8.8 has been released:
https://github.com/OSGeo/grass/releases/tag/7.8.8

Thanks to all contributors!

Next we need the news article and as many as possible binary packages
before announcing it publicly.

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 7.8.8

[Markus Neteler]

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, Jun 16, 2022 at 2:13 PM Martin Landa  
> >>> wrote:
> >>>> Dear all,
> >>>>
> >>>> 7.8.8RC1 was released on May 14. There is one open issue [1]. Do we plan 
> >>>> to release 7.8.8 anyway?
> >>>
> >>> Yes, we do asap.
> >>
> >> Well, some months have passed...
> >
> > And even more :-)
> >
> >>>> [1] https://github.com/OSGeo/grass/milestone/14
> >
> > Meanwhile no more open issues or PRs related to 7.8.8.
> >
> > This are the latest additions after RC3:
> > https://github.com/OSGeo/grass/compare/7.8.8RC3...releasebranch_7_8
> >
> > Yet another RC or goto final?
>
> +1 for final

There is one blocker PR open (r.sun). May it be merged?

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

[GRASS-dev] OSGeo code sprint at Big Data from Space 2023, November, in Vienna

[Markus Neteler]

The Annual Code Sprint comes to Vienna (Austria)!
The OSGeo Community Sprint 2023 will be hosted by the Big Data from
Space 2023 (BiDS) event.

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) together with
the European Union Satellite Center (SatCen) and the Joint Research
Center (JRC), will take place at the Austria Center Vienna, and counts
with the support of the partners FFG, Austria in Space and the Federal
Ministry Republic of Austria.

Date: November 6 to 9, 2023
Time: 9:00am to 1:30pm each day

Details at:
https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023

A great occasion to meet in person!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Markus Neteler]

On Fri, Jun 30, 2023 at 12:14 PM Martin Landa  wrote:
> čt 29. 6. 2023 v 23:30 odesílatel Veronica Andreo  
> napsal:

>> Question to all: how much longer will we support the 7.8.x branch? We are 
>> already in 8.3, so people has 8.0.x and 8.2.x to update to, no?
>> Do we have any policy on this matter?( ops, meanwhile I realized I have to 
>> update the website... will do this weekend )

Keep in mind that several distros still ship 7.8 (incl. updates):
https://repology.org/project/grass/versions

Most distros have a do-not-upgrade from 7 to 8 policy, means a new
distro release is needed to see a major version accepted.

> There is no rule to my knowledge. I remember the idea to maintain the last 
> two release branches. Currently it means 82 and 83.
>
> I would assume that 7.8.8 is most probably the latest GRASS 7.8 release...

Sound good.

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 7.8.8

[Markus Neteler]

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. There is one open issue [1]. Do we plan 
> > > to release 7.8.8 anyway?
> >
> > Yes, we do asap.
>
> Well, some months have passed...

And even more :-)

> > > [1] https://github.com/OSGeo/grass/milestone/14

Meanwhile no more open issues or PRs related to 7.8.8.

This are the latest additions after RC3:
https://github.com/OSGeo/grass/compare/7.8.8RC3...releasebranch_7_8

Yet another RC or goto final?

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

[GRASS-dev] GRASS GIS 8.3.0 released

[Markus Neteler]

GRASS GIS 8.3.0 released

The GRASS GIS 8.3.0 release provides *more than 360 improvements and fixes*
with respect to the release 8.2.0.
Highlights

   - graphical user interface: single-window GUI is now the default
   - PyWPS export in GRASS GIS modeler
   - Improved Jupyter Notebooks integration
   - parallelization: more parallel C tools (openMP) and parallel Python
   tools
   - many fixes and improvements in GRASS GIS modules and graphical user
   interface (see below)
   - move translations from Transifex (thanks for your long-term support)
   to https://weblate.osgeo.org/projects/grass-gis/
   - move of docker images from mundialis organization to
   https://hub.docker.com/r/osgeo/grass-gis/
   - update of docker images
   - improvement of the automated release creation
   - major cleanup of C/C++ code: fix of almost all compiler warnings
   - C/C++ code: adoption of Clang-Format, indent most of C code accordingly
   - support for "pre-commit" in order to reduce unnecessary runs of the
   automated checks (GitHub Actions)
   - notable improvements in the code checking section (GitHub Actions)
   - activate renovatebot to automatically maintain GitHub Actions
   - we have nine new contributors!

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

*News article:*

https://grass.osgeo.org/news/2023_06_24_grass_gis_8_3_released/
___
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.0

[Markus Neteler]

Hi,

Nicklas Larsson  schrieb am Sa., 24. Juni 2023, 18:31:

>
> Perhaps  adding '-std=gnu++17’ to CXXFLAGS might solve it?
>


I have tried to address it differently, by updating done binder
dependencies:

https://github.com/OSGeo/grass/pull/3063

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.0

[Markus Neteler]

Hi,

Binder fails:

Error loading OSGeo/grass/8.3.0
...
configure ...
pdal error.

(don't have the precise error message right now).

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.0

[Markus Neteler]

Hi devs,

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

Before announcing it publicly we need winGRASS and other binaries +
release news etc as per doc/howto_release.md.

Congrats and 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] [release planning] GRASS GIS 8.3.0

[Markus Neteler]

On Fri, Jun 23, 2023 at 12:37 PM Martin Landa  wrote:
> pá 23. 6. 2023 v 12:33 odesílatel Markus Neteler  napsal:
>>
>> > For CI containers you can break the system packages as suggested.
>>
>> Like
>>
>> RUN pip3 install grass-session  --break-system-packages

Thanks. Debian dockerfile PR submitted:

https://github.com/OSGeo/grass/pull/3062

After success and backports I can resume the 8.3.0 release 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.3.0

[Markus Neteler]

On Fri, Jun 23, 2023 at 10:38 AM Sebastiaan Couwenberg
 wrote:
>
> On 6/23/23 10:31, Markus Neteler wrote:
> > diff --git a/docker/debian/Dockerfile b/docker/debian/Dockerfile
> > index 66134a2f67..d697738633 100644
> > --- a/docker/debian/Dockerfile
> > +++ b/docker/debian/Dockerfile
> > @@ -1,5 +1,5 @@
> >   FROM debian:stable
> > -# currently Debian 11
> > +# currently Debian 12
> >
> >   # docker run -it --rm debian:stable bash
> >   # apt-get update && apt-get install lsb-release -y && lsb_release -a
> > @@ -11,7 +11,7 @@ ENV DEBIAN_FRONTEND noninteractive
> >
> >   # define versions to be used (PDAL is not available on Debian, so we
> > compile it here)
> >   # https://github.com/PDAL/PDAL/releases
> > -ARG PDAL_VERSION=2.4.3
> > +ARG PDAL_VERSION=2.5.5
>
> There is no PDAL in bookworm:
>
>   https://tracker.debian.org/pkg/pdal

For that reason we  compile it when building the image:
https://github.com/OSGeo/grass/blob/51e962abbc1176211ad2c4cb7857a61a2b6d1c6f/docker/debian/Dockerfile#L104

> > STEP 48/59: RUN pip3 install grass-session
> > error: externally-managed-environment
> >
> > × This environment is externally managed
> > ╰─> To install Python packages system-wide, try apt install
> >  python3-xyz, where xyz is the package you are trying to
> >  install.
> >
> >  If you wish to install a non-Debian-packaged Python package,
> >  create a virtual environment using python3 -m venv path/to/venv.
> >  Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
> >  sure you have python3-full installed.
> >
> >  If you wish to install a non-Debian packaged Python application,
> >  it may be easiest to use pipx install xyz, which will manage a
> >  virtual environment for you. Make sure you have pipx installed.
> >
> >  See /usr/share/doc/python3.11/README.venv for more information.
> >
> > note: If you believe this is a mistake, please contact your Python
> > installation or OS distribution provider. You can override this, at
> > the risk of breaking your Python installation or OS, by passing
> > --break-system-packages.
> > hint: See PEP 668 for the detailed specification.
> > Error: building at STEP "RUN pip3 install grass-session": while
> > running runtime: exit status 1
> >
> > What is the best practice for Debian Dockerfiles here? A venv doesn't
> > make sense in this context.
>
> The best option is to package all Python modules and install those.

If anyone wants to take over - I have no time to package that.

> For CI containers you can break the system packages as suggested.

Like

RUN pip3 install grass-session  --break-system-packages

?

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.0

[Markus Neteler]

On Fri, Jun 23, 2023 at 6:26 AM Sebastiaan Couwenberg
 wrote:
>
> On 6/23/23 00:00, Markus Neteler wrote:
> > E: Unable to locate package libopenblas-base
>
> That package doesn't exist any more, it was transitional dummy package
> provided by openblas which has been removed in openblas (0.3.21+ds-1).
>
> > https://github.com/OSGeo/grass/actions/runs/5350453362/jobs/9703565807
> >
> > Confused,
> > Markus
> >
> > PS: Shall we ignore that?
>
> The Dockefiles need to be updated to no longer install this package in
> distribution release where it's not available.
>
> The package in Debian just installs libblas-dev.

I am trying to update the Debian Dockerfile:

diff --git a/docker/debian/Dockerfile b/docker/debian/Dockerfile
index 66134a2f67..d697738633 100644
--- a/docker/debian/Dockerfile
+++ b/docker/debian/Dockerfile
@@ -1,5 +1,5 @@
 FROM debian:stable
-# currently Debian 11
+# currently Debian 12

 # docker run -it --rm debian:stable bash
 # apt-get update && apt-get install lsb-release -y && lsb_release -a
@@ -11,7 +11,7 @@ ENV DEBIAN_FRONTEND noninteractive

 # define versions to be used (PDAL is not available on Debian, so we
compile it here)
 # https://github.com/PDAL/PDAL/releases
-ARG PDAL_VERSION=2.4.3
+ARG PDAL_VERSION=2.5.5

 SHELL ["/bin/bash", "-c"]

@@ -43,7 +43,6 @@ RUN apt-get update && apt-get upgrade -y && \
 libjsoncpp-dev \
 libnetcdf-dev \
 libncurses5-dev \
-libopenblas-base \
 libopenblas-dev \
 libopenjp2-7 \
 libopenjp2-7-dev \

So far it seems to be ok but then I get

...
STEP 45/59: RUN apt-get clean -y
--> 60d9dd420330
STEP 46/59: RUN rm -r /src/grass_build/.git
--> c9ea0db622e8
STEP 47/59: WORKDIR /scripts
--> 14099929847b
STEP 48/59: RUN pip3 install grass-session
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.

See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python
installation or OS distribution provider. You can override this, at
the risk of breaking your Python installation or OS, by passing
--break-system-packages.
hint: See PEP 668 for the detailed specification.
Error: building at STEP "RUN pip3 install grass-session": while
running runtime: exit status 1

What is the best practice for Debian Dockerfiles here? A venv doesn't
make sense in this context.

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.0

[Markus Neteler]

Hi devs,

Argh. I am half way (version file committed, but building of Debian
based Docker fails):

E: Unable to locate package libopenblas-base

https://github.com/OSGeo/grass/actions/runs/5350453362/jobs/9703565807

Confused,
Markus

PS: Shall we ignore that?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] shift raster when projecting

[Markus Neteler]

On Fri, Jun 16, 2023 at 7:39 AM Paulo van Breugel
 wrote:
>
> Dear all,
>
> I am trying to project a DSM raster layer from Belgium 
> (https://overheid.vlaanderen.be/en/producten-diensten/digital-elevation-model;
>  EPSG 31370 to EPSG 28992 (Amersfoort / RD New).
>
> The result is a DEM raster layer with the features shifted roughly 100 m as 
> compared to the same features in the AHN (Dutch DEM, 
> https://www.ahn.nl/ahn-4). See screenshot and code below.
>
> Reprojecting the same in QGIS using the warp function (gdalwarp) results in 
> the Belgium DSM layer to be fairly closely aligned to the Dutch one.
>
> I tried to set the bounds before, align to the target raster, and other 
> suggestions in the help file of r.proj, to no avail. Any idea what I might be 
> doing wrong?

Just guessing, maybe some geodetic datum file missing?

Maybe try this?

# https://proj.org/usage/environmentvars.html#envvar-PROJ_NETWORK
export PROJ_NETWORK=ON

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.0

[Markus Neteler]

Dear all,

On Thu, Jun 22, 2023 at 9:17 AM Martin Landa  wrote:
>
> Dear Markus, all,
>
> st 21. 6. 2023 v 23:14 odesílatel Markus Neteler  napsal:
>>
>> We are almost there:
>> https://github.com/OSGeo/grass/milestones/8.3.0
>
>
> I think we can go ahead and release 8.3.0. Thanks, Martin

OK, I'll try to do that later today.

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.0

[Markus Neteler]

Dear all,

We are almost there:
https://github.com/OSGeo/grass/milestones/8.3.0

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.0

[Markus Neteler]

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?

I ask because FOSS4G starts in the next days.

Markus



I encountered the error with window position already some time ago in
> https://github.com/OSGeo/grass/pull/2667#issuecomment-1426832765.
> The window position is still the same, exactly these (26,23), seems like
> an error in wxPython 4.2.0.
>
> Linda
>
___
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.0

[Markus Neteler]

On Tue, Jun 20, 2023 at 9:03 AM Sebastiaan Couwenberg
 wrote:
> On 6/20/23 08:46, Martin Landa wrote:
> > RC1 has been released 2 weeks ago. Is there anything missing in order to
> > release 8.3.0 (what be nice to do for FOSS4G).
>
> Was there no announcement for RC1?

Apologies, this fell off the radar due to heavy changes in the (now
automated) release management and travelling back from the Community
meeting.

I have just sent the G8.3.0RC1 announcement.

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

[GRASS-dev] Pre-release GRASS GIS 8.3.0RC1

[Markus Neteler]

GRASS GIS 8.3.0RC1 released

The *GRASS GIS 8.3.0RC1 release* provides more than *360* improvements and
fixes with respect to the release 8.2.0.
What's Changed Highlights

   - many fixes and improvements in GRASS GIS modules and graphical user
   interface (see below)
   - move translations from Transifex (thanks for your long-term support)
   to https://weblate.osgeo.org/projects/grass-gis/
   - update of docker images
   - move of docker images from mundialis organization to
   https://hub.docker.com/r/osgeo/grass-gis/
   - improvement of the automated release creation
   - C/C++ code: adoption of Clang-Format, indent most of C code accordingly
   - major cleanup of C/C++ code: fix of almost all compiler warnings
   - support for "pre-commit" in order to reduce unnecessary runs of the
   automated checks (GitHub Actions)
   - notable improvements in the code checking section (GitHub Actions)
   - activate renovatebot to automatically maintain GitHub Actions
   - we gained nine new contributors!

*Full Changelog*: 8.2.0...8.3.0RC1

—

This release has 5 assets:

   - ChangeLog.gz
   - core_modules_with_last_commit.json
   - core_modules_with_last_commit.patch
   - Source code (zip)
   - Source code (tar.gz)

Visit the release page
 to download them.
___
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.0

[Markus Neteler]

Dear Martin, all,

Martin Landa  schrieb am Di., 20. Juni 2023, 08:46:

> Dear Markus, all,
>
> st 17. 5. 2023 v 17:27 odesílatel Markus Neteler 
> napsal:
>
> RC1 has been released 2 weeks ago. Is there anything missing in order to
> release 8.3.0 (what be nice to do for FOSS4G).
>

Yes, let's release asap.
As there was no negative feedback, I'd suggest to release this week.
If there are no objections, I could do that eg later tonight.

Best,
Markus



> Best regards, Martin
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
___
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

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

[Markus Neteler]

Hi devs,

We merged remaining open PRs, so we are at 0 open PRs!

Today Vashek and I have created the new "releasebranch_8_3" in GitHub.
Means: we need to backport fixes from main as appropriate and setup
new cronjobs for grass.osgeo.org.

We are getting close to RC1!

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

[GRASS-dev] New releasebranch_8_3 has been created

[Markus Neteler]

Hi devs,

Vashek and I have created the new "releasebranch_8_3" in GitHub.
Means: we need to backport fixes from main as appropriate.

For the release planning, see the other email thread.

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

Re: [GRASS-dev] svn required for g.extension??

[Markus Neteler]

On Wed, Apr 19, 2023 at 12:23 AM Michael Barton  wrote:
>
> I was surprised to find that svn is required in order to use g.extension 
> since GRASS moved to GitHub many years back. The interface from the GUI seems 
> to lock up on launch. Maybe the lack of SVN is the reason?

It has been worked on just recently:

https://github.com/OSGeo/grass/pull/2895

In GRASS GIS 8.3.dev it is already merged, please test it.

Markus

> 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

-- 
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/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.0

[Markus Neteler]

On Thu, Mar 23, 2023 at 10:52 AM Markus Neteler  wrote:
> On Fri, Mar 17, 2023 at 11:41 AM Markus Neteler  wrote:
> > Markus Neteler  schrieb am Fr., 17. Feb. 2023, 19:24:
...

Remaining for the 8.3.0 milestone are (currently) 7 open pull requests
(PRs) which still need testing, review or bumping to 8.4:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.3.0

Importantly, we need to branch 8.3 first.

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

Re: [GRASS-dev] no icons in the first toolbar Grass 8.2.2

[Markus Neteler]

Hi Lizardo,


On Sun, Apr 9, 2023 at 5:10 PM Lizardo Reyna via grass-dev
 wrote:
>
> Hi,
>
> I've compiled Grass 8.2.2 in ubuntu 22.04 (two times), the first toolbar do 
> not have icons, only the description appers. The console shows this:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-
> packages/wx/lib/agw/aui/auibar.py", line 3510, in OnPaint
>
> self._art.DrawButton(dc, self, item, item_rect)
>   File "/usr/lib/python3/dist-
> packages/wx/lib/agw/aui/auibar.py", line 1008, in DrawButton
>
> bmp_rect, text_rect = self.GetToolsPosition(dc, item, rect)
>   File "/usr/lib/python3/dist-
> packages/wx/lib/agw/aui/auibar.py", line 1508, in
> GetToolsPosition
>
> bmp_rect = wx.Rect(bmp_x, bmp_y, bmp_width, bmp_height)
> TypeError
> :
> Rect(): arguments did not match any overloaded call:
>   overload 1: too many arguments
>   overload 2: argument 1 has unexpected type 'float'
>   overload 3: argument 1 has unexpected type 'float'
>   overload 4: argument 1 has unexpected type 'float'
>   overload 5: argument 1 has unexpected type 'float'
>   overload 6: argument 1 has unexpected type 'float'
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-
> packages/wx/lib/agw/aui/auibar.py", line 3510, in OnPaint
[...]

You are hit by a bug in Ubuntu's wxpython4 package. Unlike e.g. Fedora
they didn't add missing backports of float -> integer fixes.

It was also discussed here:
https://github.com/OSGeo/grass/issues/2019
https://github.com/OSGeo/grass/issues/2078

We had the same in OSGeoLive, I have created a report with bugfixes
for Ubuntu here:

https://bugs.launchpad.net/ubuntu/+source/wxpython4.0/+bug/2012205

These options I see:
- you install the patches offered in the bug report (not too difficult
but needs a bit of knowledge how to use `patch`)
- convince the Ubuntu packagers of wxpython4 to fix the bug using the
provided patch
- you try to install a more recent wxpython4 version.

Best,
Markus

> --
> Lizardo Reyna, PhD
> Universidad Técnica de Manabí
> [Address] Lodana, Manabí, Ecuador | [Mobile]  +593  982924637
> PGP Key: 0xa35a15b90ee64e8d

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

[GRASS-dev] Fwd: [PROJ] GitHub changed their RSA SSH host key

[Markus Neteler]

FYI - if you try to push to GitHub and see something like

git push origin citation_cff
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczCvj3tD2s.
...

you need to do

ssh-keygen -R github.com

git push ... again

Next make sure (!) that the new fingerprint in the message matches one
of the three from
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints

If so, confirm with "yes" the prompt and you are settled.

Markus

-- Forwarded message -
From: Laurențiu Nicola via PROJ 
Date: Fri, Mar 24, 2023 at 11:10 AM
Subject: Re: [PROJ] GitHub changed their RSA SSH host key
To: 


Hi,

I believe not, but existing contributors to repositories on GitHub who
use SSH might get an warning when trying to push or pull from the
remote.

The correct action is to run ssh-keygen -R github.com, then try again,
and confirming the prompt after making sure that the new fingerprint
matches one of the three from
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.

Laurentiu

On Fri, Mar 24, 2023, at 12:01, Javier Jimenez Shaw wrote:

Hi

In case you use GitHub (for PROJ or anything else) this may be
interesting for you:
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/

First paragraph:

At approximately 05:00 UTC on March 24, out of an abundance of
caution, we replaced our RSA SSH host key used to secure Git
operations for GitHub.com. We did this to protect our users from any
chance of an adversary impersonating GitHub or eavesdropping on their
Git operations over SSH. This key does not grant access to GitHub’s
infrastructure or customer data. This change only impacts Git
operations over SSH using RSA. Web traffic to GitHub.com and HTTPS Git
operations are not affected.

Is there action needed in OSGeo repos?

Cheers,
Javier.

.___ ._ ..._ .. . ._.  .___ .. __ . _. . __..  ...  ._ .__
___
PROJ mailing list
p...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/proj
___
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.0

[Markus Neteler]

On Fri, Mar 17, 2023 at 11:41 AM Markus Neteler  wrote:
> Markus Neteler  schrieb am Fr., 17. Feb. 2023, 19:24:
>>
>> Hi devs,
>>
>> After a long time of development and many, many improvements, it is
>> time to release 8.3.0.
>>
>> Version scheme update: please note that we abandon the odd/even scheme
>> and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
>> series. See also the related RFC: Version Numbering
>> (https://github.com/OSGeo/grass/pull/2357).
>>
>> So, remaining for the 8.3.0 milestone are (currently) 19 open pull
>> requests (PRs) which still need testing or review:
>> https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.3.0
>
>
> 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
- t.register: support mapset name in input file #2863, ninsbl
- g.extension: fix getting addons path if input JSON file doesn't
exist #2717, tmszi
- i.vi: support soil_line_slope for PVI #2561, pesekon2
- libproj: simple check for area of use #2519, metzm
- temporal dbif for current mapset only #2448, metzm
- g.extension: better handle request exceptions for l flag #2203, tmszi

May I bump all of them to the next milestone?
Could even be 8.3.1 (https://github.com/OSGeo/grass/milestone/21).

...
>> I would like to prepare the 8.3.0RC1 release soon.

Importantly, we need to branch 8.3 first.

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.0

[Markus Neteler]

Hi devs,

Markus Neteler  schrieb am Fr., 17. Feb. 2023, 19:24:

> Hi devs,
>
> After a long time of development and many, many improvements, it is
> time to release 8.3.0.
>
> Version scheme update: please note that we abandon the odd/even scheme
> and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
> series. See also the related RFC: Version Numbering
> (https://github.com/OSGeo/grass/pull/2357).
>
> So, remaining for the 8.3.0 milestone are (currently) 19 open pull
> requests (PRs) which still need testing or review:
> https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.3.0


Still open PRs. Please complete them or bump them to the next milestone.


> This is the full 8.3.0 milestone (open issues and pull requests):
> https://github.com/OSGeo/grass/milestone/13
>
> Please check issues and PRs and bump those not being addressed for
> 8.3.0 to the 8.4.0 milestone.
>
> I would like to prepare the 8.3.0RC1 release soon.
>

Really soon :-)

Markus

Time to publish all the accumulated improvements!
>
> Best,
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/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.0

[Markus Neteler]

Hi Vero, all,

On Tue, Feb 21, 2023 at 7:19 PM Veronica Andreo  wrote:
>
> Hi Markus,
>
> El vie, 17 feb 2023 a las 15:25, Markus Neteler () 
> escribió:
>>
>> Hi devs,
>>
>> After a long time of development and many, many improvements, it is
>> time to release 8.3.0.
>>
>> Version scheme update: please note that we abandon the odd/even scheme
>> and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
>> series. See also the related RFC: Version Numbering
>> (https://github.com/OSGeo/grass/pull/2357).
>
>
> Just wondering.. Should we adopt an RFC that has not yet been merged nor 
> approved via motion? There's a list of tasks in the PR that still seems 
> incomplete and I see that Vashek moved the milestone of the RFC to 8.4...

Not sure why a RFC should be related to a release milestone?

> I'm not trying to delay the release -either it is called 8.3 or 8.4, it is 
> overdue-

Overdue, yes.

> but IMO we need to agree on the RFC, no? Shall I prepare a motion and we 
> approve a version 1 of the Version Numbering RFC?

Yes, let's get this RFC approved and then follow our plan.

thanks
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.3.0

[Markus Neteler]

Hi devs,

After a long time of development and many, many improvements, it is
time to release 8.3.0.

Version scheme update: please note that we abandon the odd/even scheme
and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
series. See also the related RFC: Version Numbering
(https://github.com/OSGeo/grass/pull/2357).

So, remaining for the 8.3.0 milestone are (currently) 19 open pull
requests (PRs) which still need testing or review:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.3.0

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

Please check issues and PRs and bump those not being addressed for
8.3.0 to the 8.4.0 milestone.

I would like to prepare the 8.3.0RC1 release soon.
Time to publish all the accumulated improvements!

Best,
Markus

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

[GRASS-dev] GRASS GIS 8.2.1 released

[Markus Neteler]

We are pleased to announce that GRASS GIS 8.2.1 was released!

The GRASS GIS 8.2.1 release offers over 80 improvements and bug fixes
compared to the previous release, 8.2.0. The update includes a range
of enhancements to the software’s modules. The graphical user
interface has also seen improvements, with issues being resolved for
the database manager, the image group dialog, the import of PostGIS
and SQLite geometry data, the Postscript-based mapping tool, and the
Single-Window GUI toolbar. For mobile devices, viewport support and
hamburger menu-style table of content have been added to the manual
pages. The PROJ library support received important fixes for area
bounding boxes and longitude estimation. Compatibility fixes for PDAL
2.5.0 have been added as well.

Special thanks to all contributors!

For all changes, see our detailed announcement with the full
contributors and list of features and bugs fixed at GitHub:
https://github.com/OSGeo/grass/releases/tag/8.2.1
Packages and installers are now available for Windows, macOS, Debian,
and Fedora, with more coming soon.

See more at our release announcement:
https://grass.osgeo.org/news/2023_01_21_grass_gis_8_2_1_released/
___
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.2.1

[Markus Neteler]

Hi Jürgen,

On Tue, Jan 24, 2023 at 3:56 PM Jürgen E. Fischer  wrote:
>
> Hi Markus,
>
> On Tue, 24. Jan 2023 at 15:26:44 +0100, Markus Neteler wrote:
> > > winGRASS standalone installer: 
> > > https://grass.osgeo.org/grass82/binary/mswindows/native/WinGRASS-8.2.1-1-Setup.exe
>
> > Great.
>
> grass8 was updated in osgeo4w on sunday too.

thanks a lot!

Markus


> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Nordenhttps://www.norbit.de
> QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC
___
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.2.1

[Markus Neteler]

Hi,

On Tue, Jan 24, 2023 at 11:34 AM Martin Landa  wrote:
>
> Dear all,
>
> > ne 22. 1. 2023 v 12:18 odesílatel Markus Neteler  napsal:
>
> winGRASS standalone installer: 
> https://grass.osgeo.org/grass82/binary/mswindows/native/WinGRASS-8.2.1-1-Setup.exe

Great.

> Let's update grassVersion variable for grass-website (sorry for my ignorance, 
> I am not sure how to do it, grassVersion is not defined in the code).

See
https://github.com/OSGeo/grass-website/blob/master/data/grass.json

Already done :-) And the announcement is also there:
https://grass.osgeo.org/news/2023_01_21_grass_gis_8_2_1_released/

Cheers
Markus

PS: now the marketing steps need to follow.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev