Re: [GRASS-dev] [GRASS-user] Example project on GitLab

2018-11-07 Thread Vaclav Petras
On Wed, Nov 7, 2018 at 8:47 AM Bernardo Santos <
bernardo_brand...@yahoo.com.br> wrote:

>
> thanks for that, it'll be very useful. I think a similar approach can be
> used to build repositories for addons within GitHub, right?
>

Yes, when you involve Travis CI.


> Do you see clear advantages of using GitLab instead of GitHub for this
> purposes?
>

One other reason besides the private repos mentioned by KenM, the CI is
much better integrated then GitHub and Travis CI, so for example, you don't
have to pass any tokens to connect them bidirectionally in order to publish
web pages build by CI. The built web pages on GitLab don't need to be part
of the repository which may have some drawbacks but it is mostly an
advantage I would say. This is all kind of related to the GitLab approach
to the project - it is a primary a project and Git repo is just part of it
(GitHub interface is built around a repo).

Another thing is that you can download all the data and upload it to your
own GitLab instance if you don't want to use gitlab.com anymore (at least
that's what they claim). This relates to the fact that (most of) GitLab
itself is actually open source (!).

I'm not sure if it is an advantage for real work, but I personally enjoyed
working with the GitLab WebIDE and I created the whole example just using
that although at this point is misses spell check and you need to commit in
order to run the code.

One disadvantage of GitLab is that the CI is Linux only while GitHub has
macOS and recently they added Windows too.

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

Re: [GRASS-dev] [GRASS GIS] #3226: v.select: how to handle situation where no features are found

2018-11-07 Thread GRASS GIS
#3226: v.select: how to handle situation where no features are found
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.select
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mmetz):

 Replying to [comment:9 mlennert]:
 > Actually, the applied patch did not solve the problem as the (empty) map
 was still created, but not correctly. In r73652 and r73652 I've applied a
 further modification which only goes the different aspects of creating the
 new map if elements were found. I would consider this a bug fix, so it
 should go into 74 as well, but I haven't had the time to test extensively.
 I'm thus not sure whether I should upload it into release74. I don't think
 it will cause any trouble, but MarkusM, could you have a look ?

 Trunk r73652 looks good to me and it works as expected.

 Another reason why no output is created could be that the module failed
 for any reason (return code != 0), i.e. the return code needs to be
 checked as usual.

 +1 for backporting

-- 
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] #3226: v.select: how to handle situation where no features are found

2018-11-07 Thread GRASS GIS
#3226: v.select: how to handle situation where no features are found
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.select
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mlennert):

 FYI: I did run the testsuite on v.select and it did not find any issues.

-- 
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] #3226: v.select: how to handle situation where no features are found

2018-11-07 Thread GRASS GIS
#3226: v.select: how to handle situation where no features are found
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.select
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mlennert):

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


Comment:

 Actually, the applied patch did not solve the problem as the (empty) map
 was still created, but not correctly. In r73652 and r73652 I've applied a
 further modification which only goes the different aspects of creating the
 new map if elements were found. I would consider this a bug fix, so it
 should go into 74 as well, but I haven't had the time to test extensively.
 I'm thus not sure whether I should upload it into release74. I don't think
 it will cause any trouble, but MarkusM, could you have a look ?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Problem starting GRASS GUI - ntpath splitdrive

2018-11-07 Thread Pedro Venâncio
Hi Martin,

Yes, I tried to update wxPython by pip, but it does not solved the problem.

Returning to 2.8.12 also does not help:

C:\>pip uninstall wxpython
Uninstalling wxPython-4.0.3:
  Would remove:
c:\osgeo4~1\apps\python27\lib\site-packages\wx\*
c:\osgeo4~1\apps\python27\lib\site-packages\wxpython-4.0.3.dist-info\*
c:\osgeo4~1\apps\python27\scripts\helpviewer.exe
c:\osgeo4~1\apps\python27\scripts\img2png.exe
c:\osgeo4~1\apps\python27\scripts\img2py.exe
c:\osgeo4~1\apps\python27\scripts\img2xpm.exe
c:\osgeo4~1\apps\python27\scripts\pycrust.exe
c:\osgeo4~1\apps\python27\scripts\pyshell.exe
c:\osgeo4~1\apps\python27\scripts\pyslices.exe
c:\osgeo4~1\apps\python27\scripts\pyslicesshell.exe
c:\osgeo4~1\apps\python27\scripts\pywxrc.exe
c:\osgeo4~1\apps\python27\scripts\wxdemo.exe
c:\osgeo4~1\apps\python27\scripts\wxdocs.exe
c:\osgeo4~1\apps\python27\scripts\wxget.exe
Proceed (y/n)? y
  Successfully uninstalled wxPython-4.0.3
You are using pip version 18.0, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip'
command.

C:\>grass74
Cleaning up temporary files...
Starting GRASS GIS...
ATENÇÃO: Concurrent mapset locking is not supported on Windows

  __  ___   _____
 / / __ \/   | / ___/ ___/   / /  _/ ___/
/ / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
   / /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
   \/_/ |_/_/  |_///   \/___///

Welcome to GRASS GIS 7.4.2
GRASS GIS homepage:  http://grass.osgeo.org
This version running through:Command Shell
(C:\WINDOWS\system32\cmd.exe)
Help is available with the command:  g.manual -i
See the licence terms with:  g.version -c
See citation options with:   g.version -x
Start the GUI with:  g.gui wxpython
When ready to quit enter:exit

Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos os direitos reservados.

C:\>g.gui wxpython
Launching  GUI in the background, please wait...

C:\>python
Python 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:25:58) [MSC v.1500 64
bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

>>> import wx
>>> wx.version()
'2.8.12.1 (msw-unicode)'

>>> import sys
>>> print '\n'.join(sys.path)

C:\OSGEO4~1\apps\grass\grass-7.4.2\etc\python
C:\OSGeo4W64\apps\Python27
C:\OSGEO4~1\bin\python27.zip
C:\OSGEO4~1\apps\Python27\DLLs
C:\OSGEO4~1\apps\Python27\lib
C:\OSGEO4~1\apps\Python27\lib\plat-win
C:\OSGEO4~1\apps\Python27\lib\lib-tk
C:\OSGEO4~1\bin
C:\OSGEO4~1\apps\Python27
C:\OSGEO4~1\apps\Python27\lib\site-packages
C:\OSGEO4~1\apps\Python27\lib\site-packages\jinja2-2.7.2-py2.7.egg
C:\OSGEO4~1\apps\Python27\lib\site-packages\markupsafe-0.23-py2.7-win-amd64.egg
C:\OSGEO4~1\apps\Python27\lib\site-packages\win32
C:\OSGEO4~1\apps\Python27\lib\site-packages\win32\lib
C:\OSGEO4~1\apps\Python27\lib\site-packages\Pythonwin
C:\OSGEO4~1\apps\Python27\lib\site-packages\wx-2.8-msw-unicode

Thanks!

Best regards,
Pedro



Martin Landa  escreveu no dia quarta, 7/11/2018
à(s) 12:52:

> Hi,
>
> st 7. 11. 2018 v 12:02 odesílatel Pedro Venâncio
>  napsal:
> > >>> import wx
> > >>> wx.version()
> > u'4.0.3 msw (phoenix) wxWidgets 3.0.5'
>
> btw, have you installed wxPython on your own by pip? OSGeo4W still
> comes with version 2.8.12 [1]
>
> Ma
>
> [1] https://download.osgeo.org/osgeo4w/x86_64/release/python/python-wx/
>
> --
> 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] Problem starting GRASS GUI - ntpath splitdrive

2018-11-07 Thread Martin Landa
Hi,

st 7. 11. 2018 v 12:02 odesílatel Pedro Venâncio
 napsal:
> >>> import wx
> >>> wx.version()
> u'4.0.3 msw (phoenix) wxWidgets 3.0.5'

btw, have you installed wxPython on your own by pip? OSGeo4W still
comes with version 2.8.12 [1]

Ma

[1] https://download.osgeo.org/osgeo4w/x86_64/release/python/python-wx/

-- 
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] Problem starting GRASS GUI - ntpath splitdrive

2018-11-07 Thread Pedro Venâncio
Hi all,

I've done some more tests:

C:\>grass74
Cleaning up temporary files...
Starting GRASS GIS...
ATENÇÃO: Concurrent mapset locking is not supported on Windows

  __  ___   _____
 / / __ \/   | / ___/ ___/   / /  _/ ___/
/ / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
   / /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
   \/_/ |_/_/  |_///   \/___///

Welcome to GRASS GIS 7.4.2
GRASS GIS homepage:  http://grass.osgeo.org
This version running through:Command Shell
(C:\WINDOWS\system32\cmd.exe)
Help is available with the command:  g.manual -i
See the licence terms with:  g.version -c
See citation options with:   g.version -x
Start the GUI with:  g.gui wxpython
When ready to quit enter:exit

Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos os direitos reservados.

C:\>g.gui wxpython
Launching  GUI in the background, please wait...

C:\>python
Python 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:25:58) [MSC v.1500 64
bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

>>> import wx
>>> wx.version()
u'4.0.3 msw (phoenix) wxWidgets 3.0.5'

>>> import sys
>>> sys.executable
'C:\\OSGEO4~1\\bin\\python.exe'

>>> print '\n'.join(sys.path)
C:\OSGEO4~1\apps\grass\grass-7.4.2\etc\python
C:\OSGeo4W64\apps\Python27
C:\OSGEO4~1\bin\python27.zip
C:\OSGEO4~1\apps\Python27\DLLs
C:\OSGEO4~1\apps\Python27\lib
C:\OSGEO4~1\apps\Python27\lib\plat-win
C:\OSGEO4~1\apps\Python27\lib\lib-tk
C:\OSGEO4~1\bin
C:\OSGEO4~1\apps\Python27
C:\OSGEO4~1\apps\Python27\lib\site-packages
C:\OSGEO4~1\apps\Python27\lib\site-packages\jinja2-2.7.2-py2.7.egg
C:\OSGEO4~1\apps\Python27\lib\site-packages\markupsafe-0.23-py2.7-win-amd64.egg
C:\OSGEO4~1\apps\Python27\lib\site-packages\win32
C:\OSGEO4~1\apps\Python27\lib\site-packages\win32\lib
C:\OSGEO4~1\apps\Python27\lib\site-packages\Pythonwin
C:\OSGEO4~1\apps\Python27\lib\site-packages\wx-2.8-msw-unicode
>>>

>>> quit()

C:\>where python
C:\OSGeo4W64\bin\python.exe

Any suggestion about other tests I can run to check if something is missing?


I also tried to install GRASS 6.4 with OSGeo4W, but this time I get this
error:

C:\>grass64
Traceback (most recent call last):
  File "C:/OSGEO4~1/apps/grass/grass-6.4.3/etc/wxpython/wxgui.py", line 34,
in 
from lmgr.frame import GMFrame
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\lmgr\frame.py",
line 46, in 
from lmgr.layertreeimport LayerTree, LMIcons
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\lmgr\layertree.py",
line 37, in 
from mapdisp.frame   import MapFrame
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\mapdisp\frame.py",
line 38, in 
from vdigit.toolbarsimport VDigitToolbar
  File
"C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\vdigit\toolbars.py", line
23, in 
from vdigit.mainimport VDigit
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\vdigit\main.py",
line 18, in 
from vdigit.wxdigit import IVDigit, GV_LINES
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\vdigit\wxdigit.py",
line 33, in 
from vdigit.wxdisplay import DisplayDriver
  File
"C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\wxpython\vdigit\wxdisplay.py", line
29, in 
from grass.lib.vector import *
  File "C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\python\grass\lib\vector.py",
line 23, in 
_libs["grass_vect.6.4.3"] = load_library("grass_vect.6.4.3")
  File
"C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\python\grass\lib\ctypes_loader.py",
line 55, in load_library
return self.load(path)
  File
"C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\python\grass\lib\ctypes_loader.py",
line 221, in load
return _WindowsLibrary(path)
  File
"C:\OSGEO4~1\apps\grass\grass-6.4.3\etc\python\grass\lib\ctypes_loader.py",
line 207, in __init__
self.cdll = ctypes.cdll.LoadLibrary(path)
  File "C:\OSGEO4~1\apps\Python27\lib\ctypes\__init__.py", line 444, in
LoadLibrary
return self._dlltype(name)
  File "C:\OSGEO4~1\apps\Python27\lib\ctypes\__init__.py", line 366, in
__init__
self._handle = _dlopen(self._name, mode)
WindowsError: [Error 126] The specified module could not be found


C:\>grass64 -text

Welcome to GRASS 6.4.3 (2013)

GRASS homepage:  http://grass.osgeo.org/
This version running thru:   Windows Command Shell (cmd.exe)
When ready to quit enter:exit
Help is available with the command:  g.manual -i
See the licence terms with:  g.version -c

Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. Todos os direitos reservados.

GRASS 6.4.3 (pinhel)> g.gui

Launching 'wxpython' GUI in the background, please wait ...
Traceback (most recent call last):
  File "C:/OSGEO4~1/apps/grass/grass-6.4.3/etc/wxpython/wxgui.py", line 34,
in 
from lmgr.frame import GMF