Re: [GRASS-dev] [GRASS GIS] #3766: Update "Introduction to Raster classes" document

2019-03-09 Thread GRASS GIS
#3766: Update "Introduction to Raster classes" document
---+-
  Reporter:  Nikos Alexandris  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:
 Component:  Docs  |Version:  unspecified
Resolution:|   Keywords:
   CPU:  Unspecified   |   Platform:  All
---+-

Comment (by Nikos Alexandris):

 Diff added. Also https://github.com/GRASS-GIS/grass-ci/pull/8.

 However, do we need to submit diffs for such minor cases?
 I would prefer to update such cases directly. It's good that we move to
 git because I don't need direct access to the core.

-- 
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] #3766: Update "Introduction to Raster classes" document

2019-03-09 Thread GRASS GIS
#3766: Update "Introduction to Raster classes" document
---+-
  Reporter:  Nikos Alexandris  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:
 Component:  Docs  |Version:  unspecified
Resolution:|   Keywords:
   CPU:  Unspecified   |   Platform:  All
---+-
Changes (by Nikos Alexandris):

 * Attachment "update_pygrass_raster.rst.diff" added.

 Update pygrass_raster.rst

-- 
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] #3788: Bug for flag `-n` in r.lake.series

2019-03-09 Thread GRASS GIS
#3788: Bug for flag `-n` in r.lake.series
--+-
 Reporter:  Nikos Alexandris  |  Owner:  grass-dev@…
 Type:  defect| Status:  new
 Priority:  normal|  Milestone:
Component:  Addons|Version:  unspecified
 Keywords:  r.lake.series |CPU:  Unspecified
 Platform:  Unspecified   |
--+-
 Panos (pmav99) spotted a bug in line https://trac.osgeo.org/grass/browser
 /grass-addons/grass7/raster/r.lake.series/r.lake.series.py#L193: it will
 never be True because line https://trac.osgeo.org/grass/browser/grass-
 addons/grass7/raster/r.lake.series/r.lake.series.py#L188 redefines `flag`
 to be an empty string.

 ps- @Vaclav, I can fix this since I can commit to SVN.

-- 
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] #3774: lib/gis/testsuite/test_parser_json.py are failing

2019-03-09 Thread GRASS GIS
#3774: lib/gis/testsuite/test_parser_json.py are failing
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  Tests|Version:  svn-trunk
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Just ran the test locally:

 {{{
 bin.x86_64-pc-linux-gnu/grass77 -c ./demolocation/stefan --exec python
 ./lib/gis/testsuite/test_parser_json.py
 }}}
 and it passed without error, both with demolocation and nc_spm_08_grass7.

 Closing the ticket, feel free to reopen if needed

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] Issue priority and labelling once in git

2019-03-09 Thread Veronica Andreo
Hi devs,

I just came across this issue in Qgis github:

https://github.com/qgis/QGIS-Enhancement-Proposals/issues/141

and recalled our RFC git migration document.

I like their proposed issue labels (bug and feature request) and the
priority categories (low, medium, high). I think they are more clear-cut
than the ones proposed in our RFC document [0]; especially the priority
category. Maybe they can be combined with ours, i.e., blocker. Or what do
we put when our bug report is not critical nor blocker?

Regarding components, why not keeping raster(3d), vector, temporal. I think
those are useful and then make search easier, no? Modules is maybe too
general, IMO.

Just some comments, I'd like to hear other's (more experienced) opinions

Cheers,
Vero

[0]
https://trac.osgeo.org/grass/wiki/PSC/RFC/6_MigrationGitHub#ActivatingtheGitHubissuetracker
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release] 7.6.1

2019-03-09 Thread Markus Neteler
Hi,

On Sun, Mar 3, 2019 at 8:25 PM Markus Neteler  wrote:
> On Sun, Mar 3, 2019 at 7:37 PM Martin Landa  wrote:
> > there are no known blockers [0], I would vote for 7.6.1RC1 in next few days.
> >
> > Martin
> >
> > [0] 
> > https://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&priority=blocker&priority=critical&milestone=7.6.1&group=type&order=priority
> > [1] https://trac.osgeo.org/grass/milestone/7.6.1
>
> Sounds good to me:
>
> Here the included changes (starting from r73974):
> - https://trac.osgeo.org/grass/log/grass/branches/releasebranch_7_6
> - 
> https://trac.osgeo.org/grass/changeset?reponame=&new=74146%40grass%2Fbranches%2Freleasebranch_7_6&old=73959%40grass%2Fbranches%2Freleasebranch_7_6

GRASS GIS 7.6.1RC1 as been released today:

https://trac.osgeo.org/grass/wiki/Release/7.6.1-News#ReleaseCandidate1RC1

Please test it.

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

[GRASS-dev] [GRASS GIS] #3787: pkg-config references unknown shared library

2019-03-09 Thread GRASS GIS
#3787: pkg-config references unknown shared library
+-
 Reporter:  Bas Couwenberg  |  Owner:  grass-dev@…
 Type:  defect  | Status:  new
 Priority:  normal  |  Milestone:  7.6.1
Component:  Default |Version:  svn-releasebranch76
 Keywords:  |CPU:  Unspecified
 Platform:  Linux   |
+-
 The lintian QA tool reported several pkg-config-references-unknown-shared-
 library issues:

  * usr/share/pkgconfig/grass.pc -lgrass_gmath
  * usr/share/pkgconfig/grass.pc -lgrass_gis
  * usr/share/pkgconfig/grass.pc -lgrass_datetime
  * usr/share/pkgconfig/grass.pc -lgrass_gproj
  * usr/share/pkgconfig/grass.pc -lgrass_raster
  * usr/share/pkgconfig/grass.pc -lgrass_vector
  * usr/share/pkgconfig/grass.pc -lgrass_dbmibase
  * usr/share/pkgconfig/grass.pc -lgrass_dbmiclient
  * usr/share/pkgconfig/grass.pc -lz
  * usr/share/pkgconfig/grass76.pc -lgrass_gmath
  * usr/share/pkgconfig/grass76.pc -lgrass_gis
  * usr/share/pkgconfig/grass76.pc -lgrass_datetime
  * usr/share/pkgconfig/grass76.pc -lgrass_gproj
  * usr/share/pkgconfig/grass76.pc -lgrass_raster
  * usr/share/pkgconfig/grass76.pc -lgrass_vector
  * usr/share/pkgconfig/grass76.pc -lgrass_dbmibase
  * usr/share/pkgconfig/grass76.pc -lgrass_dbmiclient
  * usr/share/pkgconfig/grass76.pc -lz

 The tag description is as follows:

 {{{
The specified pkg-config(1) file references a shared object via, for
example, Libs: -lfoo but this package appears to not ship the
associated "libfoo.so" shared library.

This will result in a linker error and was likely caused by a missing
installation step.

Please ensure that your package ships the corresponding libfoo.so
shared object file.

Refer to the pkg-config(1) manual page and
https://bugs.debian.org/919180 for details.
 }}}

 Part of the problem is that the libraries are in a private directory like:
 {{{
 ./usr/lib/grass76/lib/libgrass_gmath.7.6.so
 ./usr/lib/grass76/lib/libgrass_gmath.so -> libgrass_gmath.7.6.so
 }}}
 And not having the .so symlink provided by the grass-dev package like for
 normal shared library packages.

 Another issue is that `-lm` & `-lz` should probably be moved from `Libs:`
 to `Libs.private:`.

-- 
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] #3786: Files reference build path

2019-03-09 Thread GRASS GIS
#3786: Files reference build path
+-
 Reporter:  Bas Couwenberg  |  Owner:  grass-dev@…
 Type:  defect  | Status:  new
 Priority:  normal  |  Milestone:  7.6.1
Component:  Default |Version:  svn-releasebranch76
 Keywords:  |CPU:  Unspecified
 Platform:  Linux   |
+-
 The lintian QA tool reported several [https://lintian.debian.org/tags
 /file-references-package-build-path.html file-references-package-build-
 path] issues.

 The files in question:

  * usr/lib/grass76/bin/r.terraflow
  * usr/lib/grass76/bin/r.viewshed
  * usr/lib/grass76/etc/python/grass/lib/arraystats.py
  * usr/lib/grass76/etc/python/grass/lib/cluster.py
  * usr/lib/grass76/etc/python/grass/lib/date.py
  * usr/lib/grass76/etc/python/grass/lib/dbmi.py
  * usr/lib/grass76/etc/python/grass/lib/display.py
  * usr/lib/grass76/etc/python/grass/lib/gis.py
  * usr/lib/grass76/etc/python/grass/lib/gmath.py
  * usr/lib/grass76/etc/python/grass/lib/imagery.py
  * usr/lib/grass76/etc/python/grass/lib/nviz.py
  * usr/lib/grass76/etc/python/grass/lib/ogsf.py
  * usr/lib/grass76/etc/python/grass/lib/proj.py
  * usr/lib/grass76/etc/python/grass/lib/raster.py
  * usr/lib/grass76/etc/python/grass/lib/raster3d.py
  * usr/lib/grass76/etc/python/grass/lib/rowio.py
  * usr/lib/grass76/etc/python/grass/lib/rtree.py
  * usr/lib/grass76/etc/python/grass/lib/segment.py
  * usr/lib/grass76/etc/python/grass/lib/stats.py
  * usr/lib/grass76/etc/python/grass/lib/temporal.py
  * usr/lib/grass76/etc/python/grass/lib/vector.py
  * usr/lib/grass76/etc/python/grass/lib/vedit.py
  * usr/lib/grass76/include/Make/Platform.make

 grepping for the build path in the output of `strings` shows absolute
 paths to source files.

 These are most likely caused by the use the `__FILE__` macro or using
 `assert()` without `-DNDEBUG` in `CFLAGS`.

 Please help make the build reproducible by removing these references for
 release builds at least.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Translations and command description/options

2019-03-09 Thread Panagiotis Mavrogiorgos
On Sat, Mar 9, 2019 at 4:53 PM Markus Neteler  wrote:

> Did you try to set this within the GRASS session?
>
> export LANG=fr_FR.UTF-8
> export LANGUAGE=fr_FR.UTF-8
> export LC_MESSAGES=fr_FR.UTF-8
>

Thank you Markus,

Yes I did try that and it doesn't help.

Maybe zshell still needs some extras in grass py?
>

zsh is certainly not well supported by GRASS (e.g. #3740
). The lack of support is
probably due to using "default_startup()" in "lib/init/grass.py"


2235if sh in ['csh', 'tcsh']:
2236shell_process = csh_startup(mapset_settings.full_mapset,
2237mapset_settings.location,
2238mapset_settings.mapset,
2239grass_env_file)
2240elif sh in ['bash', 'msh', 'cygwin']:
2241shell_process = bash_startup(mapset_settings.full_mapset,
2242 mapset_settings.location,
2243 grass_env_file)
2244else:
2245shell_process = default_startup(mapset_settings.full_mapset,
2246mapset_settings.location)


Nevertheless, the issue we are discussing here is not related to zsh. Even
with bash, the translations do not work

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

Re: [GRASS-dev] [GRASS GIS] #3742: t.rast.aggregate: allow multiple methods/output

2019-03-09 Thread GRASS GIS
#3742: t.rast.aggregate: allow multiple methods/output
--+--
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Temporal |Version:  svn-trunk
Resolution:   |   Keywords:  t.rast.aggregate
   CPU:  All  |   Platform:  All
--+--

Comment (by sbl):

 Hmmm... Now I fetched fresh latest revision (r74196) from SVN, applied the
 changes to t.rast.aggregate.py and aggregation.py, but I still get the
 Error messsage above: WARNING: Bug in UI description. Missing option
 key...

 I would very much like to get this into 7.8...

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] Errored: GRASS-GIS/grass-ci#3324 (master - e7becb2)

2019-03-09 Thread Travis CI
Build Update for GRASS-GIS/grass-ci
-

Build: #3324
Status: Errored

Duration: 10 mins and 26 secs
Commit: e7becb2 (master)
Author: Markus Metz
Message: v.what.rast(3): prevent integer overflow

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

View the changeset: 
https://github.com/GRASS-GIS/grass-ci/compare/2e247e4fa3d7...e7becb26ecf4

View the full build log and details: 
https://travis-ci.org/GRASS-GIS/grass-ci/builds/504021219?utm_medium=notification&utm_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&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_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

Re: [GRASS-dev] Translations and command description/options

2019-03-09 Thread Markus Neteler
Hi

Panagiotis Mavrogiorgos  schrieb am Fr., 8. März 2019,
21:18:

> If anyone has any other ideas, I would be happy to hear them out. here
>  is
> what has been tried so far.
>

Did you try to set this within the GRASS session?


export LANG=fr_FR.UTF-8
export LANGUAGE=fr_FR.UTF-8
export LC_MESSAGES=fr_FR.UTF-8

?

Maybe zshell still needs some extras in grass py?

Markus


___
> 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