Re: [GRASS-dev] Addons manuals: logo and CSS file missing

[Martin Landa]

Hi,

čt 25. 4. 2019 v 7:56 odesílatel Markus Metz
 napsal:
> zstd is not a required dependency, you can disable it with --with-zstd=no

right, I meant "by default enabled dependency" :-) 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] Addons manuals: logo and CSS file missing

[Markus Metz]

On Thu, Apr 25, 2019 at 7:42 AM Martin Landa  wrote:
>
> Hi,
>
> st 24. 4. 2019 v 16:28 odesílatel Markus Neteler 
napsal:
> > Could you please verify?
>
> yes, the reason is that G76 is not compiled on server due to a new
> required dependency:
>
> configure: error: *** Unable to locate zstd includes.

zstd is not a required dependency, you can disable it with --with-zstd=no

Markus M

>
> I will fix it ASAP. 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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Addons manuals: logo and CSS file missing

[Martin Landa]

Hi,

st 24. 4. 2019 v 16:28 odesílatel Markus Neteler  napsal:
> Could you please verify?

yes, the reason is that G76 is not compiled on server due to a new
required dependency:

configure: error: *** Unable to locate zstd includes.

I will fix it ASAP. 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-SVN] r74422 - grass/trunk/lib/python/pygrass/modules/interface/testsuite

[Stefan Blumentrath]

Hi again,

#3825 was opened for not forgetting it.

But indeed, issuing a warning message makes sense if test is run individually.
As mentioned, in multirunner it should be visible (0 tests succeeded).

Cheers,
Stefan

From: grass-dev  On Behalf Of Markus Neteler
Sent: onsdag 24. april 2019 23:42
To: GRASS developers list 
Subject: Re: [GRASS-dev] [GRASS-SVN] r74422 - 
grass/trunk/lib/python/pygrass/modules/interface/testsuite

Hi,
mailto:svn_gr...@osgeo.org>> schrieb am Mi., 24. Apr. 
2019, 22:33:
Author: sbl
Date: 2019-04-24 13:33:36 -0700 (Wed, 24 Apr 2019)
New Revision: 74422

Modified:
   
grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
Log:
temporarily deactivate for Python 3; see #3825

Modified: 
grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
===
--- 
grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
   2019-04-24 20:33:02 UTC (rev 74421)
+++ 
grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
   2019-04-24 20:33:36 UTC (rev 74422)
@@ -39,4 +39,8 @@


 if __name__ == '__main__':
-grass.gunittest.main.test()
+# Temporarily skip test for Python 3
+if sys.version_info[0] > 2:
+pass
+else:
+grass.gunittest.main.test()

IMHO there should be at least a message... Like this the skipped test will be 
forgotten quickly.

Just my 0.02 cents,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-SVN] r74423 - grass/trunk/raster/r.basins.fill/testsuite

[Stefan Blumentrath]

Hi Markus,

Unfortunately, the test will have to be more or less rewritten, which is why I 
for now chose to deactivate it with an info message pointing to the related 
ticket.

Alternatively, it could be shortened to the one assertModule test that it 
actually performs on r.basin.fill (see also comments in the ticket).

Also skipped tests should remain visible in test reports e.g. on fatra BTW.

Cheers
Stefan

From: grass-dev  On Behalf Of Markus Neteler
Sent: onsdag 24. april 2019 22:45
To: GRASS developers list 
Subject: Re: [GRASS-dev] [GRASS-SVN] r74423 - 
grass/trunk/raster/r.basins.fill/testsuite

Hi Stefan,
mailto:svn_gr...@osgeo.org>> schrieb am Mi., 24. Apr. 
2019, 22:41:
Author: sbl
Date: 2019-04-24 13:41:37 -0700 (Wed, 24 Apr 2019)
New Revision: 74423

Modified:
   grass/trunk/raster/r.basins.fill/testsuite/testrbf.py
Log:
deactivate erroneous test; see #3822

Modified: grass/trunk/raster/r.basins.fill/testsuite/testrbf.py
===
--- grass/trunk/raster/r.basins.fill/testsuite/testrbf.py   2019-04-24 
20:33:36 UTC (rev 74422)
+++ grass/trunk/raster/r.basins.fill/testsuite/testrbf.py   2019-04-24 
20:41:37 UTC (rev 74423)
@@ -8,8 +8,10 @@
License (>=v2). Read the file COPYING that comes with GRASS
for details.
 """
+import unittest
 from grass.gunittest.case import TestCase

+@unittest.skip("See #3822")
 class TestRasterbasin(TestCase):
 celevation='elevation'
 tgeology='geology'


Did you see the attachment?
I'd prefer to fix the test rather than skip it (and forget)...

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

Re: [GRASS-dev] [GRASS-SVN] r74422 - grass/trunk/lib/python/pygrass/modules/interface/testsuite

[Markus Neteler]

Hi,

 schrieb am Mi., 24. Apr. 2019, 22:33:

> Author: sbl
> Date: 2019-04-24 13:33:36 -0700 (Wed, 24 Apr 2019)
> New Revision: 74422
>
> Modified:
>
>  
> grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
> Log:
> temporarily deactivate for Python 3; see #3825
>
> Modified:
> grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
> ===
> ---
> grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
>  2019-04-24 20:33:02 UTC (rev 74421)
> +++
> grass/trunk/lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
>  2019-04-24 20:33:36 UTC (rev 74422)
> @@ -39,4 +39,8 @@
>
>
>  if __name__ == '__main__':
> -grass.gunittest.main.test()
> +# Temporarily skip test for Python 3
> +if sys.version_info[0] > 2:
> +pass
> +else:
> +grass.gunittest.main.test()
>

IMHO there should be at least a message... Like this the skipped test will
be forgotten quickly.

Just my 0.02 cents,
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3827: Activate Python 3 tests on the inofficial testing site (fatra)

[GRASS GIS]

#3827: Activate Python 3 tests on the inofficial testing site (fatra)
+-
 Reporter:  sbl |  Owner:  grass-dev@…
 Type:  enhancement | Status:  new
 Priority:  normal  |  Milestone:  7.8.0
Component:  Tests   |Version:  svn-trunk
 Keywords:  Python3,gunittests  |CPU:  Unspecified
 Platform:  Unspecified |
+-
 As of r74423, multirunner should be able to run the testsuite with Python
 3.

 With regards to the 7.8 release, it would be great to have the testsuite
 running with Python 3 publicly.

-- 
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] #3817: raster/r.category/test_rcategory_doctest.txt is broken

[GRASS GIS]

#3817: raster/r.category/test_rcategory_doctest.txt is broken
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Tests|Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 This is no proper gunittest and most likely therefore not included in
 fatra.

 Can be run with something like:
 ./bin.x86_64-pc-linux-gnu/grass77 -c
 ~/grassdata/nc_spm_full_v2alpha/mapset --exec python -m doctest -v
 ../grass7_trunk5/raster/r.category/test_rcategory_doctest.txt

 But should be turned into a proper gunittest I guess...

-- 
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] #3822: Tests for r.basins.fill are broken

[GRASS GIS]

#3822: Tests for r.basins.fill are broken
--+-
  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 sbl):

 The test actually only tests if the module works, but contains additinal
 tests that have nothing to to with the module in question (and rather
 tests data or other modules). Took the liberty to deactivate the test
 until fixed with proper test cases.

-- 
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-SVN] r74423 - grass/trunk/raster/r.basins.fill/testsuite

[Markus Neteler]

Hi Stefan,

 schrieb am Mi., 24. Apr. 2019, 22:41:

> Author: sbl
> Date: 2019-04-24 13:41:37 -0700 (Wed, 24 Apr 2019)
> New Revision: 74423
>
> Modified:
>grass/trunk/raster/r.basins.fill/testsuite/testrbf.py
> Log:
> deactivate erroneous test; see #3822
>
> Modified: grass/trunk/raster/r.basins.fill/testsuite/testrbf.py
> ===
> --- grass/trunk/raster/r.basins.fill/testsuite/testrbf.py   2019-04-24
> 20:33:36 UTC (rev 74422)
> +++ grass/trunk/raster/r.basins.fill/testsuite/testrbf.py   2019-04-24
> 20:41:37 UTC (rev 74423)
> @@ -8,8 +8,10 @@
> License (>=v2). Read the file COPYING that comes with GRASS
> for details.
>  """
> +import unittest
>  from grass.gunittest.case import TestCase
>
> +@unittest.skip("See #3822")
>  class TestRasterbasin(TestCase):
>  celevation='elevation'
>  tgeology='geology'
>


Did you see the attachment?
I'd prefer to fix the test rather than skip it (and forget)...

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

Re: [GRASS-dev] [GRASS GIS] #3822: Tests for r.basins.fill are broken

[GRASS GIS]

#3822: Tests for r.basins.fill are broken
--+-
  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 sbl):

 In [changeset:"74423" 74423]:
 {{{
 #!CommitTicketReference repository="" revision="74423"
 deactivate erroneous test; see #3822
 }}}

-- 
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] #3826: Fix doctests for Python 3

[GRASS GIS]

#3826: Fix doctests for Python 3
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:  7.8.0
Component:  Tests|Version:  7.2.2
 Keywords:  gunittests,doctests,Python3  |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Doctests are mainly failing in Python 3 due to unicode literals.

 Possible approaches described here:

  - https://stackoverflow.com/questions/13473971/multi-version-support-for-
 python-doctests
  - https://stackoverflow.com/questions/42158733/unicode-literals-and-
 doctest-in-python-2-7-and-python-3-5

-- 
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] #3825: Fix tests stalling with Python 3

[GRASS GIS]

#3825: Fix tests stalling with Python 3
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Tests|Version:  unspecified
Resolution:   |   Keywords:  gunittests
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 In [changeset:"74422" 74422]:
 {{{
 #!CommitTicketReference repository="" revision="74422"
 temporarily deactivate for Python 3; see #3825
 }}}

-- 
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] #3825: Fix tests stalling with Python 3

[GRASS GIS]

#3825: Fix tests stalling with Python 3
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Tests|Version:  unspecified
Resolution:   |   Keywords:  gunittests
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 In [changeset:"74421" 74421]:
 {{{
 #!CommitTicketReference repository="" revision="74421"
 temporarily deactivate for Python 3; see #3825
 }}}

-- 
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] #3825: Fix tests stalling with Python 3

[GRASS GIS]

#3825: Fix tests stalling with Python 3
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Tests|Version:  unspecified
Resolution:   |   Keywords:  gunittests
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 In [changeset:"74420" 74420]:
 {{{
 #!CommitTicketReference repository="" revision="74420"
 temporarily deactivate for Python 3; see #3825
 }}}

-- 
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] #3825: Fix tests stalling with Python 3

[GRASS GIS]

#3825: Fix tests stalling with Python 3
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:  7.8.0
Component:  Tests|Version:  unspecified
 Keywords:  gunittests   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 The following tests are stalling with Python 3 and in consequence also
 stale multirunner:
  -
 
lib/python/pygrass/modules/interface/testsuite/test_pygrass_modules_interface_doctests.py
  - lib/python/temporal/testsuite/test_temporal_doctests.py
  - temporal/t.rast.neighbors/testsuite/test_neighbors.py

 They should be deactivated until they are fixed.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] Fwd: [OSGeo] #2293: Create grass lxd container based on Debian9

[Markus Neteler]

Hi devs,

FYI

I have requested a (new and fresh) container for grass.osgeo.org in order
to get rid of the compile issues with missing libraries (zstd, geopackage,
...) we want to advertise in the manual pages etc.

Regina was so kind to set it up in no time! See the ticket for technical
details.

I'll come up with more details once things are running; this week I'm
traveling.

Cheers,
Markus


-- Forwarded message -
Von:OSGeo 
Date: Mi., 24. Apr. 2019, 19:12
Subject: [OSGeo] #2293: Create grass lxd container based on Debian9
To:
Cc: 


#2293: Create grass lxd container based on Debian9
---+--
 Reporter:  robe   |  Owner:  sac@…
 Type:  task   | Status:  new
 Priority:  normal |  Milestone:  Sysadmin Contract 2019-I
Component:  Systems Admin  |   Keywords:
---+--
 Container will be based on debian 9 template with LDAP connect.

 Will give grass folks shell access.

 grass.osgeo.org is currently running on osgeo6

-- 
Ticket URL: 
OSGeo 
OSGeo committee and general foundation issue tracker.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3824: grass python editor: add templates based on pygrass

[GRASS GIS]

#3824: grass python editor: add templates based on pygrass
-+-
 Reporter:  martinl  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.8.0
Component:  wxGUI|Version:  unspecified
 Keywords:  python, editor, pygrass  |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Currently all templates available in GRASS Python Editor are based on
 GRASS Scripting Library. Would be nice to add possibility to generate
 templates also based on PyGRASS (eg. `run_command() -> Module()`)

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GRASS Facebook group

[Isaac Ullah]

Hello all, I'm writing this short note just to let you all know about the
GRASS Facebook group (https://www.facebook.com/groups/GRASS/). I've been
managing the group for the last few years, and it has recently become more
active. Currently there are more than 2,200 members, and a lot of folks are
asking questions there that could use some input from you fine folks! I
know a few of you have joined up (thanks!), but if you haven't joined yet
and are a Facebook user, please consider joining. From my experience
managing the group, we get a different sort of user than those who would
send messages to this list (or to the grass-user list), and so it may be a
nice way for us to help support an even broader community.

Many thanks,

~Isaac

-- 
---
Isaac I. Ullah, PhD
Assistant Professor of Anthropology
Anthropology Undergraduate Adviser
San Diego State University

Modelling feedbacks between human and natural processes in the land system

Derek T. Robinson, Alan Di Vittorio, Peter Alexander, Almut Arneth, C.
Michael Barton, Daniel G. Brown, Albert Kettner, Carsten Lemmen, Brian C.
O'Neill, Marco Janssen, Thomas A. M. Pugh, Sam S. Rabin, Mark Rounsevell,
James P. Syvitski, Isaac *Ullah*, and Peter H. Verburg
Earth Syst. Dynam., 9, 895-914, https://doi.org/10.5194/esd-9-895-2018, 2018
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Addons manuals: logo and CSS file missing

[Markus Metz]

On Wed, Apr 24, 2019 at 4:28 PM Markus Neteler  wrote:
>
> Hi Martin,
>
> since the switch to use G76 as the basis for the addon manual pages,
> the two files
> grassdocs.css
> grass_logo.png
> are no longer put onto the server.
>
> I suspect that they are not picked up on the build server:
>
> grass-addons/tools/addons/grass-addons-build.sh" line 38 of 59
> cp ${SRC}/grass${1}${2}_release/${DIST}/docs/html/grassdocs.css
$HTMLDIR/
> cp ${SRC}/grass${1}${2}_release/${DIST}/docs/html/grass_logo.png
$HTMLDIR/

The reason is probably that the installation directory has been changed to
include the bugfix release number in r74038, the culprit is probably the
change in configure.in:L219 [0] which needs to be reverted.

Markus M

[0]
https://trac.osgeo.org/grass/changeset/74038/grass/branches/releasebranch_7_6/configure.in

>
> Could you please verify?
>
> thanks
> 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

[GRASS-dev] Addons manuals: logo and CSS file missing

[Markus Neteler]

Hi Martin,

since the switch to use G76 as the basis for the addon manual pages,
the two files
grassdocs.css
grass_logo.png
are no longer put onto the server.

I suspect that they are not picked up on the build server:

grass-addons/tools/addons/grass-addons-build.sh" line 38 of 59
cp ${SRC}/grass${1}${2}_release/${DIST}/docs/html/grassdocs.css $HTMLDIR/
cp ${SRC}/grass${1}${2}_release/${DIST}/docs/html/grass_logo.png $HTMLDIR/

Could you please verify?

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

Re: [GRASS-dev] [GRASS-user] Motion: Migrate SVN and trac tickets to github under OSGeo organization

[Markus Neteler]

On Mon, Apr 22, 2019 at 6:46 PM Panagiotis Mavrogiorgos
 wrote:
>>
>> in case you're not aware of it, it turns out that a number of continuous
>> integration services, like Travis-CI or AppVeyor, have concurrency limits for
>> the jobs at the GitHub organization level (ie if using OSGeo/, for all
>> repositories under OSGeo/ ). For Travis-CI, OSGeo pays Travis-CI for ~ 11
>> concurrent jobs. Primary users are currently GDAL and proj.4. For AppVeyor, 
>> we
>> use the free plan, which is limited to 1 concurrent job, and is sometimes the
>> reason for pull requests to take a significant time to be completed.
>
>
> For the record, azure pipelines offers 10 concurrent jobs for Open Source 
> projects + support for multiple operating systems.
> https://azure.microsoft.com/en-us/services/devops/pipelines/

Thanks for the hint, added under
https://trac.osgeo.org/grass/wiki/GitMigration#CICDandQA

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