Re: [GRASS-dev] [GRASS GIS] #3966: Batch job examples: add GRASS_PAGER=cat to avoid getting stuck expecting a terminal
#3966: Batch job examples: add GRASS_PAGER=cat to avoid getting stuck expecting a terminal --+- Reporter: jidanni | Owner: grass-dev@… Type: enhancement | Status: closed Priority: trivial | Milestone: 7.8.3 Component: Docs |Version: unspecified Resolution: worksforme | Keywords: exec batch grass.py CPU: Unspecified | Platform: Unspecified --+- Changes (by wenzeslaus): * status: new => closed * resolution: => worksforme -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3966#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3966: Batch job examples: add GRASS_PAGER=cat to avoid getting stuck expecting a terminal
#3966: Batch job examples: add GRASS_PAGER=cat to avoid getting stuck expecting
a
terminal
--+-
Reporter: jidanni | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: trivial | Milestone: 7.8.3
Component: Docs |Version: unspecified
Resolution: | Keywords: exec batch grass.py
CPU: Unspecified | Platform: Unspecified
--+-
Comment (by wenzeslaus):
I would even say a change in the source code is more appropriate if we
understand the issue more, but I'm not able to reproduce this.
The following ones behave as expected:
{{{
grass --tmp-location XY --exec g.list type=all
nohup grass --tmp-location XY --exec g.list type=all
true | (setsid grass --tmp-location XY --exec g.list type=all) 2>&1 | cat
echo "grass --tmp-location XY --exec g.list type=all" > /tmp/test.sh
nohup bash /tmp/test.sh
}}}
Only `bash /tmp/test.sh` will jump into an interactive pager which may be
little unexpected, but I'm in an interactive terminal, so perhaps
inconvenient, but not unexpected.
I'm closing this and we can discuss this in a new issue on GitHub if
needed.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3966#comment:6>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3978: r.kappa: Segmentation fault
#3978: r.kappa: Segmentation fault --+- Reporter: sbl | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: Component: Imagery |Version: svn-trunk Resolution: fixed| Keywords: r.kappa CPU: Unspecified | Platform: Linux --+- Changes (by marisn): * status: new => closed * resolution: => fixed * milestone: 7.8.3 => Comment: The issue is fixed in 8.4.0. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3978#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3978: r.kappa: Segmentation fault
#3978: r.kappa: Segmentation fault --+- Reporter: sbl | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.3 Component: Imagery |Version: svn-trunk Resolution: | Keywords: r.kappa CPU: Unspecified | Platform: Linux --+- Comment (by marisn): There is an invalid memory access in calc_kappa.c that might result in a segfault. I'll try to deal with this issue in PR https://github.com/OSGeo/grass/pull/2573 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3978#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3677: v.surf.idw does not respect mask
#3677: v.surf.idw does not respect mask --+- Reporter: dnix | Owner: grass-dev@… Type: defect | Status: closed Priority: major| Milestone: 7.8.3 Component: Vector |Version: 7.4.1 Resolution: fixed| Keywords: v.surf.idw CPU: Unspecified | Platform: Unspecified --+- Changes (by annakrat): * status: new => closed * resolution: => fixed Comment: Fixed with https://github.com/OSGeo/grass/pull/2383. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3677#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3697: sqlite db: automatically enable vacuum
#3697: sqlite db: automatically enable vacuum --+- Reporter: mlennert | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 7.6.2 Component: Database |Version: svn-releasebranch76 Resolution: fixed| Keywords: sqlite vacuum CPU: Unspecified | Platform: Unspecified --+- Changes (by wenzeslaus): * status: reopened => closed * resolution: => fixed Comment: This was committed to trunk as well as backported to 7.6 release branch at that time, so closing this one as fixed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3697#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4000: v.import documentation megabug
#4000: v.import documentation megabug --+- Reporter: jidanni | Owner: grass-dev@… Type: defect | Status: closed Priority: trivial | Milestone: 7.8.3 Component: Docs |Version: git-releasebranch78 Resolution: wontfix | Keywords: CPU: Unspecified | Platform: Unspecified --+- Changes (by nila): * status: new => closed * resolution: => wontfix Comment: This is an open source project, based on voluntary free time work. And not a giga multinational company with unlimited resources. Please respect that and I second @annakrat’s comment, “create a pull request if it's clear what should be fixed”. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4000#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1269: ctypesgen doesn't handle OS X framework option
#1269: ctypesgen doesn't handle OS X framework option +-- Reporter: kyngchaos | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 6.5.0 Component: Python ctypes |Version: svn-develbranch6 Resolution: wontfix| Keywords: ctypes, OSX CPU: Unspecified| Platform: MacOSX +-- Changes (by nila): * status: new => closed * resolution: => wontfix Comment: I don’t see the relevance for this to GRASS. Please reopen if needed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1269#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4015: ctypes: TypeError: item 1 in _argtypes_ passes a union by value, which is unsupported
#4015: ctypes: TypeError: item 1 in _argtypes_ passes a union by value, which is unsupported +- Reporter: neteler| Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.8.3 Component: Python ctypes |Version: git-releasebranch78 Resolution: wontfix| Keywords: ctypes, python3 CPU: Unspecified| Platform: Unspecified +- Changes (by nila): * status: new => closed * resolution: => wontfix Comment: Please reopen if needed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4015#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3900: Go back to using community version of ctypesgen
#3900: Go back to using community version of ctypesgen +- Reporter: ossalanr | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 8.0.0 Component: Python ctypes |Version: unspecified Resolution: fixed | Keywords: CPU: All| Platform: All +- Changes (by nila): * status: new => closed * resolution: => fixed -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3900#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3900: Go back to using community version of ctypesgen
#3900: Go back to using community version of ctypesgen +- Reporter: ossalanr | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 8.0.0 Component: Python ctypes |Version: unspecified Resolution: | Keywords: CPU: All| Platform: All +- Comment (by nila): Solved with https://github.com/OSGeo/grass/commit/ca2d28a592064b501c0eb6c4ec648984f386dd42 on main branch (8.0dev). -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3900#comment:8> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3772: Make the grass library importable outside of a GRASS session
#3772: Make the grass library importable outside of a GRASS session --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Python |Version: svn-trunk Resolution: | Keywords: CPU: Unspecified | Platform: Unspecified --+- Comment (by wenzeslaus): If PR:1838 works, it will fix the `AttributeError` issue. Instead of deriving the path from the package path as suggested here, it delays the initialization of translations to the first translation function call. However, the new approach can be combined with or enhanced by the solution suggested here. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3772#comment:15> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3348: wxGTK3: Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
#3348: wxGTK3: Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.4 Component: wxGUI|Version: svn-trunk Resolution: | Keywords: wxGUI CPU: Unspecified | Platform: Unspecified --+- Changes (by arjan): * milestone: 7.4.5 => 7.8.4 Comment: Still seeing this with v7.8. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3348#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2230: 'g.region -p' writes new WIND file, causes race condition for parallel jobs
#2230: 'g.region -p' writes new WIND file, causes race condition for parallel jobs --+ Reporter: hamish | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 6.4.6 Component: Default |Version: svn-develbranch6 Resolution: fixed| Keywords: g.region read-only CPU: x86-64 | Platform: Linux --+ Changes (by annakrat): * status: new => closed * resolution: => fixed Comment: Implemented in https://github.com/OSGeo/grass/pull/1627 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2230#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3900: Go back to using community version of ctypesgen
#3900: Go back to using community version of ctypesgen +- Reporter: ossalanr | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 8.0.0 Component: Python ctypes |Version: unspecified Resolution: | Keywords: CPU: All| Platform: All +- Comment (by nila): This issue is addressed with [https://github.com/OSGeo/grass/pull/1651 PR #1651]. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3900#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3924: Port r.in.lidar to PDAL
#3924: Port r.in.lidar to PDAL --+- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 8.0.0 Component: Raster |Version: svn-trunk Resolution: fixed| Keywords: lblas, pdal, r.in.lidar CPU: Unspecified | Platform: Unspecified --+- Changes (by marisn): * status: new => closed * resolution: => fixed * milestone: 7.8.3 => 8.0.0 Comment: r.in.pdal will land 8.0 after merge of PR https://github.com/OSGeo/grass/pull/1200 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3924#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3558: wx.metadata: several issues in syntax
#3558: wx.metadata: several issues in syntax -+ Reporter: sbl | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.8.3 Component: Addons |Version: 7.4.0 Resolution: fixed | Keywords: wx.metadata, g.gui.metadata,r.iso.info CPU: All | Platform: All -+ Changes (by sbl): * status: new => closed * resolution: => fixed Comment: There have been various fixes to wx.metadata: https://github.com/OSGeo/grass-addons/pulls?q=is%3Apr+wx.metadata Closing the ticket. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3558#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3827: Activate Python 3 tests on the inofficial testing site (fatra)
#3827: Activate Python 3 tests on the inofficial testing site (fatra) --+ Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 7.8.3 Component: Tests|Version: svn-trunk Resolution: fixed| Keywords: Python3,gunittests CPU: Unspecified | Platform: Unspecified --+ Changes (by sbl): * status: new => closed * resolution: => fixed Comment: Tests are now implemented in github: https://github.com/OSGeo/grass/pull/1484 So this can be closed... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3827#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by wenzeslaus): Replying to [comment:21 sbl]: > Lastly, should a dependency check function go into ''g.extension'' or into the python library... g.extension can call it, but it should be in the library - length of g.extension.py being one reason. > ...(script or pygrass) This looks like a new subpackage of grass. Python and R use some names already: setuptools, distutils, devtools, ... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:27> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons
--+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.8.3
Component: Default |Version: unspecified
Resolution: | Keywords: g.extension
CPU: Unspecified | Platform: Unspecified
--+-
Comment (by wenzeslaus):
Replying to [comment:24 hcho]:
> Replying to [comment:23 sbl]:
> {{{
> cmd R 3.4 >=
> cmd cmdfail 3.4 >=
> R_package igraph 0.7.1 >=
> R_package R_fail_test 0.7.1 >=
> }}}
> looks unnatural and error-prone. Would it be possible to change this
format to
> {{{
> cmd R >= 3.4
> cmd cmdfail >= 3.4
> R_package igraph >= 0.7.1
> R_package R_fail_test >= 0.7.1
> }}}
Instead of adding another dependency format which is a custom format, I
would suggest at least using an existing general format, e.g., JSON.
However, going a step further might be even better, Conda has a somewhat
general dependency file format (environment.yml) or, alternatively, tools
like [https://mybinder.readthedocs.io/en/latest/using/config_files.html
Binder] take advantage of existing dependency formats, i.e., use
requirements.txt for Python, DESCRIPTION for R, environment.yml for Conda,
etc. When you consider setup.py for Python, this transitions nicely to my
suggestion about supporting modules which are packages.
> Also, how about defining dependency information inside modules
themselves instead of using an external file? We already have
`G_option_*()` functions to handle option dependency. Maybe,
`G_module_requires(void *first, ...), G_module_requires_python(void
*first, ...), G_module_requires_r(void *first, ...)` ... Then, add a new
global flag `--dependencies` to spit out dependency information?
In this case, you would have to compile and run the module before figuring
out the dependencies. This would not be possible for C/C++ and it still
insist on lazy imports. Even if we say these two issues are not bothering
us in the end given other issues, this would be extra confusing since it
is exactly the opposite of what any other dependency/packaging system is
doing.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:26>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by wenzeslaus): Replying to [comment:23 sbl]: > I just added a draft for a python script that could take care of dependencies in Python (conda not tested) and R packages. Other dependencies (e.g. C-libraries, commandline tools) are just checked, neither loading of the libraries not installation is supported at the moment (not sure if the latter is realistic). The current code looks straightforward and perhaps worth trying it in action (you can make an addon module which installs dependencies and then runs g.extension on the actual module). However, I think this can also get really complex. What about turning this the other way around and focusing supporting GRASS modules which are Python packages installed with conda or pip like itzi? They would just use the existing systems for dependencies. Still, g.extension could use handle_dependencies.py logic, but it would use it to install the module rather than the dependencies. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:25> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1839: Install.make should honor $DESTDIR
#1839: Install.make should honor $DESTDIR ---+- Reporter: vince | Owner: grass-dev@… Type: defect| Status: closed Priority: normal| Milestone: 7.0.7 Component: Installation |Version: svn-trunk Resolution: wontfix | Keywords: DESTDIR CPU: OSX/Intel | Platform: MacOSX ---+- Comment (by nila): DESTDIR support added with commit [https://github.com/OSGeo/grass/commit/daa8cd7f96060685901e7fa990a9d4ba96da9398 daa8cd7] to master. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1839#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #764: Can the install process accept a DESTDIR additional variable?
#764: Can the install process accept a DESTDIR additional variable? ---+- Reporter: vince | Owner: grass-dev@… Type: enhancement | Status: closed Priority: minor | Milestone: 8.0.0 Component: Installation |Version: git-releasebranch78 Resolution: fixed | Keywords: install DESTDIR CPU: All | Platform: All ---+- Changes (by nila): * status: new => closed * resolution: => fixed -- Ticket URL: <https://trac.osgeo.org/grass/ticket/764#comment:7> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #764: Can the install process accept a DESTDIR additional variable?
#764: Can the install process accept a DESTDIR additional variable? ---+- Reporter: vince | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor | Milestone: 8.0.0 Component: Installation |Version: git-releasebranch78 Resolution:| Keywords: install DESTDIR CPU: All | Platform: All ---+- Comment (by nila): DESTDIR support added with commit [https://github.com/OSGeo/grass/commit/daa8cd7f96060685901e7fa990a9d4ba96da9398 daa8cd7] to master. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/764#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Voting phase closed, presentation of results
Dear members of the GRASS GIS community, The voting phase of the GRASS GIS Election 2020 is now finished. Out of 245 registered voters, 98 completed the survey. The results are shown below and are now available in the Trac Wiki. Voting result (ranking, name, number of votes): 1. Markus Neteler 95 2. Anna Petrášová 88 3. Helena Mitasova 86 4. Martin Landa 83 5. Verónica Andreo 76 6. Moritz Lennert 74 7. Vaclav Petras68 8. Michael Barton 58 9. Huidae Cho 56 10. Helmut Kudrnovsky55 11. Peter Löwe 52 12. Māris Nartišs47 13. Stefan Blumentrath 44 The new PSC is then composed of the following 9 members: 1. Markus Neteler 95 2. Anna Petrášová 88 3. Helena Mitasova 86 4. Martin Landa 83 5. Verónica Andreo 76 6. Moritz Lennert 74 7. Vaclav Petras68 8. Michael Barton 58 9. Huidae Cho 56 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3368: warnings and errors in compilation log
#3368: warnings and errors in compilation log --+- Reporter: hellik | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.5 Component: Compiling|Version: svn-trunk Resolution: | Keywords: CPU: Unspecified | Platform: All --+- Comment (by nila): See !GitHub issue at https://github.com/OSGeo/grass/issues/1247 and related PRs. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3368#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1910: GIS manager: allow dataset managing directly
#1910: GIS manager: allow dataset managing directly --+--- Reporter: timmie | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 7.6.2 Component: wxGUI|Version: unspecified Resolution: fixed| Keywords: map management, layer manager CPU: Unspecified | Platform: Unspecified --+--- Changes (by annakrat): * status: new => closed * resolution: => fixed Comment: Closed, this can be all done now in data catalog. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1910#comment:16> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Glitch fixed, voting can proceed
Dear members of the GRASS GIS community, It now seems that the problem with the voting system has been solved and you can now vote. Thanks for your patience and apologies for the trouble. We had a few cases where the same people got more than one invitation. In case you got more than one, please be so kind to vote only once. Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] First message went without link, new message on its way
Dear members of the GRASS GIS community, We are having an issue with the voting system and are working to solve it asap. We appreciate if you wait with your vote until it is solved. Also some people had more than one e-mail adress registered and therefore got more than one invitation. Most of the duplicates have been deleted, but in case you got more than one, please be so kind to vote only once. Thanks for your patience Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] First message went without link, new message on its way
Dear members of the GRASS GIS community, By an unfortunate missatke, the first message was sent without a link. A new invitation was now sent, hopefully including a link. This last message had to be sent as a "reminder". Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Voting starts today at 12:00 UTC
Dear members of the GRASS GIS community, All eligible voters should have received an e-mail by now with the token needed to vote. Please, send me a message in case you were expecting one but got none. The voting system opens today, 2021-01-18 at 12:00 UTC and voting will be possible until Monday 2021-01-25 at 12:00 UTC. Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Last call to update names and e-mail addresses in the voter's registry
Dear members of the GRASS GIS community, The voting for the new PSC will begin on Monday 2021-01-18 at 12:00 UTC and will contiue until Monday 2021-01-25 at 12:00 UTC. This is the last call for everyone to check that their names and email addresses are given, updated and correctly spelled in the lists below. I will load these lists tomorrow evening (Central European Time). At latest on Monday 2021-01-18 before 12:00 UTC the registered voters will receive a token that will enable them to use the voting system. Lists being considered: https://github.com/OSGeo/grass/blob/master/contributors.csv https://github.com/OSGeo/grass/blob/master/contributors_extra.csv https://github.com/OSGeo/grass/blob/master/translators.csv https://github.com/OSGeo/grass-addons/blob/master/contributors.csv https://github.com/OSGeo/grass/graphs/contributors https://github.com/OSGeo/grass-addons/graphs/contributors Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Amendment to the announcement concerning lists of contributors
Dear members of the GRASS GIS community, We have now added the following three lists to the list of contributors who have voting rights: 1) GRASS GIS Addon contributors: https://github.com/OSGeo/grass-addons/blob/master/contributors.csv all those who contributed through merged pull requests which are project contributions: 2) https://github.com/OSGeo/grass/graphs/contributors 3) https://github.com/OSGeo/grass-addons/graphs/contributors The following three are the lists already being considered since the start: https://github.com/OSGeo/grass/blob/master/contributors.csv https://github.com/OSGeo/grass/blob/master/contributors_extra.csv https://github.com/OSGeo/grass/blob/master/translators.csv Please, check that your name and e-mail are correctly spelled and updated and that they appear in the corresponding list. Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: closed Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: fixed| Keywords: wxGUI, startup CPU: All | Platform: All --+ Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: Many big changes happened directly or indirectly addressing the points raised here. Considering this solved. Please, test the latest code (7.9), evaluate, provide feedback, open new issues if needed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:13> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: | Keywords: wxGUI, startup CPU: All | Platform: All --+ Comment (by wenzeslaus): Replying to [comment:5 cmbarton]: > Another one that might help would be better integrate saved workspaces with Projects (AKA Locations) or Mapsets. We could have a default workspace for each Mapset, for example, which would open when GRASS is launched and that Mapset chosen. By default it would be blank. But for demo sets like North Carolina, the default workspace could have several maps that would automatically show up in the display. This is still on the table. Consider open an issue for this. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:12> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: | Keywords: wxGUI, startup CPU: All | Platform: All --+ Comment (by wenzeslaus): Replying to [comment:1 veroandreo]: > From these students, we get comments such as: > ... > - "how do you open it after you extracted it" Tutorials for absolute beginners make use of the "Download sample location" button in the Data tab. An "Open mapset" is still under consideration. Consider creating an issue. > - "I don't know how to add dataset of north carolina ...what to do next? how to add map of north carolina" > - "I've downloaded the software and also the data base, but the map doesn't seem to open in app, I'm kind of stuck here" > - "However, I can't seem to be able to see anything upon opening it. The UI opens fine, but I can't see a map or anything after selecting the North Carolina dataset." Now the data is at least visible in Data tab in way or the or the other which hopefully mitigates some of the initial confusion and leaves some energy for the next steps. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:11> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: | Keywords: wxGUI, startup CPU: All | Platform: All --+ Comment (by wenzeslaus): Replying to [ticket:3474 hellik] (OP): > > therefore to broaden the user community, the startup should be changed to: > > - start first layer manager and map display into a default ll- wgs84-location Done in PR:705 and PR:868. > - then offer the dialogue choose location/mapset-new location/mapset Even better, the Data tab is now capable to do anything the startup screen did (e.g., PR:756, PR:731 from the recent changes). > - introduce a -vintage flag to be able to change to the old behaviour Sorry, not happening. If you are running from the command line (and you [would] have to use any vintage sort of flag), you can set the mapset from command line. If you want pick it in GUI, start in some mapset, e.g., in the demolocation or create an XY location for yourself. There is besides the default g.gui, there is also g.gui.datacatalog if you want a light weight experience. Behavior of `--gtext` is still undecided, so please do test and make suggestions. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:10> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Peter Löwe
Dear members of the GRASS GIS community, Peter Löwe has accepted a nomination to the PSC made by Stefan Blumentrath. Hernán Chief Return Officer (CRO) Forwarded Message Subject: Aw: Fwd: [GRASS-dev] [GRASS GIS Elections 2020] Nomination of Peter Löwe Date: Mon, 11 Jan 2021 10:04:28 +0100 From: Peter Löwe To: cro.gr...@osgeo.org Dear Hernán, thanks for your message. I gladly accept the nomination and will prepare a statement about my aims as a PSC member. Best regards, Peter *Gesendet:* Montag, 11. Januar 2021 um 09:50 Uhr *Von:* "Chief Return Officer (CRO) - GRASS GIS election 2020" *An:* "Peter Löwe" *Betreff:* Fwd: [GRASS-dev] [GRASS GIS Elections 2020] Nomination of Peter Löwe Dear Peter, A member of the GRASS GIS community has nominated you as a candidate for the next PSC. Please reply to me in order to accept or decline this nomination. In case you accept, and after the nomination period has passed, you will be asked to write a very brief statement on what your aims are as a member of the PSC during your tenure period. Regards, Hernán Chief Return Officer (CRO) Forwarded Message Subject: RE: [GRASS-dev] [GRASS GIS Elections 2020] Nomination phase ends tomorrow Date: Mon, 11 Jan 2021 08:42:52 + From: Stefan Blumentrath To: cro.gr...@osgeo.org Dear Hernán, I would like to nominate Peter Löwe (https://wiki.osgeo.org/wiki/User:Peter_Loewe) for the GRASS GIS PSC. Peter has been PSC member in the current period. He is a long term member of the GRASS GIS Project and FOSSGIS / OSGeo supporter. With his background in research infrastructure, reproducibility, archiving/preservation Peter brings a unique and very valuable perspective to esp. a long running project like GRASS. Cheers Stefan -Original Message- From: grass-dev On Behalf Of Chief Return Officer (CRO) - GRASS GIS election 2020 Sent: søndag 10. januar 2021 13:26 To: grass-user ; grass-dev@lists.osgeo.org; GRASS-PSC ; grass-st...@lists.osgeo.org; grass-translati...@lists.osgeo.org; grass-...@lists.osgeo.org; grass-annou...@lists.osgeo.org Subject: [GRASS-dev] [GRASS GIS Elections 2020] Nomination phase ends tomorrow Dear members of the GRASS GIS community, Please notice that the nomination phase of the GRASS GIS 2020 elections for a new Project Steering Committee (PSC) will end tomorrow, 2021-01-11 at 12:00 UTC. You still have time to nominate a member of the community to be a candidate for the next GRASS GIS PSC. I would also like to ask all voting members to check that their names and e-mails in the following lists are correctly spelled and updated: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors.csvdata=04%7C01%7C%7Cebf8a8f4265c480f9a9308d8b562dc0a%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637458783492024487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=hFpGExkLs26g7cVaxT%2BVdZB%2BS3zUCPnj0%2FO9OlxWiGU%3Dreserved=0 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Fcontributors_extra.csvdata=04%7C01%7C%7Cebf8a8f4265c480f9a9308d8b562dc0a%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637458783492024487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=MyUjWDSpBA74OXHFmDj4i9ZrgoTnyTA5pywnybvv4gU%3Dreserved=0 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fblob%2Fmaster%2Ftranslators.csvdata=04%7C01%7C%7Cebf8a8f4265c480f9a9308d8b562dc0a%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637458783492024487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=7nZiItZXCX19durHL9D%2FwBBOB1JvRWpfgVtBPSHOO4U%3Dreserved=0 Please, read the wiki in the link below to learn more about how the election is planned and how it proceeds: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.osgeo.org%2Fgrass%2Fwiki%2FPSC%2FElection2020data=04%7C01%7C%7Cebf8a8f4265c480f9a9308d8b562dc0a%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637458783492024487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=HukiHUv2SKZH0%2F4FvDtGqfey%2BgxFxPDBssmWtmvD3Z8%3Dreserved=0 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-devdata=04%7C01%7C%7Cebf8a8f4265c480f9a9308d8b562dc0a%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637458783492024487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=XxpdwAmQr9l76gNFPPt3WKcprFqx0c3D0ntU
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: | Keywords: wxGUI, startup CPU: All | Platform: All --+ Comment (by wenzeslaus): Replying to [comment:1 veroandreo]: > From these students, we get comments such as: ''once i open the grass gis console...it opens another application called layer manager'' This part should be addressed in PR:1216 (merged). -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination phase ends tomorrow
Dear members of the GRASS GIS community, Please notice that the nomination phase of the GRASS GIS 2020 elections for a new Project Steering Committee (PSC) will end tomorrow, 2021-01-11 at 12:00 UTC. You still have time to nominate a member of the community to be a candidate for the next GRASS GIS PSC. I would also like to ask all voting members to check that their names and e-mails in the following lists are correctly spelled and updated: https://github.com/OSGeo/grass/blob/master/contributors.csv https://github.com/OSGeo/grass/blob/master/contributors_extra.csv https://github.com/OSGeo/grass/blob/master/translators.csv Please, read the wiki in the link below to learn more about how the election is planned and how it proceeds: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Michael Barton
Dear members of the GRASS GIS community, Michael Barton has accepted a nomination to the PSC made by Nicklas Larsson. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Re: Nomination of Michael Barton Date: Thu, 7 Jan 2021 13:49:24 + From: Michael Barton To: cro.gr...@osgeo.org I am honored by the nomination and accept Michael Barton School of Human Evolution Change School of Complex Adaptive System Science Center for Social Dynamics & Complexity Arizona State University ...Sent from my iPad On Jan 7, 2021, at 1:27 AM, Chief Return Officer (CRO) - GRASS GIS election 2020 wrote: Dear Michael, A member of the GRASS GIS community has nominated you as a candidate for the next PSC. Please reply to me in order to accept or decline this nomination. In case you accept, and after the nomination period has passed, you will be asked to write a very brief statement on what your aims are as a member of the PSC during your tenure period. Regards, Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Michael Barton Date: Wed, 6 Jan 2021 19:12:34 +0100 From: Nicklas Larsson To: cro.gr...@osgeo.org Dear Hernán, I’d like to nominate Michael Barton for the election of the PSC. He has been an active and tireless participant in the GRASS GIS project for a long time -- if I’m not mistaken -- for about two decades now. In particular, but not exclusively, Michael has been and is very important for the support and distribution of GRASS GIS for Mac. Best regards, Nicklas Begin forwarded message: From: Michael Barton Subject: Re: GRASS GIS Elections 2020, request for nomination Date: 6 January 2021 at 16:24:19 CET To: Nicklas Larsson I would be honored. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Director, Network for Computational Modeling in Social & Ecological Sciences Associate Director, School of Complex Adaptive Systems Professor, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www: http://shesc.asu.edu, https://complexity.asu.edu, http://www.public.asu.edu/~cmbarton From: Nicklas Larsson Sent: Wednesday, January 6, 2021 8:22 AM To: Michael Barton Subject: GRASS GIS Elections 2020, request for nomination Dear Michael, I believe I’m now able, as a member of GRASS-GIS community, to nominate you for the PSC. If you will accept my nomination, I will send it to the CRO. Best, Nicklas ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #764: Can the install process accept a DESTDIR additional variable?
#764: Can the install process accept a DESTDIR additional variable? ---+- Reporter: vince | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor | Milestone: 8.0.0 Component: Installation |Version: git-releasebranch78 Resolution:| Keywords: install DESTDIR CPU: All | Platform: All ---+- Changes (by nila): * version: unspecified => git-releasebranch78 * milestone: 6.4.6 => 8.0.0 Comment: This is still an issue with 7.9.dev. PR addressing this issue https://github.com/OSGeo/grass/pull/1234. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/764#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Reminder: nomination phase still underway
Dear members of the GRASS GIS community, Please notice that the nomination phase of the GRASS GIS 2020 elections for a new Project Steering Committee (PSC) is still underway. You still have time before Monday 20201-01-11 to nominate a member of the community to be a candidate for the next GRASS GIS PSC. From the election wiki: "/During the Nomination phase, any member of the GRASS-GIS community, can nominate any community member for being a candidate for the PSC.// //Current PSC members are to be nominated for re-election in the same way by the community as possible new candidates.// //To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including name, contact e-mail and shortly why a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it.// //A nomination and its acceptance are required to be sent directly to the CRO in private. Following confirmation, it is the CRO's task to officially announce a nomination./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Māris Nartiss
Dear members of the GRASS GIS community, Māris Nartiss has accepted a nomination to the PSC made by Moritz Lennert. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Re: Nomination of Maris Nartiss Date: Sun, 3 Jan 2021 17:34:01 +0200 From: Maris Nartiss To: cro.gr...@osgeo.org Hello Hernán, I do accept the nomination. Māris. 2021-01-02 18:56 GMT+02:00, Chief Return Officer (CRO) - GRASS GIS election 2020 : Dear Maris A member of the GRASS GIS community has nominated you as a candidate for the next PSC. Please reply to me in order to accept or decline this nomination. In case you accept, and after the nomination period has passed, you will be asked to write a very brief statement on what your aims are as a member of the PSC during your tenure period. Regards, Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Maris Nartiss Date: Sat, 02 Jan 2021 17:29:26 +0100 From: Moritz Lennert To: cro.gr...@osgeo.org Dear CRO, I would like to nominate Maris Nartiss for the PSC elections. Maris has been a very active member of the GRASS GIS community for many years and would thus bring a lot of experience to the project. Best wishes, Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Martin Landa
Dear members of the GRASS GIS community, Martin Landa has accepted a nomination to the PSC made by Verónica Andreo. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Re: Nomination of Martin Landa Date: Fri, 1 Jan 2021 21:49:38 +0100 From: Martin Landa To: variablestarli...@gmail.com Dear Hernan, pá 1. 1. 2021 v 12:57 odesílatel Chief Return Officer (CRO) - GRASS GIS election 2020 napsal: A member of the GRASS GIS community has nominated you as a candidate for the next PSC. Please reply to me in order to accept or decline this nomination. In case you accept, and after the nomination period has passed, you will be asked to write a very brief statement on what your aims are as a member of the PSC during your tenure period. I accept the nomination. Best regards, Martin On 2021-01-01 01:17, Veronica Andreo wrote: Dear CRO, Happy New year! I'd like to nominate Martin Landa for PSC. I have asked him privately and he has agreed. Martin is one of the main devs of GRASS and he is very important for the project. He has mentored many students through the years leading to significant additions and improvements to grass gis. Moreover, his support (especially with windows builds) and vision in several development aspects are really valuable. He has also taught many courses and prepared great material for public use. All the best, Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Helena Mitasova
Dear members of the GRASS GIS community, Helena Mitasova has accepted a nomination to the PSC made by Anna Petrášová. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Helena Mitasova Date: Tue, 29 Dec 2020 13:01:19 -0500 From: Anna Petrášová To: Chief Return Officer (CRO) - GRASS GIS election 2020 CC: Helena Mitasova Hi Hernán, I would like to nominate Helena Mitasova. Helena has been a long term member of GRASS GIS community, actively promoting, using and testing GRASS in her research and teaching. Anna ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Reminder: nomination phase underway
Dear members of the GRASS GIS community, Happy New Year 2021 to all! This is a friendly reminder that the nomination phase of the GRASS GIS 2020 elections for a new Project Steering Committee (PSC) is underway. Please, use a few minutes these holidays to think about one member of the community who can be a valuable member of the GRASS GIS PSC and nominate her/him before 2021-01-11. From the election wiki: "/During the Nomination phase, any member of the GRASS-GIS community, can nominate any community member for being a candidate for the PSC.// // //Current PSC members are to be nominated for re-election in the same way by the community as possible new candidates.// // //To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including name, contact e-mail and shortly why a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it.// // //A nomination and its acceptance are required to be sent directly to the CRO in private. Following confirmation, it is the CRO's task to officially announce a nomination./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS PSC Elections 2020] Nomination of Huidae Cho
Dear members of the GRASS GIS community, Huidae Cho has accepted a nomination to the PSC made by Markus Neteler. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Re: [GRASS GIS PSC Elections 2020] Nomination of Huidae Cho Date: Thu, 31 Dec 2020 11:40:37 -0500 From: Huidae Cho To: Chief Return Officer (CRO) - GRASS GIS election 2020 CC: Markus Neteler Dear CRO, I accept this nomination. Best Regards, Huidae On Thu, Dec 31, 2020 at 11:31 AM Markus Neteler <mailto:nete...@osgeo.org>> wrote: Dear CRO, I hereby nominate Huidae Cho (in cc). Huidae is a long term and active member of the GRASS GIS community with a long record of contributions to the source code as well as to the community. His expertise in various parts of the project in terms of geospatial applications, operating systems being supported and programming languages makes him an important contributor. Hence I recommend him for becoming part of the PSC. Best, Markus -- Markus Neteler, PhD https://www.mundialis.de <https://www.mundialis.de> - free data with free software https://grass.osgeo.org <https://grass.osgeo.org> https://courses.neteler.org/blog <https://courses.neteler.org/blog> -- Huidae Cho, Ph.D., GISP GRASS GIS Developer https://idea.isnew.info <https://idea.isnew.info> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons
--+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.8.3
Component: Default |Version: unspecified
Resolution: | Keywords: g.extension
CPU: Unspecified | Platform: Unspecified
--+-
Comment (by hcho):
Replying to [comment:23 sbl]:
> I just added a draft for a python script that could take care of
dependencies in Python (conda not tested) and R packages. Other
dependencies (e.g. C-libraries, commandline tools) are just checked,
neither loading of the libraries not installation is supported at the
moment (not sure if the latter is realistic).
> The function has three modes: check (warns of missing dependencies),
install (installs missing dependencies (if possible), abort (stops if
dependencies are missing).
> It takes the following arguments as input:
>
> - dependency_type
> - dependency
> - version=None
> - version_comparison=None
> - repository=None
> - optional=False
>
> and could be fed e.g. from a table describing dependencies. dependency
versions, and specific repositories are not supported yet. Let me know
what you think, and i see how it could be integrated in g.extension.
handle_dependencies.py looks good. Just have a few comments.
{{{
cmd R 3.4 >=
cmd cmdfail 3.4 >=
R_package igraph 0.7.1 >=
R_package R_fail_test 0.7.1 >=
}}}
looks unnatural and error-prone. Would it be possible to change this
format to
{{{
cmd R >= 3.4
cmd cmdfail >= 3.4
R_package igraph >= 0.7.1
R_package R_fail_test >= 0.7.1
}}}
Also, how about defining dependency information inside modules themselves
instead of using an external file? We already have `G_option_*()`
functions to handle option dependency. Maybe, `G_module_requires(void
*first, ...), G_module_requires_python(void *first, ...),
G_module_requires_r(void *first, ...)` and
{{{
G_module_requires("r.stream.distance", NULL);
G_module_requires_python("numpy", "gdal", NULL);
}}}
Then, add a new global flag `--dependencies` to spit out dependency
information?
Just my 2 cents.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:24>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3789: migrate trac issues to github
#3789: migrate trac issues to github --+- Reporter: martinl | Owner: grass-dev@… Type: task | Status: closed Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: fixed| Keywords: svn, git, migration CPU: Unspecified | Platform: Unspecified --+- Changes (by neteler): * status: new => closed * resolution: => fixed Comment: Migration of the issue management has been concluded earlier this year. Open trac bugs will be managed here while new bugs are reported and being worked on here: https://github.com/OSGeo/grass/issues Closing. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3789#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4014: v.krige addon: ImportError: cannot import name '_' from 'core.utils'
#4014: v.krige addon: ImportError: cannot import name '_' from 'core.utils' --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: Component: Addons |Version: unspecified Resolution: fixed| Keywords: v.krige CPU: Unspecified | Platform: Unspecified --+- Changes (by neteler): * status: new => closed * resolution: => fixed Comment: Meanwhile `g.extension v.krige` runs successfully, closing. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4014#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by sbl): I just added a draft for a python script that could take care of dependencies in Python (conda not tested) and R packages. Other dependencies (e.g. C-libraries, commandline tools) are just checked, neither loading of the libraries not installation is supported at the moment (not sure if the latter is realistic). The function has three modes: check (warns of missing dependencies), install (installs missing dependencies (if possible), abort (stops if dependencies are missing). It takes the following arguments as input: - dependency_type - dependency - version=None - version_comparison=None - repository=None - optional=False and could be fed e.g. from a table describing dependencies. dependency versions, and specific repositories are not supported yet. Let me know what you think, and i see how it could be integrated in g.extension. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:23> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Changes (by sbl): * Attachment "handle_dependencies.py" added. Draft for a Python function to handle dependencies in g.extension -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Stefan Blumentrath
Dear members of the GRASS GIS community, Stefan Blumentrath has now accepted a nomination to the PSC made by Moritz Lennert. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Stefan Blumentrath Date: Thu, 24 Dec 2020 11:20:15 +0100 From: Moritz Lennert To: cro.gr...@osgeo.org Hi Hernán, If no one has done so already, I would like to nominate Stefan Blumentrath . Stefan has been a very active member of the community for a long time and had a good vision of the needs and prospects of GRASS GIS. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Vaclav Petras
Dear members of the GRASS GIS community, Vaclav Petras has now accepted a nomination to the PSC made by Denis Ovsienko. Hernán Chief Return Officer (CRO) Forwarded Message Subject:GRASS PSC nomination Date: Sat, 26 Dec 2020 13:56:22 + From: Denis Ovsienko To: cro.gr...@osgeo.org CC: Vaclav Petras Hello Hernán. I would like to nominate Vaclav Petras as a PSC member candidate. I think this would help to improve the feedback loop between the committee and the community. -- Denis Ovsienko ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination of Moritz Lennert
Dear members of the GRASS GIS community, Moritz Lennert has now accepted a nomination to the PSC made by Verónica Andreo. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Moritz Lennert Date: Thu, 24 Dec 2020 14:11:55 +0100 From: Veronica Andreo To: cro.gr...@osgeo.org CC: Moritz Lennert Dear CRO, I'd like to nominate Moritz Lennert (in cc) Moritz is a very active and valuable member of the GRASS GIS dev team and community. He has been continuously contributing to all different parts of the project (testing, website, addons, coding, documentation, wiki, outreach, teaching). His commitment with GRASS GIS is undoubtedly and his contributions and opinions/questions bring balance between innovation and continuity making us all think further. Best, Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Nomination of Anna Petrasova
Dear members of the GRASS GIS community, Anna Petrasova has now accepted a nomination to the PSC made by Verónica Andreo. Hernán Chief Return Officer (CRO) Forwarded Message Subject:Nomination of Anna Petrasova Date: Thu, 24 Dec 2020 14:25:01 +0100 From: Veronica Andreo To: cro.gr...@osgeo.org CC: Anna Petrášová Dear CRO, I'd like to nominate Anna Petrasova (in cc) Anna is an invaluable asset for the GRASS GIS project. Her contributions to core, addons and especially to the GUI are really impressive and always push our beloved software forward. Moreover, she has done a superb job mentoring many GSoC students that have brought significant and needed changes to GRASS. Best, Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Fwd: [GRASS-PSC] [GRASS GIS Elections 2020] Nomination of Markus Neteler
Dear members of the GRASS GIS community, Markus Neteler has now accepted a nomination to the PSC made by Helmut Kudrnovsky. Hernán Chief Return Officer (CRO) Forwarded Message Subject: [GRASS-PSC] [GRASS GIS Elections 2020] Nomination phase underway: PLEASE NOMINATE! Date: Wed, 23 Dec 2020 18:15:10 +0100 From: Helmut Kudrnovsky To: cro.gr...@osgeo.org Dear CRO, According to https://lists.osgeo.org/pipermail/grass-psc/2020-December/002276.html <https://lists.osgeo.org/pipermail/grass-psc/2020-December/002276.html> I would like to nominate Markus Neteler for the PSC election of the GRASS GIS project. Reason: Markus is the leading person of the GRASS GIS project for many years. He has a helping hand in the mailing lists, prepares software releases and does many things more. A big thank you to Markus for all his work for the project. Kind regards Helmut helmut kudrnovsky OSGeo charter member ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Fwd: [GRASS GIS PSC Elections 2020] Nomination of Helmut Kudrnovsky
Dear members of the GRASS GIS community, Helmut Kudrnovsky has now accepted a nomination to the PSC made by Markus Neteler. Hernán Chief Return Officer (CRO) Forwarded Message Subject:[GRASS GIS PSC Elections 2020] Nomination of Helmut Kudrnovsky Date: Wed, 23 Dec 2020 18:38:37 +0100 From: Markus Neteler To: Chief Return Officer (CRO) - GRASS GIS election 2020 CC: Helmut Kudrnovsky Dear CRO, I hereby nominate Helmut Kudrnovsky (in cc). Helmut is an active member of the community, taking care of especially Windows related aspects, packaging and testing (standalone and OSGeo4W installers). He's known for his continuity which is a major asset in open source communities. 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 Elections 2020] Nomination phase underway: PLEASE NOMINATE!
Dear members of the GRASS GIS community, This is a friendly reminder that the nomination phase of the GRASS GIS 2020 elections for a new Project Steering Committee (PSC) is underway. A minor but important last-minute change is that that now current PSC members will have to be nominated in the same way as any other member of the community to be able to stand up as candidates for the new PSC. *** use a few minutes these holidays to think about one worthy candidate for the GRASS GIS PSC and nominate her/him before 2021-01-11 *** From the election wiki: "/During the Nomination phase, any member of the GRASS-GIS community, can nominate any community member for being a candidate for the PSC.// // //Current PSC members are to be nominated for re-election in the same way by the community as possible new candidates.// // //To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including name, contact e-mail and shortly why a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it.// // //A nomination and its acceptance are required to be sent directly to the CRO in private. Following confirmation, it is the CRO's task to officially announce a nomination./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nomination phase underway
Dear members of the GRASS GIS community, This is a friendly reminder that the nomination phase of the GRASS GIS 2020 of new Project Steering Committee (PSC) is underway. A minor but important last-minute change is that that now current PSC members will have to be nominated in the same way as any other member of the community to be able to stand up as candidates for the new PSC. From the election wiki: "/During the Nomination phase, any member of the GRASS-GIS community, can nominate any community member for being a candidate for the PSC.// // //Current PSC members are to be nominated for re-election in the same way by the community as possible new candidates.// // //To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including name, contact e-mail and shortly why a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it.// // //A nomination and its acceptance are required to be sent directly to the CRO in private. Following confirmation, it is the CRO's task to officially announce a nomination./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Fwd: [GRASS-PSC] [GRASS GIS Elections 2020] Nominations start today 2020-12-21 at 12:00 UTC
Dear members of the GRASS GIS community, Verónica Andreo has now accepted her nomination to the PSC made by Stefan Blumentrath. Hernán Chief Return Officer (CRO) Forwarded Message Subject: RE: [GRASS-PSC] [GRASS GIS Elections 2020] Nominations start today 2020-12-21 at 12:00 UTC Date: Mon, 21 Dec 2020 08:36:44 + From: Stefan Blumentrath To: cro.gr...@osgeo.org Dear Hernán, And thanks for volunteering as CRO. Very much appreciated! I would like to nominate Veronica Andreo (veroandreo - at - gmail.com <mailto:veroand...@gmail.com>). She has been incredibly active on all parts of the project (testing, website, addons, coding, documentation, wiki, outreach and PR) for a long time and regularly introduces GRASS GIS to new users. She will also be a very valuable addition to the PSC in the sense that she adds a very applied perspective with her biological background. Furthermore, being located in Argentina she will extend the geographical coverage of the PSC (currently covering North America and Europe). Cheers Stefan *From:*grass-psc *On Behalf Of *Chief Return Officer (CRO) - GRASS GIS election 2020 *Sent:* mandag 21. desember 2020 09:25 *To:* grass-user ; grass-dev@lists.osgeo.org; GRASS-PSC ; grass-st...@lists.osgeo.org; grass-translati...@lists.osgeo.org; grass-...@lists.osgeo.org; grass-annou...@lists.osgeo.org *Subject:* [GRASS-PSC] [GRASS GIS Elections 2020] Nominations start today 2020-12-21 at 12:00 UTC Dear members of the GRASS GIS community, Today we start the election process for members of the new Project Steering Committee (PSC). We will start with nominations today, 21 December, at 12:00 UTC. The nomination period will end on 11 January 2021 at 12:00 UTC. From the election wiki: "/During the Nomination phase, *any* member of the GRASS-GIS community, can nominate *any* community member for being a candidate for the PSC. / /To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including *name*, *contact e-mail* and shortly *why* a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it. / /In short, a nomination and its acceptance *are required to be sent directly to the CRO*, in private. Following, it is the CRO's task to officially announce a nomination. / */Note/*/, current PSC members will be asked if they wish to stand as a candidate for the upcoming election./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.osgeo.org%2Fgrass%2Fwiki%2FPSC%2FElection2020=04%7C01%7C%7C08ae0e84be4b4153c95208d8a589efc2%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637441359162121546%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=nji30i70irDOh6TFm1xp01FxZHpSpBVw7SsitsixCR8%3D=0> Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Nominations start today 2020-12-21 at 12:00 UTC
Dear members of the GRASS GIS community, Today we start the election process for members of the new Project Steering Committee (PSC). We will start with nominations today, 21 December, at 12:00 UTC. The nomination period will end on 11 January 2021 at 12:00 UTC. From the election wiki: "/During the Nomination phase, //*any*//member of the GRASS-GIS community, can nominate //*any*//community member for being a candidate for the PSC. / // /To set a nomination in motion, an e-mail should be directed to the CRO (cro.grass at osgeo.org) including //*name*//, //*contact e-mail*//and shortly //*why*//a person is recommended as a PSC member. The CRO will then contact the recommended person asking for confirmation. The nominated person has to accept the candidacy for the PSC and will be asked to write a few lines stating what she/he wants to achieve as part of it. / // /In short, a nomination and its acceptance //*are required to be sent directly to the CRO*//, in private. Following, it is the CRO's task to officially announce a nomination. / // ///*Note*//, current PSC members will be asked if they wish to stand as a candidate for the upcoming election./" Please, read the wiki in the link below to learn more about how the election is planned and how they proceed: https://trac.osgeo.org/grass/wiki/PSC/Election2020 Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by neteler): In a simple way, I have defined the needed requirements of `t.rast.mosaic` addon as a small shell script: https://github.com/mundialis/t.rast.mosaic/blob/main/requirements.sh Of course it would be better if `g.extension` could take care... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:22> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons
--+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.8.3
Component: Default |Version: unspecified
Resolution: | Keywords: g.extension
CPU: Unspecified | Platform: Unspecified
--+-
Comment (by sbl):
Replying to [comment:20 wenzeslaus]:
> > Silently installing stuff can be a bit scary...
>
> Why do you think it is scary for GRASS GIS? pip, R, conda, apt, yum, ...
all install dependencies of a package you asked for. Why this should not
happen for GRASS GIS?
Yes, you are right.
So, how would we setup a requirements.txt?
Should it contain different sections, like e.g.
{{{
GRASS_addons
r.area
R_packages
ggplot2
Python_libraries
rpy2>=1.1
cmd_tools
iconv
cs2cs
libraries
libgdal-grass
}}}
Cause the way these dependencies are installed varies a bit, with a
dpendency_check function for each of them...
Maybe better with a dependency json:
{{{
{
"GRASS_addons": [
{
"name": "r.area"
}],
"Python_libraries": [
{
"name": "rpy2",
"version": "1.1"
"version_check": ">="
}], ...
}
}}}
In the functions we might have to think about OS specific aspects (package
manager (incl. conda vs. pip), library names) as well as maybe versions
(e.g. numpy>=1.17).
Also, should a failed dependency check block the installation? Because
that it is not a trivial task I would opt for a warning rather than an
error message in case of missing or unresolved dependencies...
Lastly, should a dependency check function go into ''g.extension'' or into
the python library (script or pygrass). In the python lib it could be used
by AddOn devs at runtime (e.g. if it takes a json formated string or
dict)...
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:21>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by wenzeslaus): Replying to [comment:19 sbl]: > Pyhon modules are supposed to use lazy imports and should catch if a required python library is available at runtime. +1 > For C modules, installation of libraries through g.extension is probably not very straight forward. Right. For some addons, we actually have that as an optional dependency in the core. However, pip, R, and conda can actually do that, so perhaps if we use them in background, they could take care of that. There have been suggestions like this in the past, but a lot of changed in past years. pip is now basically part of Python. conda is quite common. There is a lot of R packages using C++. For example //itzi// is using pip rather than g.extension. > Silently installing stuff can be a bit scary... Why do you think it is scary for GRASS GIS? pip, R, conda, apt, yum, ... all install dependencies of a package you asked for. Why this should not happen for GRASS GIS? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:20> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1434: g.extension: option to specify proxy server
#1434: g.extension: option to specify proxy server -+- Reporter: hamish | Owner: grass-dev@… Type: | Status: reopened enhancement| Priority: major | Milestone: 7.6.2 Component: |Version: svn-trunk Installation | Resolution: | Keywords: g.extension, urllib, wget, r.in.wms CPU: All | Platform: All -+- Comment (by sbl): Is this still relevant in more recent versions of GRASS? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/1434#comment:24> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2010: r.in.wms2 fails to install on 6.x
#2010: r.in.wms2 fails to install on 6.x -+- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.8.3 Component: Addons |Version: svn-releasebranch64 Resolution: | Keywords: r.in.wms2 CPU: All | Platform: Linux -+- Comment (by sbl): Is this still relevant, or can we close it? Anyone planning to work on it? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2010#comment:12> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons
#2895: Define dependencies for GRASS addons --+- Reporter: pmav99 | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension CPU: Unspecified | Platform: Unspecified --+- Comment (by sbl): Pyhon modules are supposed to use lazy imports and should catch if a required python library is available at runtime. The same should be true for dependency on other addons (should probably added to the SUBMITTING guidelines). For C modules, installation of libraries through g.extension is probably not very straight forward. So the question is a bit, where this is supposed to be handeled. Personally, I would probably prefer if the addon itself catches evtl. missing dependencies and gives a clear error message. Silently installing stuff can be a bit scary... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2895#comment:19> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3179: g.extension not installing addons behind proxy
#3179: g.extension not installing addons behind proxy --+ Reporter: madi | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.3 Component: Default |Version: unspecified Resolution: | Keywords: g.extension, proxy, addons CPU: Unspecified | Platform: Unspecified --+ Comment (by sbl): Is there anything left here? Can the ticket be closed? Installation through proxies should work now... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3179#comment:22> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3455: Grass 7.2.1 returns "Extension(...)not found" when installing addon
#3455: Grass 7.2.1 returns "Extension(...)not found" when installing addon --+- Reporter: bcbernardo | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.2.4 Component: Addons |Version: 7.4.0 Resolution: | Keywords: CPU: Unspecified | Platform: MSWindows --+- Comment (by sbl): Is this still an issue with more recent versions? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3455#comment:11> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Announcement and voters registry
Dear members of the GRASS community, We are about to launch the 2020 election for members of the Project Steering Committee (PSC). The nominating and voting process will be soon explained in detail in the Trac wiki (needs update, coming soon): https://trac.osgeo.org/grass/wiki/PSC/Election2020 In the meanwhile, it may be of interest for the members of the community to check whether they are eligible to vote. In this election, those who have the right to vote will be: - all people with write access to any of the GRASS GIS repositories (i.e for example also including add-ons and website). - all people that have already posted a pull request to github (possibly only those PR that have been merged) - all people that have contributed to Transifex. We are therefore considering the following lists as GRASS GIS electoral registry: https://github.com/OSGeo/grass/blob/master/contributors.csv https://github.com/OSGeo/grass/blob/master/contributors_extra.csv https://github.com/OSGeo/grass/blob/master/translators.csv If someone finds that her/his name is not on any of these lists but it should, please send an e-mail to the corresponding list to inform the members of the PSC so the situation can be solved. Hernán Chief Return Officer (CRO) GRASS GIS election 2020 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4023: TypeError: a bytes-like object is required, not 'str'
#4023: TypeError: a bytes-like object is required, not 'str' --+- Reporter: pvanbosgeo | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: Component: Default |Version: unspecified Resolution: fixed| Keywords: CPU: Unspecified | Platform: MSWindows --+- Changes (by pvanbosgeo): * status: new => closed * resolution: => fixed Comment: Replying to [comment:2 neteler]: > @pvanbosgeo is this still an issue? If not, please close the ticket Yes, these seems to be solved, thanks. Closing now -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4023#comment:3> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4023: TypeError: a bytes-like object is required, not 'str'
#4023: TypeError: a bytes-like object is required, not 'str' --+- Reporter: pvanbosgeo | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: Component: Default |Version: unspecified Resolution: | Keywords: CPU: Unspecified | Platform: MSWindows --+- Comment (by neteler): @pvanbosgeo is this still an issue? If not, please close the ticket -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4023#comment:2> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3474: Change the GRASS GIS start up to more beginner friendly
#3474: Change the GRASS GIS start up to more beginner friendly --+ Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new Priority: critical | Milestone: 8.0.0 Component: Startup |Version: svn-trunk Resolution: | Keywords: wxGUI, startup CPU: All | Platform: All --+ Comment (by neteler): For the record: continued here: https://github.com/OSGeo/grass/projects/1 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3474#comment:8> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3856: implement svn keyword substitution
#3856: implement svn keyword substitution --+--- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: closed Priority: blocker | Milestone: 7.6.2 Component: Default |Version: svn-trunk Resolution: fixed| Keywords: git, svn keywords CPU: Unspecified | Platform: Unspecified --+--- Changes (by neteler): * status: new => closed * resolution: => fixed Comment: Relevant parts of PR:9 have been merged some time ago, closing. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3856#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4001: grass78 --config broken
#4001: grass78 --config broken --+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.8.3 Component: Python |Version: git-releasebranch78 Resolution: fixed| Keywords: grass.py CPU: Unspecified | Platform: Unspecified --+- Changes (by neteler): * status: new => closed * resolution: => fixed Comment: Fixed per PR:405 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4001#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3919: db.dropcolumn and v.db.dropcolumn do not drop columns
#3919: db.dropcolumn and v.db.dropcolumn do not drop columns -+ Reporter: veroandreo | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.3 Component: Database|Version: git-releasebranch78 Resolution: | Keywords: db.dropcolumn, v.db.dropcolumn CPU: x86-64 | Platform: Linux -+ Comment (by wenzeslaus): Not really migrated, but mostly continued in: * PR:1124 lib: Increase max size of SQL statements * https://github.com/OSGeo/grass/issues/1126 [Feat] db.execute: Detect that SQL statement is longer than DB_SQL_MAX -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3919#comment:9> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3886: Importing vector training areas in g.gui.iclass (interactive)
#3886: Importing vector training areas in g.gui.iclass (interactive) ---+- Reporter: pshapley | Owner: grass-dev@… Type: defect| Status: new Priority: normal| Milestone: 7.8.3 Component: wxGUI |Version: git-releasebranch78 Resolution:| Keywords: g.gui.iclass CPU: x86-64| Platform: Linux ---+- Comment (by mlennert): Does https://github.com/OSGeo/grass/pull/1020 fix this issue ? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3886#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3429: g.gui.iclass: segfault when loading vector layer
#3429: g.gui.iclass: segfault when loading vector layer --+-- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.4.5 Component: wxGUI|Version: svn-trunk Resolution: duplicate| Keywords: g.gui.iclass import segfault CPU: Unspecified | Platform: Unspecified --+-- Changes (by mlennert): * status: new => closed * resolution: => duplicate Comment: Follow-up in https://github.com/OSGeo/grass/issues/1019, so closing this ticket. PR available in https://github.com/OSGeo/grass/pull/1020 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3429#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method
#3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: Raster |Version: svn-trunk Resolution: | Keywords: compression zstd zlib CPU: Unspecified | Platform: Unspecified --+--- Comment (by neteler): Replying to [comment:18 annakrat]: > Another reported problem: > https://gis.stackexchange.com/questions/368823/r-grow-distance-with-r -mask-returns-errors-on-a-global-scale-but-not-with-a-sma Yes, but reported with GRASS GIS 7.6 and ZSTD 1.3.2.0. Currently ZSTD 1.4.4-1 is shipped in OSGeo4W). -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3815#comment:19> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #70: imagery modules: strip @mapset part
#70: imagery modules: strip @mapset part --+- Reporter: hamish | Owner: grass-dev@… Type: task | Status: new Priority: major| Milestone: 8.0.0 Component: Imagery |Version: svn-trunk Resolution: | Keywords: imagery CPU: Unspecified | Platform: Unspecified --+- Comment (by neteler): Probably fixed in * master: https://github.com/OSGeo/grass/commit/db1f1582ddc282d8d0fdb3f79496b9163e1693ec * relbr78: https://github.com/OSGeo/grass/commit/dfe511f3d95cff8b44c970e5c3beb842d782ddd2 -- Ticket URL: <https://trac.osgeo.org/grass/ticket/70#comment:24> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #572: Remember recent GIS Data Directory
#572: Remember recent GIS Data Directory -+- Reporter: cgsbob | Owner: grass-dev@… Type: | Status: closed enhancement| Priority: normal | Milestone: 7.8.3 Component: wxGUI |Version: unspecified Resolution: fixed | Keywords: recent, startup, database, CPU: | gisdbase, dbase Unspecified| Platform: Unspecified -+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: I believe the original use case is addressed now by adding multiple databases to the data catalog (PR:761) and storing this list in the settings (PR:858), so closing this as fixed. The "remember recent" concept is still of interest, so if anybody has an idea how that would work within the [https://github.com/OSGeo/grass/projects/1 New Startup], please create a new issue on !GitHub. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/572#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #504: wxGUI location wizard: set bounds by drawing a box on world map
#504: wxGUI location wizard: set bounds by drawing a box on world map --+-- Reporter: hamish | Owner: grass-dev@… Type: enhancement | Status: closed Priority: trivial | Milestone: 6.5.0 Component: wxGUI|Version: svn-develbranch6 Resolution: wontfix | Keywords: location wizard CPU: All | Platform: All --+-- Changes (by wenzeslaus): * status: new => closed * resolution: => wontfix Comment: The bounding box/default region is now set automatically from a file or not at all in the location wizard, so this does not really apply, so I'm closing this now as won't fix. However, now you can draw the region like this in the main GUI and there is room for more some improvements regarding this own the New Startup project is finished. If there are other suggestions in context of the current state of things, please open a new issue on !GitHub. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/504#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2217: Win 7 Grass 6.4.2 and 6.4.3 - location wizard not creating mapset AND cannot launch with any mapset
#2217: Win 7 Grass 6.4.2 and 6.4.3 - location wizard not creating mapset AND cannot launch with any mapset --+- Reporter: jvdmdoacpro | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 6.4.6 Component: wxGUI|Version: 6.4.3 Resolution: fixed| Keywords: location wizard CPU: x86-32 | Platform: MSWindows 7 --+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: Neither of the tracebacks can be matched with current code (v7.8): No ctypes are loaded on GUI start and there is not attr1 in location wizard. Assuming this was fixed. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2217#comment:4> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3957: Clicking Help on first screen does nothing
#3957: Clicking Help on first screen does nothing
--+-
Reporter: jidanni | Owner: grass-dev@…
Type: defect | Status: new
Priority: trivial | Milestone: 7.8.3
Component: Startup |Version: git-releasebranch78
Resolution: | Keywords: help, Debian
CPU: Unspecified | Platform: Linux
--+-
Comment (by wenzeslaus):
If you have `xdg-open` available, this should just work. It's the default
in `grass.py` for all systems except Windows and macOS.
I'm getting some strange behavior when I actually set the variable:
{{{
GRASS_HTML_BROWSER=firefox grass
GRASS_HTML_BROWSER=chromium grass
}}}
However, in that case, not even g.manual is working. Anybody else
observing this? If yes, can you just open a new issue on !GitHub for that?
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3957#comment:10>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3964: Update browser list to check for chrome
#3964: Update browser list to check for chrome --+- Reporter: jidanni | Owner: grass-dev@… Type: enhancement | Status: closed Priority: trivial | Milestone: 7.8.3 Component: Startup |Version: unspecified Resolution: fixed| Keywords: CPU: Unspecified | Platform: Unspecified --+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: The Chrome/Chromium part was resolved in PR:201, so closing as fixed. I created a new issue on !GitHub for the `BROWSER` suggestion: [https://github.com/OSGeo/grass/issues/890 GitHub Issue 890]. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3964#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3656: cannot launch GRASS GIS 7.4.1 gis_set error
#3656: cannot launch GRASS GIS 7.4.1 gis_set error --+--- Reporter: cgarzon | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.4.5 Component: Startup |Version: 7.4.0 Resolution: fixed| Keywords: gis_set error, python CPU: Unspecified | Platform: MacOSX --+--- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: After transition to Python 3 when a lot of encoding issues was fixed, I'm assuming this issue fixed. If you have problems, please open a new issue on [https://github.com/OSGeo/grass/issues GitHub]. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3656#comment:18> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3713: add powershell shell support to grass74.py
#3713: add powershell shell support to grass74.py --+- Reporter: pmolzer | Owner: grass-dev@… Type: enhancement | Status: closed Priority: normal | Milestone: 7.6.2 Component: Startup |Version: 7.4.2 Resolution: fixed| Keywords: CPU: Unspecified | Platform: MSWindows --+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: This seems to be already added in r73814. No remaining issues obvious from comments. Closing as fixed. Please, open a new issue on !GitHub if you need to follow up. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3713#comment:13> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3578: Add New Location action to the Datacatalog
#3578: Add New Location action to the Datacatalog -+- Reporter: wenzeslaus | Owner: grass-dev@… Type: | Status: closed enhancement| Priority: normal | Milestone: 8.0.0 Component: wxGUI |Version: unspecified Resolution: fixed | Keywords: datacatalog, location, new, create, CPU: | download Unspecified| Platform: Unspecified -+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: New context menu item added in PR:790 and new button in PR:803. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3578#comment:1> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3740: The "Quit GRASS GIS" button does not close the GRASS shell/session
#3740: The "Quit GRASS GIS" button does not close the GRASS shell/session --+- Reporter: pmav99 | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.8.3 Component: Startup |Version: svn-trunk Resolution: fixed| Keywords: CPU: x86-64 | Platform: Linux --+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: Z shell support added in PR:722. Closing as fixed. See also (already closed) #3009 for the exit issue. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3740#comment:14> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method
#3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: Raster |Version: svn-trunk Resolution: | Keywords: compression zstd zlib CPU: Unspecified | Platform: Unspecified --+--- Comment (by annakrat): Another reported problem: https://gis.stackexchange.com/questions/368823/r-grow-distance-with-r -mask-returns-errors-on-a-global-scale-but-not-with-a-sma -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3815#comment:18> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3009: "Quit GRASS GIS" button only exits GUI
#3009: "Quit GRASS GIS" button only exits GUI --+- Reporter: cmbarton | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.8.3 Component: wxGUI|Version: unspecified Resolution: fixed| Keywords: "quit grass gis button" CPU: Unspecified | Platform: MacOSX --+- Changes (by nila): * status: new => closed * resolution: => fixed -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3009#comment:13> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3009: "Quit GRASS GIS" button only exits GUI
#3009: "Quit GRASS GIS" button only exits GUI --+- Reporter: cmbarton | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.3 Component: wxGUI|Version: unspecified Resolution: | Keywords: "quit grass gis button" CPU: Unspecified | Platform: MacOSX --+- Comment (by nila): This issue has been solved for bash and zsh terminal with [https://github.com/OSGeo/grass/pull/722 PR722]. The cause of the problem is that some shells often ignore SIGTERM when interactive, which is the case - as it seems - for e.g. mac and FreeBSD shells. Adding a `trap "exit" TERM` did the trick. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3009#comment:12> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3295: GRASS GIS fails to start without terminal
#3295: GRASS GIS fails to start without terminal -+- Reporter: wenzeslaus | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 8.0.0 Component: Startup |Version: unspecified Resolution: fixed | Keywords: gisset, wxGUI, init, grass.py, CPU: | nohup, terminal, shell, GUI, CLI, exec, g.gui Unspecified| Platform: Linux -+- Changes (by wenzeslaus): * status: new => closed * resolution: => fixed Comment: Both cases, Ctrl+F2 and nohup, fixed by PR:768. Open new issues on !GitHub in case there are follow up problems. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3295#comment:5> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method
#3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: Raster |Version: svn-trunk Resolution: | Keywords: compression zstd zlib CPU: Unspecified | Platform: Unspecified --+--- Comment (by wenzeslaus): Problems reported between Oct 31, 2019 and now: * [https://lists.osgeo.org/pipermail/grass-dev/2019-December/093800.html ZSTD error] * [https://lists.osgeo.org/pipermail/grass-dev/2020-May/094351.html ZSTD compression error on Windows] Generally speaking, changing the default in minor version became challenge for users sharing data (locations, packs) with other users ([https://lists.osgeo.org/pipermail/grass-dev/2019-December/093802.html ...choice of raster compression method...]) since the requirement was version 7.6 compiled //with newly introduced ZSTD//. Expected issues between major versions, but not minor ones. Even more problems were created by compatibility issues between different ZSTD versions. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3815#comment:17> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method
#3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method --+--- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.2 Component: Raster |Version: svn-trunk Resolution: | Keywords: compression zstd zlib CPU: Unspecified | Platform: Unspecified --+--- Comment (by neteler): For the record: in G7.8 and master ZSTD is the default compression: * https://github.com/OSGeo/grass/blob/releasebranch_7_8/lib/gis/compress.c#L126 * https://github.com/OSGeo/grass/blob/master/lib/gis/compress.c#L126 As we didn't get any complaints with that, I suggest to keep it as is. -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3815#comment:16> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2919: Use SFD above this threshold - infinity doesn't work in r.stream.extract
#2919: Use SFD above this threshold - infinity doesn't work in r.stream.extract
--+-
Reporter: PitStop | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.8.3
Component: Raster |Version: git-releasebranch78
Resolution: | Keywords: r.stream.extract
CPU: x86-64 | Platform: MSWindows 8
--+-
Comment (by hellik):
some background information:
https://sourceforge.net/p/mingw/bugs/2358/
{{{
[...]
You are using Microsoft's implementation of scanf(), (because that is all
that MinGW has ever used for this function, and its siblings), so the
behaviour is as Microsoft have specified it, (and there appears to be
nothing in their documentation to suggest how infinities and nans might be
converted,
[...]
You may consider Microsoft's implementation to be broken -- and you may
well be right -- but good luck with trying to get them to acknowledge
that, much less fix it.
}}}
AFAIR there was also some discussion some times ago how winGRASS (not)
handling NaN in raster data. (can't find ticket or thread at the moment).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2919#comment:17>
GRASS GIS <https://grass.osgeo.org>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #2919: Use SFD above this threshold - infinity doesn't work in r.stream.extract
#2919: Use SFD above this threshold - infinity doesn't work in r.stream.extract --+- Reporter: PitStop | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.3 Component: Raster |Version: git-releasebranch78 Resolution: | Keywords: r.stream.extract CPU: x86-64 | Platform: MSWindows 8 --+- Changes (by neteler): * version: svn-releasebranch72 => git-releasebranch78 * milestone: 7.2.4 => 7.8.3 Comment: The code is now here: https://github.com/OSGeo/grass/blob/75ac17f0a3f19cbff749badaf0a46aa7d0f91537/raster/r.stream.extract/main.c#L107 Not sure what to look for? -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2919#comment:15> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #4020: r.in.lidar / v.in.lidar missing in Ubunutgis package
#4020: r.in.lidar / v.in.lidar missing in Ubunutgis package +- Reporter: sbl| Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: Component: Packaging |Version: unspecified Resolution: wontfix| Keywords: Ubuntugis CPU: All| Platform: Linux +- Changes (by sbl): * status: new => closed * resolution: => wontfix Comment: Closing this cause liblas is deprecated and pdal available... -- Ticket URL: <https://trac.osgeo.org/grass/ticket/4020#comment:6> GRASS GIS <https://grass.osgeo.org> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
