Re: [GRASS-dev] svn/trac -> git/github migration plan

[Vaclav Petras]

On Wed, May 15, 2019 at 4:24 PM Markus Neteler  wrote:
>
> On Wed, May 15, 2019 at 10:20 PM Luca Delucchi 
wrote:
> > On Wed, 15 May 2019 at 21:40, Veronica Andreo 
wrote:
> > >> Another thing is the need for new contributing guidelines. Git is
not Subversion and committing to master won't work (please, let me know if
you want me to show some examples).
> > >
> > > I am very interested in such examples, esp. how the workflow will be
from now on for example when making a small change in manuals.
> >
> > Yes, it is important to know this. How to use branches and also how to
> > update local version from the master one. Should we use a private
> > clone and make pull request to the main repository o use the main
> > repository directly?
>
> AFAIK it is recommended to open an own "feature branch" in the own
> fork and then open a pull request.

Exactly. The important part to recognize is that trying to emulate the
Subversion workflow, i.e. simply committing to master, would soon turn into
a repo full of automatic merge commits in the best case and big confusion
in the worst case. Basically all projects (I think I checked QGIS, PROJ,
GDAL, PDAL) have fork+branch+pull request as their best practice. This
means that even if you are a core developer, you still should do that. The
exception common for the core developers is that they skip the fork part,
i.e. they branch in the main repo. However, I haven't seen that formalized,
so I think it is a tolerated practice rather than a guideline.

Hopefully, for the general case, GRASS GIS will not need any special
instructions. Often projects simply point to GitHub documentation for
making and maintaining a fork and making a pull request.

Although there will be extra steps for the people with direct access to
source code comparing to Subversion, the benefit is that there is (will be)
actually an extra step and that's CI build and (hopefully) test as well.
This should catch many issues before they get to master.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Microsoft's SPTAG search algorithm

[Nikos Alexandris]

Perhaps of interest: https://github.com/microsoft/SPTAG

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

Re: [GRASS-dev] [GRASS GIS] #3225: r.plane: ValueError: invalid literal for float(): 0:04:14.5E

[GRASS GIS]

#3225: r.plane: ValueError: invalid literal for float(): 0:04:14.5E
--+-
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:  r.plane
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by lucadelu):

 In [changeset:"74485" 74485]:
 {{{
 #!CommitTicketReference repository="" revision="74485"
 libpython: float_or_dms accept E,W,N,S. see #3225
 }}}

-- 
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 on an Alpine Linux docker

[Markus Neteler]

Hi again,

On Wed, May 15, 2019 at 3:18 PM Pietro  wrote:
>
> Dear all,
>
> Recently I've started looking for a docker image with GRASS, I'm looking for 
> a minimal image that is as small as possible.
> From my test the other images available where always above 1GB of size, the 
> current version once built have a size of ~220 MB.
> Another difference respect to others dockers available that I found is that 
> it is possible to select which version use when building the image:
>
> ```
> sudo docker build --build-arg GRASS_VERSION=7.7 \
>   --build-arg PYTHON_VERSION=3  \
>   --build-arg PROJ_VERSION=5.2.0 \
>   --build-arg PROJ_DATUMGRID_VERSION=1.8 \
>   --volume \
>   zarch/alpine-grass-gis
> ```
>
> You can find the repository here:
>
> https://github.com/zarch/docker-alpine-grass-gis
>
> Do you have any feedback?

It looks much better now than my old attempts - thank you :)

> Any hint to improve the `Dockerfile` or the `README.md` are welcome. :-)

I'll give it a try as will report back.

Best
Markus

> Thank you for the support.
> Best regards
>
> Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
>> which is the relevant xml-file?
>>
> 
> it creates gui/wxpython/xml/menudata.xml and module_tree_menudata.xml
> during compilation.

module_tree_menudata.xml is empty here. I have to wait for the next daily
build to test.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3227: g.gui.rlisetup: possibility to execute in command line ?

[GRASS GIS]

#3227: g.gui.rlisetup: possibility to execute in command line ?
--+-
  Reporter:  tgrippa  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  8.0.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  All
--+-
Changes (by lucadelu):

 * version:  unspecified => svn-trunk
 * milestone:  7.0.7 => 8.0.0


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] pywin32 missing

[Anna Petrášová]

On Wed, May 15, 2019 at 4:14 PM Helmut Kudrnovsky  wrote:

> Anna Petrášová wrote
> > Did you compile it with those local changes? It needs to be compiled to
> > create the xml files.
>
> no compilation yet, just copied the updated python script.
>
> which is the relevant xml-file?
>

it creates gui/wxpython/xml/menudata.xml and module_tree_menudata.xml
during compilation.


>
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> 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] svn/trac -> git/github migration plan

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Wed, May 15, 2019 at 9:32 PM Helmut Kudrnovsky 

> hellik@

>  wrote:
>>
>> Markus Neteler wrote
>> > So, if someone isn't listed yet:
>> > Please get a GitHub account and/or communicate it to us (name + related
>> > email).
>>
>> svn: hellik
>>
>> gh account: hellik
> 
> You were already in the list.
> 
> But:
> 
>> email: 

> hkmyricaria@

> 
> Your 

> hellik@

>  is apparently not yet registered at Github.
> Solution:
> 
> Or, simply, to match your commits to your GitHub account, just add
> your associated email address(es) to your account in order to claim
> your contributions (https://github.com/settings/emails).
> 
> Then you should show up there after some minutes or so.

additional email in my github account added, so lets see 




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

On Wed, May 15, 2019 at 10:20 PM Luca Delucchi  wrote:
> On Wed, 15 May 2019 at 21:40, Veronica Andreo  wrote:
> >> Another thing is the need for new contributing guidelines. Git is not 
> >> Subversion and committing to master won't work (please, let me know if you 
> >> want me to show some examples).
> >
> > I am very interested in such examples, esp. how the workflow will be from 
> > now on for example when making a small change in manuals.
>
> Yes, it is important to know this. How to use branches and also how to
> update local version from the master one. Should we use a private
> clone and make pull request to the main repository o use the main
> repository directly?

AFAIK it is recommended to open an own "feature branch" in the own
fork and then open a pull request.

Concerning backports we could check the bot magic used by other OSGeo projects.

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Luca Delucchi]

On Wed, 15 May 2019 at 21:40, Veronica Andreo  wrote:
>
> Hi,
>

Hi,


>> Another thing is the need for new contributing guidelines. Git is not 
>> Subversion and committing to master won't work (please, let me know if you 
>> want me to show some examples).
>
>
> I am very interested in such examples, esp. how the workflow will be from now 
> on for example when making a small change in manuals.
>

Yes, it is important to know this. How to use branches and also how to
update local version from the master one. Should we use a private
clone and make pull request to the main repository o use the main
repository directly?

> I think it is very important that those of you more familiar with git and 
> GitHub develop or show example workflows of how to contribute, backport (if 
> that will be still called like that), and so on.
>

+1

> my 0.01 cent
> Vero
>

-- 
ciao
Luca

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

Re: [GRASS-dev] pywin32 missing

[Helmut Kudrnovsky]

Helmut Kudrnovsky wrote
> there is no win32-site package inside.
> 
> it's an package issue.

looking at
https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Packager.bat.tmpl#L98

96  @echo.
97  @echo
---
98  @echo Copy Python content to PACKAGE_DIR\Python37
99  @echo
---
100 @echo.
101 
102 mkdir %PACKAGE_DIR%\Python37
103 
104 xcopy %OSGEO4W_PKG_DIR%\apps\Python37\* %PACKAGE_DIR%\Python37 /S/V/F/I

the OSGeo4W-package environment on Martin's build server has to be upated to
include pywin32.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

On Wed, May 15, 2019 at 9:32 PM Helmut Kudrnovsky  wrote:
>
> Markus Neteler wrote
> > So, if someone isn't listed yet:
> > Please get a GitHub account and/or communicate it to us (name + related
> > email).
>
> svn: hellik
>
> gh account: hellik

You were already in the list.

But:

> email: hkmyrica...@gmail.com

Your hel...@web.de is apparently not yet registered at Github.
Solution:

Or, simply, to match your commits to your GitHub account, just add
your associated email address(es) to your account in order to claim
your contributions (https://github.com/settings/emails).

Then you should show up there after some minutes or so.

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

On Wed, May 15, 2019 at 9:27 PM Vaclav Petras  wrote:
> On Wed, May 15, 2019 at 12:47 PM Markus Neteler  wrote:
>> Later on, also commit claiming is possible and easy, so nothing is lost.
>
> Sounds good. I didn't know. We just have to be very clear about the current 
> state not capturing everyone.

So I wrote this section just now:
https://trac.osgeo.org/grass/wiki/GitMigration#Authorship:RecognizingtheGRASSGIScontributorsduringandaftermigration

Feel free to improve the wording.

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

Re: [GRASS-dev] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
> Did you compile it with those local changes? It needs to be compiled to
> create the xml files.

no compilation yet, just copied the updated python script.

which is the relevant xml-file?




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
>> are the related python packages in the bundled python
>> (Python37\lib\site-packages\win32)?
>>
> 
> no, win32 was not there as far as I remember

looking at 

https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/setup_x86_64.hint.tmpl

requires: liblas avce00 gpsbabel gs python3-gdal python3-matplotlib msvcrt
msvcrt2013 msvcrt2015 iconv libtiff gdal proj pdcurses zlib fftw libpng
python3-wx python3-numpy python3-pillow python3-pip python3-ply
python3-pyopengl cairo python3-psycopg2 python3-six rbatch zstd zstd-bin
python3-pywin32 <=

https://trac.osgeo.org/grass/browser/grass/trunk/mswindows/osgeo4w/setup_x86.hint.tmpl

requires: liblas avce00 gpsbabel gs python3-gdal python3-matplotlib msvcrt
msvcrt2013 msvcrt2015 iconv libtiff gdal proj freetype-mingw pdcurses zlib
fftw libpng python3-wx python3-numpy python3-pillow python3-pip python3-ply
python3-pyopengl cairo python3-psycopg2 python3-six rbatch zstd zstd-bin
python3-pywin32

there is pywin32 as a requirement for winGRASS.

comparing the OSGeo4W python3

C:\OSGeo4W64\apps\Python37\lib\site-packages\win32\

and a win32file inside

with a just downloaded
https://wingrass.fsv.cvut.cz/grass77/x86_64/WinGRASS-7.7.svn-r74475M-23-Setup-x86_64.exe

WinGRASS-7.7.svn-r74475M-23-Setup-x86_64\$_93_\Python37\Lib\site-packages

there is no win32-site package inside.

it's an package issue.









-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pywin32 missing

[Anna Petrášová]

Did you compile it with those local changes? It needs to be compiled to
create the xml files.

On Wed, May 15, 2019 at 3:56 PM Helmut Kudrnovsky  wrote:

> Anna Petrášová wrote
> > Hi,
> >
> > I am testing some changes in Python library on Windows and when I get
> over
> > the current problem, I run into that I can't import win32file in
> > core/gcmd.py. Some problem with packaging?
>
> applied locally your commits (r74480), I get:
>
> 
> C:\>grass77svn --text
> Starting GRASS GIS...
> WARNUNG: Sperren gleichzeitiger Zugriffe auf ein Mapset ist unter Windows
>  nicht möglich.
> Cleaning up temporary files...
>
>   __  ___   _____
>  / / __ \/   | / ___/ ___/   / /  _/ ___/
> / / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
>/ /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
>\/_/ |_/_/  |_///   \/___///
>
> Welcome to GRASS GIS 7.7.svn (r74474M)
> GRASS GIS homepage:  https://grass.osgeo.org
> This version running through:Command Prompt
> (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.17763.475]
> (c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.
>
> C:\>g.gui wxpython
> Starte  GUI im Hintergrund. Bitte warten Sie ...
> C:\OSGEO4~1\apps\grass\grass77/gui/wxpython/wxgui.py:101:
> DeprecationWarning: Yield() is deprecated
>   wx.Yield()
> Traceback (most recent call last):
>   File "C:\OSGEO4~1\apps\grass\grass77/gui/wxpython/wxgui.py", line 106, in
> OnInit
> workspace=self.workspaceFile)
>   File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\lmgr\frame.py", line
> 131, in __init__
> self._moduleTreeBuilder =
> LayerManagerModuleTree(message_handler=add_menu_error)
>   File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\lmgr\menudata.py", line
> 68, in __init__
> message_handler=message_handler)
>   File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\core\menutree.py", line
> 71, in __init__
> xmlTree = etree.parse(filename)
>   File "C:\OSGEO4~1\apps\Python37\lib\xml\etree\ElementTree.py", line 1197,
> in parse
> tree.parse(source, parser)
>   File "C:\OSGEO4~1\apps\Python37\lib\xml\etree\ElementTree.py", line 598,
> in parse
> self._root = parser._parse_whole(source)
> xml.etree.ElementTree.ParseError: no element found: line 1, column 0
> OnInit returned false, exiting...
> 
>
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> 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] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
> Hi,
> 
> I am testing some changes in Python library on Windows and when I get over
> the current problem, I run into that I can't import win32file in
> core/gcmd.py. Some problem with packaging?

applied locally your commits (r74480), I get:


C:\>grass77svn --text
Starting GRASS GIS...
WARNUNG: Sperren gleichzeitiger Zugriffe auf ein Mapset ist unter Windows
 nicht möglich.
Cleaning up temporary files...

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

Welcome to GRASS GIS 7.7.svn (r74474M)
GRASS GIS homepage:  https://grass.osgeo.org
This version running through:Command Prompt
(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.17763.475]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

C:\>g.gui wxpython
Starte  GUI im Hintergrund. Bitte warten Sie ...
C:\OSGEO4~1\apps\grass\grass77/gui/wxpython/wxgui.py:101:
DeprecationWarning: Yield() is deprecated
  wx.Yield()
Traceback (most recent call last):
  File "C:\OSGEO4~1\apps\grass\grass77/gui/wxpython/wxgui.py", line 106, in
OnInit
workspace=self.workspaceFile)
  File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\lmgr\frame.py", line
131, in __init__
self._moduleTreeBuilder =
LayerManagerModuleTree(message_handler=add_menu_error)
  File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\lmgr\menudata.py", line
68, in __init__
message_handler=message_handler)
  File "C:\OSGEO4~1\apps\grass\grass77\gui\wxpython\core\menutree.py", line
71, in __init__
xmlTree = etree.parse(filename)
  File "C:\OSGEO4~1\apps\Python37\lib\xml\etree\ElementTree.py", line 1197,
in parse
tree.parse(source, parser)
  File "C:\OSGEO4~1\apps\Python37\lib\xml\etree\ElementTree.py", line 598,
in parse
self._root = parser._parse_whole(source)
xml.etree.ElementTree.ParseError: no element found: line 1, column 0
OnInit returned false, exiting...





-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pywin32 missing

[Anna Petrášová]

On Wed, May 15, 2019 at 3:48 PM Helmut Kudrnovsky  wrote:

> Anna Petrášová wrote
> > standalone
>
> trying here with OSGeo4W-winGRASS7.7.svn
>
> #
> C:\>grass77svn ---text D:\grassdata\nc_spm_08_grass7\user1
> Starting GRASS GIS...
> WARNUNG: Sperren gleichzeitiger Zugriffe auf ein Mapset ist unter Windows
>  nicht möglich.
> Cleaning up temporary files...
>
>   __  ___   _____
>  / / __ \/   | / ___/ ___/   / /  _/ ___/
> / / __/ /_/ / /| | \__ \\_  \   / / __ / / \__ \
>/ /_/ / _, _/ ___ |___/ /__/ /  / /_/ // / ___/ /
>\/_/ |_/_/  |_///   \/___///
>
> Welcome to GRASS GIS 7.7.svn (r74474M)
> GRASS GIS homepage:  https://grass.osgeo.org
> This version running through:Command Prompt
> (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
> If required, restart the GUI with:   g.gui wxpython
> When ready to quit enter:exit
>
> Launching  GUI in the background, please wait...
> Microsoft Windows [Version 10.0.17763.475]
> (c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.
>
> C:\>g.version --help
> Displays GRASS GIS version info.
>
> Benutzung:
>  g.version [-cxbreg] [--help] [--verbose] [--quiet] [--ui]
>
> Schalter:
>   -c   Gebe auch die Copyright-Informationen aus
>   -x   Print also the citation options
>   -b   Print also the build information
>   -r   Print also the GIS library revision number and date
>   -e   Print also extended info for additional libraries
>   -g   Gebe Info im Shell-Skript-Style aus (inklusive SVN Revisionsnummer)
>
> C:\>python
> Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit
> (AMD64)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> import win32com.client as win32
> >>> import win32api
> >>> import win32file
> >>>
>
> #
>
> pywin32 and related things seems to work here.
>
> are the related python packages in the bundled python
> (Python37\lib\site-packages\win32)?
>

no, win32 was not there as far as I remember

>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> 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] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
> standalone

trying here with OSGeo4W-winGRASS7.7.svn

#
C:\>grass77svn ---text D:\grassdata\nc_spm_08_grass7\user1
Starting GRASS GIS...
WARNUNG: Sperren gleichzeitiger Zugriffe auf ein Mapset ist unter Windows
 nicht möglich.
Cleaning up temporary files...

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

Welcome to GRASS GIS 7.7.svn (r74474M)
GRASS GIS homepage:  https://grass.osgeo.org
This version running through:Command Prompt
(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
If required, restart the GUI with:   g.gui wxpython
When ready to quit enter:exit

Launching  GUI in the background, please wait...
Microsoft Windows [Version 10.0.17763.475]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.

C:\>g.version --help
Displays GRASS GIS version info.

Benutzung:
 g.version [-cxbreg] [--help] [--verbose] [--quiet] [--ui]

Schalter:
  -c   Gebe auch die Copyright-Informationen aus
  -x   Print also the citation options
  -b   Print also the build information
  -r   Print also the GIS library revision number and date
  -e   Print also extended info for additional libraries
  -g   Gebe Info im Shell-Skript-Style aus (inklusive SVN Revisionsnummer)

C:\>python
Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> import win32com.client as win32
>>> import win32api
>>> import win32file
>>>

#

pywin32 and related things seems to work here.

are the related python packages in the bundled python
(Python37\lib\site-packages\win32)?



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Veronica Andreo]

Hi,

El mié., 15 may. 2019 13:20, Vaclav Petras  escribió:

>
>
> On Wed, May 15, 2019 at 9:14 AM Martin Landa 
> wrote:
>
>> Hi,
>>
>> st 15. 5. 2019 v 9:51 odesílatel Martin Landa 
>> napsal:
>> > Something strange happen with svn repo after r74441. I will publish
>> > testing repo for public review hopefully today.
>>
>> OK, finally a new fresh grass repo preview available for review (last
>> processed commit 74475).
>>
>> Please compare git content [1], branches [2] and tags [3] with svn.
>> Please review logs reporting changed message [4] and unchanged
>> messages [5].
>
>
> I was also looking at the list of contributors [6]. I know this was
> discussed, but now I'm not really sure what to expect there.
>
> [6] https://github.com/grass-svn2git/grass/graphs/contributors
>
>
>> If no problems appears this will be the last
>> preview before REAL migration.
>>
>
> When comparing the content of the repositories, I see the difference in
> $Date$ which of course has the whole system related to it. What we are
> doing with that?
>
> Another thing is the need for new contributing guidelines. Git is not
> Subversion and committing to master won't work (please, let me know if you
> want me to show some examples).
>

I am very interested in such examples, esp. how the workflow will be from
now on for example when making a small change in manuals.

I think it is very important that those of you more familiar with git and
GitHub develop or show example workflows of how to contribute, backport (if
that will be still called like that), and so on.

my 0.01 cent
Vero


What other OSGeo projects are doing is that contributing guidelines say
> that you should do pull request. It seems that this is often preferred way
> even for core developers. From what I gathered from a small sample of
> people at OSGeo sprint, the core devs don't go though fork, but they do go
> through a branch. In GitHub, we can set "Require pull request reviews
> before merging" and "Include administrators" for the master branch to
> enforce that. I think we should do it at least at the beginning.
>
> Vaclav
>
>
>>
>> [1] https://github.com/grass-svn2git/grass
>> [2] https://github.com/grass-svn2git/grass
>> [3] https://github.com/grass-svn2git/grass/releases
>> [4] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_touched.txt
>> [5] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_untouched.txt
>>
>> --
>> 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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Helmut Kudrnovsky]

Markus Neteler wrote
> So, if someone isn't listed yet:
> Please get a GitHub account and/or communicate it to us (name + related
> email).

svn: hellik

gh account: hellik
email: hkmyrica...@gmail.com




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Vaclav Petras]

On Wed, May 15, 2019 at 12:47 PM Markus Neteler  wrote:

>
> Later on, also commit claiming is possible and easy, so nothing is lost.
>

Sounds good. I didn't know. We just have to be very clear about the current
state not capturing everyone.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pywin32 missing

[Anna Petrášová]

standalone

On Wed, May 15, 2019 at 1:57 PM Helmut Kudrnovsky  wrote:

> Anna Petrášová wrote
> > Hi,
> >
> > I am testing some changes in Python library on Windows and when I get
> over
> > the current problem, I run into that I can't import win32file in
> > core/gcmd.py. Some problem with packaging?
> >
> > Thank you,
> >
> > Anna
> >
> > ___
> > grass-dev mailing list
>
> > grass-dev@.osgeo
>
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>
> winGRASS 7.7.svn standalone or OSGeo4W-winGRASS7.7.svn?
>
>
>
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> 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] pywin32 missing

[Helmut Kudrnovsky]

Anna Petrášová wrote
> Hi,
> 
> I am testing some changes in Python library on Windows and when I get over
> the current problem, I run into that I can't import win32file in
> core/gcmd.py. Some problem with packaging?
> 
> Thank you,
> 
> Anna
> 
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-dev

winGRASS 7.7.svn standalone or OSGeo4W-winGRASS7.7.svn?



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3781: v.in.geonames - fails in winGRASS7.7 (python3)

[GRASS GIS]

#3781: v.in.geonames - fails in winGRASS7.7 (python3)
-+--
  Reporter:  hellik  |  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.8.0
 Component:  Python  |Version:  svn-trunk
Resolution:  |   Keywords:  python3, py3
   CPU:  x86-64  |   Platform:  MSWindows
-+--

Comment (by annakrat):

 In [changeset:"74481" 74481]:
 {{{
 #!CommitTicketReference repository="" revision="74481"
 v.in.geonames: read as utf8, see #3781
 }}}

-- 
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] #3846: r.contour started producing broken/segmented contour lines since 7.4

[GRASS GIS]

#3846: r.contour started producing broken/segmented contour lines since 7.4
---+-
 Reporter:  metello|  Owner:  grass-dev@…
 Type:  defect | Status:  new
 Priority:  normal |  Milestone:
Component:  Raster |Version:  unspecified
 Keywords:  r.contour  |CPU:  x86-64
 Platform:  MSWindows  |
---+-
 Since GRASS 7.4, some contour lines generated by r.contour are broken into
 several segments (until 7.2 was ok). I have a system that uses r.contour
 to trace reservoirs for hydroelectric plants and that problem is breaking
 my algorithm.
 In the attached GRASS project, you can see the result generated by
 different GRASS versions (contour level = 229) - look at the largest
 contour line. I tested the following versions: 7.2.3, 7.4.4, 7.6 and
 7.7svn. Only 7.2.3 produced a continuous/unbroken contour.

-- 
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 on an Alpine Linux docker

[Markus Neteler]

Hi

Martin Landa  schrieb am Mi., 15. Mai 2019, 15:30:

> Hi,
>
> st 15. 5. 2019 v 15:18 odesílatel Pietro  napsal:
> > Recently I've started looking for a docker image with GRASS, I'm looking
> for a minimal image that is as small as possible.
> > From my test the other images available where always above 1GB of size,
> the current version once built have a size of ~220 MB.
>

I also made an Alpine based docker some time ago, see GitHub. Lately it
didn't build any more but I didn't have time to fix it.

> Another difference respect to others dockers available that I found is
> that it is possible to select which version use when building the image:
>
> great, probably we should start collecting all GRASS-related dockers
> on GRASS wiki?
>


Yes. At time they are collected here

https://grass.osgeo.org/download/software/docker-images/

I think that the wiki might be better.

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

Re: [GRASS-dev] pywin32 missing

[Anna Petrášová]

Related to wingrass, I committed some changes in script/core.py which might
break something because I can't test it properly on Windows, but hopefully
it will fix some issues

On Wed, May 15, 2019 at 12:44 PM Anna Petrášová 
wrote:

> Hi,
>
> I am testing some changes in Python library on Windows and when I get over
> the current problem, I run into that I can't import win32file in
> core/gcmd.py. Some problem with packaging?
>
> Thank you,
>
> Anna
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

Hi,

a quick comment on this one:


Vaclav Petras  schrieb am Mi., 15. Mai 2019, 18:20:

>
> ...

> I was also looking at the list of contributors [6]. I know this was
> discussed, but now I'm not really sure what to expect there.
>
> [6] https://github.com/grass-svn2git/grass/graphs/contributors
>

This are the authors who have a GitHub account known to us. There is a
lookup table which maps SVN account to GitHub account (in
addons/tools/svn2git somewhere).
In fact, the list is currently a tiny fraction of the real authorship!

So, if someone isn't listed yet:
Please get a GitHub account and/or communicate it to us (name + related
email).

Later on, also commit claiming is possible and easy, so nothing is lost.

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

Re: [GRASS-dev] [GRASS GIS] #2970: Replace Vect_point_in_box() by Vect_point_in_box_2d() where appropriate

[GRASS GIS]

#2970: Replace Vect_point_in_box() by Vect_point_in_box_2d() where appropriate
--+-
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  task | Status:  new
  Priority:  minor|  Milestone:  8.0.0
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  vlib, bbox, box
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by wenzeslaus):

 * milestone:  7.2.4 => 8.0.0


Comment:

 I'm not aware of any changes in this, so the danger that #2734 applies for
 other usages of `Vect_point_in_box()` besides ''v.distance'' is still
 there.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] pywin32 missing

[Anna Petrášová]

Hi,

I am testing some changes in Python library on Windows and when I get over
the current problem, I run into that I can't import win32file in
core/gcmd.py. Some problem with packaging?

Thank you,

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Vaclav Petras]

On Wed, May 15, 2019 at 9:14 AM Martin Landa  wrote:

> Hi,
>
> st 15. 5. 2019 v 9:51 odesílatel Martin Landa 
> napsal:
> > Something strange happen with svn repo after r74441. I will publish
> > testing repo for public review hopefully today.
>
> OK, finally a new fresh grass repo preview available for review (last
> processed commit 74475).
>
> Please compare git content [1], branches [2] and tags [3] with svn.
> Please review logs reporting changed message [4] and unchanged
> messages [5].


I was also looking at the list of contributors [6]. I know this was
discussed, but now I'm not really sure what to expect there.

[6] https://github.com/grass-svn2git/grass/graphs/contributors


> If no problems appears this will be the last
> preview before REAL migration.
>

When comparing the content of the repositories, I see the difference in
$Date$ which of course has the whole system related to it. What we are
doing with that?

Another thing is the need for new contributing guidelines. Git is not
Subversion and committing to master won't work (please, let me know if you
want me to show some examples). What other OSGeo projects are doing is that
contributing guidelines say that you should do pull request. It seems that
this is often preferred way even for core developers. From what I gathered
from a small sample of people at OSGeo sprint, the core devs don't go
though fork, but they do go through a branch. In GitHub, we can set
"Require pull request reviews before merging" and "Include administrators"
for the master branch to enforce that. I think we should do it at least at
the beginning.

Vaclav


>
> [1] https://github.com/grass-svn2git/grass
> [2] https://github.com/grass-svn2git/grass
> [3] https://github.com/grass-svn2git/grass/releases
> [4] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_touched.txt
> [5] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_untouched.txt
>
> --
> 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] [GRASS GIS] #3790: Cleanup gettext usage for python code

[GRASS GIS]

#3790: Cleanup gettext usage for python code
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by wenzeslaus):

 Replying to [comment:5 pmav99]:
 > Disclaimer: The real goal of this refactoring was to get rid of
 {{{os.getenv("GISBASE")}}} calls at the module level from all over the
 place. This is a prerequisite for #3772. The scripts and the GUI code
 didn't really need to be touched, but I did them too for uniformity.

 You will have to help me here. Why is the relative path solution from
 #3772 not applicable to the explicit import approach?

 In relation to that, since #3772 is about using `grass` as a standard
 Python package, I think it should follow the "Helman's advice" for a
 Python package.

 > Replying to [comment:4 wenzeslaus]:
 > > The things in lib/python are potentially (and actually) used as Python
 modules by other applications or scripts. Thus from
 https://pymotw.com/2/gettext/index.html#module-localization, it is
 actually the second option which applies:
 > >
 > > > //For a library, or individual module, modifying `__builtins__` is
 not a good idea because you don’t know what conflicts you might introduce
 with an application global value. You can import or re-bind the names of
 translation functions by hand at the top of your module.//
 >
 > ...
 >
 > I am not sure that GRASS was actually following Doug Helman's advice.
 More specifically, almost all GRASS modules used to import the {{{grass}}}
 library before actually calling {{{gettext.install()}}} on their own
 ([https://github.com/GRASS-GIS/grass-
 ci/pull/9/commits/0983ca068d6f7363d2fede26f77b8aed76c87bcc source]). ...
 Anyway, the end result is that most of the time, if not always, as soon as
 you imported the {{{grass}}} lib, the {{{builtins}}} were modified anyway.

 Please read #1739 and #2425 linked from there. I explain that the wxGUI is
 using the practice while the library (lib/python) is not and it should.

 > That being said, I am completely open to any improvements. I am also
 perfectly fine with following Mr. Helman's advice (i.e. by adding explicit
 imports in each and every {{{grass}}} lib module) if someone wants to
 contribute that. But IMHV the proposed implementation is cleaner than the
 previous one.

 Cleaner in which way? I think the registration of the domains separately
 and all at once is a separate issue from "Helman's advice" (which is
 notably also the way which Django is following).

 > > So far we were relatively successful in keeping the GUI separate
 (whether for performance or code organization reasons).
 >
 > I don't really see any coupling of the GUI code with the {{{grass}}}
 library. All the {{{grass}}} library does is registering the "grasswxpy"
 domain. It doesn't import anything.

 It is not just the imports. The idea is that you should be able to install
 GRASS GIS as command line only application without any GUI parts. But
 there is more than one way to deal with this. If the registration of the
 domain can just fail silently, that's probably good enough in this
 particular case. However, as I said, this is a separate issue.

 What is crucial here are the explicit imports versus using builtin. There
 were issues with builtin solution in the past (hence #1739), builtin `_`
 currently causes issues (doctests, static code linting), builtin solution
 is not considered good practice for libraries (Helman, Django) and the
 change breaks wxGUI according to #3838. Thus, I suggest reverting it (at
 least the builtin part) and finding a different solution for #3772.

-- 
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] #3838: r74307 breaks GUI: UnicodeDecodeError

[GRASS GIS]

#3838: r74307 breaks GUI: UnicodeDecodeError
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by annakrat):

 Replying to [comment:5 marisn]:
 > Replying to [comment:3 pmav99]:
 > > Q: Is it necessary to support multiple wxPython versions? Is there any
 problem with picking either v3 or v4 and moving forward?
 > There is no v4 in Gentoo and also Ubuntu LTS (only one year old) sits on
 v3. Due to required changes in various other packages using wxPython, v4
 widespread adoption will take some time.


 Yes, we need to support both Python 2 and 3, and wxPython 3 and 4, at
 least for some time.

 Regarding this ticket, I believe it's Python 2 vs 3 problem, not wx 3 vs
 4.

-- 
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 on an Alpine Linux docker

[Martin Landa]

Hi,

st 15. 5. 2019 v 15:18 odesílatel Pietro  napsal:
> Recently I've started looking for a docker image with GRASS, I'm looking for 
> a minimal image that is as small as possible.
> From my test the other images available where always above 1GB of size, the 
> current version once built have a size of ~220 MB.
> Another difference respect to others dockers available that I found is that 
> it is possible to select which version use when building the image:

great, probably we should start collecting all GRASS-related dockers
on GRASS wiki?

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] GRASS GIS on an Alpine Linux docker

[Pietro]

Dear all,

Recently I've started looking for a docker image with GRASS, I'm looking
for a minimal image that is as small as possible.
>From my test the other images available where always above 1GB of size, the
current version once built have a size of ~220 MB.
Another difference respect to others dockers available that I found is that
it is possible to select which version use when building the image:

```
sudo docker build --build-arg GRASS_VERSION=7.7 \
  --build-arg PYTHON_VERSION=3  \
  --build-arg PROJ_VERSION=5.2.0 \
  --build-arg PROJ_DATUMGRID_VERSION=1.8 \
  --volume \
  zarch/alpine-grass-gis
```

You can find the repository here:

https://github.com/zarch/docker-alpine-grass-gis

Do you have any feedback?
Any hint to improve the `Dockerfile` or the `README.md` are welcome. :-)

Thank you for the support.
Best regards

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Martin Landa]

> [2] https://github.com/grass-svn2git/grass

[2] https://github.com/grass-svn2git/grass/branches/all

-- 
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] svn/trac -> git/github migration plan

[Martin Landa]

Hi,

st 15. 5. 2019 v 9:51 odesílatel Martin Landa  napsal:
> Something strange happen with svn repo after r74441. I will publish
> testing repo for public review hopefully today.

OK, finally a new fresh grass repo preview available for review (last
processed commit 74475).

Please compare git content [1], branches [2] and tags [3] with svn.
Please review logs reporting changed message [4] and unchanged
messages [5]. Thanks! If no problems appears this will be the last
preview before REAL migration. Ma

[1] https://github.com/grass-svn2git/grass
[2] https://github.com/grass-svn2git/grass
[3] https://github.com/grass-svn2git/grass/releases
[4] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_touched.txt
[5] http://geo102.fsv.cvut.cz/~landa/tmp/log_grass_untouched.txt

-- 
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] #3838: r74307 breaks GUI: UnicodeDecodeError

[GRASS GIS]

#3838: r74307 breaks GUI: UnicodeDecodeError
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by marisn):

 Replying to [comment:3 pmav99]:
 > Q: Is it necessary to support multiple wxPython versions? Is there any
 problem with picking either v3 or v4 and moving forward?
 There is no v4 in Gentoo and also Ubuntu LTS (only one year old) sits on
 v3. Due to required changes in various other packages using wxPython, v4
 widespread adoption will take some time.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Martin Landa]

Hi,

po 13. 5. 2019 v 15:32 odesílatel Martin Landa  napsal:
> unfortunately attempt to run `git svn fetch` incrementally fails with
> similar error:
>
> $ git svn -r74443:75000 --authors-file=../AUTHORS.txt fetch
> Error from SVN, (160006): Invalid filesystem revision number: No such
> revision 74543

I tried to run `0-migrate-fetch.sh` directly on svn osgeo server.
Fetching over `file://` fails with the same error. Strangely when
fetching over `http://` the command is somehow able to recover:

...
r74441 = 9f7eef32fec5f0e898e794854591b9015afed26d (refs/remotes/trunk)
Mraster/r.thin/thin_lines.c
r74442 = 13e9f72398b8e3db69dd5f2c567553f6d46878b5 (refs/remotes/trunk)
W: Ignoring error from SVN, path probably does not exist: (175002): RA
layer request failed: Unexpected HTTP status 500 'Internal Server
Error' on '/grass/!svn/rvr/74542'
: Additional errors:: No such revision 74542
W: Do not be alarmed at the above message git-svn is just searching
aggressively for old history.
This may take a while on large repositories
Path 'grass' was probably deleted:
RA layer request failed: Unexpected HTTP status 500 'Internal Server
Error' on '/grass/!svn/rvr/74542'
: Additional errors:: No such revision 74542
Will attempt to follow revisions r74443 .. r74542 committed before the deletion
r74443 .. r74476 OK
Mraster/r.thin/thin_lines.c
r74443 = 4e76c156c6b0b547e30a3399642074d82f5729bf
(refs/remotes/releasebranch_7_6)
Mraster/r.thin/local_proto.h
Mraster/r.thin/thin_lines.c
...

Something strange happen with svn repo after r74441. I will publish
testing repo for public review hopefully today.

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