Re: [GRASS-dev] [GRASS GIS] #3815: compression: libzstd should be a default config and a requirement if ZSTD is default compression method

[GRASS GIS]

#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:3 mmetz]:
 > Replying to [comment:2 mlennert]:
 > > +1 for backporting.
 >
 > Done in relbr76 r74398

 Just FYI:
 This broke the manual-building cronjobs on the grass.osgeo.org server but
 I fixed it by now actively disabling zstd in the configure step (Debian
 Jessie doesn't have zstd yet and #3486 = compile in a docker container is
 still open).

 In any case, the manuals on the server are now back.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3820: Error i.pansharpen in grass76 relbranch

[GRASS GIS]

#3820: Error i.pansharpen in grass76 relbranch
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Imagery  |Version:  svn-releasebranch76
Resolution:   |   Keywords:  i.pansharpen
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by veroandreo):

 It does work in trunk with no reported errors. However, if I run it in
 trunk compiled with python 3 in a virtualenv, I get:

 {{{
 i.pansharpen red=lsat7_2002_30@PERMANENT   green=lsat7_2002_20
 blue=lsat7_2002_10 pan=lsat7_2002_80 method=ihs   output=lsat7_2002_ihs
 Using 8bit image channels
 Performing pan sharpening with hi res pan image: 14.25
 Transforming to IHS color space...
  100%
 Histogram matching...
  100%
 Traceback (most recent call last):
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 632, in 
 main()
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 259, in main
 ihs(pan, ms1, ms2, ms3, out, pid, sproc)
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 380, in ihs
 panmatch = matchhist(pan, target, outname)
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 552, in matchhist
 stats = stats_out.communicate()[0].split('\n')[:-1]
 TypeError: a bytes-like object is required, not 'str'
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by veroandreo):

 Just re-compiled and tested. Now, it does not crash, but the dialog to
 submit each new feature does not appear and cat is not written.
 v.db.select of new vector digitized is empty.

 This is what I get in the GUI console when digitizing polygons:

 {{{
 Traceback (most recent call last):
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/mapwin/buffered.py", line 1397, in
 MouseActions

 self.OnRightUp(event)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/mapwin/buffered.py", line 1644, in
 OnRightUp

 self._onRightUp(event)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/vdigit/mapwindow.py", line 1001, in
 _onRightUp

 action="add", ignoreError=True)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/dbmgr/dialogs.py", line 119, in
 __init__

 self.UpdateDialog(query=query, cats=cats)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/dbmgr/dialogs.py", line 442, in
 UpdateDialog

 self.fid = self.cats.keys()[0]
 TypeError
 :
 'dict_keys' object is not subscriptable
 Traceback (most recent call last):
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/mapwin/buffered.py", line 1397, in
 MouseActions

 self.OnRightUp(event)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/mapwin/buffered.py", line 1644, in
 OnRightUp

 self._onRightUp(event)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/vdigit/mapwindow.py", line 1001, in
 _onRightUp

 action="add", ignoreError=True)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/dbmgr/dialogs.py", line 119, in
 __init__

 self.UpdateDialog(query=query, cats=cats)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/dbmgr/dialogs.py", line 442, in
 UpdateDialog

 self.fid = self.cats.keys()[0]
 TypeError
 :
 'dict_keys' object is not subscriptable
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3820: Error i.pansharpen in grass76 relbranch

[GRASS GIS]

#3820: Error i.pansharpen in grass76 relbranch
--+-
 Reporter:  veroandreo|  Owner:  grass-dev@…
 Type:  defect| Status:  new
 Priority:  normal|  Milestone:  7.6.2
Component:  Imagery   |Version:  svn-releasebranch76
 Keywords:  i.pansharpen  |CPU:  Unspecified
 Platform:  Unspecified   |
--+-
 When compiling grass76_relbranch I got an indentation error in
 i.pansharpen at line 257
 
(https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_6/scripts/i.pansharpen/i.pansharpen.py#L257)

 {{{
 File "/home/veroandreo/software/grass76_release/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 256
 pr.wait()
 ^
 IndentationError: unexpected indent
 }}}

 I entered the directory of i.pansharpen, run make, still the same error.
 So I open the code and locally moved lines 257-263 to the left.
 Compilation of i.pansharpen went fine, no errors. But when I try to run
 the examples in the manual page for Landsat 7 in NC Location, I get:

 {{{
 GRASS 7.6.2svn (nc_spm_08_grass7):~ > i.pansharpen
 red=lsat7_2002_30@PERMANENT   green=lsat7_2002_20 blue=lsat7_2002_10
 pan=lsat7_2002_80 method=ihs   output=lsat7_2002_ihs
 Traceback (most recent call last):
   File "/home/veroandreo/software/grass76_release/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 402, in 
 main()
   File "/home/veroandreo/software/grass76_release/dist.x86_64-pc-linux-
 gnu/scripts/i.pansharpen", line 135, in main
 if bits == 8:
 NameError: global name 'bits' is not defined
 }}}

 Is this related to the backport in r74385?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

[Martin Landa]

Ciao,

čt 18. 4. 2019 v 22:44 odesílatel Veronica Andreo  napsal:
> It would be nice if the vector digitizer is fixed before release, see 
> https://trac.osgeo.org/grass/ticket/3777.

should be fixed in r74401.

> I try to do as much testing as I can with python3.

Thanks! Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---
Changes (by martinl):

 * owner:  grass-dev@… => martinl
 * status:  new => assigned
 * cc: grass-dev@… (added)


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by martinl):

 Hopefully fixed in r74401

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by martinl):

 In [changeset:"74401" 74401]:
 {{{
 #!CommitTicketReference repository="" revision="74401"
 vector digitizer crashes with python 3, see #3777
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

[Veronica Andreo]

Hi all,

It would be nice if the vector digitizer is fixed before release, see
https://trac.osgeo.org/grass/ticket/3777.
I try to do as much testing as I can with python3.

best,
Vero

El lun., 8 abr. 2019 a las 14:19, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

> On 8/04/19 09:35, Martin Landa wrote:
> > Hi,
> >
> > po 1. 4. 2019 v 11:20 odesílatel Moritz Lennert
> >  napsal:
> >> I'm sorry, I have been fairly absent from grass-dev in the last months,
> >> and the situation will not get much better in the near future, and so I
> >> don't want to block if others are for releasing quickly. Also, I'm not
> >> aware of the testing efforts that have already happened (except for
> >> Mundialis). Are the automatic tests run systematically in a Python 3
> >> environment ?
> >
> > no worry, there are very few people testing GRASS in Python3
> > environment. I hope that it will change when there will be RC1 for
> > testing available ;-)
> >
> > To avoid confusion. I am not suggesting to release a buggy version. I
> > am just suggesting to start working on release. Creating branch is
> > just a first step. Personally I would avoid "technical previews" as we
> > did in the past. Just normal release policy as described in RFC. We
> > can do more that two RCs if needed.
>
> Ok, +1 from me for your release plan, but with careful scrutiny before
> the actual release.
>
> Moritz
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by veroandreo):

 The error points to slightly different lines:

 {{{
 Traceback (most recent call last):
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/vdigit/toolbars.py", line 817, in
 OnSelectMap

 disableAdd=True)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/gui_core/dialogs.py", line 524, in
 CreateNewVector

 stdin=sql)
   File
 "/home/veroandreo/software/grass7_trunk/dist.x86_64-pc-
 linux-gnu/gui/wxpython/core/gcmd.py", line 719, in
 RunCommand

 ps.stdin.write(stdin)
 TypeError
 :
 a bytes-like object is required, not 'str'
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3777: vector digitizer crashes with python 3

[GRASS GIS]

#3777: vector digitizer crashes with python 3
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  vector digitizer, python3
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by veroandreo):

 This is still an issue in r74400 compiled and run in a virtualenv with
 python3. If trunk is compiled with python2 as usual, it works as expected.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3478: g.extension does not work with bitbucket repo

[GRASS GIS]

#3478: g.extension does not work with bitbucket repo
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:  g.extension
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by veroandreo):

 It seems to work as expected now, extension successfully installed.

 Backport?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3792: Use unique names on test modules

[GRASS GIS]

#3792: Use unique names on test modules
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Tests|Version:  svn-trunk
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 In [changeset:"74400" 74400]:
 {{{
 #!CommitTicketReference repository="" revision="74400"
 testsuite: convert the following test to a proper python module name
 (fixes #3792)
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS-user] Nice opportunity to show off GRASS functionality and topological vector format ?

[Markus Metz]

On Tue, Apr 16, 2019 at 11:07 AM Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
>
> Hi,
>
> If anyone has some time and wants to show off some GRASS GIS power:
>
> https://www.ecmwf.int/en/learning/workshops/ecmwf-summer-weather-code-2019
>
> "The Summer of Weather Code(ESoWC) programme by the European Centre for
> Medium-Range Weather Forecasts (ECMWF) is a collabrative online
> programme to promote the development of weather-related open-source
> software."
>
> More specificially:
>
> https://github.com/esowc/challenges_2019
>
> And even more, I think this challenge is a fairly low hanging fruit
> using GRASS GIS tools:
>
> https://github.com/esowc/challenges_2019/issues/3

I agree, this reads like a low-hanging fruit. I could submit an abstract
until Sunday 21 April with a fairly detailed workflow, but I will most
probably not have the time to write such a tool: apparently they would like
to have a custom QGIS plugin.

Markus M
>
>
> APPLICATION DEADLINE: SUNDAY, 21 APRIL 23:59 GMT
>
>
> Moritz
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3819: Add test coverage of C files

[GRASS GIS]

#3819: Add test coverage of C files
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Compiling|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by rouault):

 > GDAL is already using gcov/lcov, too, so it might make sense to see how
 they have integrated them

 This is quite messy to be honest. Partly because I didn't try to make this
 better :-) So basically, I've a job that forks the GDAL master branch and
 re-applies the following changes on top of it :
 
https://github.com/rouault/gdal_coverage/commit/3b63c70890a0897dcbe1cbd49f36b76e0a5e704a
 But the gist is build with lcov, run the tests, run lcov, filter some
 stuff in its output to have a clean report, run genhtml and then push this
 to a github repo. The interesting part that could be more or less reused
 by GRASS is in
 
https://github.com/rouault/gdal_coverage/commit/3b63c70890a0897dcbe1cbd49f36b76e0a5e704a
 #diff-46c965c7db8bedae7518f42e783c44dd

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3819: Add test coverage of C files

[GRASS GIS]

#3819: Add test coverage of C files
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Compiling|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pmav99):

 For the record, GDAL is already using gcov/lcov, too, so it might make
 sense to see how they have integrated them: https://gdalautotest-coverage-
 results.github.io/coverage_html/index.html

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3819: Add test coverage of C files

[GRASS GIS]

#3819: Add test coverage of C files
-+-
 Reporter:  pmav99   |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:
Component:  Compiling|Version:  svn-trunk
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Disclaimer: I've only tested with gcc.

 Using the info from these links I managed to get test coverage for the C
 codebase:

 - https://stackoverflow.com/questions/16682606/how-to-resovle-gcov-init-
 undefined-reference-issue-when-link
 - https://stackoverflow.com/questions/39086957/test-coverage-from-swig-
 compiled-c-python-code

 1. install [https://gcc.gnu.org/onlinedocs/gcc/Gcov.html gcov]
 2. Compile with these options:
 {{{
 export CFLAGS='-O0 -fPIC -march=native -std=gnu99 -fprofile-arcs -ftest-
 coverage -g'
 export LDFLAGS='-s -lgcov --coverage'
 }}}
 3. Run tests
 4. Generate test coverage reports (there may be warning/errors):
 {{{
 mkdir -p coverage
 gcovr -r . --filter="" --html --html-details -o coverage/coverage.html
 }}}
 5. Inspect coverage:
 {{{
 firefox coverage/coverage.html
 }}}

 If possible, this should be added to fatra and once #3771 is resolved, on
 travis too.

 I guess that it would also make sense to add a configure option like e.g.
 [https://www.gaia-gis.it/fossil/libspatialite/artifact/f5c88dedc9888f65
 libspatialite]:
 {{{

 #---
 #--enable-gcov
 #
 # Check whether --enable-gcov was given.
 if test "${enable_gcov+set}" = set; then :
   enableval=$enable_gcov;
 fi

 if test "x$enable_gcov" = "xyes"; then
 CFLAGS=$CFLAGS" -fprofile-arcs -ftest-coverage -g"
 GCOV_FLAGS="-lgcov"
 fi
 #---
 }}}

-- 
Ticket URL: 
GRASS GIS 

___
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

[GRASS GIS]

#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
--+---
Changes (by martinl):

 * milestone:  7.8.0 => 7.6.2


-- 
Ticket URL: 
GRASS GIS 

___
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

[GRASS GIS]

#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.8.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  compression zstd zlib
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by mmetz):

 Replying to [comment:2 mlennert]:
 > Replying to [comment:1 mmetz]:
 > > Replying to [ticket:3815 mlennert]:
 [...]
 > > > I would plead [...] for libzstd to become a compulsory requirement
 for GRASS GIS, and for the configure script to default to --with-zstd=yes.
 > >
 > > Done in trunk r74391. The default is now `--with-zstd=yes`, you can
 disable ZSTD support with `--with-zstd=no`. To be backported I guess.
 >
 > +1 for backporting.

 Done in relbr76 r74398
 >
 > Should libzstd be added to REQUIREMENTS.html ?

 Yes, done in r74396,9 (trunk, relbr76)

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3816: test_r_slope_aspect.py is not idempotent

[GRASS GIS]

#3816: test_r_slope_aspect.py is not idempotent
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Tests|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pmav99):

 After removing the following maps, the tests pass again:

 {{{
 fractal_aspect
 fractal_slope
 limits_aspect
 limits_slope
 limits_percent_aspect
 limits_percent_slope
 reference_aspect
 reference_slope
 sa_separately_aspect
 sa_separately_slope
 sa_together_aspect
 sa_together_slope
 small_aspect
 small_elevation
 small_slope
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3818: Bug in modules.xml (double man1 in path)

[GRASS GIS]

#3818: Bug in modules.xml (double man1 in path)
-+-
 Reporter:  AnikaBettge  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Compiling|Version:  svn-trunk
 Keywords:   |CPU:  x86-64
 Platform:  Linux|
-+-
 In the file https://grass.osgeo.org/addons/grass7/modules.xml there stands
 e.g. "docs/man/man1/man1/r.area.1" but the r.area.1 file is
 in "docs/man/man1".

-- 
Ticket URL: 
GRASS GIS 

___
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

[GRASS GIS]

#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.8.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  compression zstd zlib
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by mlennert):

 Replying to [comment:1 mmetz]:
 > Replying to [ticket:3815 mlennert]:
 > > I just came upon the problem that in my grass installation ZSTD is
 configured and I thus worked with raster data which was automatically
 compressed using ZSTD, but when I transferred the data to our HPC system,
 I realized that grass there is not configure with ZSTD and the latter is
 currently not available on the system.
 > >
 > > As the r.compress man page says, ZSTD is the default compressor if
 available. However, when I check in current trunk's configure, it says:
 > >
 > >
 > > {{{
 > >   --with-zstd support Zstandard functionality (default:
 no)"
 > > }}}
 > >
 > > Does that mean that even if libzstd is available on a system, GRASS is
 not compiled with support for it, unless --with-zstd is set ?
 >
 > yes
 > >
 > > I find this situation a bit uncomfortable as it can lead to situations
 where the user creates data without actively thinking about the
 compression method and this data is the unusable elsewhere.
 > >
 > > I would plead, thus, for libzstd to become a compulsory requirement
 for GRASS GIS, and for the configure script to default to --with-zstd=yes.
 >
 > Done in trunk r74391. The default is now `--with-zstd=yes`, you can
 disable ZSTD support with `--with-zstd=no`. To be backported I guess.

 +1 for backporting.

 Should libzstd be added to REQUIREMENTS.html ?

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] Passed: GRASS-GIS/grass-ci#3449 (master - 5755b5a)

[Travis CI]

Build Update for GRASS-GIS/grass-ci
-

Build: #3449
Status: Passed

Duration: 9 mins and 31 secs
Commit: 5755b5a (master)
Author: Markus Metz
Message: pygrass: use getenv from pygrass.utils, fixes r74383

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@74394 
15284696-431f-4ddb-bdfa-cd5b030d7da7

View the changeset: 
https://github.com/GRASS-GIS/grass-ci/compare/bd814925fefc...5755b5a9ce22

View the full build log and details: 
https://travis-ci.org/GRASS-GIS/grass-ci/builds/521595775?utm_medium=notification_source=email

--

You can unsubscribe from build emails from the GRASS-GIS/grass-ci repository 
going to 
https://travis-ci.org/account/preferences/unsubscribe?repository=5458449_medium=notification_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

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